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 613 records · Page 34
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

Technical parameters for specifying imagery requirements

Providing visual information acquired from remote events to various operators, researchers, and practitioners has become progressively more important as the application of special skills in alien or hazardous situations increases. To provide an understanding of the technical parameters required to specify imagery, we have identified, defined, and discussed seven salient characteristics of images: spatial resolution, linearity, luminance resolution, spectral discrimination, temporal discrimination, edge definition, and signal-to-noise ratio. We then describe a generalizing imaging system and identified how various parts of the system affect the image data. To emphasize the different applications of imagery, we have constrasted the common television system with the significant parameters of a televisual imaging system for technical applications. Finally, we have established a method by which the required visual information can be specified by describing certain technical parameters which are directly related to the information content of the imagery. This method requires the user to complete a form listing all pertinent data requirements for the imagery.

Coan, Paul P.↗
NASA NTRS1994

National Maglev initiative: California line electric utility power system requirements

The electrical utility power system requirements were determined for a Maglev line from San Diego to San Francisco and Sacramento with a maximum capacity of 12,000 passengers an hour in each direction at a speed of 300 miles per hour, or one train every 30 seconds in each direction. Basically the Maglev line requires one 50-MVA substation every 12.5 miles. The need for new power lines to serve these substations and their voltage levels are based not only on equipment loading criteria but also on limitations due to voltage flicker and harmonics created by the Maglev system. The resulting power system requirements and their costs depend mostly on the geographical area, urban or suburban with 'strong' power systems, or mountains and rural areas with 'weak' power systems. A reliability evaluation indicated that emergency power sources, such as a 10-MW battery at each substation, were not justified if sufficient redundancy is provided in the design of the substations and the power lines serving them. With a cost of $5.6 M per mile, the power system requirements, including the 12-kV DC cables and the inverters along the Maglev line, were found to be the second largest cost component of the Maglev system, after the cost of the guideway system ($9.1 M per mile), out of a total cost of $23 M per mile.

Save, Phil↗
NASA NTRS1993

Automating test case generation for coverages required by FAA standard DO-178B

Coverage testing techniques are required by the FAA for various levels of subsystem criticality at the unit testing level. Higher levels of criticality require coverage schemes that frequently require more and more test cases, particularly when the number of conditions in a decision grows. For example, if we have a decision with n conditions of the form: if (/ci/ or /c2/ or .... or /cn/) then there are 2(n) possible combinations of condition outcomes. Given the enormous number of inputs that may be required to satisfy different coverages, and given that there are no automated tools for determining these inputs (to our knowledge), we will show how one alternative testing technique, mutation testing, can be coerced into generating inputs that satisfy a code coverage scheme X, i.e., if we modify the rules for mutant generation during mutation testing, this technique will provide test cases that satisfy X.

Voas, Jeffrey M.↗
NASA NTRS1994

Resolution requirements for velocity gradients in turbulence

Since high resolution numerical simulations of turbulent flows, or experiments at high Reynolds numbers, represent a substantial investment in resources, the estimation of the minimum resolution required for the study of a given property has been the subject of continued interest. Different properties require, in general, different resolutions, and the present paper is dedicated to the requirements for the measurement of the probability distribution functions of the velocity gradients and, in particular, of their low order moments. The deviation of these quantities from the values corresponding to a Gaussian distribution was one of the first indications of the presence of Reynolds number-dependent intermittency and has been the object of recent interest as numerical simulations have become able to explore the distribution of gradients in the low Reynolds number range, while new experiments have extended the range to increasingly high Reynolds numbers. We will use progressive filtering of the results of numerical simulations of isotropic turbulence as a model for the effect of a sensor of finite size. The numerical issues will be addressed first to ensure that the simulations are fully resolved from the point of view of the velocity gradients. This will also give us an estimate for the numerical resolution required for the different quantities.

Jimenez, Javier↗
NASA NTRS1994

Utilizing inheritance in requirements engineering

The scope of this paper is the utilization of inheritance for requirements specification, i.e., the tasks of analyzing and modeling the domain, as well as forming and defining requirements. Our approach and the tool supporting it are named RETH (Requirements Engineering Through Hypertext). Actually, RETH uses a combination of various technologies, including object-oriented approaches and artificial intelligence (in particular frames). We do not attempt to exclude or replace formal representations, but try to complement and provide means for gradually developing them. Among others, RETH has been applied in the CERN (Conseil Europeen pour la Rechereche Nucleaire) Cortex project. While it would be impossible to explain this project in detail here, it should be sufficient to know that it deals with a generic distributed control system. Since this project is not finished yet, it is difficult to state its size precisely. In order to give an idea, its final goal is to substitute the many existing similar control systems at CERN by this generic approach. Currently, RETH is also tested using real-world requirements for the Pastel Mission Planning System at ESOC in Darmstadt. First, we outline how hypertext is integrated into a frame system in our approach. Moreover, the usefulness of inheritance is demonstrated as performed by the tool RETH. We then summarize our experiences of utilizing inheritance in the Cortex project. Lastly, RETH will be related to existing work.

Kaindl, Hermann↗
NASA NTRS1995

Using SCR methods to analyze requirements documentation

Software Cost Reduction (SCR) methods are being utilized to analyze and verify selected parts of NASA's EOS-DIS Core System (ECS) requirements documentation. SCR is being used as a spot-inspection tool. Through this formal and systematic approach of the SCR requirements methods, insights as to whether the requirements are internally inconsistent or incomplete as the scenarios of intended usage evolve in the OC (Operations Concept) documentation. Thus, by modelling the scenarios and requirements as mode charts using the SCR methods, we have been able to identify problems within and between the documents.

Callahan, John↗
NASA NTRS1995

Requirements for effective use of CFD in aerospace design

This paper presents a perspective on the requirements that Computational Fluid Dynamics (CFD) technology must meet for its effective use in aerospace design. General observations are made on current aerospace design practices and deficiencies are noted that must be rectified for the U.S. aerospace industry to maintain its leadership position in the global marketplace. In order to rectify deficiencies, industry is transitioning to an integrated product and process development (IPPD) environment and design processes are undergoing radical changes. The role of CFD in producing data that design teams need to support flight vehicle development is briefly discussed. An overview of the current state of the art in CFD is given to provide an assessment of strengths and weaknesses of the variety of methods currently available, or under development, to produce aerodynamic data. Effectiveness requirements are examined from a customer/supplier view point with design team as customer and CFD practitioner as supplier. Partnership between the design team and CFD team is identified as an essential requirement for effective use of CFD. Rapid turnaround, reliable accuracy, and affordability are offered as three key requirements that CFD community must address if CFD is to play its rightful role in supporting the IPPD design environment needed to produce high quality yet affordable designs.

Raj, Pradeep↗
NASA NTRS1994

Experience report: Using formal methods for requirements analysis of critical spacecraft software

Formal specification and analysis of requirements continues to gain support as a method for producing more reliable software. However, the introduction of formal methods to a large software project is difficult, due in part to the unfamiliarity of the specification languages and the lack of graphics. This paper reports results of an investigation into the effectiveness of formal methods as an aid to the requirements analysis of critical, system-level fault-protection software on a spacecraft currently under development. Our experience indicates that formal specification and analysis can enhance the accuracy of the requirements and add assurance prior to design development in this domain. The work described here is part of a larger, NASA-funded research project whose purpose is to use formal-methods techniques to improve the quality of software in space applications. The demonstration project described here is part of the effort to evaluate experimentally the effectiveness of supplementing traditional engineering approaches to requirements specification with the more rigorous specification and analysis available with formal methods.

Lutz, Robyn R.↗
NASA NTRS1995

An overview of NASA testing requirements for alternate cleaning solvents used in liquid and gaseous oxygen environments

The elimination of CFC-containing cleaning solvents for oxygen systems has prompted the development of a number of alternative cleaning solvents that must now be evaluated not only for cleanability, but compatibility as well. NASA Handbook 8060.1(NHB 8060.1) establishes the requirements for evaluation, testing, and selection of materials for use in oxygen rich environments. Materials intended for use in space vehicles, specified test facilities, and ground support equipment must meet the requirements of this document. In addition to the requirements of NHB 8060.1 for oxygen service, alternative cleaning solvents must also be evaluated in other areas (such as corrosivity, non-metals compatibility, non-volatile residue contamination, etc.). This paper will discuss the testing requirements of NHB 8060.1 and present preliminary results from early screening tests performed at Marshall Space Flight Center's Materials Combustion Research Facility.

Strickland, John W.↗
NASA NTRS1995

Aerothermodynamic testing requirements for future space transportation systems

Aerothermodynamics, encompassing aerodynamics, aeroheating, and fluid dynamic and physical processes, is the genesis for the design and development of advanced space transportation vehicles. It provides crucial information to other disciplines involved in the development process such as structures, materials, propulsion, and avionics. Sources of aerothermodynamic information include ground-based facilities, computational fluid dynamic (CFD) and engineering computer codes, and flight experiments. Utilization of this triad is required to provide the optimum requirements while reducing undue design conservatism, risk, and cost. This paper discusses the role of ground-based facilities in the design of future space transportation system concepts. Testing methodology is addressed, including the iterative approach often required for the assessment and optimization of configurations from an aerothermodynamic perspective. The influence of vehicle shape and the transition from parametric studies for optimization to benchmark studies for final design and establishment of the flight data book is discussed. Future aerothermodynamic testing requirements including the need for new facilities are also presented.

Paulson, John W., Jr.↗
NASA NTRS1996

An introduction to requirements capture using PVS: Specification of a simple autopilot

This paper presents an introduction to capturing software requirements in the PVS formal language. The object of study is a simplified digital autopilot that was motivated in part by the mode control panel of NASA Langley's Boeing 737 research aircraft. The paper first presents the requirements for this autopilot in English and then steps the reader through a translation of these requirements into formal mathematics. Along the way deficiencies in the English specification are noted and repaired. Once completed, the formal PVS requirement is analyzed using the PVS theorem prover and shown to maintain an invariant over its state space.

Butler, Ricky W.↗
NASA NTRS1996

Experiences Using Formal Methods for Requirements Modeling

This paper describes three cases studies in the lightweight application of formal methods to requirements modeling for spacecraft fault protection systems. The case studies differ from previously reported applications of formal methods in that formal methods were applied very early in the requirements engineering process, to validate the evolving requirements. The results were fed back into the projects, to improve the informal specifications. For each case study, we describe what methods were applied, how they were applied, how much effort was involved, and what the findings were. In all three cases, the formal modeling provided a cost effective enhancement of the existing verification and validation processes. We conclude that the benefits gained from early modeling of unstable requirements more than outweigh the effort needed to maintain multiple representations.

Easterbrook, Steve↗
NASA NTRS1996

Communication Problems in Requirements Engineering: A Field Study

The requirements engineering phase of software development projects is characterized by the intensity and importance of communication activities. During this phase, the various stakeholders must be able to communicate their requirements to the analysts, and the analysts need to be able to communicate the specifications they generate back to the stakeholders for validation. This paper describes a field investigation into the problems of communication between disparate communities involved in the requirements specification activities. The results of this study are discussed in terms of their relation to three major communication barriers: (1) ineffectiveness of the current communication channels; (2) restrictions on expressiveness imposed by notations; and (3) social and organizational barriers. The results confirm that organizational and social issues have great influence on the effectiveness of communication. They also show that in general, end-users find the notations used by software practitioners to model their requirements difficult to understand and validate.

Al-Rawas, Amer↗
NASA NTRS1996

Explicit and Implicit Resources: A Simplified Approach to User Requirements Modeling

The International Space Station (ISS) program is dependent on the concept of distributed planning, which places a large responsibility in the hands of the science users. The users assume the responsibility in submitting the operations scheduling requirements in the format required by the scheduling software. The concept of explicit and implicit resources, developed to facilitate the operations scheduling of ISS by non-scheduling experts, is presented. The proposed concepts are defined and examples of scheduling requirements, implemented using explicit and implicit resources, are described together with the requirements modeling and scheduler formatting functions. The software developed to support the implicit and explicit resources concept is discussed.

Hagopian, Jeff↗
NASA NTRS1998

A modernized approach to meet diversified earth observing system (EOS) AM-1 mission requirements

From a flight dynamics perspective, the EOS AM-1 mission design and maneuver operations present a number of interesting challenges. The mission design itself is relatively complex for a low Earth mission, requiring a frozen, Sun-synchronous, polar orbit with a repeating ground track. Beyond the need to design an orbit that meets these requirements, the recent focus on low-cost, 'lights out' operations has encouraged a shift to more automated ground support. Flight dynamics activities previously performed in special facilities created solely for that purpose and staffed by personnel with years of design experience are now being shifted to the mission operations centers (MOCs) staffed by flight operations team (FOT) operators. These operators' responsibilities include flight dynamics as a small subset of their work; therefore, FOT personnel often do not have the experience to make critical maneuver design decisions. Thus, streamlining the analysis and planning work required for such a complicated orbit design and preparing FOT personnel to take on the routine operation of such a spacecraft both necessitated increasing the automation level of the flight dynamics functionality. The FreeFlyer(TM) software developed by AI Solutions provides a means to achieve both of these goals. The graphic interface enables users to interactively perform analyses that previously required many parametric studies and much data reduction to achieve the same result In addition, the fuzzy logic engine enables the simultaneous evaluation of multiple conflicting constraints, removing the analyst from the loop and allowing the FOT to perform more of the operations without much background in orbit design. Modernized techniques were implemented for EOS AM-1 flight dynamics support in several areas, including launch window determination, orbit maintenance maneuver control strategies, and maneuver design and calibration automation. The benefits of implementing these techniques include increased fuel available for on-orbit maneuvering, a simplified orbit maintenance process to minimize science data downtime, and an automated routine maneuver planning process. This paper provides an examination of the modernized techniques implemented for EOS AM-1 to achieve these benefits.

Newman, Lauri Kraft↗
NASA NTRS1961

The Effect of Lift on Entry Corridor Depth and Guidance Requirements for the Return Lunar Flight

Corridors for manned vehicles are defined consistent with requirements for avoiding radiation exposure and for limiting values of peak deceleration. Use of lift increases the depth of the entry corridor. Mid-course guidance requirements appear to be critical only for the flight-path angle. Increasing the energy of the transport orbit increases the required guidance accuracy for the flight-path angle. Corrective thrust applied essentially parallel to the local horizontal produces the maximum change in perigee altitude for a given increment of velocity. Energy required to effect a given change in perigee altitude varies inversely with range measured from the center of the earth.

Wong, Thomas J.↗
NASA NTRS1998

Investigation of Propulsion System Requirements for Spartan Lite

This paper discusses the (chemical or electric) propulsion system requirements necessary to increase the Spartan Lite science mission lifetime to over a year. Spartan Lite is an extremely low-cost (less than 10 M) spacecraft bus being developed at the NASA Goddard Space Flight Center to accommodate sounding rocket class (40 W, 45 kg, 35 cm dia by 1 m length) payloads. While Spartan Lite is compatible with expendable launch vehicles, most missions are expected to be tertiary payloads deployed by. the Space Shuttle. To achieve a one year or longer mission life from typical Shuttle orbits, some form of propulsion system is required. Chemical propulsion systems (characterized by high thrust impulsive maneuvers) and electrical propulsion systems (characterized by low-thrust long duration maneuvers and the additional requirement for electrical power) are discussed. The performance of the Spartan Lite attitude control system in the presence of large disturbance torques is evaluated using the Trectops(Tm) dynamic simulator. This paper discusses the performance goals and resource constraints for candidate Spartan Lite propulsion systems and uses them to specify quantitative requirements against which the systems are evaluated.

Urban, Mike↗
NASA NTRS1998

A Modernized Approach to Meet Diversified Earth Observing System (EOS) AM-1 Mission Requirements

From a flight dynamics perspective, the EOS AM-1 mission design and maneuver operations present a number of interesting challenges. The mission design itself is relatively complex for a low Earth mission, requiring a frozen, Sun-synchronous, polar orbit with a repeating ground track. Beyond the need to design an orbit that meets these requirements, the recent focus on low-cost, "lights out" operations has encouraged a shift to more automated ground support. Flight dynamics activities previously performed in special facilities created solely for that purpose and staffed by personnel with years of design experience are now being shifted to the mission operations centers (MOCs) staffed by flight operations team (FOT) operators. These operators' responsibilities include flight dynamics as a small subset of their work; therefore, FOT personnel often do not have the experience to make critical maneuver design decisions. Thus, streamlining the analysis and planning work required for such a complicated orbit design and preparing FOT personnel to take on the routine operation of such a spacecraft both necessitated increasing the automation level of the flight dynamics functionality. The FreeFlyer(trademark) software developed by AI Solutions provides a means to achieve both of these goals. The graphic interface enables users to interactively perform analyses that previously required many parametric studies and much data reduction to achieve the same result. In addition, the fuzzy logic engine .enables the simultaneous evaluation of multiple conflicting constraints, removing the analyst from the loop and allowing the FOT to perform more of the operations without much background in orbit design. Modernized techniques were implemented for EOS AM-1 flight dynamics support in several areas, including launch window determination, orbit maintenance maneuver control strategies, and maneuver design and calibration automation. The benefits of implementing these techniques include increased fuel available for on-orbit maneuvering, a simplified orbit maintenance process to minimize science data downtime, and an automated routine maneuver planning process. This paper provides an examination of the modernized techniques implemented for EOS AM-1 to achieve these benefits.

Newman, Lauri Kraft↗