Engineering PapersSearch

SEARCH · Engineering Papers

Results for “Requirement analysis”

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 55 records · Page 3

Navigation systems requirement analysis for the Aeroassist Flight Experiment (AFE)

Navigation requirements for Aeroassist Flight Experiment (AFE) spacecraft passing through the earth's atmosphere have been studied using a 6-DOF dynamics model, an Inertial Measurement Unit model, a baseline AFE aeropass flight guidance logic, and a baseline AFE aeropass control model. The goal of this study is to determine, in a statistical sense, how much flight path angle error can be tolerated at Entry Interface (EI) and still have acceptable delta-V requirements at exit to position the AFE spacecraft for recovery. Assuming there is fuel available to produce 370 ft/sec of delta-V at atmospheric exit, a 3-sigma standard deviation in flight path angle error of 0.04 degree at EI would result in a 98 percent probability of mission success. In addition to the required delta-V at exit, other aeropass parameters such as maximum aeroheating rate, fuel consumption, and the science requirements affecting mission success are also investigated.

Huang, K. H.

Importance of Requirements Analysis & Traceability to Improve Software Quality and Reduce Cost and Risk

The goal of this paper is to emphasize the importance of developing complete and unambiguous requirements early in the project cycle (prior to Preliminary Design Phase). Having a complete set of requirements early in the project cycle allows sufficient time to generate a traceability matrix. Requirements traceability and analysis are the key elements in improving verification and validation process, and thus overall software quality. Traceability can be most beneficial when the system changes. If changes are made to high-level requirements it implies that low-level requirements need to be modified. Traceability ensures that requirements are appropriately and efficiently verified at various levels whereas analysis ensures that a rightly interpreted set of requirements is produced.

Kapoor, Manju M.

Knowledge-based requirements analysis for automating software development

We present a new software development paradigm that automates the derivation of implementations from requirements. In this paradigm, informally-stated requirements are expressed in a domain-specific requirements specification language. This language is machine-understable and requirements expressed in it are captured in a knowledge base. Once the requirements are captured, more detailed specifications and eventually implementations are derived by the system using transformational synthesis. A key characteristic of the process is that the required human intervention is in the form of providing problem- and domain-specific engineering knowledge, not in writing detailed implementations. We describe a prototype system that applies the paradigm in the realm of communication engineering: the prototype automatically generates implementations of buffers following analysis of the requirements on each buffer.

Markosian, Lawrence Z.

Spacecraft attitude control momentum requirements analysis

The relationship between attitude and angular momentum control requirements is derived for a fixed attitude, Earth orbiting spacecraft with large area articulating appendages. Environmental effects such as gravity gradient, solar radiation pressure, and aerodynamic forces arising from a dynamic, rotating atmosphere are examined. It is shown that, in general, each environmental effect contributes to both cyclic and secular momentum requirements both within and perpendicular to the orbit plane. The gyroscopic contribution to the angular momentum control requirements resulting from a rotating, Earth oriented spacecraft is also discussed. Special conditions are described where one or more components of the angular momentum can be made to vanish, or become purely cyclical. Computer generated plots for a candidate space station configuration are presented to supplement the analytically derived results.

Robertson, Brent P.

Pyrotechnic shock measurement and data analysis requirements

An investigation is described into the laboratory measurement and analysis of pyrotechnic shock which was prompted at JPL when two separate facilities generated discrepant pyrotechnic shock data while testing Mariner Jupiter/Saturn 1977 spacecraft hardware. Both of the testing facilities were surveyed. The only difference noted was in the FM tape recorders used to record the data. One facility used a tape recorder operating at 60 in./sec with a frequency response of 20 kHz; the other used a tape recorder operating at 120 in./sec with a frequency response of 80 kHz. The accelerometers, cables, charge amplifiers, and mechanical setups were identical.

Albers, L.

Requirement analysis of an intelligent, redundant, actuation system

The reliability and fault tolerance requirements of integrated, critical, digital fly-by-wire control systems for advanced military and civil aircraft requires redundant, reconfigurable implementations of the actuation system. An effective way for controlling the actuators and implementing the required fault detection and reconfiguration strategies is by means of dedicated microprocessors. This paper describes a laboratory implementation of a flexible intelligent redundant actuation system capable of demonstrating the concept and analyzing a variety of configurations and technical issues.

De Feo, P.

Space Operations Center System Analysis: Requirements for a Space Operations Center, revision A

The system and program requirements for a space operations center as defined by systems analysis studies are presented as a guide for future study and systems definition. Topics covered include general requirements for safety, maintainability, and reliability, service and habitat modules, the health maintenance facility; logistics modules; the docking tunnel; and subsystem requirements (structures, electrical power, environmental control/life support; extravehicular activity; data management; communications and tracking; docking/berthing; flight control/propulsion; and crew support). Facilities for flight support, construction, satellite and mission servicing, and fluid storage are included as well as general purpose support equipment.

Woodcock, G. R.

An application of computer aided requirements analysis to a real time deep space system

The entire procedure of incorporating the requirements and goals of a space flight project into integrated, time ordered sequences of spacecraft commands, is called the uplink process. The Uplink Process Control Task (UPCT) was created to examine the uplink process and determine ways to improve it. The Problem Statement Language/Problem Statement Analyzer (PSL/PSA) designed to assist the designer/analyst/engineer in the preparation of specifications of an information system is used as a supporting tool to aid in the analysis. Attention is given to a definition of the uplink process, the definition of PSL/PSA, the construction of a PSA database, the value of analysis to the study of the uplink process, and the PSL/PSA lessons learned.

Farny, A. M.

Ground Systems Development Environment (GSDE) interface requirements analysis: Operations scenarios

This report is a preliminary assessment of the functional and data interface requirements to the link between the GSDE GS/SPF (Amdahl) and the Space Station Control Center (SSCC) and Space Station Training Facility (SSTF) Integration, Verification, and Test Environments (IVTE's). These interfaces will be involved in ground software development of both the control center and the simulation and training systems. Our understanding of the configuration management (CM) interface and the expected functional characteristics of the Amdahl-IVTE interface is described. A set of assumptions and questions that need to be considered and resolved in order to complete the interface functional and data requirements definitions are presented. A listing of information items defined to describe software configuration items in the GSDE CM system is included. It also includes listings of standard reports of CM information and of CM-related tools in the GSDE.

Church, Victor E.

Electrical power requirements analysis. Single failure tolerant entry

The results of an analysis of the orbiter electrical power system for the case of a single failure tolerant (SFT) entry are presented. The analysis was performed using the shuttle electrical power system analysis computer program. It was performed to permit assessment of the capability of the orbiter systems to support the proposed entry configuration and to provide the data necessary to identify potential constraints and limitations. Three contingency modes have been identified which would require an SFT entry. This analysis addresses an SFT entry resulting from the loss of two fuel cell powerplants, while on orbit. The results of the analysis indicate that, even under near optimum conditions, the fuel cell power demand will exceed the tested operating capacity of 16 kw, and that various electrical components may experience voltages below 24 VDC.

Pipher, M. D.

High-Rate Delay Tolerant Networking (HDTN) Software Requirements Analysis

This document serves as a detailed analysis of the main networking protocols implemented by HDTN. Sources of the protocol specifications include Internet Engineering Task Force (IETF) Request for Comments (RFC) and Consultative Committee for Space Data Systems (CCSDS) standards. The focus of this report is to derive software requirements suitable for NASA Procedural Requirements 7150.2D Class B compliance, including requirements traceability and software verification and validation, from the source specifications. This analysis will be incorporated into the finalized HDTN Software Requirements Specification (SRS) but does not encompass the full scope of the HDTN SRS. Requirements in this document are considered draft. The complete requirements will include bundle application requirements, interface requirements, computer resource requirements, software quality factors, and additional requirements as determined by the project. This document is publicly released to the greater community to receive feedback and foster collaboration opportunities.

Rachel Dudukovich

Data requirements analysis in support of system safety

The development of a user-oriented safety data bank is reported and its data requirements are outlined. The information retrieval system employed is described along with the problems involved in its establishment and operation.

Irving Pinkel

Rendezvous radar requirements analysis for mission 3B

Data are presented verifying the compatibility of currently proposed rendezvous radar measurement accuracies with Mission 3B rendezvous requirements. In addition, data presented indicate a potential for increasing the acceptable time lag between termination of thrusting and availability of accurate measurement data. Additional investigation is recommended to define any acceptable time lag above the current proposed value. Finally, Mission 3B rendezvous performance is shown to be sensitive to variations in the relative downrange position dispersions at insertion. It is therefore recommended that insertion relative state dispersions used in studies of 3B rendezvous be reviewed when results of 3B ascent dispersion studies are available.

Hutchison, W. L.

State analysis requirements database for engineering complex embedded systems

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer's intent, potentially leading to software errors. This problem is addressed by a systems engineering tool called the State Analysis Database, which provides a tool for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using the State Analysis Database.

model base engineering

Spacelab user implementation assessment study (software requirements analysis). Volume 1: Executive study

The primary objective of this study was to develop an integrated approach for the development, implementation, and utilization of all software that is required to efficiently and cost-effectively support advanced technology laboratory flight and ground operations. It was recognized that certain aspects of the operations would be mandatory computerized services; computerization of other aspects would be optional. Thus, the analyses encompassed not only alternate computer utilization and implementations but trade studies of the programmatic effects of non-computerized versus computerized approaches to the operations. A general overview of the study is presented.

Source record

Simulation Framework to Estimate the Performance of CO2 and O2 Sensing from Space and Airborne Platforms for the ASCENDS Mission Requirements Analysis

The Active Sensing of CO2 Emissions over Nights Days and Seasons (ASCENDS) mission recommended by the NRC Decadal Survey has a desired accuracy of 0.3% in carbon dioxide mixing ratio (XCO2) retrievals requiring careful selection and optimization of the instrument parameters. NASA Langley Research Center (LaRC) is investigating 1.57 micron carbon dioxide as well as the 1.26-1.27 micron oxygen bands for our proposed ASCENDS mission requirements investigation. Simulation studies are underway for these bands to select optimum instrument parameters. The simulations are based on a multi-wavelength lidar modeling framework being developed at NASA LaRC to predict the performance of CO2 and O2 sensing from space and airborne platforms. The modeling framework consists of a lidar simulation module and a line-by-line calculation component with interchangeable lineshape routines to test the performance of alternative lineshape models in the simulations. As an option the line-by-line radiative transfer model (LBLRTM) program may also be used for line-by-line calculations. The modeling framework is being used to perform error analysis, establish optimum measurement wavelengths as well as to identify the best lineshape models to be used in CO2 and O2 retrievals. Several additional programs for HITRAN database management and related simulations are planned to be included in the framework. The description of the modeling framework with selected results of the simulation studies for CO2 and O2 sensing is presented in this paper.

Plitau, Denis