Search NASA⌕ Search

SEARCH · Search NASA

Results for “Requirements development”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1972

Astronomy sortie missions definition study. Volume 4: Program development requirements

Program development requirements for the selected Astronomy Sortie Missions concept were generated and are presented in four parts as follows: (1)the gross planning requirements that must be considered in subsequent phases of the project; (2)the schedules and logic networks for the design, development, and operation of the overall project; (3)the supporting research and technology required to support the project; and (4)the work breakdown data, from which cost data will be generated. Data reported in each part includes the appropriate rationale with explanations of the guidelines and assumptions that were used in the analyses and estimates.

Source record↗
NASA NTRS2002

Requirements Development Issues for Advanced Life Support Systems: Solid Waste Management

Long duration missions pose substantial new challenges for solid waste management in Advanced Life Support (ALS) systems. These possibly include storing large volumes of waste material in a safe manner, rendering wastes stable or sterilized for extended periods of time, and/or processing wastes for recovery of vital resources. This is further complicated because future missions remain ill-defined with respect to waste stream quantity, composition and generation schedule. Without definitive knowledge of this information, development of requirements is hampered. Additionally, even if waste streams were well characterized, other operational and processing needs require clarification (e.g. resource recovery requirements, planetary protection constraints). Therefore, the development of solid waste management (SWM) subsystem requirements for long duration space missions is an inherently uncertain, complex and iterative process. The intent of this paper is to address some of the difficulties in writing requirements for missions that are not completely defined. This paper discusses an approach and motivation for ALS SWM requirements development, the characteristics of effective requirements, and the presence of those characteristics in requirements that are developed for uncertain missions. Associated drivers for life support system technological capability are also presented. A general means of requirements forecasting is discussed, including successive modification of requirements and the need to consider requirements integration among subsystems.

Levri, Julie A.↗
NASA NTRS1988

Mars rover technology development requirements

The technology development requirements for various Mars rover range capabilities are discussed, focusing on local navigation of the rover. The capabilities of two methods are compared. In one method, operators on the earth view stereo pictures sent by the rover and determine short traverse paths which the rover follows. The other method achieves more autonomous capability by using computer vision from orbital imagery with approximate long routes commanded from earth. The locomotion, navigation, ground operations, computation, power, thermal control, communications, sample acquisition, and analysis and preservation requirements are examined.

Bedard, Roger↗
NASA NTRS2006

An Integrated Approach to Exploration Launch Office Requirements Development

The proposed paper will focus on the Project Management and Systems Engineering approach utilized to develop a set of both integrated and cohesive requirements for the Exploration Launch Office, within the Constellation Program. A summary of the programmatic drivers which influenced the approach along with details of the resulting implementation will be discussed as well as metrics evaluating the efficiency and accuracy of the various requirements development activities. Requirements development activities will focus on the procedures utilized to ensure that technical content was valid and mature in preparation for the Crew Launch Vehicle and Constellation System s Requirements Reviews. This discussion will begin at initial requirements development during the Exploration Systems Architecture Study and progress through formal development of the program structure. Specific emphasis will be given to development and validation of the requirements. This discussion will focus on approaches to garner the appropriate requirement owners (or customers), project infrastructure utilized to emphasize proper integration, and finally the procedure to technically mature, verify and validate the requirements. Examples of requirements being implemented on the Launch Vehicle (systems, interfaces, test & verification) will be utilized to demonstrate the various processes and also provide a top level understanding of the launch vehicle(s) performance goals. Details may also be provided on the approaches for verification, which range from typical aerospace hardware development (qualification/acceptance) through flight certification (flight test, etc.). The primary intent of this paper is to provide a demonstrated procedure for the development of a mature, effective, integrated set of requirements on a complex system, which also has the added intricacies of both heritage and new hardware development integration. Ancillary focus of the paper will include discussion of Test and Verification approaches along with top level systems/elements performance capabilities.

Holladay, Jon B.↗
NASA NTRS1992

Supersonic HLFC: Potential benefits and technology development requirements

The viewgraphs and discussion of the potential benefits and technology development requirements of supersonic Hybrid Laminar Flow Control (HLFC) are reviewed. For the last three years, Boeing has performed studies on the application of laminar flow control to High Speed Civil Transport (HSCT) configurations. Large potential net benefits were identified for laminar flow control, even after accounting for the significant implementation penalties. However, the technical risks are high at this time, and an early, aggressive technology development program is required if laminar flow control (LFC) is to be incorporated in a year 2005 HSCT program. The benefits and required development effort are addressed. Of all the aerodynamic advances that are being considered for the HSCT, LFC has the largest potential for improving the supersonic lift drag ratio of a given configuration. The work accomplished to date, sponsored by NASA Langley, is summarized. This work includes studies on HLFC application to HSCT, cruise HLFC/low speed boundary layer control (BLC) compatibility, and impact of M 0.9 HLFC and high lift BLC. Requirements for production committments are listed. The need for a HSCT-HLFC Risk Reduction Program is addressed. Supersonic HLFC development planning and future applications are addressed. Laminar flow/high-lift integration is addressed.

Neumann, Frank↗
NASA NTRS2014

Advanced Extravehicular Activity Pressure Garment Requirements Development

The NASA Johnson Space Center advanced pressure garment technology development team is addressing requirements development for exploration missions. Lessons learned from the Z‐2 high fidelity prototype development have reiterated that clear low‐level requirements and verification methods reduce risk to the government, improve efficiency in pressure garment design efforts, and enable the government to be a smart buyer. The expectation is to provide requirements at the specification level that are validated so that their impact on pressure garment design is understood. Additionally, the team will provide defined verification protocols for the requirements. However, in reviewing exploration space suit high level requirements there are several gaps in the team's ability to define and verify related lower level requirements. This paper addresses the efforts in requirement areas such as mobility/fit/comfort and environmental protection (dust, radiation, plasma, secondary impacts) to determine the by what method the requirements can be defined and use of those methods for verification. Gaps exist at various stages. In some cases component level work is underway, but no system level effort has begun, in other cases no effort has been initiated to close the gap. Status of ongoing efforts and potential approaches to open gaps are discussed.

Ross, Amy↗
NASA NTRS1993

Virtual environment and computer-aided technologies used for system prototyping and requirements development

The Space Station Freedom (SSF) Data Management System (DMS) consists of distributed hardware and software which monitor and control the many onboard systems. Virtual environment and off-the-shelf computer technologies can be used at critical points in project development to aid in objectives and requirements development. Geometric models (images) coupled with off-the-shelf hardware and software technologies were used in The Space Station Mockup and Trainer Facility (SSMTF) Crew Operational Assessment Project. Rapid prototyping is shown to be a valuable tool for operational procedure and system hardware and software requirements development. The project objectives, hardware and software technologies used, data gained, current activities, future development and training objectives shall be discussed. The importance of defining prototyping objectives and staying focused while maintaining schedules are discussed along with project pitfalls.

Logan, Cory↗
NASA NTRS2015

Advanced Extra-Vehicular Activity Pressure Garment Requirements Development

The NASA Johnson Space Center advanced pressure garment technology development team is addressing requirements development for exploration missions. Lessons learned from the Z-2 high fidelity prototype development have reiterated that clear low-level requirements and verification methods reduce risk to the government, improve efficiency in pressure garment design efforts, and enable the government to be a smart buyer. The expectation is to provide requirements at the specification level that are validated so that their impact on pressure garment design is understood. Additionally, the team will provide defined verification protocols for the requirements. However, in reviewing exploration space suit high level requirements there are several gaps in the team's ability to define and verify related lower level requirements. This paper addresses the efforts in requirement areas such as mobility/fit/comfort and environmental protection (dust, radiation, plasma, secondary impacts) to determine the method by which the requirements can be defined and use of those methods for verification. Gaps exist at various stages. In some cases component level work is underway, but no system level effort has begun; in other cases no effort has been initiated to close the gap. Status of on-going efforts and potential approaches to open gaps are discussed.

Ross, Amy↗
NASA NTRS2008

A Scenario-Based Process for Requirements Development: Application to Mission Operations Systems

The notion of using operational scenarios as part of requirements development during mission formulation (Phases A & B) is widely accepted as good system engineering practice. In the context of developing a Mission Operations System (MOS), there are numerous practical challenges to translating that notion into the cost-effective development of a useful set of requirements. These challenges can include such issues as a lack of Project-level focus on operations issues, insufficient or improper flowdown of requirements, flowdown of immature or poor-quality requirements from Project level, and MOS resource constraints (personnel expertise and/or dollars). System engineering theory must be translated into a practice that provides enough structure and standards to serve as guidance, but that retains sufficient flexibility to be tailored to the needs and constraints of a particular MOS or Project. We describe a detailed, scenario-based process for requirements development. Identifying a set of attributes for high quality requirements, we show how the portions of the process address many of those attributes. We also find that the basic process steps are robust, and can be effective even in challenging Project environments.

MOS↗
NASA NTRS2019

Requirements Development and Management on the Psyche Project

In January 2017, Psyche was one of two mission concepts selected by NASA for flight as part of the 14th Discovery mission competition. The project has been staffing up and maturing the spacecraft, instrument and mission system baseline designs on the path towards a 2022 launch. During much of 2018, the Project has been executing the lifecycle stage called Phase B, “Preliminary Design and Technology Completion,” one key element of which is the development and management of requirements at various levels. In the case of the Psyche project, this process has been particularly unique for several reasons. The project utilizes a Solar Electric Propulsion (SEP) Chassis from Space Systems Loral (SSL), a high volume manufacturer of commercial geostationary (GEO) telecom spacecraft based on the 1300 satellite bus. While SSL has an extensive, well-vetted set of requirements based on their very successful Earth-orbiting product line, translating that heritage to a deep space science mission required special care. In addition to the differences associated with the deep space environment and longer communication times, new interfaces had to be incorporated. While a substantial portion of the Flight System consists of the SEP Chassis, there were several new interfaces within various subsystems between SSL components and those provided by JPL and other contractors. Managing these interfaces through requirements at a relatively higher level than normally seen on internal or external builds proved challenging. Finally, the Psyche spacecraft plans to host the flight terminal of the Deep Space Optical Communications (DSOC) technology demonstration, which is itself a separate project with its own requirements that must be flowed down and managed. This paper will present an overview of the requirement development and management process for the Psyche project. It will discuss in detail the various challenges summarized above, the methods and decisions chosen to address them, and evaluate their overall effectiveness at this stage in the project.

Elkins-Tanton, Linda T.↗
NASA NTRS2003

Requirements Development for the NASA Advanced Engineering Environment (AEE)

The requirements development process for the Advanced Engineering Environment (AEE) is presented. This environment has been developed to allow NASA to perform independent analysis and design of space transportation architectures and technologies. Given the highly collaborative and distributed nature of AEE, a variety of organizations are involved in the development, operations and management of the system. Furthermore, there are additional organizations involved representing external customers and stakeholders. Thorough coordination and effective communication is essential to translate desired expectations of the system into requirements. Functional, verifiable requirements for this (and indeed any) system are necessary to fulfill several roles. Requirements serve as a contractual tool, configuration management tool, and as an engineering tool, sometimes simultaneously. The role of requirements as an engineering tool is particularly important because a stable set of requirements for a system provides a common framework of system scope and characterization among team members. Furthermore, the requirements provide the basis for checking completion of system elements and form the basis for system verification. Requirements are at the core of systems engineering. The AEE Project has undertaken a thorough process to translate the desires and expectations of external customers and stakeholders into functional system-level requirements that are captured with sufficient rigor to allow development planning, resource allocation and system-level design, development, implementation and verification. These requirements are maintained in an integrated, relational database that provides traceability to governing Program requirements and also to verification methods and subsystem-level requirements.

Rogers, Eric↗
NASA NTRS2018

Navigation Requirements Development and Performance Assessment of a Martian Ascent Vehicle

To support development of Martian Ascent Vehicles, analysis tools are needed to support the development of Guidance, Navigation, and Control requirements. This paper presents a focused approach to Navigation analysis to capture development of requirements on initial state knowledge and inertial sensor capabilities. A simulation and analysis framework was used to assess the capability of a range of sensors to operate inertially along a range of launch trajectories. The baseline Martian Ascent Vehicle was used as the input for optimizing a set of trajectories from each launch site. These trajectories were used to perform Monte Carlo analysis dispersing error sensor terms and their effects on integrated vehicle performance. Additionally, this paper provides insight into the use of optical navigation techniques to assess state determination and the potential to use observations of local extraplanetary bodies to estimate state. This paper provides an initial level of performance assessment of navigation components to support continued requirements development of a Martian Ascent Vehicle with applications to both crew and sample return missions.

Anzalone, Evan J.↗
NASA NTRS1968

Development requirements for a high-energy hybrid propulsion system Final report

This document presents the development requirements, costs, and schedule for a high-energy upper-stage hybrid propulsion system. High energy is achieved through the use of a lithium fuel formulation (solid) and fluorinated oxidizer (liquid). The propulsion system contains 3 2OO lb of propellant and may be used as a terminal stage for Atlas/Centaur or DSV-3M Delta launch vehicle. A program to develop a fluorinated hybrid propulsion system could be initiated with little risk. An extensive investigation revealed that the technology required to develop most of the components has either been demonstrated or is in progress. Further, it was found that there were no areas of critical technology. The cost to develop a hybrid propulsion system to a status where it could be integrated into a flight-test stage is about $17 million. This cost does not include the development of the stage astrionics. Length of the total development program is 34 months. A total recurring cost of $381 600 was estimated for the first unit (less astrionics and fee). This includes purchased hard\rare, manufacturing, material, assembly, and test costs.

M.B. Adams↗
NASA NTRS2020

Development Requirements for the Exploration PLSS (xPLSS) Feedwater Supply Assembly (FSA)

The "Development Requirements for the Exploration PLSS (xPLSS) Feedwater Supply Assembly (FSA)" provides information regarding the current requirements for the Exploration Extravehicular Mobility Unit (xEMU). Specifically, the document provide an overview of expected features, capabilities, and requirements for safe integration of the components within the Portable Life Support System (PLSS) and the xEMU program.

Exploration PLSS (xPLSS)↗
NASA NTRS1980

Coal liquefaction processes and development requirements analysis for synthetic fuels production

Focus of the study is on: (1) developing a technical and programmatic data base on direct and indirect liquefaction processes which have potential for commercialization during the 1980's and beyond, and (2) performing analyses to assess technology readiness and development trends, development requirements, commercial plant costs, and projected synthetic fuel costs. Numerous data sources and references were used as the basis for the analysis results and information presented.

Source record↗