Search NASA⌕ Search

SEARCH · Search NASA

Results for “software 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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
DOE OSTI2022

M-Star® Software Test and Verification for Impeller Mixing in a Tank

Before a sample of the Slurry Mix Evaporator (SME) can be taken, the SME product sampling procedure requires that the agitator power be stable between 20 and 30 kW for at least one hour. The SME transfer to Melter Feed Tank (MFT) procedure also requires the SME agitator power be stabilized between 20 and 30 kW prior to transfer. These requirements are specified to ensure samples are homogeneous, as discussed in the Waste Form Qualification Report. During SME Batch 804, the agitator power dropped to 19 kW and struggled to achieve and maintain 20 kW. It was later discovered that the cause of the power drop was due to one of the bottom blades of the agitator breaking off. Both the sample and the transfer occurred without the power stabilizing between 20 and 30 kW. Therefore, the quality of SME Batch 804 is indeterminate, and homogeneity was questionable.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS1976

A methodology for producing reliable software, volume 1

An investigation into the areas having an impact on producing reliable software including automated verification tools, software modeling, testing techniques, structured programming, and management techniques is presented. This final report contains the results of this investigation, analysis of each technique, and the definition of a methodology for producing reliable software.

Stucki, L. G.↗
NASA NTRS1982

Investigating tectonic and bathymetric features of the Indian Ocean using MAGSAT magnetic anomaly data

MAGSAT Investigator-B tapes were preprocessed by (1) removing all data points with obvious erroneous values and location errors; (2) removing smaller spikes (typically 15 nT or more), and deleting data tracks with fewer than 20 points; and (3) removing a linear trend from each track. The remaining data were recorded on tape for use by the equivalent source mapping (ESMAP) program which uses a least squares algorithm to fit the magnetization parameter of the grid of equivalent source dipoles in the crust to satellite data acquired at different times and locations. ESMAP was implemented on the TASC computing system and modified to read preprocessed MAGSAT tapes and interface with TASC plotting software. Some verification of the software was accomplished. Gridded 1-degree mean values of gravity anomaly and sea surface undulation computed from SEASAT radar altimeter were obtained and brought on line.

Lazarewicz, A. R.↗
NASA NTRS1987

A NASA initiative: Software engineering for reliable complex systems

The objective is the development of methods, technology, and skills that will enable NASA to cost-effectively specify, build, and manage reliable software which can evolve and be maintained over an extended period. The need for such software is rooted in the increasing integration of software and computing components into NASA systems. Current NASA Software Engineering expertise was applied toward some of the largest reliable systems including: shuttle launch; ground support; shuttle simulation; minor control; satellite tracking; and scientific data systems. Unfortunately, no theory exists for reliable complex software systems. NASA is seeking to fill this theoretical gap through a number of approaches. One such approach is to conduct research on theoretical foundations for managing complex software systems. It includes: communication models, new and modified paradigms, and life-cycle models. Another approach is research in the theoretical foundations for reliable software development and validation. It focuses upon formal specifications, programming languages, software engineering systems, software reuse, formal verification, and software safety. Further approaches involve benchmarking a NASA software environment, experimentation within the NASA context, evolution of present NASA methodology, and transfer of technology to the space station software support environment.

Holcomb, Lee B.↗
DOE OSTI2024

Verification of the PERSENT Software

Ongoing commercial design activities require a thorough verification of the Argonne Reactor Computation codes to be performed. DIF3D is central to this system and substantial work has been done to verify its accuracy on several identified commercial needs. This manuscript details the verification work done on PERSENT which relies upon the DIF3D for its forward and adjoint flux solution.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2025

Verification of the PERSENT Software

Ongoing commercial design activities require a thorough verification of the Argonne Reactor Computation codes be performed. DIF3D is central to this system and substantial work has been done to verify its accuracy on several identified commercial needs. This manuscript details the verification work done on PERSENT which relies upon the DIF3D code for its forward and adjoint flux solution. Previous work identified the PERSENT features required to be verified to support commercial design activities, features of which are generally applicable to hexagonal-Z fast reactor designs. The scope of this verification effort includes verifying PERSENT’s ability to correctly calculate four key quantities: perturbation worth distributions, kinetics parameters, sensitivity coefficients, and cross section uncertainty quantification. This manuscript provides the verification tasks and their results with respect to these quantities needed for commercial design activities. For the perturbation worth distributions, hand calculations are deployed to verify the PERSENT calculated results. Similarly, hand calculation of the PERSENT computed kinetics parameters is also used to verify the PERSENT results. In both of these, the input to PERSENT is manipulated to ensure the hand calculation exactly matches the equations PERSENT is calculating. The sensitivity coefficients involve calculating the derivatives of a parameter (such as reactivity worth), with respect to the cross section data. Direct finite difference calculations with DIF3D are used to verify the PERSENT calculated results. For the uncertainty quantification, manufactured input to PERSENT is used to allow an exact hand calculation to reproduce the PERSENT calculated results. The work detailed in this report verified that significant issues were identified for earlier versions of PERSENT for sensitivity coefficients which were corrected in this work and thus version 12.1.0 of PERSENT must be used to reproduce all of the verified work in this report.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS2005

Application of Lightweight Formal Methods to Software Security

Formal specification and verification of security has proven a challenging task. There is no single method that has proven feasible. Instead, an integrated approach which combines several formal techniques can increase the confidence in the verification of software security properties. Such an approach which species security properties in a library that can be reused by 2 instruments and their methodologies developed for the National Aeronautics and Space Administration (NASA) at the Jet Propulsion Laboratory (JPL) are described herein The Flexible Modeling Framework (FMF) is a model based verijkation instrument that uses Promela and the SPIN model checker. The Property Based Tester (PBT) uses TASPEC and a Text Execution Monitor (TEM). They are used to reduce vulnerabilities and unwanted exposures in software during the development and maintenance life cycles.

security↗
NASA NTRS1996

V&V Within Reuse-Based Software Engineering

Verification and Validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission-critical software. V&V is a systems engineering discipline that evaluates the software in a systems context, and is currently applied during the development of a specific application system. In order to bring the effectiveness of V&V to bear within reuse-based software engineering, V&V must be incorporated within the domain engineering process.

Addy, Edward A.↗
NASA NTRS1996

V & V Within Reuse-Based Software Engineering

Verification and validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission critical software. This paper describes the working group's success in identifying V&V tasks that could be performed in the domain engineering and transition levels of reuse-based software engineering. The primary motivation for V&V at the domain level is to provide assurance that the domain requirements are correct and that the domain artifacts correctly implement the domain requirements. A secondary motivation is the possible elimination of redundant V&V activities at the application level. The group also considered the criteria and motivation for performing V&V in domain engineering.

Addy, Edward A.↗
NASA NTRS1992

Providing an empirical basis for optimizing the verification and testing phases of software development

Applying equal testing and verification effort to all parts of a software system is not very efficient, especially when resources are limited and scheduling is tight. Therefore, one needs to be able to differentiate low/high fault density components so that the testing/verification effort can be concentrated where needed. Such a strategy is expected to detect more faults and thus improve the resulting reliability of the overall system. This paper presents an alternative approach for constructing such models that is intended to fulfill specific software engineering needs (i.e. dealing with partial/incomplete information and creating models that are easy to interpret). Our approach to classification is as follows: (1) to measure the software system to be considered; and (2) to build multivariate stochastic models for prediction. We present experimental results obtained by classifying FORTRAN components developed at the NASA/GSFC into two fault density classes: low and high. Also we evaluate the accuracy of the model and the insights it provides into the software process.

Briand, Lionel C.↗
NASA NTRS2016

NASA Operational Simulator for Small Satellites: Tools for Software Based Validation and Verification of Small Satellites

The NASA Operational Simulator for Small Satellites (NOS3) is a suite of tools to aid in areas such as software development, integration test (IT), mission operations training, verification and validation (VV), and software systems check-out. NOS3 provides a software development environment, a multi-target build system, an operator interface-ground station, dynamics and environment simulations, and software-based hardware models. NOS3 enables the development of flight software (FSW) early in the project life cycle, when access to hardware is typically not available. For small satellites there are extensive lead times on many of the commercial-off-the-shelf (COTS) components as well as limited funding for engineering test units (ETU). Considering the difficulty of providing a hardware test-bed to each developer tester, hardware models are modeled based upon characteristic data or manufacturers data sheets for each individual component. The fidelity of each hardware models is such that FSW executes unaware that physical hardware is not present. This allows binaries to be compiled for both the simulation environment, and the flight computer, without changing the FSW source code. For hardware models that provide data dependent on the environment, such as a GPS receiver or magnetometer, an open-source tool from NASA GSFC (42 Spacecraft Simulation) is used to provide the necessary data. The underlying infrastructure used to transfer messages between FSW and the hardware models can also be used to monitor, intercept, and inject messages, which has proven to be beneficial for VV of larger missions such as James Webb Space Telescope (JWST). As hardware is procured, drivers can be added to the environment to enable hardware-in-the-loop (HWIL) testing. When strict time synchronization is not vital, any number of combinations of hardware components and software-based models can be tested. The open-source operator interface used in NOS3 is COSMOS from Ball Aerospace. For testing, plug-ins are implemented in COSMOS to control the NOS3 simulations, while the command and telemetry tools available in COSMOS are used to communicate with FSW. NOS3 is actively being used for FSW development and component testing of the Simulation-to-Flight 1 (STF-1) CubeSat. As NOS3 matures, hardware models have been added for common CubeSat components such as Novatel GPS receivers, ClydeSpace electrical power systems and batteries, ISISpace antenna systems, etc. In the future, NASA IVV plans to distribute NOS3 to other CubeSat developers and release the suite to the open-source community.

Verification↗