Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 955 records · Page 53
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

Reconfigurable Hardware Adapts to Changing Mission Demands

A new class of computing architectures and processing systems, which use reconfigurable hardware, is creating a revolutionary approach to implementing future spacecraft systems. With the increasing complexity of electronic components, engineers must design next-generation spacecraft systems with new technologies in both hardware and software. Derivation Systems, Inc., of Carlsbad, California, has been working through NASA s Small Business Innovation Research (SBIR) program to develop key technologies in reconfigurable computing and Intellectual Property (IP) soft cores. Founded in 1993, Derivation Systems has received several SBIR contracts from NASA s Langley Research Center and the U.S. Department of Defense Air Force Research Laboratories in support of its mission to develop hardware and software for high-assurance systems. Through these contracts, Derivation Systems began developing leading-edge technology in formal verification, embedded Java, and reconfigurable computing for its PF3100, Derivational Reasoning System (DRS ), FormalCORE IP, FormalCORE PCI/32, FormalCORE DES, and LavaCORE Configurable Java Processor, which are designed for greater flexibility and security on all space missions.

Source record↗
NASA NTRS2005

JAVA PathFinder

JPF is an explicit state software model checker for Java bytecode. Today, JPF is a swiss army knife for all sort of runtime based verification purposes. This basically means JPF is a Java virtual machine that executes your program not just once (like a normal VM), but theoretically in all possible ways, checking for property violations like deadlocks or unhandled exceptions along all potential execution paths. If it finds an error, JPF reports the whole execution that leads to it. Unlike a normal debugger, JPF keeps track of every step how it got to the defect.

Mehhtz, Peter↗
NASA NTRS2012

Upgrades at the NASA Langley Research Center National Transonic Facility

Several projects have been completed or are nearing completion at the NASA Langley Research Center (LaRC) National Transonic Facility (NTF). The addition of a Model Flow-Control/Propulsion Simulation test capability to the NTF provides a unique, transonic, high-Reynolds number test capability that is well suited for research in propulsion airframe integration studies, circulation control high-lift concepts, powered lift, and cruise separation flow control. A 1992 vintage Facility Automation System (FAS) that performs the control functions for tunnel pressure, temperature, Mach number, model position, safety interlock and supervisory controls was replaced using current, commercially available components. This FAS upgrade also involved a design study for the replacement of the facility Mach measurement system and the development of a software-based simulation model of NTF processes and control systems. The FAS upgrades were validated by a post upgrade verification wind tunnel test. The data acquisition system (DAS) upgrade project involves the design, purchase, build, integration, installation and verification of a new DAS by replacing several early 1990's vintage computer systems with state of the art hardware/software. This paper provides an update on the progress made in these efforts. See reference 1.

Paryz, Roman W.↗
NASA NTRS2012

Model-Based Verification and Validation of Spacecraft Avionics

Verification and Validation (V&V) at JPL is traditionally performed on flight or flight-like hardware running flight software. For some time, the complexity of avionics has increased exponentially while the time allocated for system integration and associated V&V testing has remained fixed. There is an increasing need to perform comprehensive system level V&V using modeling and simulation, and to use scarce hardware testing time to validate models; the norm for thermal and structural V&V for some time. Our approach extends model-based V&V to electronics and software through functional and structural models implemented in SysML. We develop component models of electronics and software that are validated by comparison with test results from actual equipment. The models are then simulated enabling a more complete set of test cases than possible on flight hardware. SysML simulations provide access and control of internal nodes that may not be available in physical systems. This is particularly helpful in testing fault protection behaviors when injecting faults is either not possible or potentially damaging to the hardware. We can also model both hardware and software behaviors in SysML, which allows us to simulate hardware and software interactions. With an integrated model and simulation capability we can evaluate the hardware and software interactions and identify problems sooner. The primary missing piece is validating SysML model correctness against hardware; this experiment demonstrated such an approach is possible.

MBV&V↗
NASA NTRS2017

Applying Standard Independent Verification and Validation (IVV) Techniques Within an Agile Framework: Is There a Compatibility Issue?

Agile methods have gained wide acceptance over the past several years, to the point that they are now a standard management and execution approach for small-scale software development projects. While conventional Agile methods are not generally applicable to large multi-year and mission-critical systems, Agile hybrids are now being developed (such as SAFe) to exploit the productivity improvements of Agile while retaining the necessary process rigor and coordination needs of these projects. From the perspective of Independent Verification and Validation (IVV), however, the adoption of these hybrid Agile frameworks is becoming somewhat problematic. Hence, we find it prudent to question the compatibility of conventional IVV techniques with (hybrid) Agile practices.This paper documents our investigation of (a) relevant literature, (b) the modification and adoption of Agile frameworks to accommodate the development of large scale, mission critical systems, and (c) the compatibility of standard IVV techniques within hybrid Agile development frameworks. Specific to the latter, we found that the IVV methods employed within a hybrid Agile process can be divided into three groups: (1) early lifecycle IVV techniques that are fully compatible with the hybrid lifecycles, (2) IVV techniques that focus on tracing requirements, test objectives, etc. are somewhat incompatible, but can be tailored with a modest effort, and (3) IVV techniques involving an assessment requiring artifact completeness that are simply not compatible with hybrid Agile processes, e.g., those that assume complete requirement specification early in the development lifecycle.

Agile↗
DOE OSTI2016

SU-F-T-586: Pre-Treatment QA of InCise2 MLC Plans On a Cyberknife-M6 Using the Delta4 System in SBRT

Purpose: Performing pre-treatment quality assurance (QA) with the Delta4 system (ScandiDos Inc., Madison, WI) is well established for linac-based radiotherapy. This is not true when using a Cyberknife (Accuray Inc., Sunnyvale, CA) where, typically film-based QA is applied. The goal of this work was to test the feasibility to use the Delta4 system for pre-treatment QA for stereotactic body radiation therapy (SBRT) using a Cyberknife-M6 equipped with the InCise2 multileaf collimator (MLC). Methods: In order to perform measurements without accelerator pulse signal, the Tomotherapy option within the Delta4 software was used. Absolute calibration of the Delta4 phantom was performed using a 10×10 cm{sup 2} field shaped by the InCise2 MLC of the Cyberknife-M6. Five fiducials were attached to the Delta4 phantom in order to be able to track the phantom before and during measurements. For eight SBRT treatment plans (two liver, two prostate, one lung, three bone metastases) additional verification plans were recalculated on the Delta4 phantom using MultiPlan. Dicom data was exported from MultiPlan and was adapted in order to be compatible with the Delta4 software. The measured and calculated dose distributions were compared using the gamma analysis of the Delta4 system. Results: All eight SBRT plans were successfully measured with the aid of the Delta4 system. In the mean, 98.0±1.9%, 95.8±4.1% and 88.40±11.4% of measured dose points passed the gamma analysis using a global dose deviation criterion of 3% (100% corresponds to the dose maximum) and a distance-to-agreement criterion of 3 mm, 2 mm and 1 mm, respectively, and a threshold of 20%. Conclusion: Pre-treatment QA of SBRT plans using the Delta4 system on a Cyberknife-M6 is feasible. Measured dose distributions of SBRT plans showed clinically acceptable agreement with the corresponding calculated dose distributions.

60 APPLIED LIFE SCIENCES↗
NASA NTRS2008

Closing the Certification Gaps in Adaptive Flight Control Software

Over the last five decades, extensive research has been performed to design and develop adaptive control systems for aerospace systems and other applications where the capability to change controller behavior at different operating conditions is highly desirable. Although adaptive flight control has been partially implemented through the use of gain-scheduled control, truly adaptive control systems using learning algorithms and on-line system identification methods have not seen commercial deployment. The reason is that the certification process for adaptive flight control software for use in national air space has not yet been decided. The purpose of this paper is to examine the gaps between the state-of-the-art methodologies used to certify conventional (i.e., non-adaptive) flight control system software and what will likely to be needed to satisfy FAA airworthiness requirements. These gaps include the lack of a certification plan or process guide, the need to develop verification and validation tools and methodologies to analyze adaptive controller stability and convergence, as well as the development of metrics to evaluate adaptive controller performance at off-nominal flight conditions. This paper presents the major certification gap areas, a description of the current state of the verification methodologies, and what further research efforts will likely be needed to close the gaps remaining in current certification practices. It is envisioned that closing the gap will require certain advances in simulation methods, comprehensive methods to determine learning algorithm stability and convergence rates, the development of performance metrics for adaptive controllers, the application of formal software assurance methods, the application of on-line software monitoring tools for adaptive controller health assessment, and the development of a certification case for adaptive system safety of flight.

Jacklin, Stephen A.↗
DOE OSTI2015

SU-E-T-634: Pre-Verification of FFF Prostate VMAT Plans with Gamma Method and DVHs Reconstructed Based On Measurements with 2D-ARRAY (PTW 1500) and OCTAVIUS 4D

Purpose: The aim of this work was to characterize the clinical correctness of FFF prostate treatment VMAT plans based on analysis of DVHs reconstructed from pre-verification 2D-arrays measurements. Methods: The new 2D ion chamber array 1500 with rotational phantom cylindrical Octavius 4D and Verisoft 6.1 software with DVH option (PTW, Freiburg) were used to determine the clinical usefulness of the treatment plans. Ten patients treated with VMAT high-fractionated (2 fraction x 7,5 Gy) FFF prostate plans (TrueBeam, Varian) were analyzed using the 3D gamma analysis by local dose method with a 5% threshold for various tolerance parameters DTA [mm] and DD [%] were 1%/1, 2%/2, 3%/3. Additional, based on the measurements of irradiation dose distributions and patients’ CT scans with contoured structures of organs, the DVHs were reconstructed using a software. The obtained DVHs were compared to planned dose distributions and the deviations were analysed with parameters: for CTV D50, D98, D2, and D25, D50, Dmax for OARs — rectum, bladder and left/right femoral heads. Results: The analyzed treatment plans passed gamma criteria (3/3%; 95%), the results obtained were as follow: mean value and standard deviation of gamma score for criteria (DTA[mm]/DD[%]): 1/1% (L53.3±3.2); 2/2% (L87.0±2.2); 3/3% (L97.5±0.9). In the DVH analysis, the highest differences were observed for OARs (especially for bladder): the mean percentage differences values for rectum, bladder and left/right femoral heads were: D25 (1.67; 6.83)%, D50 (0.18; 7.18; 1.53; 0.30)%, Dmax (−0.84; −1.64; 0.37; −4.63)%, respectively. For the CTV mean relative deviations for proper parameters were in good agreement with TPS: D98 (0.95±2.21)%, D50 (1.93±0.67)%, D2 (1.76±0.76)%. Conclusion: The gamma method is recommended tool for pre-verification analysis of correctness of treatment plans. Moreover, the scrutiny checking with reconstructed DVH gives additional, clinical information about quality of plan, especially about coverage of CTV and sparing of health tissues.

62 RADIOLOGY AND NUCLEAR MEDICINE↗
DOE OSTI2026

Investigating Temperature Uniformity and Accuracy in PV Module Lamination: A Verification Study

This study investigates the temperature uniformity and accuracy of a photovoltaic (PV) module lamination process by addressing inconsistencies identified in 2017 data where irregular temperature changes were observed across setpoints. The 2017 data showed a notable drop in temperature upon bladder initiation, except for the 145 degrees Celsius profile. This inconsistency indicated potential inaccuracies in manual data recording methods. To address this concern, a verification experiment was conducted to evaluate temperature uniformity across the 2014 Bent River SPL2828 laminator platen and within test samples. Thermocouples, paired with Omega data acquisition software, were deployed to measure temperatures at multiple platen locations and within test samples. The experiment compared lamination temperatures of polyethylene-co-vinyl acetate (EVA) encapsulant when paired with solite glass or TPE backsheets. The methodology included verifying temperature uniformity directly on the platen and by using a large glass/EVA/glass sample using multiple thermocouples. Smaller samples were built with glass/EVA/glass and glass/EVA/backsheet configurations with one centered thermocouple to verify and compare sample temperatures. This verification aims to refine lamination temperature profiles, enhance data accuracy and provide insights into optimal process control for uniform module lamination. Ensuring consistent and uniform lamination may improve the accuracy and reliability of research outcomes.

14 SOLAR ENERGY↗
NASA NTRS2018

From Formal Requirements to Highly Assured Software for Unmanned Aircraft Systems

Operational requirements of safety-critical systems are often written in restricted specification logics. These restricted logics are amenable to automated analysis techniques such as model-checking, but are not rich enough to express complex requirements of unmanned systems. This short paper advocates for the use of expressive logics, such as higher-order logic, to specify the complex operational requirements and safety properties of unmanned systems. These rich logics are less amenable to automation and, hence, require the use of interactive theorem proving techniques. However, these logics support the formal verification of complex requirements such as those involving the physical environment. Moreover, these logics enable validation techniques that increase con dence in the correctness of numerically intensive software. These features result in highly-assured software that may be easier to certify. The feasibility of this approach is illustrated with examples drawn for NASA's unmanned aircraft systems.

Munoz, Cesar↗
NASA NTRS2017

Risk-Significant Adverse Condition Awareness Strengthens Assurance of Fault Management Systems

As spaceflight systems increase in complexity, Fault Management (FM) systems are ranked high in risk-based assessment of software criticality, emphasizing the importance of establishing highly competent domain expertise to provide assurance. Adverse conditions (ACs) and specific vulnerabilities encountered by safety- and mission-critical software systems have been identified through efforts to reduce the risk posture of software-intensive NASA missions. Acknowledgement of potential off-nominal conditions and analysis to determine software system resiliency are important aspects of hazard analysis and FM. A key component of assuring FM is an assessment of how well software addresses susceptibility to failure through consideration of ACs. Focus on significant risk predicted through experienced analysis conducted at the NASA Independent Verification Validation (IVV) Program enables the scoping of effective assurance strategies with regard to overall asset protection of complex spaceflight as well as ground systems. Research efforts sponsored by NASA's Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs and allowing queries based on project, mission type, domaincomponent, causal fault, and other key characteristics. Vulnerability in off-nominal situations, architectural design weaknesses, and unexpected or undesirable system behaviors in reaction to faults are curtailed with the awareness of ACs and risk-significant scenarios modeled for analysts through this database. Integration within the Enterprise Architecture at NASA IVV enables interfacing with other tools and datasets, technical support, and accessibility across the Agency. This paper discusses the development of an improved workflow process utilizing this database for adaptive, risk-informed FM assurance that critical software systems will safely and securely protect against faults and respond to ACs in order to achieve successful missions.

Fault management↗
NASA NTRS2017

Risk-Significant Adverse Condition Awareness Strengthens Assurance of Fault Management Systems

As spaceflight systems increase in complexity, Fault Management (FM) systems are ranked high in risk-based assessment of software criticality, emphasizing the importance of establishing highly competent domain expertise to provide assurance. Adverse conditions (ACs) and specific vulnerabilities encountered by safety- and mission-critical software systems have been identified through efforts to reduce the risk posture of software-intensive NASA missions. Acknowledgement of potential off-nominal conditions and analysis to determine software system resiliency are important aspects of hazard analysis and FM. A key component of assuring FM is an assessment of how well software addresses susceptibility to failure through consideration of ACs. Focus on significant risk predicted through experienced analysis conducted at the NASA Independent Verification & Validation (IV&V) Program enables the scoping of effective assurance strategies with regard to overall asset protection of complex spaceflight as well as ground systems. Research efforts sponsored by NASAs Office of Safety and Mission Assurance (OSMA) defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs and allowing queries based on project, mission type, domain/component, causal fault, and other key characteristics. Vulnerability in off-nominal situations, architectural design weaknesses, and unexpected or undesirable system behaviors in reaction to faults are curtailed with the awareness of ACs and risk-significant scenarios modeled for analysts through this database. Integration within the Enterprise Architecture at NASA IV&V enables interfacing with other tools and datasets, technical support, and accessibility across the Agency. This paper discusses the development of an improved workflow process utilizing this database for adaptive, risk-informed FM assurance that critical software systems will safely and securely protect against faults and respond to ACs in order to achieve successful missions.

IV&V↗
DOE OSTI2018

Verification and Validation of Optimization of Replacement Portal Monitoring Replay Tools

The Los Alamos National Laboratory and the Johns Hopkins Applied Physics Laboratory (APL) are both developing optimization software to fulfill the objective of Phase III of the Replacement Portal Monitoring (RPM) Program for the Department of Homeland Security. The objective of the Phase III of the RPM Program is to conduct an evaluation of three RPM systems designed to enhance mission effectiveness, gain operational efficiencies, and to address emerging mission needs against the Countering Weapons of Mass Destruction (CWMD ) nuclear threat basis and special nuclear material (SNM) used in performance testing. As such this task involves the use of global optimization algorithms.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗
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

ThinCurr: An open-source 3D thin-wall eddy current modeling code for the analysis of large-scale systems of conducting structures

In this paper we present a new thin-wall eddy current modeling code, ThinCurr, for studying inductively-coupled currents in 3D conducting structures -- with primary application focused on the interaction between currents flowing in coils, plasma, and conducting structures of magnetically-confined plasma devices. The code utilizes a boundary finite element method on an unstructured, triangular grid to accurately capture device structures. The new code, part of the broader Open FUSION Toolkit, is open-source and designed for ease of use without sacrificing capability and speed through a combination of Python, Fortran, and C/C++ components. Scalability to large models is enabled through use of hierarchical off-diagonal low-rank compression of the inductance matrix, which is otherwise dense. Ease of handling large models of complicated geometry is further supported by automatic determination of supplemental elements through a greedy homology approach. Here, a detailed description of the numerical methods of the code and verification of the implementation of those methods using cross-code comparisons against the VALEN code and Ansys commercial analysis software is shown.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗
DOE OSTI2019

CIAE-ANL CRADA for SFR SAFETY ANALYSIS: Final CRADA Report

The purpose of this project is joint verification and validation of system analysis code capabilities for Sodium-cooled Fast Reactor (SFR) design and licensing. As the researchers and code developers at the Argonne National Laboratory (ANL) and China Institute of Atomic Energy (CIAE) independently build their own SFR system analysis capabilities, this collaboration facilitated exchange of information on, and evaluation of alternative approaches for, modeling the key phenomena (such as decay heat removal and natural circulation) and the safety-related components (such as pumps, heat exchangers, and outlet plenum) common in SFR systems. The analysis at ANL and CIAE also applied their respective computational capabilities and methods (in SAS4A/SASSYS-1 computer code at ANL and FR-Sdaso computer code at CIAE) on jointly identified benchmark problems for verification, and publicly available integral tests for validation, of their results. ANL team also shared the expertise on the established software quality assurance practices and the techniques for component reliability estimates to support probabilistic risk assessments.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
NASA NTRS1988

International interface design for Space Station Freedom - Challenges and solutions

The definition of interfaces for the International Space Station is discussed, with a focus on negotiations between NASA and ESA. The program organization and division of responsibilities for the Space Station are outlined; the basic features of physical and functional interfaces are described; and particular attention is given to the interface management and documentation procedures, architectural control elements, interface implementation and verification, and examples of Columbus interface solutions (including mechanical, ECLSS, thermal-control, electrical, data-management, standardized user, and software interfaces). Diagrams, drawings, graphs, and tables listing interface types are provided.

Mayo, Richard E.↗
NASA NTRS1991

NASA software documentation standard software engineering program

The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Source record↗