Search NASA⌕ Search

SEARCH · Search NASA

Results for “std”

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 379 records · Page 21

Gas Dynamic Spray Technology Demonstration

Zinc primer systems are currently used across NASA and AFSPC for corrosion protection of steel. AFSPC and NASA have approved the use of Thermal Spray Coatings (TSCs) as an environmentally preferable alternative. TSCs are approved in NASA-STD-5008 and AFSPC and KSC is currently looking for additional applications in which TSC can be used. Gas Dynamic Spray (GDS, also known as Cold Spray) is being evaluated as a means of repairing TSCs and for areas such as corners and edges where TSCs do not work as well. Other applications could include spot repair/maintenance of steel on structures, facilities, and ground support equipment.

Burford, Pattie Lewis↗

Loads and Structural Dynamics Requirements for Spaceflight Hardware

The purpose of this document is to establish requirements relating to the loads and structural dynamics technical discipline for NASA and commercial spaceflight launch vehicle and spacecraft hardware. Requirements are defined for the development of structural design loads and recommendations regarding methodologies and practices for the conduct of load analyses are provided. As such, this document represents an implementation of NASA STD-5002. Requirements are also defined for structural mathematical model development and verification to ensure sufficient accuracy of predicted responses. Finally, requirements for model/data delivery and exchange are specified to facilitate interactions between Launch Vehicle Providers (LVPs), Spacecraft Providers (SCPs), and the NASA Technical Authority (TA) providing insight/oversight and serving in the Independent Verification and Validation role. In addition to the analysis-related requirements described above, a set of requirements are established concerning coupling phenomena or other interaction between structural dynamics and aerodynamic environments or control or propulsion system elements. Such requirements may reasonably be considered structure or control system design criteria, since good engineering practice dictates consideration of and/or elimination of the identified conditions in the development of those subsystems. The requirements are included here, however, to ensure that such considerations are captured in the design space for launch vehicles (LV), spacecraft (SC) and the Launch Abort Vehicle (LAV). The requirements in this document are focused on analyses to be performed to develop data needed to support structural verification. As described in JSC 65828, Structural Design Requirements and Factors of Safety for Spaceflight Hardware, implementation of the structural verification requirements is expected to be described in a Structural Verification Plan (SVP), which should describe the verification of each structural item for the applicable requirements. The requirement for and expected contents of the SVP are defined in JSC 65828. The SVP may also document unique verifications that meet or exceed these requirements with Technical Authority approval.

George James↗

NASA Tech Briefs, November 2004

Topics include: Multifunction Imaging and Spectroscopic Instrument; Position-Finding Instrument Built Around a Magnetometer; Improved Measurement of Dispersion in an Optical Fiber; Probe for Sampling of Interstitial Fluid From Bone; Neuropsychological Testing of Astronauts; Method of Calibration for a Large Cathetometer System; Four-Channel PC/104 MIL-STD-1553 Circuit Board; Improved Method of Locating Defects in Wiring Insulation; Strobe Traffic Lights Warn of Approaching Emergency Vehicles; Improved Timing Scheme for Spaceborne Precipitation Radar; Concept for Multiple-Access Free-Space Laser Communications; Variable Shadow Screens for Imaging Optical Devices; Verifying Diagnostic Software; Initial Processing of Infrared Spectral Data; Activity-Centric Approach to Distributed Programming; Controlling Distributed Planning; New Material for Surface-Enhanced Raman Spectroscopy; Treated Carbon Nanofibers for Storing Energy in Aqueous KOH; Advanced Infant Car Seat Would Increase Highway Safety; Development of Biomorphic Flyers; Second-Generation Six-Limbed Experimental Robot; Miniature Linear Actuator for Small Spacecraft; Process for Making Single-Domain Magnetite Crystals; A New Process for Fabricating Random Silicon Nanotips; Resin-Transfer-Molding of a Tool Face; Improved Phase-Mask Fabrication of Fiber Bragg Gratings; Tool for Insertion of a Fiber-Optic Terminus in a Connector; Nanofluidic Size-Exclusion Chromatograph; Lightweight, Low-CTE Tubes Made From Biaxially Oriented LCPs; Using Redundancy To Reduce Errors in Magnetometer Readings; Compact Instrument for Measuring Profile of a Light Beam; Multilayer Dielectric Transmissive Optical Phase Modulator; Second-Generation Multi-Angle Imaging Spectroradiometer; Real-Time Adaptive Color Segmentation by Neural Networks; Research and Development in Optical Communications; Tests of Multibeam Scintillation Mitigation on Laser Uplinks; and Spaceborne Infrared Atmospheric Sounder.

Source record↗

Developing a Habitat for Long Duration, Deep Space Missions

One possible next leap in human space exploration is a mission to a near Earth asteroid (NEA). In order to achieve such an ambitious goal, a space habitat will need to be designed to accommodate a crew of four for the 380-day round trip. The Human Spaceflight Architecture Team (HAT) developed a conceptual design for such a habitat. The team identified activities that would be performed inside a long-duration, deep space habitat, and the capabilities needed to support such a mission. A list of seven functional activities/capabilities was developed: individual and group crew care, spacecraft and mission operations, subsystem equipment, logistics and resupply, and contingency operations. The volume for each activity was determined using NASA STD-3001 and the companion Human Integration Design Handbook (HIDH). Although, the sum of these volumes produced an over-sized spacecraft, the team evaluated activity frequency and duration to identify functions that could share a common volume without conflict, reducing the total volume by 24%. After adding 10% for growth, the resulting functional pressurized volume was calculated to be 268 m3 distributed over the functions. The work was validated through comparison with the International Space Station (ISS), Bigelow Aerospace s proposed habitat module, and NASA s Trans-Hab concepts. In the end, the team developed an internal layout that (a) minimized the transit time between related crew stations, (b) accommodated expected levels of activity at each station, (c) isolated stations when necessary for health, safety, performance, and privacy, and (d) provided a safe, efficient, and comfortable work and living environment.

Rucker, Michelle A.↗

NASA Tech Briefs, November 2003

Topics covered include: Computer Program Recognizes Patterns in Time-Series Data; Program for User-Friendly Management of Input and Output Data Sets; Noncoherent Tracking of a Source of a Data-Modulated Signal; Software for Acquiring Image Data for PIV; Detecting Edges in Images by Use of Fuzzy Reasoning; A Timer for Synchronous Digital Systems; Prototype Parts of a Digital Beam-Forming Wide-Band Receiver; High-Voltage Droplet Dispenser; Network Extender for MIL-STD-1553 Bus; MMIC HEMT Power Amplifier for 140 to 170 GHz; Piezoelectric Diffraction-Based Optical Switches; Numerical Modeling of Nanoelectronic Devices; Organizing Diverse, Distributed Project Information; Eigensolver for a Sparse, Large Hermitian Matrix; Modified Polar-Format Software for Processing SAR Data; e-Stars Template Builder; Software for Acoustic Rendering; Functionally Graded Nanophase Beryllium/Carbon Composites; Thin Thermal-Insulation Blankets for Very High Temperatures; Prolonging Microgravity on Parabolic Airplane Flights; Device for Locking a Control Knob; Cable-Dispensing Cart; Foam Sensor Structures Would be Self-Deployable and Survive Hard Landings; Real-Gas Effects on Binary Mixing Layers; Earth-Space Link Attenuation Estimation via Ground Radar Kdp; Wedge Heat-Flux Indicators for Flash Thermography; Measuring Diffusion of Liquids by Common-Path Interferometry; Zero-Shear, Low-Disturbance Optical Delay Line; Whispering-Gallery Mode-Locked Lasers; Spatial Light Modulators as Optical Crossbar Switches; Update on EMD and Hilbert-Spectra Analysis of Time Series; Quad-Tree Visual-Calculus Analysis of Satellite Coverage; Dyakonov-Perel Effect on Spin Dephasing in n-Type GaAs; Update on Area Production in Mixing of Supercritical Fluids; and Quasi-Sun-Pointing of Spacecraft Using Radiation Pressure.

Source record↗

Dynamic Monitoring of Cleanroom Fallout Using an Air Particle Counter

The particle fallout limitations and periodic allocations for the James Webb Space Telescope are very stringent. Standard prediction methods are complicated by non-linearity and monitoring methods that are insufficiently responsive. A method for dynamically predicting the particle fallout in a cleanroom using air particle counter data was determined by numerical correlation. This method provides a simple linear correlation to both time and air quality, which can be monitored in real time. The summation of effects provides the program better understanding of the cleanliness and assists in the planning of future activities. Definition of fallout rates within a cleanroom during assembly and integration of contamination-sensitive hardware, such as the James Webb Space Telescope, is essential for budgeting purposes. Balancing the activity levels for assembly and test with the particle accumulation rate is paramount. The current approach to predicting particle fallout in a cleanroom assumes a constant air quality based on the rated class of a cleanroom, with adjustments for projected work or exposure times. Actual cleanroom class can also depend on the number of personnel present and the type of activities. A linear correlation of air quality and normalized particle fallout was determined numerically. An air particle counter (standard cleanroom equipment) can be used to monitor the air quality on a real-time basis and determine the "class" of the cleanroom (per FED-STD-209 or ISO-14644). The correlation function provides an area coverage coefficient per class-hour of exposure. The prediction of particle accumulations provides scheduling inputs for activity levels and cleanroom class requirements.

Perry, Radford↗

Status of a NASA Standard and Three NASA Handbooks

NASA-STD-7003 Pyroshock Test Criteria, May 18, 1999, has been revised per direction of NASA Headquarters to make it a mandatory standard and to update it for advances in the discipline since it's initial release. NASA-HDBK-7004B Force Limited Vibration Testing, January 31, 2003, and NASA-HDBK-7005 Dynamic Environmental Criteria, March 13, 2001, are being updated to reflect advances in the disciplines since their last release. Additionally, a new NASA handbook, NASA-HDBK-7008 Spacecraft Structural Dynamics Testing is currently being prepared. This paper provides an overview of each document, summarizes the major revisions for the documents undergoing update, and provides the development schedules.

dynamics environment criteria↗

The Development and Implementation of Ground Safety Requirements for Project Orion Abort Flight Testing - A Case Study

A rigorous set of detailed ground safety requirements is required to make sure that ground support equipment (GSE) and associated planned ground operations are conducted safely. Detailed ground safety requirements supplement the GSE requirements already called out in NASA-STD-5005. This paper will describe the initial genesis of these ground safety requirements, the establishment and approval process and finally the implementation process for Project Orion. The future of the requirements will also be described. Problems and issues encountered and overcame will be discussed.

Kirkpatrick, Paul D.↗

Developing a Habitat for Long Duration, Deep Space Missions

One possible next leap in human space exploration for the National Aeronautics and Space Administration (NASA) is a mission to a near Earth asteroid (NEA). In order to achieve such an ambitious goal, a space habitat will need to accommodate a crew of four for the 380-day round trip. The Human Spaceflight Architecture Team (HAT) developed a conceptual design for such a habitat. The team identified activities that would be performed inside a long-duration, deep space habitat, and the capabilities needed to support such a mission. A list of seven functional activities/capabilities was developed: individual and group crew care, spacecraft and mission operations, subsystem equipment, logistics and resupply, and contingency operations. The volume for each activity was determined using NASA STD-3001 and the companion Human Integration Design Handbook (HIDH). Although, the sum of these volumes produced an over-sized spacecraft, the team evaluated activity frequency and duration to identify functions that could share a common volume without conflict, reducing the total volume by 24%. After adding 10% for growth, the resulting functional pressurized volume was calculated to be a minimum of 268 cu m (9,464 cu ft) distributed over the functions. The work was validated through comparison to Mir, Skylab, the International Space Station (ISS), Bigelow Aerospace s proposed habitat module, and NASA s Trans-Hab concept. Using HIDH guidelines, the team developed an internal layout that (a) minimized the transit time between related crew stations, (b) accommodated expected levels of activity at each station, (c) isolated stations when necessary for health, safety, performance, and privacy, and (d) provided a safe, efficient, and comfortable work and living environment.

Rucker, Michelle A.↗

Factors Impacting Habitable Volume Requirements for Long Duration Missions

One possible next leap in human space exploration for the National Aeronautics and Space Administration (NASA) is a mission to a near Earth asteroid (NEA). In order to achieve such an ambitious goal, a space habitat will need to accommodate a crew of four for the 380-day round trip. The Human Spaceflight Architecture Team (HAT) developed a conceptual design for such a habitat. The team identified activities that would be performed inside a long-duration, deep space habitat, and the capabilities needed to support such a mission. A list of seven functional activities/capabilities was developed: individual and group crew care, spacecraft and mission operations, subsystem equipment, logistics and resupply, and contingency operations. The volume for each activity was determined using NASA STD-3001 and the companion Human Integration Design Handbook (HIDH). Although, the sum of these volumes produced an over-sized spacecraft, the team evaluated activity frequency and duration to identify functions that could share a common volume without conflict, reducing the total volume by 24%. After adding 10% for growth, the resulting functional pressurized volume was calculated to be a minimum of 268 m3 (9,464 ft3) distributed over the functions. The work was validated through comparison to Mir, Skylab, the International Space Station (ISS), Bigelow Aerospace s proposed habitat module, and NASA s Trans-Hab concept. Using HIDH guidelines, the team developed an internal layout that (a) minimized the transit time between related crew stations, (b) accommodated expected levels of activity at each station, (c) isolated stations when necessary for health, safety, performance, and privacy, and (d) provided a safe, efficient, and comfortable work and living environment.

Simon, Matthew↗

Development of Human System Integration at NASA

Human Systems Integration seeks to design systems around the capabilities and limitations of the humans which use and interact with the system, ensuring greater efficiency of use, reduced error rates, and less rework in the design, manufacturing and operational deployment of hardware and software. One of the primary goals of HSI is to get the human factors practitioner involved early in the design process. In doing so, the aim is to reduce future budget costs and resources in redesign and training. By the preliminary design phase of a project nearly 80% of the total cost of the project is locked in. Potential design changes recommended by evaluations past this point will have little effect due to lack of funding or a huge cost in terms of resources to make changes. Three key concepts define an effective HSI program. First, systems are comprised of hardware, software, and the human, all of which operate within an environment. Too often, engineers and developers fail to consider the human capacity or requirements as part of the system. This leads to poor task allocation within the system. To promote ideal task allocation, it is critical that the human element be considered early in system development. Poor design, or designs that do not adequately consider the human component, could negatively affect physical or mental performance, as well as, social behavior. Second, successful HSI depends upon integration and collaboration of all the domains that represent acquisition efforts. Too often, these domains exist as independent disciplines due to the location of expertise within the service structure. Proper implementation of HSI through participation would help to integrate these domains and disciplines to leverage and apply their interdependencies to attain an optimal design. Via this process domain interests can be integrated to perform effective HSI through trade-offs and collaboration. This provides a common basis upon which to make knowledgeable decisions. Finally, HSI must be considered early in the requirements development phase of system design and acquisition. This will provide the best opportunity to maximize return on investment (ROI) and system performance. HSI requirements must be developed in conjunction with capability ]based requirements generation through functional. HSI requirements will drive HSI metrics and embed HSI issues within the system design. After a system is designed, implementation of HSI oversights can be very expensive. An HSI program should be included as an integral part of a total system approach to vehicle and habitat development. This would include, but not limited to, workstation design, D&C development, volumetric analysis, training, operations, and human -robotic interaction. HSI is a necessary process for Human Space Flight programs to meet the Agency Human ]System standards and thus mitigate human risks to acceptable levels. NASA has been involved in HSI planning, procedures development, process, and implementation for many years, and has been building several internal and publicly accessible products to facilitate HSI fs inclusion in the NASA Systems Engineering Lifecycle. Some of these products include: NASA STD 3001 Volumes 1 and 2, Human Integration Design Handbook, NASA HSI Implementation Plan, NASA HSI Implementation Plan Templates, NASA HSI Implementation Handbook, and a 2 ]hour short course on HSI delivered as part of the NASA Space and Life Sciences Directorate Academy. These products have been created leveraging industry best practices and lessons learned from other Federal Government agencies.

Whitmore, Mihriban↗

Enhancing the NASA Expendable Launch Vehicle Payload Safety Review Process Through Program Activities

The safety review process for NASA spacecraft flown on Expendable Launch Vehicles (ELVs) has been guided by NASA-STD 8719.8, Expendable Launch Vehicle Payload Safety Review Process Standard. The standard focused primarily on the safety approval required to begin pre-launch processing at the launch site. Subsequent changes in the contractual, technical, and operational aspects of payload processing, combined with lessons-learned supported a need for the reassessment of the standard. This has resulted in the formation of a NASA ELV Payload Safety Program. This program has been working to address the programmatic issues that will enhance and supplement the existing process, while continuing to ensure the safety of ELV payload activities.

Palo, Thomas E.↗

Estimated Probability of a Cervical Spine Injury During an ISS Mission

Introduction: The Integrated Medical Model (IMM) utilizes historical data, cohort data, and external simulations as input factors to provide estimates of crew health, resource utilization and mission outcomes. The Cervical Spine Injury Module (CSIM) is an external simulation designed to provide the IMM with parameter estimates for 1) a probability distribution function (PDF) of the incidence rate, 2) the mean incidence rate, and 3) the standard deviation associated with the mean resulting from injury/trauma of the neck. Methods: An injury mechanism based on an idealized low-velocity blunt impact to the superior posterior thorax of an ISS crewmember was used as the simulated mission environment. As a result of this impact, the cervical spine is inertially loaded from the mass of the head producing an extension-flexion motion deforming the soft tissues of the neck. A multibody biomechanical model was developed to estimate the kinematic and dynamic response of the head-neck system from a prescribed acceleration profile. Logistic regression was performed on a dataset containing AIS1 soft tissue neck injuries from rear-end automobile collisions with published Neck Injury Criterion values producing an injury transfer function (ITF). An injury event scenario (IES) was constructed such that crew 1 is moving through a primary or standard translation path transferring large volume equipment impacting stationary crew 2. The incidence rate for this IES was estimated from in-flight data and used to calculate the probability of occurrence. The uncertainty in the model input factors were estimated from representative datasets and expressed in terms of probability distributions. A Monte Carlo Method utilizing simple random sampling was employed to propagate both aleatory and epistemic uncertain factors. Scatterplots and partial correlation coefficients (PCC) were generated to determine input factor sensitivity. CSIM was developed in the SimMechanics/Simulink environment with a Monte Carlo wrapper (MATLAB) used to integrate the components of the module. Results: The probability of generating an AIS1 soft tissue neck injury from the extension/flexion motion induced by a low-velocity blunt impact to the superior posterior thorax was fitted with a lognormal PDF with mean 0.26409, standard deviation 0.11353, standard error of mean 0.00114, and 95% confidence interval [0.26186, 0.26631]. Combining the probability of an AIS1 injury with the probability of IES occurrence was fitted with a Johnson SI PDF with mean 0.02772, standard deviation 0.02012, standard error of mean 0.00020, and 95% confidence interval [0.02733, 0.02812]. The input factor sensitivity analysis in descending order was IES incidence rate, ITF regression coefficient 1, impactor initial velocity, ITF regression coefficient 2, and all others (equipment mass, crew 1 body mass, crew 2 body mass) insignificant. Verification and Validation (V&V): The IMM V&V, based upon NASA STD 7009, was implemented which included an assessment of the data sets used to build CSIM. The documentation maintained includes source code comments and a technical report. The software code and documentation is under Subversion configuration management. Kinematic validation was performed by comparing the biomechanical model output to established corridors.

Brooker, John E.↗

Software Safety Risk in Legacy Safety-Critical Computer Systems

Safety Standards contain technical and process-oriented safety requirements. Technical requirements are those such as "must work" and "must not work" functions in the system. Process-Oriented requirements are software engineering and safety management process requirements. Address the system perspective and some cover just software in the system > NASA-STD-8719.13B Software Safety Standard is the current standard of interest. NASA programs/projects will have their own set of safety requirements derived from the standard. Safety Cases: a) Documented demonstration that a system complies with the specified safety requirements. b) Evidence is gathered on the integrity of the system and put forward as an argued case. [Gardener (ed.)] c) Problems occur when trying to meet safety standards, and thus make retrospective safety cases, in legacy safety-critical computer systems.

Hill, Janice L.↗

Small Projects Rapid Integration and Test Environment (SPRITE): Application for Increasing Robustness

Marshall Space Flight Center's (MSFC) Small Projects Rapid Integration and Test Environment (SPRITE) is a Hardware-In-The-Loop (HWIL) facility that provides rapid development, integration, and testing capabilities for small projects (CubeSats, payloads, spacecraft, and launch vehicles). This facility environment focuses on efficient processes and modular design to support rapid prototyping, integration, testing and verification of small projects at an affordable cost, especially compared to larger type HWIL facilities. SPRITE (Figure 1) consists of a "core" capability or "plant" simulation platform utilizing a graphical programming environment capable of being rapidly re-configured for any potential test article's space environments, as well as a standard set of interfaces (i.e. Mil-Std 1553, Serial, Analog, Digital, etc.). SPRITE also allows this level of interface testing of components and subsystems very early in a program, thereby reducing program risk.

Rakoczy, John↗

Verification, Validation and Credibility Assessment of a Computational Model of the Advanced Resistive Exercise Device (ARED)

The Advanced Resistive Exercise Device (ARED) is the resistive exercise device used by astronauts on the International Space Station (ISS) to mitigate bone loss and muscle atrophy due to extended exposure to microgravity (micro g). The Digital Astronaut Project (DAP) has developed a multi-body dynamics model of biomechanics models for use in spaceflight exercise physiology research and operations. In an effort to advance model maturity and credibility of the ARED model, the DAP performed verification, validation and credibility (VV and C) assessment of the analyses of the model in accordance to NASA-STD-7009 'Standards for Models and Simulations'.

Werner, C. R.↗

Opposed-Flow Flame Spread in a Narrow Channel Apparatus over Thin PMMA Sheets

Flame spread tests have been conducted over polymethylmethacrylate (PMMA) samples in San Diego State University's Narrow Channel Apparatus (SDSU NCA). The Narrow Channel Apparatus (NCA) has the ability to suppress buoyant flow in horizontally spreading flames, and is currently being investigated as a possible replacement or complement to NASA's current material flammability test standard for non-metallic solids, NASA-STD-(I)-6001B Test 1. The buoyant suppression achieved with a NCA allows for tests to be conducted in a simulated microgravity atmosphere-a characteristic that Test 1 lacks since flames present in Test 1 are buoyantly driven. The SDSU NCA allows for flame spread tests to be conducted with varying opposed flow oxidizer velocities, oxygen percent by volume, and total pressure. Also, since the test sample is placed symmetrically between two confining plates so that there is a gap above and below the sample, this gap can be adjusted. This gap height adjustment allows for a compromise between heat loss from the flame to the confining boundaries and buoyancy suppression achieved by those boundaries. This article explores the effect gap height has on the flame spread rate for 75 μm thick PMMA at 1 atm pressure and 21% oxygen concentration by volume in the SDSU NCA. Flame spread results from the SDSU NCA for thin cellulose fuels have previously been compared to results from tests in actual microgravity at various test conditions with the same sample materials and were found to be in good agreement. This article also presents results from the SDSU NCA for PMMA at 1 atm pressure, opposed oxidizer velocity ranging from 3 to 35 cm/s, oxygen concentration by volume at 21%, 30 %, and 50% and fuel thicknesses of 50 and 75 μm. These results are compared to results obtained in actual microgravity for PMMA obtained at the 4.5s drop tower of MGLAB in Gifu, Japan, and the 5.2s drop tower at NASA's Zero-Gravity Research Facility in Cleveland, OH. This comparison confirms that at 1 atm pressure, the SDSU NCA successfully simulates microgravity for not only thin cellulose fuels, but also for thin PMMA sheets as well. This further supports the idea that the NCA is a viable option to complement or replace NASA's Test 1 for material flammability testing. Tests with thick fuels will be conducted in the future to further characterize the SDSU NCA.

flame spread↗

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George↗