Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software Test Tool”

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 397 records · Page 22
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

Versatile Controller For CCD's

General-purpose controller for charge-coupled device (CCD) programmed to accommodate variety of CCD designs. In operation of controller, software used to specify CCD-clock waveforms, available in great diversity. Includes timing-signal generator controlled by microcomputer. Flexibility and speed makes it versatile tool for laboratory testing and for variety of applications. Controller operates existing CCD's and able to operate CCD's expected to be developed in foreseeable future.

Novello, J.↗
NASA NTRS1999

Reinventing The Design Process: Teams and Models

The future of space mission designing will be dramatically different from the past. Formerly, performance-driven paradigms emphasized data return with cost and schedule being secondary issues. Now and in the future, costs are capped and schedules fixed-these two variables must be treated as independent in the design process. Accordingly, JPL has redesigned its design process. At the conceptual level, design times have been reduced by properly defining the required design depth, improving the linkages between tools, and managing team dynamics. In implementation-phase design, system requirements will be held in crosscutting models, linked to subsystem design tools through a central database that captures the design and supplies needed configuration management and control. Mission goals will then be captured in timelining software that drives the models, testing their capability to execute the goals. Metrics are used to measure and control both processes and to ensure that design parameters converge through the design process within schedule constraints. This methodology manages margins controlled by acceptable risk levels. Thus, teams can evolve risk tolerance (and cost) as they would any engineering parameter. This new approach allows more design freedom for a longer time, which tends to encourage revolutionary and unexpected improvements in design.

Wall, Stephen D.↗
NASA NTRS2010

Modeling and Performance Considerations for Automated Fault Isolation in Complex Systems

The purpose of this paper is to document the modeling considerations and performance metrics that were examined in the development of a large-scale Fault Detection, Isolation and Recovery (FDIR) system. The FDIR system is envisioned to perform health management functions for both a launch vehicle and the ground systems that support the vehicle during checkout and launch countdown by using suite of complimentary software tools that alert operators to anomalies and failures in real-time. The FDIR team members developed a set of operational requirements for the models that would be used for fault isolation and worked closely with the vendor of the software tools selected for fault isolation to ensure that the software was able to meet the requirements. Once the requirements were established, example models of sufficient complexity were used to test the performance of the software. The results of the performance testing demonstrated the need for enhancements to the software in order to meet the demands of the full-scale ground and vehicle FDIR system. The paper highlights the importance of the development of operational requirements and preliminary performance testing as a strategy for identifying deficiencies in highly scalable systems and rectifying those deficiencies before they imperil the success of the project

Ferrell, Bob↗
NASA NTRS1993

Formal Functional Test Designs with a Test Representation Language

This article discusses the application of the Category-Partition Method to the test design phase. The method provides a formal framework for reducing the total number of possible test cases to a minimum logical subset for effective testing. An automatic tool and a formal language have been developed to implement the method and produce the specification of test cases

software↗
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 NTRS2000

Formal Analysis of the Remote Agent Before and After Flight

This paper describes two separate efforts that used the SPIN model checker to verify deep space autonomy flight software. The first effort occurred at the beginning of a spiral development process and found five concurrency errors early in the design cycle that the developers acknowledge would not have been found through testing. This effort required a substantial manual modeling effort involving both abstraction and translation from the prototype LISP code to the PROMELA language used by SPIN. This experience and others led to research to address the gap between formal method tools and the development cycle used by software developers. The Java PathFinder tool which directly translates from Java to PROMELA was developed as part of this research, as well as automatic abstraction tools. In 1999 the flight software flew on a space mission, and a deadlock occurred in a sibling subsystem to the one which was the focus of the first verification effort. A second quick-response "cleanroom" verification effort found the concurrency error in a short amount of time. The error was isomorphic to one of the concurrency errors found during the first verification effort. The paper demonstrates that formal methods tools can find concurrency errors that indeed lead to loss of spacecraft functions, even for the complex software required for autonomy. Second, it describes progress in automatic translation and abstraction that eventually will enable formal methods tools to be inserted directly into the aerospace software development cycle.

Havelund, Klaus↗
NASA NTRS2004

Completing the Loop: Linking Software Features to Failures

The PITS Modification Script has been under development. Testing, debugging, and optimization of the script are in progress. MSIS has begun population of ODC values from historic issue data. Design of the Linker Tool is also continuing. The quarterly review meeting held on December 17,2003, allowed for a venue to discuss installing the PITS Modification Script to the production version of PITS upon completion and incorporation of ODC into an IV&V project s issue tracking process. Feedback from NASA was positive although any global implementation will likely be timed to coordinate with other activities such as establishment of an IV&V Work Breakdown Structure.

Source record↗
NASA NTRSDate not supplied

Network Emulation Testbed Capabilities for Prototyping Space DTN Software and Protocols

This paper delves into network emulation tools essential for evaluating and designing Delay Tolerant Networking (DTN) protocols in space and satellite networking. It surveys and assesses the capability of current testbeds to create realistic test environments crucial for developing and evaluating DTN protocols. Specifically, this study provides a comprehensive overview of key DTN protocol stacks and related network emulation platforms and a detailed exploration of NASA’s research facilities. Finally, the paper underscores the fundamental emulation capabilities and the importance of a standardized framework for scenario creation, highlighting its vital role in evaluating and advancing future emulation platforms for space DTN.

Network Emulation and Simulation↗
NASA NTRS1994

Recent Developments in Grid Generation and Force Integration Technology for Overset Grids

Recent developments in algorithms and software tools for generating overset grids for complex configurations are described. These include the overset surface grid generation code SURGRD and version 2.0 of the hyperbolic volume grid generation code HYPGEN. The SURGRD code is in beta test mode where the new features include the capability to march over a collection of panel networks, a variety of ways to control the side boundaries and the marching step sizes and distance, a more robust projection scheme and an interpolation option. New features in version 2.0 of HYPGEN include a wider range of boundary condition types. The code also allows the user to specify different marching step sizes and distance for each point on the surface grid. A scheme that takes into account of the overlapped zones on the body surface for the purpose of forces and moments computation is also briefly described, The process involves the following two software modules: MIXSUR - a composite grid generation module to produce a collection of quadrilaterals and triangles on which pressure and viscous stresses are to be integrated, and OVERINT - a forces and moments integration module.

Chan, William M.↗
NASA NTRSDate not supplied

Structural Sizing of a Tow-Steered Truss-Braced Wing Box Test Article

Tailoring of composite laminates is traditionally performed by changing the orientation of straight fibers in one or more plies. Modern automated fiber placement machines facilitate placement of bundles of curved fibers (tows) in a process called tow-steering, but additional variables must be used to define the shapes of tow-steered fiber paths. In this paper, the design of a tow-steered truss-braced wing test article called the Structural Wing Experiment Evaluating Truss-bracing 15-ft concept (SWEET-15) is discussed. The SWEET-15 test article is scaled to 18.6% of the span length and chord width of a full-scale vehicle. The test article is designed to withstand +2.5-g (positive limit) and -1.0-g (negative limit) maneuvering loads with a factor of safety of 1.5 under strength and buckling constraints. Design studies were performed using commercial finite element analysis and optimization software in conjunction with a tow-steering modeling tool called ATSCOOL (Automated Tool for Steered COmposite Optimizable Laminates) developed at NASA Langley Research center. A 6.4% weight reduction in the upper cover panels was achieved using a tow-steered layup configuration.

Composites↗
NASA NTRS1977

Navigation for IUS deployment. TDRSS navigation accuracy in support of IUS deployment, phase 1

The navigation accuracy for tracking the orbiter prior to interim upper stage (IUS) deployment using the tracking data relay satellite system (TDRSS) was studied. The orbiter navigation accuracy for both one and two TDRSS satellites, for short and long data arcs, and for Doppler-only and Doppler-plus range solutions was examined. All test cases were run with the orbiter in a 150-n. mi. circular orbit, 28.5 degree inclination, at the time interval from the completion of the orbital maneuvering system (OMS)-2 maneuver to OMS-2 plus 2 hours (approximate time for IUS deployment). The data used were simulated by the simulation navigation (SIMNAV) program. The software tool used to process the TDRS data was the Shuttle Navigation Analysis Program (SNAP), a Kalman filter tool used to solve for the orbiter position and velocity. Results summarize the expected navigation accuracy using the TDRS system. It was concluded that: (1) data from both TDRS satellites were essential for accurate navigation results: (2) range data were essential for the short arc test case but were not needed for the long arc test case; and (3) with Doppler and range data from both TDRS satellites, the results converged to a reasonable solution after 5 to 10 minutes of data.

Wylie, A. D.↗
NASA NTRS2011

NASA Tech Briefs, November 2011

The topics include: 1) Flight Test Results from the Rake Airflow Gage Experiment on the F-15B; 2) Telemetry and Science Data Software System; 3) CropEx Web-Based Agricultural Monitoring and Decision Support; 4) High-Performance Data Analysis Tools for Sun-Earth Connection Missions; 5) Experiment in Onboard Synthetic Aperture Radar Data Processing; 6) Microfabrication of a High-Throughput Nanochannel Delivery/Filtration System; 7) Improved Design and Fabrication of Hydrated-Salt Pills; 8) Monolithic Flexure Pre-Stressed Ultrasonic Horns; 9) Cryogenic Quenching Process for Electronic Part Screening; 10) Broadband Via-Less Microwave Crossover Using Microstrip-CPW Transitions; 11) Wheel-Based Ice Sensors for Road Vehicles; 12) G-DYN Multibody Dynamics Engine; 13) Multibody Simulation Software Testbed for Small-Body Exploration and Sampling; 14) Propulsive Reaction Control System Model; 15) Licklider Transmission Protocol Implementation; 16) Core Recursive Hierarchical Image Segmentation; 17) Two-Stage Centrifugal Fan; 18) Combined Structural and Trajectory Control of Variable-Geometry Planetary Entry Systems; 19) Pressure Regulator With Internal Ejector Circulation Pump, Flow and Pressure Measurement Porting, and Fuel Cell System Integration Options; 20) Temperature-Sensitive Coating Sensor Based on Hematite; 21) Standardization of a Volumetric Displacement Measurement for Two-Body Abrasion Scratch Test Data Analysis; 22) Detection of Carbon Monoxide Using Polymer-Carbon Composite Films; 23) Substituted Quaternary Ammonium Salts Improve Low-Temperature Performance of Double-Layer Capacitors; 24) Sustainably Sourced, Thermally Resistant, Radiation Hard Biopolymer; 25) Integrated Lens Antennas for Multi-Pixel Receivers; 26) 180-GHz Interferometric Imager; 27) Maturation of Structural Health Management Systems for Solid Rocket Motors; 28) Validating Phasing and Geometry of Large Focal Plane Arrays; 29) Transverse Pupil Shifts for Adaptive Optics Non-Common Path Calibration; 30) Qualification of Fiber Optic Cables for Martian Extreme Temperature Environments; 31) Solid-State Spectral Light Source System; 32) Multiple-Event, Single-Photon Counting Imaging Sensor; 33) Surface Modeling to Support Small-Body Spacecraft Exploration and Proximity Operations; and 34) Achieving Exact and Constant Turnaround Ratio in a DDS-Based Coherent Transponder.

Source record↗
NASA NTRS1981

Using CAD/CAM to improve productivity - The IPAD approach

Progress in designing and implementing CAD/CAM systems as a result of the NASA Integrated Programs for Aerospace-Vehicle Design is discussed. Essential software packages have been identified as executive, data management, general user, and geometry and graphics software. Data communication, as a means to integrate data over a network of computers of different vendors, provides data management with the capability of meeting design and manufacturing requirements of the vendors. Geometry software is dependent on developmental success with solid geometry software, which is necessary for continual measurements of, for example, a block of metal while it is being machined. Applications in the aerospace industry, such as for design, analysis, tooling, testing, quality control, etc., are outlined.

Fulton, R. E.↗
NASA NTRS1993

Formal functional test designs with a test representation language

The application of the category-partition method to the test design phase of hardware, software, or system test development is discussed. The method provides a formal framework for reducing the total number of possible test cases to a minimum logical subset for effective testing. An automatic tool and a formal language were developed to implement the method and produce the specification of test cases.

Hops, J. M.↗
NASA NTRS1995

The development of the Final Approach Spacing Tool (FAST): A cooperative controller-engineer design approach

Historically, the development of advanced automation for air traffic control in the United States has excluded the input of the air traffic controller until the need of the development process. In contrast, the development of the Final Approach Spacing Tool (FAST), for the terminal area controller, has incorporated the end-user in early, iterative testing. This paper describes a cooperative between the controller and the developer to create a tool which incorporates the complexity of the air traffic controller's job. This approach to software development has enhanced the usability of FAST and has helped smooth the introduction of FAST into the operational environment.

Lee, Katharine K.↗
NASA NTRS2005

Failure Assessment

Three questions to which software developers want accurate, precise answers are "How can the software system fail?", "mat bad things will happen if the software fails?t', and "How many failures will the software experience?". Numerous techniques have been devised to answer these questions; three of the best known are: 1) Software Fault Tree Analysis (SFTA) 2) Software Failure Modes, Effects, and Criticality Analysis (SFMECA 3) Software Fault/Failure Modeling. SFTA and SFMECA have been successfully used to analyze the flight software for a number of robotic planetary exploration missions, including Galileo, Cassini, and Deep Space 1. Given the increasing interest in reusing software components from mission to mission, one of us has developed techniques for reusing the corresponding portions of the SFTA and SFMECA, reducing the effort required to conduct these analyses. SFTA has also been shown to be effective in analyzing the security aspects of software systems; intrusion mechanisms and effects can easily be modeled using these techniques. The Bi- Directional Safety Analysis (BDSA) method combines a forward search (similar to SFMECA) from potential failure modes to their effects, with a backward search (similar to SFTA) from feasible hazards to the contributing causes of each hazard. BDSA offers an efficient way to identify latent failures. Recent work has extended BDSA to product-line applications such as flight-instrumentation displays and developed tool support for the reuse of the failure-analysis artifacts within a product line. BDSA has also been streamlined to support those projects having tight cost and/or schedule constraints for their failure analysis efforts. We discuss lessons learned from practice, describe available tools, and identi@ some future directions for the topic. A substantial amount of research has been devoted to estimating the number of failures that a software system will experience during test and operations, as well as the number of faults that have been inserted into that system during its development. One of us has found that the amount of structural change to a system during its development is strongly related to the number of faults inserted into it. Using techniques requiring no additional effort on the part of the development organization, the required measurements of structural evolution can be easily obtained from a development effort's configuration management system and readily transformed into an estimate of fault content. So far, structure-fault relationships have been identified for source code; current work seeks to examine artifacts available earlier in the lifecycle to determine if similar relationships between structure and fault content can be found. In particular, relationships between requirements change requests and the number of faults inserted into the implemented system would provide a significant improvement in our ability to control software quality during the early development phases.

fault tree↗
NASA NTRSDate not supplied

Development and Demonstration of a Digital NDE Pipeline for Streamlined Analysis of Ultrasonic Data

Currently when nondestructive evaluation (NDE) is performed on composite structures, the results, although recorded digitally are often manually interpreted and indicated (drawn) on the part being inspected by hand. Following this, a determination must be made on how to disposition that part. This decision could be based on engineering guidelines and best practices, rule-of-thumb, expert opinion or finite-element analysis of the part with some approximate representation of the damage. In order to streamline this process for ultrasonic inspection an effort was undertaken as part of NASA Advanced Composites Project to develop the Digital NDE Pipeline. The Digital NDE Pipeline is an integrated tool suite and associated framework that streamlines the inspection and defect disposition process through model-assisted inspection optimization, automated defect analysis of NDE data, and mapping of NDE data into finite element analysis software. This paper will provide an overview of the Digital NDE Pipeline and provide details of the individual tools developed along with the results of applying these tools to a demonstration test case.

Composites↗
NASA NTRS1991

Rule groupings: An approach towards verification of expert systems

Knowledge-based expert systems are playing an increasingly important role in NASA space and aircraft systems. However, many of NASA's software applications are life- or mission-critical and knowledge-based systems do not lend themselves to the traditional verification and validation techniques for highly reliable software. Rule-based systems lack the control abstractions found in procedural languages. Hence, it is difficult to verify or maintain such systems. Our goal is to automatically structure a rule-based system into a set of rule-groups having a well-defined interface to other rule-groups. Once a rule base is decomposed into such 'firewalled' units, studying the interactions between rules would become more tractable. Verification-aid tools can then be developed to test the behavior of each such rule-group. Furthermore, the interactions between rule-groups can be studied in a manner similar to integration testing. Such efforts will go a long way towards increasing our confidence in the expert-system software. Our research efforts address the feasibility of automating the identification of rule groups, in order to decompose the rule base into a number of meaningful units.

Mehrotra, Mala↗