Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “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 1,009 records · Page 56

Managing Approach Plate Information Study (MAPLIST): An Information Requirements Analysis of Approach Chart Use

Adequately presenting all necessary information on an approach chart represents a challenge for cartographers. Since many tasks associated with using approach charts are cognitive (e.g., planning the approach and monitoring its progress), and since the characteristic of a successful interface is one that conforms to the users' mental models, understanding pilots' underlying models of approach chart information would greatly assist cartographers. To provide such information, a new methodology was developed for this study that enhances traditional information requirements analyses by combining psychometric scaling techniques with a simulation task to provide quantifiable links between pilots' cognitive representations of approach information and their use of approach information. Results of this study should augment previous information requirements analyses by identifying what information is acquired, when it is acquired, and what presentation concepts might facilitate its efficient use by better matching the pilots' cognitive model of the information. The primary finding in this study indicated that pilots mentally organize approach chart information into ten primary categories: communications, geography, validation, obstructions, navigation, missed approach, final items, other runways, visibility requirement, and navigation aids. These similarity categories were found to underlie the pilots' information acquisitions, other mental models, and higher level cognitive processes that are used to accomplish their approach and landing tasks.

Ricks, Wendell R.↗

Storage and network bandwidth requirements through the year 2000 for the NASA Center for Computational Sciences

The data storage and retrieval demands of space and Earth sciences researchers have made the NASA Center for Computational Sciences (NCCS) Mass Data Storage and Delivery System (MDSDS) one of the world's most active Convex UniTree systems. Science researchers formed the NCCS's Computer Environments and Research Requirements Committee (CERRC) to relate their projected supercomputing and mass storage requirements through the year 2000. Using the CERRC guidelines and observations of current usage, some detailed projections of requirements for MDSDS network bandwidth and mass storage capacity and performance are presented.

Salmon, Ellen↗

Evolving Requirements for Magnetic Tape Data Storage Systems

Magnetic tape data storage systems have evolved in an environment where the major applications have been back-up/restore, disaster recovery, and long term archive. Coincident with the rapidly improving price-performance of disk storage systems, the prime requirements for tape storage systems have remained: (1) low cost per MB, (2) a data rate balanced to the remaining system components. Little emphasis was given to configuring the technology components to optimize retrieval of the stored data. Emerging new applications such as network attached high speed memory (HSM), and digital libraries, place additional emphasis and requirements on the retrieval of the stored data. It is therefore desirable to consider the system to be defined both by STorage And Retrieval System (STARS) requirements. It is possible to provide comparative performance analysis of different STARS by incorporating parameters related to (1) device characteristics, and (2) application characteristics in combination with queuing theory analysis. Results of these analyses are presented here in the form of response time as a function of system configuration for two different types of devices and for a variety of applications.

Gniewek, John J.↗

Advanced Environmental Monitoring and Control Program: Technology Development Requirements

Human missions in space, from the International Space Station on towards potential human exploration of the moon, Mars and beyond into the solar system, will require advanced systems to maintain an environment that supports human life. These systems will have to recycle air and water for many months or years at a time, and avoid harmful chemical or microbial contamination. NASA's Advanced Environmental Monitoring and Control program has the mission of providing future spacecraft with advanced, integrated networks of microminiaturized sensors to accurately determine and control the physical, chemical and biological environment of the crew living areas. This document sets out the current state of knowledge for requirements for monitoring the crew environment, based on (1) crew health, and (2) life support monitoring systems. Both areas are updated continuously through research and space mission experience. The technologies developed must meet the needs of future life support systems and of crew health monitoring. These technologies must be inexpensive and lightweight, and use few resources. Using these requirements to continue to push the state of the art in miniaturized sensor and control systems will produce revolutionary technologies to enable detailed knowledge of the crew environment.

Jan, Darrell↗

A revisit to the requirements methodologies for services provided by the Office of Space Communications

The methodologies of the NASA requirements processing system, originally designed to enhance NASA's customer interface and response time, are reviewed. The response of NASA to the problems associated with the system is presented, and it is shown what was done to facilitate the process and to improve customer relations. The requirements generation system (RGS), a computer-supported client-server system, adopted by NASA is presented. The RGS system is configurable on a per-mission basis and can be structured to allow levels of requirements. The details provided concerning the RGS include the recommended configuration, information on becoming an RGS user and network connectivity worksheets for computer users.

Fishkind, Stanley↗

Requirements and Development of an Acceleration Measurement System for International Space Station Microgravity Science Payloads

The International Space Station is being developed by NASA and international partners as a versatile user platform to allow long term on-orbit investigations of a variety of scientific and technology arenas. In particular, scientific studies are planned within a research class known as microgravity science in areas such as biotechnology, combustion, fluid physics, and materials sciences. An acceleration measurement system is in development to aid such research conducted in the on-orbit conditions of apparent weightlessness. This system provides a general purpose acceleration measurement capability in support of these payloads and investigators. Such capability allows for systematic study of scientific phenomena by obtaining information regarding the local accelerations present during experiment operations. Preparations for implementing this flight measurement system involves two distinct stages: requirements development prior to initiating the design activity, and the design activity itself. This paper defines the requirements definition approach taken, provides an overview of the results of the requirements phase, and outlines the initial design considerations being addressed for this measurement system. Some preliminary engineering approaches are also described.

Sutliff, Thomas J.↗

Towards a Methodology for Identifying Program Constraints During Requirements Analysis

Requirements analysis is the activity that involves determining the needs of the customer, identifying the services that the software system should provide and understanding the constraints on the solution. The result of this activity is a natural language document, typically referred to as the requirements definition document. Some of the problems that exist in defining requirements in large scale software projects includes synthesizing knowledge from various domain experts and communicating this information across multiple levels of personnel. One approach that addresses part of this problem is called context monitoring and involves identifying the properties of and relationships between objects that the system will manipulate. This paper examines several software development methodologies, discusses the support that each provide for eliciting such information from experts and specifying the information, and suggests refinements to these methodologies.

Romo, Lilly↗

Integrated Requirements Analysis and Technology Roadmaps

In fiscal year 1997, Strategic Insight performed analytical studies for NASA's Highly Reusable Space Transportation (HRST) program, creating program documents which illuminated technical requirements and critical research opportunities. Studies were performed to structure and confirm HRST's evolving technical requirements, building on Marshall's Phase 1 work, which defined HRST system concepts, analytical tools and high-level issues for assessment in Phase 2. Specifically, Strategic Insight: (1) Performed a requirements analysis to update HRST: An Advanced Concepts Study, Study Guidelines, Version 2.0 of January 22, 1996; only minor changes were recommended for the given parameters of interest to concept designers; (2) Conducted mini-workshops during HRST Working Group meetings on April 14-15, 1997 and July 22-24, 1997; and (3) Created structures for technology road maps of candidate HRST concepts, both subsystem and end-to-end concepts, emerging from the 13 cooperative agreement projects.

Source record↗

Analyzing Tabular and State-Transition Requirements Specifications in PVS

We describe PVS's capabilities for representing tabular specifications of the kind advocated by Parnas and others, and show how PVS's Type Correctness Conditions (TCCs) are used to ensure certain well-formedness properties. We then show how these and other capabilities of PVS can be used to represent the AND/OR tables of Leveson and the Decision Tables of Sherry, and we demonstrate how PVS's TCCs can expose and help isolate errors in the latter. We extend this approach to represent the mode transition tables of the Software Cost Reduction (SCR) method in an attractive manner. We show how PVS can check these tables for well-formedness, and how PVS's model checking capabilities can be used to verify invariants and reachability properties of SCR requirements specifications, and inclusion relations between the behaviors of different specifications. These examples demonstrate how several capabilities of the PVS language and verification system can be used in combination to provide customized support for specific methodologies for documenting and analyzing requirements. Because they use only the standard capabilities of PVS, users can adapt and extend these customizations to suit their own needs. Those developing dedicated tools for individual methodologies may find these constructions in PVS helpful for prototyping purposes, or as a useful adjunct to a dedicated tool when the capabilities of a full theorem prover are required. The examples also illustrate the power and utility of an integrated general-purpose system such as PVS. For example, there was no need to adapt or extend the PVS model checker to make it work with SCR specifications described using the PVS TABLE construct: the model checker is applicable to any transition relation, independently of the PVS language constructs used in its definition.

Owre, Sam↗

Validating Requirements for Fault Tolerant Systems Using Model Checking

Model checking is shown to be an effective tool in validating the behavior of a fault tolerant embedded spacecraft controller. The case study presented here shows that by judiciously abstracting away extraneous complexity, the state space of the model could be exhaustively searched allowing critical functional requirements to be validated down to the design level. Abstracting away detail not germane to the problem of interest leaves by definition a partial specification behind. The success of this procedure shows that it is feasible to effectively validate a partial specification with this technique. Three anomalies were found in the system one of which is an error in the detailed requirements, and the other two are missing/ambiguous requirements. Because the method allows validation of partial specifications, it also is an effective methodology towards maintaining fidelity between a co-evolving specification and an implementation.

Schneider, Francis↗

Preliminary Survey of Retrograde Velocities Required for Insertion Into Low-Altitude Lunar Orbits

Closed lunar orbits are envisaged in lunar mission programs. The study described herein was undertaken to obtain an appreciation of the relevant fuel consumption requirements. The retrograde impulses necessary for establishing the orbits were assumed to occur at the point of closest approach of the main earth-moon trajectory; this point, designated as the arrival position, was restricted to a lunar altitude of 5,000 nautical miles or less. The orientation of the arrival position vector relevant to any coplanar radius vector is not constrained, however, and similarly the scalar value of the arrival velocity is unrestrained. Since the arrival altitude is restricted to 5,000 nautical miles or less, the perturbing accelerations of the earth and sun are sufficiently small that the vehicle and moon essentially comprise an isolated two-body system; this is discussed in the report. Retrograde velocities are determined for any required pericynthion position. If the pericynthion orientation requirement is relaxed then a smaller retrograde velocity is in some cases possible. A comparison between minimum retrograde velocities and retrograde velocities necessary for stipulated pericynthion positions is given. Arrival velocities are correlated with feasible earth departure conditions. The equations developed for determining retrograde velocities for desired pericynthion positions are considered useful for estimating essential data for the preliminary planning of lunar missions. Some graphical representation is included herein for immediate familiarization with possible conditions.

Jenkins, Morris V.↗

Velocity Requirements for Abort From the Boost Trajectory of a Manned Lunar Mission

An investigation is made of the abort velocity requirements associated with failure of a propulsion system for a manned lunar mission. Two cases are considered: abort at less than satellite speed, which results in maximum decelerations in the following entry, and abort at greater than satellite speed with immediate return to earth. The velocity requirements associated with the latter problem are found to be substantial (several thousand feet per second) and are found to be even more severe if boost trajectories which lead to burnout at high altitudes or large flight-path angles are used. The velocity requirements associated with abort at less than satellite speed are found to be less severe than those for abort at greater than satellite speed except for nonlifting vehicles. It is found that abort rockets sufficient for abort at greater than satellite speed can be used to reduce maximum decelerations in entries following an abort at lower speeds. This reduction is accomplished by use of the abort rockets to decrease entry angle immediately prior to entry into the atmosphere.

Slye, Robert E.↗

Requirement Metrics for Risk Identification

The Software Assurance Technology Center (SATC) is part of the Office of Mission Assurance of the Goddard Space Flight Center (GSFC). The SATC's mission is to assist National Aeronautics and Space Administration (NASA) projects to improve the quality of software which they acquire or develop. The SATC's efforts are currently focused on the development and use of metric methodologies and tools that identify and assess risks associated with software performance and scheduled delivery. This starts at the requirements phase, where the SATC, in conjunction with software projects at GSFC and other NASA centers is working to identify tools and metric methodologies to assist project managers in identifying and mitigating risks. This paper discusses requirement metrics currently being used at NASA in a collaborative effort between the SATC and the Quality Assurance Office at GSFC to utilize the information available through the application of requirements management tools.

Hammer, Theodore↗

Requirements for Planetary Outpost Life-Support Systems and the Possible Use of In Situ Resources

If humans are ever to live and work on the Moon or Mars for extended periods of time, the operation of regenerative life-support systems at the planetary outposts will be a critical requirement. The substantial amount of materials consumed by humans and the inevitable waste products make open-loop life-support systems and resupply missions (as used in Space Shuttle and Mir operations) impractical and expensive. Natural resources found on the Moon and Mars could be used in conjunction with regenerative life support systems to further reduce the amount of material that would need to be delivered from Earth. There have been numerous studies and experiments conducted on the production of O from regolith materials on the Moon and from the atmosphere of Mars. One or several of these processes could undoubtedly be used to produce the O required by the crews at planetary outposts. Water is required in the greatest quantities, primarily for tasks such as personal hygiene and clothes washing, and it will be the most precious consumable. Again, several process have been described to produce water on the Moon using solar-wind implanted H and O, and if water ice can be found and mined at the lunar poles, another source of water may be available.

Gruener, John E.↗

Integration Time Required to Extract Accurate Data from Transonic Wind-Tunnel Tests

Because the forces and pressures on wind-tunnel models tested at transonic speeds are not steady, even for static aerodynamic tests, integration time is required to obtain data of acceptable accuracy. The integration time required for both static and dynamic tests is evaluated analytically and confirmed by experimental measurements. It is shown that, for static and dynamic tests, the accuracy obtained is a function of integration time, frequency of the signal, and the ratio of the dynamic amplitude to the full signal of interest. In addition, for the dynamic case, the frequency bandwidth used in analysis is important. Results of this study indicate that, for typical data accuracy desired from models in a large transonic wind tunnel (11- by 11-ft), up to the following integration times are required: static force and moment tests, 0.5 s; static pressure tests, 1 s; flutter tests, 30 to 60 s; and random-dynamic tests, 10 s.

Muhlstein, Lado, Jr.↗

Kinetic Requirements for the Measurement of Mesospheric Water Vapor at 6.8 (microns) under Non-LTE Conditions

We present accuracy requirements for specific kinetic parameters used to calculate the populations and vibrational temperatures of the H2O(010) and H2O(020) states in the terrestrial mesosphere. The requirements are based on rigorous simulations of the retrieval of mesospheric water vapor profiles from measurements of water vapor infrared emission made by limb scanning instruments on orbiting satellites. Major improvements in the rate constants that describe vibration-to- vibration exchange between the H2O(010) and 02(1) states are required in addition to improved specification of the rate of quenching Of O2(1) by atomic oxygen (0). It is also necessary to more accurately determine the yield of vibrationally excited O2(l) resulting from ozone photolysis. A contemporary measurement of the rate of quenching of H2O(010) by N2 and O2 is also desirable. These rates are either highly uncertain or have never before been measured at atmospheric temperatures. The suggested improvements are necessary for the interpretation of water vapor emission measurements at 6.8 microns to be made from a new spaceflight experiment in less than 2 years. The approach to retrieving water vapor under non-LTE conditions is also presented.

Zhou, Daniel K.↗

Development of Airport Surface Required Navigation Performance (RNP)

The U.S. and international aviation communities have adopted the Required Navigation Performance (RNP) process for defining aircraft performance when operating the en-route, approach and landing phases of flight. RNP consists primarily of the following key parameters - accuracy, integrity, continuity, and availability. The processes and analytical techniques employed to define en-route, approach and landing RNP have been applied in the development of RNP for the airport surface. To validate the proposed RNP requirements several methods were used. Operational and flight demonstration data were analyzed for conformance with proposed requirements, as were several aircraft flight simulation studies. The pilot failure risk component was analyzed through several hypothetical scenarios. Additional simulator studies are recommended to better quantify crew reactions to failures as well as additional simulator and field testing to validate achieved accuracy performance, This research was performed in support of the NASA Low Visibility Landing and Surface Operations Programs.

Cassell, Rick↗

A Table-Driven Control Method to Meet Continuous, Near-Real-Time Observation Requirements for the Solar X-Ray Imager

The design of the Solar X-Ray Imager (SXI) for the Geostationary Operational Environmental Satellite (GOES) presents an unusual scenario for controlling the observing sequences. The SXI is an operational instrument, designed not primarily for scientific research, but for providing "operational" data used by the National Oceanic and Atmospheric Administration (NOAA) to forecast the near-term space weather. To this end, a sequence of images selected to cover the full dynamic range of the sun will be executed routinely. As the dynamics of the sun have differing temporal cadences, the frequency of various images will differ. These images must be routinely received at the forecast center in near real-time, 24-hours a day, with a minimum of interruptions. While these requirements clearly lead to a 'routine patrol' of images, the parameters for each do not form a static set. The dynamics of the sun will change with the I 1-year solar cycle. The performance of the imaging will vary with on-orbit conditions and time. And while the SXI is not intended as a research instrument, forecasting techniques may change with time, which in turn will further alter the imaging sequences. An additional complication is the highly restricted commanding window, and a very slow commanding rate. To fulfill these requirements, the SXI was designed to utilize a table-driven approach. Sequences are defined using structured loops, with nested repetitions and delays. These sequences reference combinations of imaging parameters which in turn reference tables of parameters than can be loaded by ground commands. Multiple sequences can be built and stored in preparation for execution when determined appropriate by the NOAA forecasters. The result is an approach that can be used to provide a flexible, yet autonomous SXI capable of meeting both arbitrary forecasting requirements, and operating within the commanding constraints.

Wallace, Shawn↗