Search NASA⌕ Search

SEARCH · Search NASA

Results for “Verification and Validation (V&V)”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
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 NTRS2020

Validation on the Europa Clipper Mission in the Formulation Phase

The Europa Clipper mission will perform a detailed investigation of Europa’s environment and habitability by placing a spacecraft into a looping orbit around Jupiter and performing repeated close Europa flybys. The Europa Clipper Project Verification and Validation (V&V) team is responsible for verifying that the Project System is compliant with the science and engineering requirements levied on it and validating that it is capable of meeting the mission objectives. Europa Clipper has developed a V&V framework to ensure that mission capabilities are realized at a reasonable confidence level prior to launch. The V&V team will coordinate the validation activities defined by this framework throughout the project lifecycle as the spacecraft evolves from design to implementation and operations. Validation of space missions is typically grouped into three categories: 1) requirements validation, 2) model validation, and 3) system validation. System validation, along with verification activities, are often the primary focus of V&V programs and these efforts peak in the implementation phase. However, the increasing reliance of exploration missions on models and simulations, and the complexity of the Europa Clipper mission, have dictated attention to requirements and model validation in the formulation phase. This paper discusses the development of the Europa Clipper V&V framework with emphasis on the validation of models and simulations, and of requirements. Approaches include the adaptation of institutional guidelines, such as those in the NASA-STD-7009 document, to create a Project Model V&V Plan and the use of tools such as DOORS NG to plan model validation and derive requirement quality metrics.

Srivastava, Priyanka↗
NASA NTRS1994

A process improvement model for software verification and validation

We describe ongoing work at the NASA Independent Verification and Validation (IV&V) Facility to establish a process improvement model for software verification and validation (V&V) organizations. This model, similar to those used by some software development organizations, uses measurement-based techniques to identify problem areas and introduce incremental improvements. We seek to replicate this model for organizations involved in V&V on large-scale software development projects such as EOS and Space Station. At the IV&V Facility, a university research group and V&V contractors are working together to collect metrics across projects in order to determine the effectiveness of V&V and improve its application. Since V&V processes are intimately tied to development processes, this paper also examines the repercussions for development organizations in large-scale efforts.

Callahan, John↗
NASA NTRS1994

A process improvement model for software verification and validation

We describe ongoing work at the NASA Independent Verification and Validation (IV&V) Facility to establish a process improvement model for software verification and validation (V&V) organizations. This model, similar to those used by some software development organizations, uses measurement-based techniques to identify problem areas and introduce incremental improvements. We seek to replicate this model for organizations involved in V&V on large-scale software development projects such as EOS and space station. At the IV&V Facility, a university research group and V&V contractors are working together to collect metrics across projects in order to determine the effectiveness of V&V and improve its application. Since V&V processes are intimately tied to development processes, this paper also examines the repercussions for development organizations in large-scale efforts.

Callahan, John↗
NASA NTRS2000

Independent Verification and Validation (IV and V) Criteria

The purpose of this appendix is to establish quantifiable criteria for determining whether IV&V should be applied to a given software development. Since IV&V should begin in the Formulation Subprocess of a project, the process here described is based on metrics which are available before project approval.

McGill, Kenneth↗
DOE OSTI2025

Summary Report Of The FY25 Computational Fluid Dynamics Verification And Validation Exercises In The Advanced Reactor Technologies - Gas-cooled Reactor Program

Verification and Validation (V&V) of numerical tools is critical for ensuring reasonable predictions during design, safety analysis, and licensing. Recent work in the Advanced Reactor Technologies - Gas-cooled Reactor (ART-GCR) program has focused on V&V of common Computational Fluid Dynamics (CFD) tools that are used within the Untied States. This report presents an update on these CFD V&V activities. These Generation IV Forum (GIF) Very High Temperature Reactor (VHTR) Computational Methods, Validation, and Benchmarking (CMVB) is an international organization dedicated to the verification and validation of High Temperature Gas-Cooled Reactor (HTGR) simulation tools. Participation in the CMVB provides additional value to the V&V activities, as it allows for access to a wider range of data, and provides valuable benchmarking exercises. Three HTGR phenomena are targeted: Reactor Cavity Cooling System (RCCS) performance, core bypass flow, and lower plenum mixing. Simulations of the University of Wisconsin-Madison (UW-Madison) RCCS facilities are performed with Reynolds Averaged Navier-Stokes (RANS) in StarCCM+. Results are compared for both forced and natural convection conditions, with both exhibiting good agreement with experimental measurements. The Idaho National Laboratory (INL) matched index of refraction (MIR) and Korean Atomic Energy Research Institute (KAERI) bypass flow expeirments are used to validation CFD predictions of bypass flow. Simulations are performed with RANS in StarCCM+ and with Large Eddy Simulation (LES) in NekRS. Finally, preliminary simulations of the Institute of Nuclear and New Energy Technology (INET) lower plenum mixing facilities are presented. Initial work has developed models with LES, RANS, and porous media models. These preliminary models are presented and compared to each other to gauge differences in predictions with each of the three methods.

and Benchmarking (CMVB)↗
NASA NTRS1999

Synthetic Scene Generation of the Stennis V and V Target Range for the Calibration of Remote Sensing Systems

The verification and validation (V&V) target range developed at Stennis Space Center is a useful test site for the calibration of remote sensing systems. In this paper, we present a simple algorithm for generating synthetic radiance scenes or digital models of this target range. The radiation propagation for the target in the solar reflective and thermal infrared spectral regions is modeled using the atmospheric radiative transfer code MODTRAN 4. The at-sensor, in-band radiance and spectral radiance for a given sensor at a given altitude is predicted. Software is developed to generate scenes with different spatial and spectral resolutions using the simulated at-sensor radiance values. The radiometric accuracy of the simulation is evaluated by comparing simulated with AVIRIS acquired radiance values. The results show that in general there is a good match between AVIRIS sensor measured and MODTRAN predicted radiance values for the target despite the fact that some anomalies exist. Synthetic scenes provide a cost-effective way for in-flight validation of the spatial and radiometric accuracy of the data. Other applications include mission planning, sensor simulation, and trade-off analysis in sensor design.

Cao, Chang-Yong↗
NASA NTRS1998

V & V of A Spacecrafts Autonomous Planner Through Extended Automation

We have introduced and used significant automation during the verification and validation (V & V) of a spacecraft's autonomous planner. This paper describes the problem we faced, the solution we employed, and the applicability of our approach in a general V & V setting.

planning↗
NASA NTRS2013

Model-Based Verification and Validation of the SMAP Uplink Processes

This case study stands as an example of how a project can validate a system-level design earlier in the project life cycle than traditional V&V processes by using simulation on a system model. Specifically, this paper describes how simulation was added to a system model of the Soil Moisture Active-Passive (SMAP) mission's uplink process.Also discussed are the advantages and disadvantages of the methods employed and the lessons learned; which are intended to benefit future model-based and simulation-based V&V development efforts.

verification and validation (V&V)↗
NASA NTRS1996

The Role of Independent V&V in Upstream Software Development Processes

This paper describes the role of Verification and Validation (V&V) during the requirements and high level design processes, and in particular the role of Independent V&V (IV&V). The job of IV&V during these phases is to ensure that the requirements are complete, consistent and valid, and to ensure that the high level design meets the requirements. This contrasts with the role of Quality Assurance (QA), which ensures that appropriate standards and process models are defined and applied. This paper describes the current state of practice for IV&V, concentrating on the process model used in NASA projects. We describe a case study, showing the processes by which problem reporting and tracking takes place, and how IV&V feeds into decision making by the development team. We then describe the problems faced in implementing IV&V. We conclude that despite a well defined process model, and tools to support it, IV&V is still beset by communication and coordination problems.

Easterbrook, Steve↗
NASA NTRS2002

Survey of NASA V and V Processes/Methods

The purpose of this report is to describe current NASA Verification and Validation (V&V) techniques and to explain how these techniques are applicable to 2nd Generation RLV Integrated Vehicle Health Management (IVHM) software. It also contains recommendations for special V&V requirements for IVHM. This report is divided into the following three sections: 1) Survey - Current NASA V&V Processes/Methods; 2) Applicability of NASA V&V to 2nd Generation RLV IVHM; and 3) Special 2nd Generation RLV IVHM V&V Requirements.

Pecheur, Charles↗
DOE OSTI2021

Verification and Validation of Systems in which AI is a Key Element

Many systems are being considered in which artificial intelligence (AI) will be a key element. Failure of an AI element can lead to system failure, hence the need for AI verification and validation (V&V). This article addresses V&V of such a system, focusing on the issues created by characteristics of AI that make V&V challenging. The element(s) containing AI capabilities is treated as a subsystem and V&V is conducted on that subsystem and its interfaces with other elements of the system under study, just as V&V would be conducted on other subsystems. That is, the high-level definitions of verification and of validation do not change for systems containing one or more AI elements. However, AI V&V challenges require approaches and solutions beyond those for conventional or traditional (those without AI elements) systems. This article provides an overview of how machine learning components/subsystems “fit” in the systems engineering framework (Section 1), identifies characteristics of AI subsystems that create challenges in their V&V (Section 2), describes those challenges (Section 3) and provides some potential solutions (Section 4).

Pullum, Laura↗
DOE OSTI2023

HYBRID Modeling Validation and Verification Status Matrix

The HYBRID modeling repository is a premier resource for integrated energy systems modeling. HYBRID models have been developed since 2015 to describe the physical operation of tightly coupled thermal systems including power generators, thermal transport systems, thermal storage, thermal-to-electric conversion systems, and other thermal applications. Due to the increased size of the repository, a concise summary matrix of available models is desired. This matrix will consolidate not only the list of available models but also indicate original information sources, publications that have model examples, and level of validation and verification that exists for the models. Validation and verification (V&V) levels begin from simplified algebraic relationship and advance to dynamic data validation. Moving forward, as new models are contributed to HYBRID, their V&V level will be included, updating this matrix.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
NASA NTRS2006

Verification and Validation in NASA-CUIP LOX/methane Injector Research Efforts

The NASA-CUIP program is supporting experimental and modeling/computational research efforts investigating wall heat flux characteristics of LOX/methane single-element injectors. A Verification and Validation (V&V) task has begun with the objective of quantifying the degree of accuracy of the models for wall heat flux distributions at specific sets of conditions. The V&V approach used is that being drafted as a standard by the ASME Performance Test Codes Committee, PTC 61: Verification and Validation in Computational Fluid Dynamics and Heat Transfer. The approach is based on well-established concepts from experimental uncertainty analysis. Initially the V&V and uncertainty estimation efforts will use data obtained previously in the same facility using oxygen/hydrogen in single-element injector testing. In this paper the V&V process, experimental facility, and computer code are described, and approaches to estimating the associated uncertainties are discussed.

Coleman, Hugh W.↗
NASA NTRS2012

Integrated Simulation Design Challenges to Support TPS Repair Operations

During the Orbiter Repair Maneuver (ORM) operations planned for Return to Flight (RTF), the Shuttle Remote Manipulator System (SRMS) must grapple the International Space Station (ISS), undock the Orbiter, maneuver it through a long duration trajectory, and orient it to an EVA crewman poised at the end of the Space Station Remote Manipulator System (SSRMS) to facilitate the repair of the Thermal Protection System (TPS). Once repair has been completed and confirmed, then the SRMS proceeds back through the trajectory to dock the Orbiter to the Orbiter Docking System. In order to support analysis of the complex dynamic interactions of the integrated system formed by the Orbiter, ISS, SRMS, and SSMS during the ORM, simulation tools used for previous ‘nominal’ mission support required substantial enhancements. These upgrades were necessary to provide analysts with the capabilities needed to study integrated system performance. Prevalent throughout this ORM operation is a dynamically varying topology. In other words, the ORM starts with the SRMS grappled to the mated Shuttle/ISS stack (closed loop topology), moves to an open loop chain topology consisting of the Shuttle, SRMS, and ISS, and then, at the repair configuration, extends the chain topology to one consisting of the Shuttle, SMS, ISS, and SSRMS/EVA crewman. The resulting long dynamic chain of vehicles and manipulators may exhibit significant motion between the Shuttle worksite and the EVA crewman due to the system flexibility throughout the topology (particularly within the SRMS/SSRMS joints and links). Since the attachment points of both manipulators span the flexible structure of the ISS, simulation analysis may also need to take that into consideration. Moreover, due to the lengthy time duration associated with the maneuver and repair, orbital effects become a factor and require the ISS vehicle control system to maintain active attitude control. Several facets of the ORM operation make the associated analytical efforts different from previous mission support, including: (1) the magnitude of the SRMS handled payload (Le., Orbiter class), (2) the orbital effects induced on the integrated system consisting of the large Shuttle and ISS masses connected by a light flexible SRMS, (3) long duration environmental consequences due to the lengthy operational times associated with the maneuver and repair of the TPS, (4) active attitude control (as opposed to free drift) interacting with the SRMS and SSRMS manipulators (also due to the length of the maneuver and repair), (5) relative dynamics between the EVA crewman and thc worksite influenced by the extended flexible topology. In order to meet these analysis challenges, an ORM simulation architecture was developed leveraging upon numerous pre-existing simulation elements to analyze the various subsystems individually. For example, core manipulator subsystem simulations for both the SRMS and SSRMS were originally combined to provide the dual-arm dynamics topology simulation (in the absence of orbital dynamics and vehicle control). This capability was later merged with the simulation used to analyze SRMS loading with a heavy payload in the orbital environment with an active payload control system (in this case, the ISS Attitude Control System (ACS)), configured for the ORM. The resulting worksite dynamics simulation, based off of the modified ORM simulation, provided the extended topological chain of vehicles and manipulators, while taking into account the orbital effects of both the Shuttle and ISS (as well as its ACS). Verification and validation (V&V) of these integrated simulations became a challenge in itself. A systematic approach needed to be developed such that integration simulation results could be tested against previous constituent simulations upon which these simulations were built. General V&V categories included: (1) core orbital state propagation, (2), stand-alone SRMS, (3) stand-alone SSRMS, (4) stand-alone ISS ACS, (5) integrated Shuttle, SRMS, ISS (with active ACS) in the orbital environment, and (5) dual-arm SRMS/SSRMS dynamics topology. Integrated simulation V&V run suites were created and correlated to verification runs from subsystem simulations, in order to establish the validity of the results. This paper discusses the simulation design challenges encountered while developing simulation capabilities to mirror the ORM operations. The paper also describes the incremental build approach that was utilized, starting with the subsystem simulation elements and integration into increasing more complex simulations until the resulting ORM worksite dynamics simulation had been assembled. Furthermore, the paper presents an overall integrated simulation V&V methodology based upon a subsystem level testing, integrated comparisons, and phased checkout.

Thermal Protection System↗
NASA NTRS1987

KBS V and V as related to automation of space station subsystems: Rationale for a KBS lifecycle

The role of verification and validation (V and V) in software has been to support and strengthen the software lifecycle and to ensure that the resultant code meets the standards of the requirements document. Knowledge based systems (KBS) V and V should serve the same role, but the KBS lifecycle is ill-defined. Here, the rationale of the simple form of the KBS lifecycle is explained. Special KBS development requirements are accommodated where possible by modifications to the traditional software lifecycle. Research areas are suggested for those aspects which present new or unusual difficulties for V and V.

Richardson, K.↗