Search NASA⌕ Search

SEARCH · Search NASA

Results for “Requirements Verification”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS1977

Documentation requirements for Applications Systems Verification and Transfer projects (ASVTs)

NASA's Application Systems Verification and Transfer Projects (ASVTs) are deliberate efforts to facilitate the transfer of applications of NASA-developed space technology to users such as federal agencies, state and local governments, regional planning groups, public service institutions, and private industry. This study focused on the role of documentation in facilitating technology transfer both to primary users identified during project planning and to others with similar information needs. It was understood that documentation can be used effectively when it is combined with informal (primarily verbal) communication within each user community and with other formal techniques such as organized demonstrations and training programs. Documentation examples from eight ASVT projects and one potential project were examined to give scope to the investigation.

Suchy, J. T.↗
NASA NTRS1992

Electromagnetic compatibility (EMC) standard test chamber upgrade requirements for spacecraft design verification tests

In view of the serious performance deficiencies inherent in conventional modular and welded shielding EMC test enclosures, in which multipath reflections and resonant standing waves can damage flight hardware during RF susceptibility tests, NASA-Goddard has undertaken the modification of a 20 x 24 ft modular-shielded enclosure through installation of steel panels to which ferrite tiles will be mounted with epoxy. The internally reflected RF energy will thereby be absorbed, and exterior power-line noise will be reduced. Isolation of power-line filters and control of 60-Hz ground connections will also be undertaken in the course of upgrading.

Dyer, Edward F.↗
NASA NTRS2011

Verification and Validation of Requirements on the CEV Parachute Assembly System Using Design of Experiments

The Crew Exploration Vehicle Parachute Assembly System (CPAS) project conducts computer simulations to verify that flight performance requirements on parachute loads and terminal rate of descent are met. Design of Experiments (DoE) provides a systematic method for variation of simulation input parameters. When implemented and interpreted correctly, a DoE study of parachute simulation tools indicates values and combinations of parameters that may cause requirement limits to be violated. This paper describes one implementation of DoE that is currently being developed by CPAS, explains how DoE results can be interpreted, and presents the results of several preliminary studies. The potential uses of DoE to validate parachute simulation models and verify requirements are also explored.

Schulte, Peter Z.↗
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 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 NTRS2006

Systems Integration Processes for NASA's Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable low earth orbit. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific processes for requirements development and verification, integrated design and analysis, integrated simulation and testing and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The CLV Project is broken logically into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.

Reuter, James L.↗
NASA NTRS2006

Systems Integration Processes for NASA Ares I Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable Low Earth Orbit (LEO). This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and nonpropulsion elements within NASA's Crew Launch Vehicle (CLV), now known as the Ares I. The objective of the Ares I is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to LEO in support of the lunar and Mars missions. The Ares I must successfully provide this capability within cost and schedule, and with an acceptable risk approach. This paper will describe the systems engineering management processes that will be applied to assure Ares I Project success through complete and efficient technical integration. Discussion of technical review and management processes for requirements development and verification, integrated design and analysis, integrated simulation and testing, and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The Ares I Project is logically divided into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these Ares I elements and among the other Constellation projects. Also discussed is launch vehicle stack integration (Ares I to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage. The processes for decomposing requirements to the elements and ensuring that requirements have been correctly validated, decomposed, and allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements, will be discussed.

Taylor, James L.↗
NASA NTRS2010

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, within a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability, and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation, testing results, and other information. Where appropriate, actual performance history was used to calculate failure rates for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to assess compliance with requirements and to highlight design or performance shortcomings for further decision making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability, and maintainability analysis, and present findings and observation based on analysis leading to the Ground Operations Project Preliminary Design Review milestone.

Gernand, Jeffrey L.↗
NASA NTRS2010

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, in a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation; testing results, and other information. Where appropriate, actual performance history was used for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to verify compliance with requirements and to highlight design or performance shortcomings for further decision-making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability and maintainability analysis, and present findings and observation based on analysis leading to the Ground Systems Preliminary Design Review milestone.

Gernand, Jeffrey L.↗
NASA NTRS1987

Wind tunnel requirements for computational fluid dynamics code verification

The role of experiment in the development of Computational Fluid Dynamics (CFD) for aerodynamic flow field prediction is discussed. Requirements for code verification from two sources that pace the development of CFD are described for: (1) development of adequate flow modeling, and (2) establishment of confidence in the use of CFD to predict complex flows. The types of data needed and their accuracy differs in detail and scope and leads to definite wind tunnel requirements. Examples of testing to assess and develop turbulence models, and to verify code development, are used to establish future wind tunnel testing requirements. Versatility, appropriate scale and speed range, accessibility for nonintrusive instrumentation, computerized data systems, and dedicated use for verification were among the more important requirements identified.

Marvin, Joseph G.↗
NASA NTRS1988

Wind tunnel requirements for computational fluid dynamics code verification

The role of experiment in the development of computational fluid dynamics (CFD) for aerodynamic flow field prediction is discussed. Requirements for code verification from two sources that pace the development of CFD are described for: (1) development of adequate flow modeling, and (2) establishment of confidence in the use of CFD to predict complex flows. The types of data needed and their accuracy differs in detail and scope and leads to definite wind tunnel requirements. Examples of testing to assess and develop turbulence models, and to verify code development, are used to establish future wind tunnel testing requirements. Versatility, appropriate scale and speed range, accessibility for nonintrusive instrumentation, computerized data systems, and dedicated use for verification were among the more important requirements identified.

Marvin, Joseph G.↗
NASA NTRS1986

Use of a 35mm camera for remote surface cleanliness verification

Non-contact or remote monitoring of surfaces for both particle and molecular contaminants is required for verification of surface cleanliness on many program subsystems. The capability of a 35mm camera to satisfy this need is presented. The many limitations imposed by standard available lens systems are compared to actual required sensitivities. Methods of optimizing camera systems for specific applications and descriptions of support systems for extending the range of usefulness of the recorded data are also provided. Although this general concept is not new, significant improvements in the technique involving the use of polarized light and diffraction effects have resulted in a more efficient utilization of information recorded on the film.

Crutcher, E. R.↗
NASA NTRS2019

Formalizing and Analyzing Requirements with FRET

Formal verification and simulation are powerful tools to validate requirements against complex systems. Requirements are developed in early stages of the software lifecycle and are typically written in ambiguous natural language. There is a gap between such requirements and formal notations that can be used by verification tools, and lack of support for proper association of requirements with software artifacts for verification. We propose to write requirements in an intuitive, structured natural language with formal semantics, and to support formalization and model/code verification as a smooth, well-integrated process. To this end, we have developed an end-to-end, open source requirements analysis framework that checks Simulink models against requirements written structured natural language.

Mavridou, Anastasia↗
NASA NTRS2021

Deriving Deformable Mirror Performance Requirements in Simulation with Experimental Verification

Coronagraph instruments rely on predictable and stable deformable mirror (DM) surface displacement to achieve the contrast required to detect Earth-sized exoplanets orbiting nearby Solar-type stars. Anomalous DM behavior, such as unstable or pinned actuators, can limit contrast in coronagraphs. Simulating how these undesired behaviors affect the performance of a high contrast imaging architecture is important for developing requirements on their associated hardware. Simulating a vortex coronagraph (VC) with two deformable mirrors, this study quantifies how the number of pinned actuators affect the performance of Focal Plane Wavefront Sensing and Control algorithms using both Grid Search Electric Field Conjugation (EFC) and Planned EFC, which uses Beta-Bumping. The simulation also quantifies how various types of voltage noise such as zero-mean Gaussian noise, zero-mean periodic noise, and drift can affect the contrast of a VC during an observation run. A tolerance of a change in the Mean Normalized Intensity of ${1\times10^{-11}}$ is allocated to both types of error. If Planned EFC is used, only 1 pinned actuator on both DMs can be tolerated. If only pure Grid Search EFC is used the DMs cannot have any pinned actuators. For the case of zero-mean Gaussian noise and zero-mean periodic noise, one can tolerate a noise standard deviation of no more than ${\sigma = 0.45 \text{ mV}}$. For drift, we can only tolerate ${\sigma = 0.30 \text{ mV}}$ or less. These results show that the DM electronics and the DM themselves need to be nearly defect free to avoid having more than 1 pinned actuator. The electronics need to be tested for different types of noise statistics and that both the average and standard deviation of the noise should be measured.

Dean L. Palmer↗
NASA NTRS1982

Performance criteria guideline for three explosion protection methods of electrical equipment rated up to 15,000 volts AC

The Bureau of Mines, U.S. Department of the Interior, is reviewing explosion protection methods for use in gassy coal mines. This performance criteria guideline is an evaluation of three explosion protection methods of machines electrically powered with voltages up to 15,000 volts ac. A sufficient amount of basic research has been accomplished to verify that the explosion proof and pressurized enclosure methods can provide adequate explosion protection with the present state of the art up to 15,000 volts ac. This routine application of the potted enclosure as a stand alone protection method requires further investigation or development in order to clarify performance criteria and verification certification requirements. An extensive literature search, a series of high voltage tests, and a design evaluation of the three explosion protection methods indicate that the explosion proof, pressurized, and potted enclosures can all be used to enclose up to 15,000 volts ac.

Linley, L. J.↗
NASA NTRS2001

STEP-AIRSEDS System Engineering Support

This report summarizes and highlights the activities in support of the Space Transportation using Electrodynamic Propulsion Atmospheric Ionospheric Research Small Expendable Deployer Satellite (STEP-AIRSEDS) Project for the period of May 16, 2000 through September 28, 2001. The Alpha Technology, Inc. was tasked to provide support to the MSFC (Marshall Space Flight Center) in requirements development and in verification activities. Specifically, the Alpha Technology, Inc. task was to: (1) develop and maintain the STEP-AIRSEDS Project System Requirements Database; (2) develop and maintain the STEP-AIRSEDS requirements verification definition and planning support database; (3) perform requirements flow down analysis of STEP-AIRSEDS Project System Requirements to TMTC (The Michigan Technic Corporation) Level IV Requirements; (4) provide system engineering guidance to the Project as needed; (5) provide guidance to TMTC in preparation of Level IV Requirements; and (6) provide support to STEP-AIRSEDS meetings, reviews, and telecons as needed.

Rowell, Tom↗