SEARCH · Search NASA
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.
The use of software fault trees for requirements identification and analysis in an Intrusion Detection System (IDS) is described.
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.
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.
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.
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.
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.
One of the methods of analysis of spectra measured in a Lead Slowing Down Spectrometer (LSDS) requires the measurement of time spectra in isotopic fission chambers (e.g., chambers lined with 235 U and 239 Pu), in addition to the measurement in threshold fission chambers. Since there is a correspondence between time after the initiating neutron pulse, and the neutron energy, it would seem possible that the response in one isotopic chamber can be converted to the response of any other isotopic fission chamber using the cross-section ratio of the fissile materials.
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.
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.
Summary of analyses on research requirements and research facilities for hypersonic aircraft
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.
Computer requirements of self contained guidance, navigation and control system onboard manned orbital space station
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.
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.
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.
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.
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.
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.