Search NASA⌕ Search

SEARCH · Search NASA

Results for “system requirements”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS1983

A summary of mission and system performance requirements for large space antennas

Mission definition studies and system analyses have been described for a number of potential civilian missions and a few military missions. In this paper, an attempt is made to summarize the most formidable mission and system performance requirements for large space antennas. The emphasis will be on the civilian systems; only those aspects of military mission and system requirements that are unclassified are included.

Keafer, L. S., Jr.↗
NASA NTRS2010

Systems, methods and apparatus for implementation of formal specifications derived from informal requirements

Systems, methods and apparatus are provided through which in some embodiments an informal specification is translated without human intervention into a formal specification. In some embodiments the formal specification is a process-based specification. In some embodiments, the formal specification is translated into a high-level computer programming language which is further compiled into a set of executable computer instructions.

Hinchey, Michael G.↗
NASA NTRS2011

Exploration Planetary Surface Structural Systems: Design Requirements and Compliance

The Lunar Surface Systems Project developed system concepts that would be necessary to establish and maintain a permanent human presence on the Lunar surface. A variety of specific system implementations were generated as a part of the scenarios, some level of system definition was completed, and masses estimated for each system. Because the architecture studies generally spawned a large number of system concepts and the studies were executed in a short amount of time, the resulting system definitions had very low design fidelity. This paper describes the development sequence required to field a particular structural system: 1) Define Requirements, 2) Develop the Design and 3) Demonstrate Compliance of the Design to all Requirements. This paper also outlines and describes in detail the information and data that are required to establish structural design requirements and outlines the information that would comprise a planetary surface system Structures Requirements document.

Dorsey, John T.↗
NASA NTRS1993

Measurements over distributed high performance computing and storage systems

Requirements are carefully described in descriptions of systems to be acquired but often there is no requirement to provide measurements and performance monitoring to ensure that requirements are met over the long term after acceptance. A set of measurements for various UNIX-based systems will be available at the 1992 Goddard Conference on Mass Storage Systems and Technologies. The authors invite others to contribute to the set of measurements. The framework for presenting the measurements of supercomputers, workstations, file servers, mass storage systems, and the networks that interconnect them are given. Production control and database systems are also included. Though other applications and third party software systems are not addressed, it is important to measure them as well. The capability to integrate measurements from all these components from different vendors, and from the third party software systems was recognized and there are efforts to standardize a framework to do this. The measurement activity falls into the domain of management standards. Standards work is ongoing for Open Systems Interconnection (OSI) systems management; AT&T, Digital, and Hewlett-Packard are developing management systems based on this architecture even though it is not finished. Another effort is in the UNIX International Performance Management Working Group. In addition, there are the Open Systems Foundation's Distributed Management Environment and the Object Management Group. A paper comparing the OSI systems management model and the Object Management Group model has been written. The IBM world has had a capability for measurement for various IBM systems since the 1970's and different vendors were able to develop tools for analyzing and viewing these measurements. Since IBM was the only vendor, the user groups were able to lobby IBM for the kinds of measurements needed. In the UNIX world of multiple vendors, a common set of measurements will not be as easy to get.

Williams, Elizabeth↗
NASA NTRS1984

Design of a variable-focal-length optical system

Requirements to place an entire optical system with a variable focal length ranging from 20 to 200 cm within a overall length somewhat less than 100 cm placed severe restrictions on the design of a zoom lens suitable for use on a comet explorer. The requirements of a wavelength range of 0.4 to 1.0 microns produced even greater limitations on the possibilities for a design that included a catadioptric (using mirrors and glass) front and followed by a zooming refractive portion. Capabilities available commercial zoom lenses as well as patents of optical systems are reviewed. Preliminary designs of the refractive optics zoom lens and the catadioptric system are presented and evaluated. Of the two, the latter probably has the best chance of success, so long as the shortest focal lengths are not really needed.

Ricks, D.↗
NASA NTRS1990

System identification requirements for high-bandwidth rotorcraft flight control system design

The application of system identification methods to high-bandwidth rotorcraft flight control system design is examined. Flight test and modeling requirements are illustrated using flight test data from a BO-105 hingeless rotor helicopter. The proposed approach involves the identification of nonparametric frequency-response models followed by parametric (transfer funtion and state space) model identification. Results for the BO-105 show the need for including coupled body/rotor flapping and lead-lag dynamics in the identification model structure to allow the accurate prediction of control system bandwidth limitations. Lower-order models are useful for estimating nominal control system performance only when the flight data used for the identification are band-limited to be consistent with the frequency range of applicability of the model. The flight test results presented in this paper are consistent with theoretical studies by previous researchers.

Tischler, Mark B.↗
NASA NTRS1991

System identification requirements for high-bandwidth rotorcraft flight control system design

The application of system identification methods to high-bandwidth rotorcraft flight control system design is examined. Flight test and modeling requirements are illustrated using flight test data from a BO-105 hingeless rotor helicopter. The proposed approach involves the identification of nonparametric (transfer function and state space) model identification. Results for the BO-105 show the need for including coupled body/rotor flapping and lead-lag dynamics in the identification model structure to allow the accurate prediction of control ssytem bandwidth limitations.

Tischler, Mark B.↗
NASA NTRS1979

Implementation Procedure for STS Payloads, System Safety Requirements

Guidelines and instructions for the implementation of the SP&R system safety requirements applicable to STS payloads are provided. The initial contact meeting with the payload organization and the subsequent safety reviews necessary to comply with the system safety requirements of the SP&R document are described. Waiver instructions are included for the cases in which a safety requirement cannot be met.

Source record↗
NASA NTRS1992

HSCT high lift system aerodynamic requirements

The viewgraphs and discussion of high lift system aerodynamic requirements are provided. Low speed aerodynamics has been identified as critical to the successful development of a High Speed Civil Transport (HSCT). The airplane must takeoff and land at a sufficient number of existing or projected airports to be economically viable. At the same time, community noise must be acceptable. Improvements in cruise drag, engine fuel consumption, and structural weight tend to decrease the wing size and thrust required of engines. Decreasing wing size increases the requirements for effective and efficient low speed characteristics. Current design concepts have already been compromised away from better cruise wings for low speed performance. Flap systems have been added to achieve better lift-to-drag ratios for climb and approach and for lower pitch attitudes for liftoff and touchdown. Research to achieve improvements in low speed aerodynamics needs to be focused on areas most likely to have the largest effect on the wing and engine sizing process. It would be desirable to provide enough lift to avoid sizing the airplane for field performance and to still meet the noise requirements. The airworthiness standards developed in 1971 will be the basis for performance requirements for an airplane that will not be critical to the airplane wing and engine size. The lift and drag levels that were required to meet the performance requirements of tentative airworthiness standards established in 1971 and that were important to community noise are identified. Research to improve the low speed aerodynamic characteristics of the HSCT needs to be focused in the areas of performance deficiency and where noise can be reduced. Otherwise, the wing planform, engine cycle, or other parameters for a superior cruising airplane would have to be changed.

Paulson, John A.↗
NASA NTRS2020

Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗
NASA NTRS2020

Medical Data Architecture Platform and Recommended Requirements for A Medical Data System for Exploration Missions

Minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions.In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗