Search NASA⌕ Search

SEARCH · Search NASA

Results for “Program verification”

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 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS2012

A Change Impact Analysis to Characterize Evolving Program Behaviors

Change impact analysis techniques estimate the potential effects of changes made to software. Directed Incremental Symbolic Execution (DiSE) is an intraprocedural technique for characterizing the impact of software changes on program behaviors. DiSE first estimates the impact of the changes on the source code using program slicing techniques, and then uses the impact sets to guide symbolic execution to generate path conditions that characterize impacted program behaviors. DiSE, however, cannot reason about the flow of impact between methods and will fail to generate path conditions for certain impacted program behaviors. In this work, we present iDiSE, an extension to DiSE that performs an interprocedural analysis. iDiSE combines static and dynamic calling context information to efficiently generate impacted program behaviors across calling contexts. Information about impacted program behaviors is useful for testing, verification, and debugging of evolving programs. We present a case-study of our implementation of the iDiSE algorithm to demonstrate its efficiency at computing impacted program behaviors. Traditional notions of coverage are insufficient for characterizing the testing efforts used to validate evolving program behaviors because they do not take into account the impact of changes to the code. In this work we present novel definitions of impacted coverage metrics that are useful for evaluating the testing effort required to test evolving programs. We then describe how the notions of impacted coverage can be used to configure techniques such as DiSE and iDiSE in order to support regression testing related tasks. We also discuss how DiSE and iDiSE can be configured for debugging finding the root cause of errors introduced by changes made to the code. In our empirical evaluation we demonstrate that the configurations of DiSE and iDiSE can be used to support various software maintenance tasks

Rungta, Neha Shyam↗
NASA NTRS1984

Assessment of Galileo modal test results for mathematical model verification

The modal test program for the Galileo Spacecraft was completed at the Jet Propulsion Laboratory in the summer of 1983. The multiple sine dwell method was used for the baseline test. The Galileo Spacecraft is a rather complex 2433 kg structure made of a central core on which seven major appendages representing 30 percent of the total mass are attached, resulting in a high modal density structure. The test revealed a strong nonlinearity in several major modes. This nonlinearity discovered in the course of the test necessitated running additional tests at the unusually high response levels of up to about 21 g. The high levels of response were required to obtain a model verification valid at the level of loads for which the spacecraft was designed. Because of the high modal density and the nonlinearity, correlation between the dynamic mathematical model and the test results becomes a difficult task. Significant changes in the pre-test analytical model are necessary to establish confidence in the upgraded analytical model used for the final load verification. This verification, using a test verified model, is required by NASA to fly the Galileo Spacecraft on the Shuttle/Centaur launch vehicle in 1986.

Trubert, M.↗
NASA NTRS1975

Automatic documentation system extension to multi-manufacturers' computers and to measure, improve, and predict software reliability

The DOMONIC system has been modified to run on the Univac 1108 and the CDC 6600 as well as the IBM 370 computer system. The DOMONIC monitor system has been implemented to gather data which can be used to optimize the DOMONIC system and to predict the reliability of software developed using DOMONIC. The areas of quality metrics, error characterization, program complexity, program testing, validation and verification are analyzed. A software reliability model for estimating program completion levels and one on which to base system acceptance have been developed. The DAVE system which performs flow analysis and error detection has been converted from the University of Colorado CDC 6400/6600 computer to the IBM 360/370 computer system for use with the DOMONIC system.

Simmons, D. B.↗
NASA NTRS1974

Utilization survey of prototype structural test article

A survey was conducted of six aerospace companies and two NASA agencies to determine how prototype structural test articles are used in flight operations. The prototype structures are airframes and similar devices which are used for testing and generally are not flown. The survey indicated the following: (1) prototype test articles are not being discarded after development testing is complete, but are used for other purposes, (2) only two cases of prototypes being refurbished and flown were identified, (3) protective devices and inspection techniques are available to prevent or minimize test article damage, (4) substitute programs from design verification are availabel in lieu of using prototype structural articles, and (5) there is a trend away from dedicated test articles. Four options based on these study results were identified to reduce test and hardware costs without compromising reliability of the flight program.

Baber, S.↗
NASA NTRS1976

Computer program for design and performance analysis of navigation-aid power systems

The paper examines the requirements, design rationale, operation, and verification of a computer program designated as design synthesis/performance analysis (DSPA) computer program, which is capable of performing all the calculations necessary to understand the overall characteristics of solar array/battery power systems for navigation-aid applications. Despite the uncertainties in the erratic solar array degradation data and the potential impact on actual battery behavior, verification of the DSPA is considered successful. The program is shown to have the capability of simulating the performance of solar array/battery navigation-aid power systems. It can also be used to synthesize power system designs and provide essential design and cost data.

Weiner, H.↗
NASA NTRS1994

A distributed computing model for telemetry data processing

We present a new approach to distributing processed telemetry data among spacecraft flight controllers within the control centers at NASA's Johnson Space Center. This approach facilitates the development of application programs which integrate spacecraft-telemetered data and ground-based synthesized data, then distributes this information to flight controllers for analysis and decision-making. The new approach combines various distributed computing models into one hybrid distributed computing model. The model employs both client-server and peer-to-peer distributed computing models cooperating to provide users with information throughout a diverse operations environment. Specifically, it provides an attractive foundation upon which we are building critical real-time monitoring and control applications, while simultaneously lending itself to peripheral applications in playback operations, mission preparations, flight controller training, and program development and verification. We have realized the hybrid distributed computing model through an information sharing protocol. We shall describe the motivations that inspired us to create this protocol, along with a brief conceptual description of the distributed computing models it employs. We describe the protocol design in more detail, discussing many of the program design considerations and techniques we have adopted. Finally, we describe how this model is especially suitable for supporting the implementation of distributed expert system applications.

Barry, Matthew R.↗
NASA NTRS2003

Validation of ADAR System 5500 Digital Imagery: Delivery Task Order #1, Task Request #857 - Brookings, SD

This work was performed under NASA's Verification and Validation Program as an independent check of data supplied by Positive Systems, Inc. through the Earth Science Enterprise's Scientific Data Purchase (SDP) Program. This document serves as the basis for reporting results associated with validation of multispectral imagery according to the specifications of contract NAS 13-98049. The validation was performed under the Positive Systems Imaging System Validation Work Instruction CRSP-WI-28: Spectral registration, spatial resolution, endlaps, sidelaps, and image quality were evaluated. The validation was proceded by Shipment Verification, as described in the Work Instruction CRSP-WI-22: Every image was passed through an automatic ingest verification and thumbnail review process to identify omissions, problems with media integrity, and gross errors in data quality. Validation of metadata files is not within the scope of this report, but it was performed separately.

Blonski, Slawomir↗
NASA NTRS2014

Time and Frequency-Domain Cross-Verification of SLS 6DOF Trajectory Simulations

The SLS GNC team and its partners have developed several time- and frequency-based simulations for development and analysis of the proposed SLS launch vehicle. The simulations differ in fidelity and some have unique functionality that allows them to perform specific analyses. Some examples of the purposes of the various models are: trajectory simulation, multi-body separation, Monte Carlo, hardware in the loop, loads, and frequency domain stability analyses. While no two simulations are identical, many of the models are essentially six degree-of-freedom (6DOF) representations of the SLS plant dynamics, hardware implementation, and flight software. Thus at a high level all of those models should be in agreement. Comparison of outputs from several SLS trajectory and stability analysis tools are ongoing as part of the program's current verification effort. The purpose of these comparisons is to highlight modeling and analysis differences, verify simulation data sources, identify inconsistencies and minor errors, and ultimately to verify output data as being a good representation of the vehicle and subsystem dynamics. This paper will show selected verification work in both the time and frequency domain from the current design analysis cycle of the SLS for several of the design and analysis simulations. In the time domain, the tools that will be compared are MAVERIC, CLVTOPS, SAVANT, STARS, ARTEMIS, and POST 2. For the frequency domain analysis, the tools to be compared are FRACTAL, SAVANT, and STARS. The paper will include discussion of these tools including their capabilities, configurations, and the uses to which they are put in the SLS program. Determination of the criteria by which the simulations are compared (matching criteria) requires thoughtful consideration, and there are several pitfalls that may occur that can severely punish a simulation if not considered carefully. The paper will discuss these considerations and will present a framework for responding to these issues when they arise. For example, small event timing differences can lead to large differences in mass properties if the criteria are to measure those properties at the same time, or large differences in altitude if the criteria are to measure those properties when the simulation experiences a staging event. Similarly, a tiny difference in phase can lead to large gain margin differences for frequency-domain comparisons of gain margins.

VanZwieten, Tannen↗
NASA NTRS2017

Time and Frequency-Domain Cross-Verification of SLS 6DOF Trajectory Simulations

The Space Launch System (SLS) Guidance, Navigation, and Control (GNC) team and its partners have developed several time- and frequency-based simulations for development and analysis of the proposed SLS launch vehicle. The simulations differ in fidelity and some have unique functionality that allows them to perform specific analyses. Some examples of the purposes of the various models are: trajectory simulation, multi-body separation, Monte Carlo, hardware in the loop, loads, and frequency domain stability analyses. While no two simulations are identical, many of the models are essentially six degree-of-freedom (6DOF) representations of the SLS plant dynamics, hardware implementation, and flight software. Thus at a high level all of those models should be in agreement. Comparison of outputs from several SLS trajectory and stability analysis tools are ongoing as part of the program's current verification effort. The purpose of these comparisons is to highlight modeling and analysis differences, verify simulation data sources, identify inconsistencies and minor errors, and ultimately to verify output data as being a good representation of the vehicle and subsystem dynamics. This paper will show selected verification work in both the time and frequency domain from the current design analysis cycle of the SLS for several of the design and analysis simulations. In the time domain, the tools that will be compared are MAVERIC, CLVTOPS, SAVANT, STARS, ARTEMIS, and POST 2. For the frequency domain analysis, the tools to be compared are FRACTAL, SAVANT, and STARS. The paper will include discussion of these tools including their capabilities, configurations, and the uses to which they are put in the SLS program. Determination of the criteria by which the simulations are compared (matching criteria) requires thoughtful consideration, and there are several pitfalls that may occur that can severely punish a simulation if not considered carefully. The paper will discuss these considerations and will present a framework for responding to these issues when they arise. For example, small event timing differences can lead to large differences in mass properties if the criteria are to measure those properties at the same time, or large differences in altitude if the criteria are to measure those properties when the simulation experiences a staging event. Similarly, a tiny difference in phase can lead to large gain margin differences for frequency-domain comparisons of gain margins.

Johnson, Matthew↗
NASA NTRS2003

Enhancing the Human Factors Engineering Role in an Austere Fiscal Environment

An austere fiscal environment in the aerospace community creates pressures to reduce program costs, often minimizing or sometimes even deleting the human interface requirements from the design process. With an assumption that the flight crew can recover real time from a poorly human factored space vehicle design, the classical crew interface requirements have been either not included in the design or not properly funded, though carried as requirements. Cost cuts have also affected quality of retained human factors engineering personnel. In response to this concern, planning is ongoing to correct the acting issues. Herein are techniques for ensuring that human interface requirements are integrated into a flight design, from proposal through verification and launch activation. This includes human factors requirements refinement and consolidation across flight programs; keyword phrases in the proposals; closer ties with systems engineering and other classical disciplines; early planning for crew-interface verification; and an Agency integrated human factors verification program, under the One NASA theme. Importance is given to communication within the aerospace human factors discipline, and utilizing the strengths of all government, industry, and academic human factors organizations in an unified research and engineering approach. A list of recommendations and concerns are provided in closing.

Stokes, Jack W.↗
NASA NTRS1989

Progress toward the development of an airfoil icing analysis capability

The NASA-Lewis aircraft icing analysis program is composed of three major sub-programs. These sub-programs are ice accretion simulation, performance degradation evaluation, and ice protection system evaluation. These topics cover all areas of concern related to the simulation of aircraft icing and its consequences. The motivation for these activities is twofold, reduction of time and effort required in experimental programs and the ability to provide reliable information for aircraft certification in icing, over the complete range of environmental conditions. In addition to the analytical activities associated with development of these codes, several experimental programs are underway to provide verification information for existing codes. These experimental programs are also used to investigate the physical processes associated with ice accretion and removal for improvement of present analytical models. The NASA-Lewis icing analysis program is thus striving to provide a full range of analytical tools necessary for evaluation of the consequences of icing and of ice protection systems.

Potapczuk, Mark G.↗
NASA NTRS1998

Thermal Management Design for the X-33 Lifting Body

The X-33 Advantage Technology Demonstrator offers a rare and exciting opportunity in Thermal Protection System development. The experimental program incorporates the latest design innovation in re-useable, low life cycle cost, and highly dependable Thermal Protection materials and constructions into both ground based and flight test vehicle validations. The unique attributes of the X-33 demonstrator for design application validation for the full scale Reusable Launch Vehicle, (RLV), are represented by both the configuration of the stand-off aeroshell, and the extreme exposures of sub-orbital hypersonic re-entry simulation. There are several challenges of producing a sub-orbital prototype demonstrator of Single Stage to Orbit/Reusable Launch Vehicle (SSTO/RLV) operations. An aggressive schedule with budgetary constraints precludes the opportunity for an extensive verification and qualification program of vehicle flight hardware. However, taking advantage of off the shelf components with proven technologies reduces some of the requirements for additional testing. The effects of scale on thermal heating rates must also be taken into account during trajectory design and analysis. Described in this document are the unique Thermal Protection System (TPS) design opportunities that are available with the lifting body configuration of the X-33. The two principal objectives for the TPS are to shield the primary airframe structure from excessive thermal loads and to provide an aerodynamic mold line surface. With the relatively benign aeroheating capability of the lifting body, an integrated stand-off aeroshell design with minimal weight and reduced procurement and operational costs is allowed. This paper summarizes the design objectives of the X-33 TPS, the flight test requirements driven configuration, and design benefits. Comparisons are made of the X-33 flight profiles and Space Shuttle Orbiter, and lifting body Reusable Launch Vehicle aerothermal environments. The X-33 TPS is based on a design to cost configuration concept. Only RLV critical technologies are verified to conform to cost and schedule restrictions. The one-off prototype vehicle configuration has evolved to minimize the tooling costs by reducing the number of unique components. Low cost approaches such as a composite/blanket leeward aeroshell and the use of Shuttle technology are implemented where applicable. The success of the X-33 will overcome the ballistic re-entry TPS mindset. The X-33 TPS is tailored to an aircraft type mission while maintaining sufficient operational margins. The flight test program for the X-33 will demonstrate that TPS for the RLV is not simply a surface insulation but rather an integrated aeroshell system.

Bouslog, S.↗
NASA NTRS1979

Drive program documentation

The program description and user's guide for the Downlist Requirement Integrated Verification and Evaluation (DRIVE) program is provided. The program is used to compare existing telemetry downlist files with updated downlist requirements.

Graham, S.↗
NASA NTRSDate not supplied

Integrating Human System Information with the Systems Platform for Aggregating and Relating Capabilities (SPARC)

Within Human Health and Performance, there exists a wealth of human system information that’s used a regular basis in support of NASA human exploration objectives, but the challenge is that all of this information was stored in multiple different locations and organized for specific uses, limiting its effectiveness and straining communication across multiple groups. To address this challenge, our project, the Systems Platform for Aggregating and Relating Capabilities (SPARC) was tasked with developing a new NASA internal web application that aggregates and relates multiple programs’ human system products, such as technical standards, program requirements and verifications, human system risks, research and evidence, and exploration capabilities, into one centralized platform that addresses the needs of human health and performance from multiple different perspectives. Using agile development methodologies, user-experience (UX) driven design principles, data visualization, and a strong emphasis on continuous improvement though consistent stakeholder engagement, the SPARC project released a beta version in less than 4 months, broadly launched version 1.0.0 Agency-wide three months after the beta, and has over 180 users in the first year of development. Our second year of development will see us moving from our initial capabilities to increasingly robust and complex integrations and visualizations, including Directed Acyclical Graphs (DAGs), natural language processing (NLP) for dynamic generation of relationships between the sources of truth, and an expansion into hierarchical levels of system design in support of the human exploration programs.

Data science↗
NASA NTRS1981

The evaluation of OSTA's APT and ASVT programs

The results of an evaluation of NASA's Applications Pilot Test (APT) and Applications System Verification and Transfer (AVST) Programs are presented. These programs sponsor cooperative projects between NASA and potential users of remote sensing (primarily LANDSAT) technology from federal and state government and the private sector. Fifteen specific projects, seven APT's and eight ASVT's, are examined as mechanisms for technology development, test, and transfer by comparing their results against stated objectives. Interviews with project managers from NASA field centers and user agency representatives provide the basis for project evaluation from NASA and user perspectives.

Source record↗
NASA NTRS2007

Model Checker for Java Programs

Java Pathfinder (JPF) is a verification and testing environment for Java that integrates model checking, program analysis, and testing. JPF consists of a custom-made Java Virtual Machine (JVM) that interprets bytecode, combined with a search interface to allow the complete behavior of a Java program to be analyzed, including interleavings of concurrent programs. JPF is implemented in Java, and its architecture is highly modular to support rapid prototyping of new features. JPF is an explicit-state model checker, because it enumerates all visited states and, therefore, suffers from the state-explosion problem inherent in analyzing large programs. It is suited to analyzing programs less than 10kLOC, but has been successfully applied to finding errors in concurrent programs up to 100kLOC. When an error is found, a trace from the initial state to the error is produced to guide the debugging. JPF works at the bytecode level, meaning that all of Java can be model-checked. By default, the software checks for all runtime errors (uncaught exceptions), assertions violations (supports Java s assert), and deadlocks. JPF uses garbage collection and symmetry reductions of the heap during model checking to reduce state-explosion, as well as dynamic partial order reductions to lower the number of interleavings analyzed. JPF is capable of symbolic execution of Java programs, including symbolic execution of complex data such as linked lists and trees. JPF is extensible as it allows for the creation of listeners that can subscribe to events during searches. The creation of dedicated code to be executed in place of regular classes is supported and allows users to easily handle native calls and to improve the efficiency of the analysis.

Visser, Willem↗
NASA NTRS1987

Approaches to the verification of rule-based expert systems

Expert systems are a highly useful spinoff of artificial intelligence research. One major stumbling block to extended use of expert systems is the lack of well-defined verification and validation (V and V) methodologies. Since expert systems are computer programs, the definitions of verification and validation from conventional software are applicable. The primary difficulty with expert systems is the use of development methodologies which do not support effective V and V. If proper techniques are used to document requirements, V and V of rule-based expert systems is possible, and may be easier than with conventional code. For NASA applications, the flight technique panels used in previous programs should provide an excellent way to verify the rules used in expert systems. There are, however, some inherent differences in expert systems that will affect V and V considerations.

Culbert, Chris↗