Search NASA⌕ Search

SEARCH · Search NASA

Results for “Requirements engineering”

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 NTRS2006

Questioning the Role of Requirements Engineering in the Causes of Safety-Critical Software Failures

Many software failures stem from inadequate requirements engineering. This view has been supported both by detailed accident investigations and by a number of empirical studies; however, such investigations can be misleading. It is often difficult to distinguish between failures in requirements engineering and problems elsewhere in the software development lifecycle. Further pitfalls arise from the assumption that inadequate requirements engineering is a cause of all software related accidents for which the system fails to meet its requirements. This paper identifies some of the problems that have arisen from an undue focus on the role of requirements engineering in the causes of major accidents. The intention is to provoke further debate within the emerging field of forensic software engineering.

Johnson, C. W.↗
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 NTRS1991

Tracing And Control Of Engineering Requirements

TRACER (Tracing and Control of Engineering Requirements) is data-base/word-processing software system created to document and maintain order of both requirements and descriptions associated with engineering project. Implemented on IBM PC under PC-DOS. Written with CLIPPER.

Turner, Philip R.↗
NASA NTRS2008

The First Development of Human Factors Engineering Requirements for Application to Ground Task Design for a NASA Flight Program

The National Aeronautics and Space Administration has long applied standards-derived human engineering requirements to the development of hardware and software for use by astronauts while in flight. The most important source of these requirements has been NASA-STD-3000. While there have been several ground systems human engineering requirements documents, none has been applicable to the flight system as handled at NASA's launch facility at Kennedy Space Center. At the time of the development of previous human launch systems, there were other considerations that were deemed more important than developing worksites for ground crews; e.g., hardware development schedule and vehicle performance. However, experience with these systems has shown that failure to design for ground tasks has resulted in launch schedule delays, ground operations that are more costly than they might be, and threats to flight safety. As the Agency begins the development of new systems to return humans to the moon, the new Constellation Program is addressing this issue with a new set of human engineering requirements. Among these requirements is a subset that will apply to the design of the flight components and that is intended to assure ground crew success in vehicle assembly and maintenance tasks. These requirements address worksite design for usability and for ground crew safety.

Dischinger, H. Charles, Jr.↗
NASA NTRS1990

STV engine requirements

The Space Exploration Initiative program and the Space Transfer Vehicle studies provide the opportunity to evaluate the engine requirements for the next generation space engine within the context of a credible but technologically demanding program. Some of these requirements are generic, basically independent of the architecture, and others are mission and configuration dependent. Generic requirements include high reliability, space-basing, man-rataing, long life and reusability, and extended health monitoring, including automatic pre-mission checkout. Mission and configuration dependent requirements include vehicle/engine interfaces, engine throttling, performance specifications, engine system architecture, and operational requirements. It is argued that engine technology requirements must be extended from the usual performance-related issues to encompass reliability, space-basing, life, and extended health monitoring.

Redus, J. R.↗
NASA NTRS2023

Requirements Engineering Scorecard and the Next-Generation Space Suit

The objective for a NASA contractor, the performing organization in this case study, is to provide engineering services to develop and deliver the next generation space suit to NASA, the customer in this case study. A case study with qualitative and quantitative analyses regarding a new process and approach to requirements engineering is described, with the intent that if utilized, these tools may have contributed to improvements across the project in terms of meeting cost, scope, budget and quality while appropriately accounting for risk management. The procedure entails a research method in which the current state of the project, current state of the art, and the identified systems engineering challenges are evaluated. Iterative models are tempered through development by continual improvements by engineering evaluation of engineers on the project. The current results have produced a prototype of a requirements engineering scorecard with implementations of FMEA and quantitative analysis to (i) identify root cause of underdeveloped requirements and (ii) project management impacts with regards to project risk. Forward work includes customer, performing organization, acceptance against applicable INCOSE community accepted practices.

INCOSE↗
NASA NTRS2010

What is the Final Verification of Engineering Requirements?

This slide presentation reviews the process of development through the final verification of engineering requirements. The definition of the requirements is driven by basic needs, and should be reviewed by both the supplier and the customer. All involved need to agree upon a formal requirements including changes to the original requirements document. After the requirements have ben developed, the engineering team begins to design the system. The final design is reviewed by other organizations. The final operational system must satisfy the original requirements, though many verifications should be performed during the process. The verification methods that are used are test, inspection, analysis and demonstration. The plan for verification should be created once the system requirements are documented. The plan should include assurances that every requirement is formally verified, that the methods and the responsible organizations are specified, and that the plan is reviewed by all parties. The options of having the engineering team involved in all phases of the development as opposed to having some other organization continue the process once the design has been complete is discussed.

Poole, Eric↗
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 NTRS2003

The case for applying an early-lifecycle technology evaluation methodology to comparative evaluation of requirements engineering research

The premise of this paper is taht there is a useful analogy between evaluation of proposed problem solutions and evaluation of requirements engineering research itself. Both of these application areas face the challenges of evaluation early in the lifecycle, of the need to consider a wide variety of factors, and of the need to combine inputs from multiple stakeholders in making thse evaluation and subsequent decisions.

technology transfer↗
NASA NTRS2001

Requirements engineering and program synthesis: Mutually exclusive or synergistic?

There has often been a clash within the formal methods community between early life-cycle proponents such as the requirements engineering community and late life-cycle proponents such as the program synthesis community. This talk will first characterize these positions and their underlying assumptions, and then expose a common set of problems and approaches. The talk will then propose an integrated life-cycle framework, and expound on its potential benefits. Technical challenges to achieving this integrated life-cycle framework will be described, as well as some preliminary work towards that goal.

Program synthesis↗
DOE OSTI2026

Cyber-Informed Engineering Requirements Framework Use Cases

The requirement analysis use case effort leverages the Cyber-Informed Engineering (CIE) requirements framework to examine two real-world scenarios: Battery Energy Storage System (BESS) installation at the Flatirons Campus, NLR; SCADA improvement program. This work evaluates the existing requirements for each use case, applies the CIE requirements framework, and assesses the benefits and enhancements gained compared to the current requirements. The results will advance CIE from concept to practical application by identifying key opportunities for integrating CIE principles into established engineering workflows during the requirements phase.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS1985

Future heavy duty trucking engine requirements

Developers of advanced heavy duty diesel engines are engaged in probing the opportunities presented by new materials and techniques. This process is technology driven, but there is neither assurance that the eventual users of the engines so developed will be comfortable with them nor, indeed, that those consumers will continue to exist in either the same form, or numbers as they do today. To ensure maximum payoff of research dollars, the equipment development process must consider user needs. This study defines motor carrier concerns, cost tolerances, and the engine parameters which match the future projected industry needs. The approach taken to do that is to be explained and the results presented. The material to be given comes basically from a survey of motor carrier fleets. It provides indications of the role of heavy duty vehicles in the 1998 period and their desired maintenance and engine performance parameters.

Strawhorn, L. W.↗
NASA NTRS2009

Compressor Study to Meet Large Civil Tilt Rotor Engine Requirements

A vehicle concept study has been made to meet the requirements of the Large Civil Tilt Rotorcraft vehicle mission. A vehicle concept was determined, and a notional turboshaft engine system study was conducted. The engine study defined requirements for the major engine components, including the compressor. The compressor design-point goal was to deliver a pressure ratio of 31:1 at an inlet weight flow of 28.4 lbm/sec. To perform a conceptual design of two potential compressor configurations to meet the design requirement, a mean-line compressor flow analysis and design code were used. The first configuration is an eight-stage axial compressor. Some challenges of the all-axial compressor are the small blade spans of the rear-block stages being 0.28 in., resulting in the last-stage blade tip clearance-to-span ratio of 2.4%. The second configuration is a seven-stage axial compressor, with a centrifugal stage having a 0.28-in. impeller-exit blade span. The compressors conceptual designs helped estimate the flow path dimensions, rotor leading and trailing edge blade angles, flow conditions, and velocity triangles for each stage.

Veres, Joseph P.↗
NASA NTRS2009

Compressor Study to Meet Large Civil Tilt Rotor Engine Requirements

A vehicle concept study has been made to meet the requirements of the Large Civil Tilt Rotorcraft vehicle mission. A vehicle concept was determined, and a notional turboshaft engine system study was conducted. The engine study defined requirements for the major engine components, including the compressor. The compressor design-point goal was to deliver a pressure ratio of 31:1 at an inlet weight flow of 28.4 lbm/sec. To perform a conceptual design of two potential compressor configurations to meet the design requirement, a mean-line compressor flow analysis and design code were used. The first configuration is an eight-stage axial compressor. Some challenges of the all-axial compressor are the small blade spans of the rear-block stages being 0.28 in., resulting in the last-stage blade tip clearance-to-span ratio of 2.4 percent. The second configuration is a seven-stage axial compressor, with a centrifugal stage having a 0.28-in. impeller-exit blade span. The compressors conceptual designs helped estimate the flow path dimensions, rotor leading and trailing edge blade angles, flow conditions, and velocity triangles for each stage.

Veres, Joseph P.↗
NASA NTRS1975

US Army Corps of Engineers requirements and programs

Plans by the Corps of Engineers to utilize data collection systems to support their mission of development, utilization, and conservation of the water resources of the Nation, flood control, water management, hydroelectric power, maintenance of navigable waterways, reservoir construction, and river basin control are briefly addressed.

Jarman, J. W.↗
NASA NTRS1981

Heat engine requirements for advanced solar thermal power systems

Requirements and constraints are established for power conversion subsystems, including heat engine, alternator and auxiliaries, of dish concentrator solar thermal power systems. In order to be competitive with conventional power systems, it is argued that the heat engine should be of less than 40 kW rated output, in a subsystem with an efficiency of at least 40% at rated output and at least 37% at half power. An interval between major overhauls of 50,000 hours is also desirable, along with minor maintenance and lubrication not more than four times a year requiring no more than one man-hour each time, and optimal reliability. Also found to be important are the capability for hybrid operation using heat from a solar receiver, fuel-fired combustor or both simultaneously, operation at any attitude, stability to transients in input power and output loading, operation at ambient temperatures from -30 to 50 C, and compatibility with environmental and safety requirements. Cost targets include a price of $180/kWe, and operation, maintenance and replacement costs averaging $0.001/kWh for 30 years of operation.

Jaffe, L. D.↗