Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software engineering safety”

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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

Software and System Health Management with R2U2

R2U2 (Realizable, Responsive, Unobtrusive Unit) is a hardware-supported tool and framework for the real-time system and software health management of cyber-physical systems. R2U2 continuously monitors properties about safety, performance, and security of the vehicle and can perform diagnostic reasoning. Efficient observers for past-time and future-time Metric Temporal Logic, reasoners for Bayesian Networks, and model-based prognostics algorithms are major components of R2U2. Their combination makes it possible to design powerful models for system runtime monitoring, diagnostics, software health management, prognostics, and security monitoring. The R2U2 monitoring engine is designed for minimal runtime overhead and is available as Simulink block or as a software component for integration into the flight software stack, and enables R2U2 to monitor complex cyber-physical systems without any instrumentation of the flight software. In this presentation, we give an overview of R2U2 architecture and reasoning algorithms, present its features, and give a life demo of the tool.

Schumann, Johann↗
NASA NTRS1992

Intelligent systems for KSC ground processing

The ground processing and launch of Shuttle vehicles and their payloads is the primary task of Kennedy Space Center. It is a process which is largely manual and contains little inherent automation. Business is conducted today much as it was during previous NASA programs such as Apollo. In light of new programs and decreasing budgets, NASA must find more cost effective ways in which to do business while retaining the quality and safety of activities. Advanced technologies including artificial intelligence could cut manpower and processing time. This paper is an overview of the research and development in Al technology at KSC with descriptions of the systems which have been implemented, as well as a few under development which are promising additions to ground processing software. Projects discussed cover many facets of ground processing activities, including computer sustaining engineering, subsystem monitor and diagnosis tools and launch team assistants. The deployed Al applications have proven an effectiveness which has helped to demonstrate the benefits of utilizing intelligent software in the ground processing task.

Heard, Astrid E.↗
NASA NTRS1998

Testing and Troubleshooting Automatically Generated Source Code

Tools allowing engineers to model the real-time behavior of systems that control many types of NASA systems have become widespread. These tools automatically generate source code that is compiled, linked, then downloaded into computers controlling everything from wind tunnels to space flight systems. These tools save hundreds of hours of software development time and allow engineers with thorough application area knowledge but little software development experience to generate software to control the systems they use daily. These systems are verified and validated by simulating the real-time models, and by other techniques that focus on the model or the hardware. The automatically generated source code is typically not subjected to rigorous testing using conventional software testing techniques. Given the criticality and safety issues surrounding these systems, the application of conventional and new software testing and troubleshooting techniques to the automatically generated will improve the reliability of the resulting systems.

Henry, Joel↗
NASA NTRS2016

Modifying a Commercial Centrifuge to Reduce Electromagnetic Interference and Evaluating Functionality of Ultrasound Equipment

The Project Management and Engineering Branch (SF4) supports the Human Health and Performance Directorate (HH&P) and is responsible for developing and supporting human systems hardware for the International Space Station (ISS). When a principal investigator's (PI) medical research project on the ISS is accepted, SF4 develops the necessary hardware and software to transport to the ISS. The two projects I primarily worked on were the centrifuge and ultrasound projects. Centrifuge: One concern with spacecraft such as the ISS is electromagnetic interference (EMI) from onboard equipment, typically from radio waves (frequencies of ~3 kHz to ~300 GHz), which can negatively affect nearby circuitry. Standard commercial centrifuges produce EMI above safety limits, so my task was to help reduce EMI production from this equipment. Two centrifuges were tested: one unmodified as a control and one modified. To reduce EMI below safety limits, one centrifuge was modified to become a Faraday shield, in which significant electrical contact was made between all regions of the centrifuge housing. This included removing non-conductive paint, applying conductive fabric to the lid and foam sealer, adding a 10,000 μF decoupling capacitor across the power supply, and adding copper adhesive-mount gaskets to the housing interior. EMI testing of both centrifuges was performed in the EMI/EMC Control Test and Measurement Facility. EMI for both centrifuges was below safety limits for frequencies between 10 MHz and 15 GHz (pass); however, between 14 kHz and 10 MHz, EMI for the unmodified centrifuge exceeded safety limits (fail) as expected. Alternatively, for the modified centrifuge with the Faraday shield, EMI was below the safely limit of 55 dBμV/m for electromagnetic frequencies between 14 kHz and 10 MHz. This result indicates our modifications were successful. The successful EMI test allowed us to communicate with the vendor what modifications they needed to make to their commercial unit to meet our specifications and to understand what needs to be done in lab to the new centrifuge. Our modifications will provide a standard for readying centrifuges for future missions. Once the new modified centrifuge arrives by the vendor, it will need to undergo EMI testing again for validation. The centrifuge is also in the process of compatibility testing with a custom stowage drawer, which is an ongoing project in SF4. Both of these items will be payloads on future missions to the ISS for various research purposes. Ultrasound: ISS currently has an onboard ultrasound (Ultrasound 2 system) for research and medical purposes. Every piece of medical flight hardware has an equivalent ground-unit so instrumentation can be routinely evaluated and transported to the ISS if necessary. The ground-unit ultrasound equipment must be evaluated every six months using a task performance sheet (TPS). A TPS is a document, written by the appropriate scientists and engineers, which describes how to run equipment and is written in such a way that astronauts with unspecialized training can follow the tasks. I was responsible for performing six TPSs on a combination of three ultrasounds and two video power converters (VPCs). Performing a TPS involves checking out and computationally documenting each piece of equipment removed from storage locations, setting up hardware and software, performing tasks to verify functionality, returning equipment, and logging items back into the computerized system. My work revealed all ground-unit ultrasounds were functioning properly. Because of proper function, a discrepancy report (DR) did not have to be opened. The TPS was then passed along to the Quality Engineering (QE) for review and ultimately given to Quality Assurance (QA). Other projects: In addition to my main projects, I participated in other tasks including troubleshooting an EEG headband, volunteering for an ultrasound training research study, and conformal coating printed circuit boards. My internship at SF4 has helped me understand how space systems hardware development for the ISS fits into NASA's mission and vision.

Greening, Gage J.↗
NASA NTRS2002

REACH: Real-Time Data Awareness in Multi-Spacecraft Missions

Missions have been proposed that will use multiple spacecraft to perform scientific or commercial tasks. Indeed, in the commercial world, some spacecraft constellations already exist. Aside from the technical challenges of constructing and flying these missions, there is also the financial challenge presented by the tradition model of the flight operations team (FOT) when it is applied to a constellation mission. Proposed constellation missions range in size from three spacecraft to more than 50. If the current ratio of three-to-five FOT personnel per spacecraft is maintained, the size of the FOT becomes cost prohibitive. The Advanced Architectures and Automation Branch at the Goddard Space Flight Center (GSFC Code 588) saw the potential to reduce the cost of these missions by creating new user interfaces to the ground system health-and-safety data. The goal is to enable a smaller FOT to remain aware and responsive to the increased amount of ground system information in a multi-spacecraft environment. Rather than abandon the tried and true, these interfaces were developed to run alongside existing ground system software to provide additional support to the FOT. These new user interfaces have been combined in a tool called REACH. REACH-the Real-time Evaluation and Analysis of Consolidated Health-is a software product that uses advanced visualization techniques to make spacecraft anomalies easy to spot, no matter how many spacecraft are in the constellation. REACH reads a real-time stream of data from the ground system and displays it to the FOT such that anomalies are easy to pick out and investigate. Data visualization has been used in ground system operations for many years. To provide a unique visualization tool, we developed a unique source of data to visualize: the REACH Health Model Engine. The Health Model Engine is rule-based software that receives real-time telemetry information and outputs "health" information related to the subsystems and spacecraft that the telemetry belong to. The Health Engine can run out-of-the-box or can be tailored with a scripting language. Out of the box, it uses limit violations to determine the health of subsystems and spacecraft; when tailored, it determines health using equations combining the values and limits of any telemetry in the spacecraft. The REACH visualizations then "roll up" the information from the Health Engine into high level, summary displays. These summary visualizations can be "zoomed" into for increasing levels of detail. Currently REACH is installed in the Small Explorer (SMEX) lab at GSFC, and is monitoring three of their five spacecraft. We are scheduled to install REACH in the Mid-sized Explorer (MIDEX) lab, which will allow us to monitor up to six more spacecraft. The process of installing and using our "research" software in an operational environment has provided many insights into which parts of REACH are a step forward and which of our ideas are missteps. Our paper explores both the new concepts in spacecraft health-and-safety visualization, the difficulties of such systems in the operational environment, and the cost and safety issues of multi-spacecraft missions.

Maks, Lori↗
NASA NTRS2024

GCAS Visualization Codebase Augmentation Migration to Modern Standards and Feature Enhancements

The Glenn Research Center Communication Analysis Suite (GCAS) includes many analysis tools that can be used to support a wide range of scenarios. It includes a visualization tool that implements the three.js graphics library to display a three-dimensional (3D) representation of its results. This software will enable researchers, engineers, and mission planners to interact intuitively with and understand the results of their analyses, which might not be apparent from raw data. With NASA’s efforts to return humans to the Moon as a part of the Artemis missions, the GCAS has been used extensively for lunar terrain and landing system development analysis, which is vital to ensuring mission achievability and safety. This has created the need to add several significant features to the visualization tool, such as the ability to display the terrain of the lunar surface accurately and to provide information demonstrating how a given region might impact mission objectives. Many of the changes made to the visualization tool can be separated into one of three general advancements: code restructuring to adhere to modern coding standards and practices, new user camera controls for first-person and third-person perspective views, and a terrain generation feature to enable rendering highly accurate terrains based on any celestial body’s digital elevation model (DEM) in GeoTIFF format. These improvements notably elevate the visualization tool's functionality, accuracy, and user interaction while providing a robust foundation for future development.

Visualization↗
NASA NTRS2024

The NASA Orbital Debris Program Office - In Service of Space Safety

Since the NASA Orbital Debris Program Office’s (ODPO) founding in 1979 at the Johnson Space Center in Houston, Texas, it has been at the forefront of orbital debris research, modeling, and policy development. The ODPO has worked in collaboration with NASA and other U.S. government missions since the 1980s to mitigate the growth of the orbital debris environment and protect the population of the Earth. Two main products from the ODPO, the Orbital Debris Engineering Model (ORDEM) and the Debris Assessment Software (DAS), are frequently among the top three most-downloaded software packages from the NASA Software Catalog. These products are provided free of charge to the public in furtherance of the goal to ensure that new space missions, in compliance with NASA’s orbital debris mitigation requirements, are developed, operated, and disposed of responsibly. In addition to these external-facing software tools, the ODPO maintains high-fidelity internal tools for reentry simulation (the Object Reentry Survival Analysis Tool, ORSAT), short-term risk assessment for robotic and human spaceflight missions (the Satellite Breakup Risk Assessment Module, SBRAM), among others. Using data from the ORDEM model, as well as using the Meteoroid Environment Model (MEM) developed by the Meteoroid Environment Office (MEO) at NASA’s Marshall Space Flight Center, the Hypervelocity Impact Technology (HVIT) team uses the BUMPER code to assess penetration risk to space vehicles in Earth orbit and beyond. This paper will discuss the services that the ODPO and HVIT provide, from mission concept development through end-of-mission, for NASA-related and commercial missions.

Chris Ostrom↗
NASA NTRS2022

A Systems Model for System-Wide Safety Safety Demonstrator (SD-1): Wildfire Response Operations

The aim of this internship-based project was to contribute to the ongoing development of a systems model for System-Wide Safety’s first Technical Challenge 5 (TC5) series Safety Demonstrator (SD-1), which will be a demonstration of an In-Time Aviation Safety Management System (IASMS) in emerging wildfire response operations. Using Models-Based Systems Engineering (MBSE) principles to develop the model, I organized and traced previously collected stakeholder needs from the Spring 2022 NASA System-Wide Safety Wildland Firefighting Operations Virtual Workshop (https://nari.arc.nasa.gov/sws-wildfire) to system elements, creating connections which can be used in the future by the project engineers to identify and address requirements gaps throughout the system design process. I also identified and modeled preliminary use case scenarios for aerial assets in the demonstrator and, building on previously produced preliminary high-level models of the 8 SD-1 Services, Functions, and Capabilities (SFCs) and their IASMS data flows, worked to model the Real-Time Risk Assessment (RTRA) tool as an implementation of Risk Assessment and Management that can take in multiple sets of data monitored by SFCs. Project deliverables include stakeholder requirements tables and matrices and systems model diagrams produced with MagicDraw software in the SysML Systems Modeling Language, with eventual plans to connect model diagrams to a Department of Defense Operational Viewpoint (OV-1) graphic, a high-level operational concept graphic that will be used to visualize the SD-1 scenarioin a future phase. The system model serves to provide a common understanding of the scope of and activities necessary for the completion of SD-1,and traces how stakeholder needs are to be addressed.

model-based systems engineering↗
NASA NTRS2001

Space Debris Modeling at NASA

Since the Second European Conference on Space Debris in 1997, the Orbital Debris Program Office at the NASA Johnson Space Center has undertaken a major effort to update and improve the principal software tools employed to model the space debris environment and to evaluate mission risks. NASA's orbital debris engineering model, ORDEM, represents the current and near-term Earth orbital debris population from the largest spacecraft to the smallest debris in a manner which permits spacecraft engineers and experimenters to estimate the frequency and velocity with which a satellite may be struck by debris of different sizes. Using expanded databases and a new program design, ORDEM2000 provides a more accurate environment definition combined with a much broader array of output products in comparison with its predecessor, ORDEM96. Studies of the potential long-term space debris environment are now conducted with EVOLVE 4.0, which incorporates significant advances in debris characterization and breakup modeling. An adjunct to EVOLVE 4.0, GEO EVOLVE has been created to examine debris issues near the geosynchronous orbital regime. In support of NASA Safety Standard 1740.14, which establishes debris mitigation guidelines for all NASA space programs, a set of evaluation tools called the Debris Assessment Software (DAS) is specifically designed for program offices to determine whether they are in compliance with NASA debris mitigation guidelines. DAS 1.5 has recently been released with improved WINDOWS compatibility and graphics functions. DAS 2.0 will incorporate guideline changes in a forthcoming revision to NASA Safety Standard 1740.14. Whereas DAS contains a simplified model to calculate possible risks associated with satellite reentries, NASA's higher fidelity Object Reentry Survival Analysis Tool (ORSAT) has been upgraded to Version 5.0. With the growing awareness of the potential risks posed by uncontrolled satellite reentries to people and property on Earth, the application of both DAS and ORSAT has increased markedly in the past two years.

Johnson, Nicholas L.↗
NASA NTRS2011

NASA Tech Briefs, January 2011

The topics include: 1) Distributed Aerodynamic Sensing and Processing Toolbox; 2) Collaborative Supervised Learning for Sensor Networks; 3) Hazard Detection Software for Lunar Landing; 4) Onboard Nonlinear Engine Sensor and Component Fault Diagnosis and Isolation Scheme; 5) Network-Capable Application Process and Wireless Intelligent Sensors for ISHM; 6) Interface Supports Multiple Broadcast Transceivers for Flight Applications; 7) FPGA Sequencer for Radar Altimeter Applications; 8) Miniature Sapphire Acoustic Resonator - MSAR; 9) Process-Hardened, Multi-Analyte Sensor for Characterizing Rocket Plume Constituents; 10) SAD5 Stereo Correlation Line-Striping in an FPGA; 11) Hybrid Composite Cryogenic Tank Structure; 12) Nanoscale Deformable Optics; 13) Reliability-Based Design Optimization of a Composite Airframe Component; 14) Zinc Oxide Nanowire Interphase for Enhanced Lightweight Polymer Fiber Composites; 15) Plasma Igniter for Reliable Ignition of Combustion in Rocket Engines; 16) Wire Test Grip Fixture; 17) A Sub-Hertz, Low-Frequency Vibration Isolation Platform; 18) Carbon Nanofibers Synthesized on Selective Substrates for Nonvolatile Memory and 3D Electronics; 19) Nanoparticle/Polymer Nanocomposite Bond Coat or Coating; 20) High-Resolution Wind Measurements for Offshore Wind Energy Development; 21) Spring Tire; 22) Marsviewer 2008; 23) Mission Services Evolution Center Message Bus; 24) Major Constituents Analysis for the Vehicle Cabin Atmosphere Monitor; 25) Astronaut Health Participant Summary Application; 26) Adaption of the AMDIS Method to Flight Status on the VCAM Instrument; 27) Natural Language Interface for Safety Certification of Safety-Critical Software; 28) Cryogenic Caging for Science Instrumentation; 29) Wide-Range Neutron Detector for Space Nuclear Applications; 30) In Situ Guided Wave Structural Health Monitoring System; 31) Multiplexed Energy Coupler for Rotating Equipment; 32) Attitude Estimation in Fractionated Spacecraft Cluster Systems; 33) Full Piezoelectric Multilayer-Stacked Hybrid Actuation/Transduction Systems; 34) Active Flow Effectors for Noise and Separation Control; 35) Method and System for Temporal Filtering in Video Compression Systems; 36) Apparatus for Measuring Total Emissivity of Small, Low-Emissivity Samples; 37) Multiple-Zone Diffractive Optic Element for Laser Ranging Applications; 38) Simplified Architecture for Precise Aiming of a Deep-Space Communication Laser Transceiver; 39) Two-Photon-Absorption Scheme for Optical Beam Tracking; 40) High-Sensitivity, Broad-Range Vacuum Gauge Using Nanotubes for Micromachined Cavities; 41) Wide-Field Optic for Autonomous Acquisition of Laser Link; 42) Extracting Zero-Gravity Surface Figure of a Mirror; 43) Modeling Electromagnetic Scattering From Complex Inhomogeneous Objects; 44) Visual Object Recognition and Tracking of Tools; 45) Method for Implementing Optical Phase Adjustment; 46) Visual SLAM Using Variance Grid Maps; 47) Rapid Calculation of Spacecraft Trajectories Using Efficient Taylor Series Integration; 48) Efficient Kriging Algorithms; 49) Predicting Spacecraft Trajectories by the WeavEncke Method; 50) An Augmentation of G-Guidance Algorithms; 51) Comparison of Aircraft Icing Growth Assessment Software; 52) Silicon-Germanium Voltage-Controlled Oscillator at 105 GHz; 53) Estimation of Coriolis Force and Torque Acting on Ares-1; 54) Null Lens Assembly for X-Ray Mirror Segments; and 55) High-Precision Pulse Generator.

Source record↗
NASA NTRS1993

Canadian aeronautical mobile data trials

This paper describes a series of aeronautical mobile data trials conducted on small aircraft (helicopters and fixed wing) utilizing a low-speed store-and-forward mobile data service. The paper outlines the user requirements for aeronautical mobile satellite communications. 'Flight following' and improved wide-area dispatch communications were identified as high priority requirements. A 'proof-of-concept' trial in a Cessna Skymaster aircraft is described. This trial identified certain development work as essential to the introduction of commercial service including antenna development, power supply modifications and doppler software modifications. Other improvements were also proposed. The initial aeronautical mobile data service available for pre-operational (Beta) trials is outlined. Pre-operational field trials commenced in October 1992 and consisted of installations on a Gralen Communications Inc. Cessna 177 and an Aerospatiale Astar 350 series light single engine helicopter. The paper concludes with a discussion of desirable near term mobile data service developments, commercial benefits, current safety benefits and potential future applications for improved safety.

Pedersen, Allister↗
NASA NTRS2018

Independent Configurable Architecture for Reliable Operation of Unmanned Systems with Distributed Onboard Services

This paper presents the development of ICAROUS-2 (Independent Configurable Architecture for Reliable Operation of Unmanned Systems with Distributed Onboard Services), the second generation of a software architecture that integrates several algorithms as distributed onboard services to enable robust autonomous UAS applications. In particular, the ICAROUS architecture defines a framework to perform detect and avoid, geofencing, path monitoring, path planning, and autonomous decision making to ensure safety and mission progress. Most of the core algorithms implemented in ICAROUS are formally verified using an interactive theorem prover. These algorithms are composed together using a plan execution engine, whose operational semantics is formally specified. A description of the integrated architecture, services currently available, and flight test results highlighting the capability of ICAROUS are presented.

Balachandran, Swee↗
NASA NTRS2018

Independent Configurable Architecture for Reliable Operation of Unmanned Systems with Distributed Onboard Services

This paper presents the development of ICAROUS-2 (Independent Configurable Architecture for Reliable Operation of Unmanned Systems with Distributed Onboard Services), the second generation of a software architecture that integrates several algorithms as distributed onboard services to enable robust autonomous UAS applications. In particular, the ICAROUS architecture defines a framework to perform detect and avoid, geofencing, path monitoring, path planning, and autonomous decision making to ensure safety and mission progress. Most of the core algorithms implemented in ICAROUS are formally verified using an interactive theorem prover. These algorithms are composed together using a plan execution engine, whose operational semantics is formally specified. A description of the integrated architecture, services currently available, and flight test results highlighting the capability of ICAROUS are presented.

Balachandran, Swee↗
NASA NTRS2004

Development of Risk Assessment Matrix for NASA Engineering and Safety Center

This paper describes a study, which had as its principal goal the development of a sufficiently detailed 5 x 5 Risk Matrix Scorecard. The purpose of this scorecard is to outline the criteria by which technical issues can be qualitatively and initially prioritized. The tool using this score card has been proposed to be one of the information resources the NASA Engineering and Safety Center (NESC) takes into consideration when making decisions with respect to incoming information on safety concerns across the entire NASA agency. The contents of this paper discuss in detail each element of the risk matrix scorecard, definitions for those elements and the rationale behind the development of those definitions. This scorecard development was performed in parallel with the tailoring of the existing Futron Corporation Integrated Risk Management Application (IRMA) software tool. IRMA was tailored to fit NESC needs for evaluating incoming safety concerns and was renamed NESC Assessment Risk Management Application (NAFMA) which is still in developmental phase.

Malone, Roy W., Jr.↗
DOE OSTI2026

ARCH Technology Snapshot Autonomous Robot Control Hierarchy (ARCH): A universal software system that removes the need to rebuild robotic software for every new platform or task

Robots are increasingly used to perform repetitive, hazardous, and time-sensitive tasks, improving safety and operational efficiency. However, most robotic systems remain difficult to adapt because they are tightly tied to specific hardware and require extensive reprogramming for each new configuration.

42 ENGINEERING↗
NASA NTRS1989

Computational methods and software systems for dynamics and control of large space structures

The deployment, assembly and mission-oriented maneuvering of space structures in orbit will trigger large motions of flexible, truss-type structures. In addition, the presence of on-board controls both for attitude stabilization and specified vibration tolerance requirements may further complicate the dynamic behavior of the orbiting structures. Because of safety and cost considerations, the dynamic response of the combined structural and control systems must be predicted reliably. This need can only be met through the development of reliable and efficient simulation capabilities, since there is general agreement that on-orbit experiments should be limited because of cost, time and facility constraints. The long-term objective of this research effort is to develop a next-generation computer simulator for the dynamics and control of large space structures. The simulator will be based on integrating four research thrusts: a new multibody dynamics formulation methodology, modeling capabilities in long/slender truss-beam components with realistic joints, efficient computational procedures that can be implemented either in sequential or concurrent computers, and prototype simulation modules that can be easily processed into a modern large-scale engineering software system such as the NASA/Computational Structural Mechanics (CSM) testbed.

Park, K. C.↗
NASA NTRS1997

An Approach to Building a Traceability Tool for Software Development

It is difficult in a large, complex computer program to ensure that it meets the specified requirements. As the program evolves over time, a11 program constraints originally elicited during the requirements phase must be maintained. In addition, during the life cycle of the program, requirements typically change and the program must consistently reflect those changes. Imagine the following scenario. Company X wants to develop a system to automate its assembly line. With such a large system, there are many different stakeholders, e.g., managers, experts such as industrial and mechanical engineers, and end-users. Requirements would be elicited from all of the stake holders involved in the system with each stakeholder contributing their point of view to the requirements. For example, some of the requirements provided by an industrial engineer may concern the movement of parts through the assembly line. A point of view provided by the electrical engineer may be reflected in constraints concerning maximum power usage. End-users may be concerned with comfort and safety issues, whereas managers are concerned with the efficiency of the operation. With so many points of view affecting the requirements, it is difficult to manage them, communicate information to relevant stakeholders. and it is likely that conflicts in the requirements will arise. In the coding process, the implementors will make additional assumptions and interpretations on the design and the requirements of the system. During any stage of development, stakeholders may request that a requirement be added or changed. In such a dynamic environment, it is difficult to guarantee that the system will preserve the current set of requirements. Tracing, the mapping between objects in the artifacts of the system being developed, addresses this issue. Artifacts encompass documents such as the system definition, interview transcripts, memoranda, the software requirements specification, user's manuals, the functional specifications, design reports, and system code. Tracing helps 1) validate system features against, the requirement specification, 2) identify error sources and, most importantly, 3) manage change. With so many people involved in the development of the system, it becomes necessary to identify the reasons behind the design requirements or the implementation decisions. This paper is concerned with an approach that maps documents to constraints that capture properties of and relationships between the objects being modeled by the program. Section 2 provides the reader with a background on traceability tools. Section 3 gives a brief description of the context monitoring system on which the approach suggested in this paper is based. Section 4 presents an overview of our approach to providing traceability. The last section presents our future direction of research.

Delgado, Nelly↗
NASA NTRS1994

Hot gas ingestion effects on fuel control surge recovery and AH-1 rotor drive train torque spikes

This report summarizes the work accomplished through computer simulation to understand the impact of the hydromechanical turbine assembly (TA) fuel control on rocket gas ingestion induced engine surges on the AH-1 (Cobra) helicopter. These surges excite the lightly damped torsional modes of the Cobra rotor drive train and can cause overtorqueing of the tail rotor shaft. The simulation studies show that the hydromechanical TA control has a negligible effect on drive train resonances because its response is sufficiently attenuated at the resonant frequencies. However, a digital electronic control working through the TA control's separate, emergency fuel metering system has been identified as a solution to the overtorqueing problem. State-of-the-art software within the electronic control can provide active damping of the rotor drive train to eliminate excessive torque spikes due to any disturbances including engine surges and aggressive helicopter maneuvers. Modifications to the existing TA hydromechanical control are relatively minor, and existing engine sensors can be utilized by the electronic control. Therefore, it is concluded that the combination of full authority digital electronic control (FADEC) with hydromechanical backup using the existing TA control enhances flight safety, improves helicopter performance, reduces pilot workload, and provides a substantial payback for very little investment.

Tokarski, Frank↗