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 559 records · Page 31

TU-C-17A-03: An Integrated Contour Evaluation Software Tool Using Supervised Pattern Recognition for Radiotherapy

Purpose: Radiotherapy (RT) contours delineated either manually or semiautomatically require verification before clinical usage. Manual evaluation is very time consuming. A new integrated software tool using supervised pattern contour recognition was thus developed to facilitate this process. Methods: The contouring tool was developed using an object-oriented programming language C# and application programming interfaces, e.g. visualization toolkit (VTK). The C# language served as the tool design basis. The Accord.Net scientific computing libraries were utilized for the required statistical data processing and pattern recognition, while the VTK was used to build and render 3-D mesh models from critical RT structures in real-time and 360° visualization. Principal component analysis (PCA) was used for system self-updating geometry variations of normal structures based on physician-approved RT contours as a training dataset. The inhouse design of supervised PCA-based contour recognition method was used for automatically evaluating contour normality/abnormality. The function for reporting the contour evaluation results was implemented by using C# and Windows Form Designer. Results: The software input was RT simulation images and RT structures from commercial clinical treatment planning systems. Several abilities were demonstrated: automatic assessment of RT contours, file loading/saving of various modality medical images and RT contours, and generation/visualization of 3-D images and anatomical models. Moreover, it supported the 360° rendering of the RT structures in a multi-slice view, which allows physicians to visually check and edit abnormally contoured structures. Conclusion: This new software integrates the supervised learning framework with image processing and graphical visualization modules for RT contour verification. This tool has great potential for facilitating treatment planning with the assistance of an automatic contour evaluation module in avoiding unnecessary manual verification for physicians/dosimetrists. In addition, its nature as a compact and stand-alone tool allows for future extensibility to include additional functions for physicians’ clinical needs.

62 RADIOLOGY AND NUCLEAR MEDICINE↗

Verification of the 3-Region Advanced Test Reactor MCNP Model

The verification of the 3-region homogenized fuel Advanced Test Reactor MCNP model. The 3-region model was compared to the 19-plate model found in the 94-CIC report. Flux tallies, energy deposition tallies, and quarter core mesh tallies were used to compare the two models. The 3-region model needed updating in order to make good comparisons between the models. The percent error from the flux and energy deposition tallies data shows that experiment positions inside the flux trap have higher errors than positions outside the fuel ring. The standard deviation data obtained from the mesh tallies shows that the two models agree within two standard deviations throughout the reactor. It is concluded that the model works adequately for what it is used for.

99 GENERAL AND MISCELLANEOUS↗

Verification of the 3-Region Advanced Test Reactor MCNP Model

The verification of the 3-region homogenized fuel Advanced Test Reactor MCNP model. The 3-region model was compared to the 19-plate model found in the 94-CIC report. Flux tallies, energy deposition tallies, and quarter core mesh tallies were used to compare the two models. The 3-region model needed updating in order to make good comparisons between the models. The percent error from the flux and energy deposition tallies data shows that experiment positions inside the flux trap have higher errors than positions outside the fuel ring. The standard deviation data obtained from the mesh tallies shows that the two models agree within two standard deviations throughout the reactor. It is concluded that the model works adequately for what it is used for.

99 GENERAL AND MISCELLANEOUS↗

Software Specification Language

SSL translator aids in developing and checking software systems. Goal of SSL is to provide form of verification and consistency checking early in design phase. Serves as formal document to communicate software architecure to detailed designers.

Buckles, B. P.↗

Formal Verification for a Next-Generation Space Shuttle

This paper discusses the verification and validation (V&2) of advanced software used for integrated vehicle health monitoring (IVHM), in the context of NASA's next-generation space shuttle. We survey the current VBCV practice and standards used in selected NASA projects, review applicable formal verification techniques, and discuss their integration info existing development practice and standards. We also describe two verification tools, JMPL2SMV and Livingstone PathFinder, that can be used to thoroughly verify diagnosis applications that use model-based reasoning, such as the Livingstone system.

Nelson, Stacy D.↗

Cyclomatic Complexity and Basis Path Testing Study

The NASA Chief Engineer requested the NASA Engineering and Safety Center (NESC) to conduct a study to determine the benefits of cyclomatic complexity and basis path testing (BPT) for software and whether they should be required. The principal focus of the assessment was to assess the use of cyclomatic complexity and BPT on safety-critical software. The purpose was to ensure that safety-critical software is not overly complicated to the point of increasing coding errors and that verification is more robust than for non-safety-critical software. This document contains the outcome of the assessment.

Cyclomatic Complexity; NASA Engineering and Safety↗

Software-Only Key Management and Cryptography (KMC) for Spacecraft Command Encryption

The Jet Propulsion Laboratory (JPL) Advanced Multi-Mission Operations System (AMMOS) in partnership with NASA’s Katherine Johnson Independent Verification and Validation (NASA IV&V) Jon McBride Software Testing and Research (JSTAR) laboratory have jointly developed a command encryption capability that provides a software-only encryption solution utilizing the CCSDS Space Data Link Security Protocol. This solution, named Key Management and Cryptography (KMC), incorporates JPL’s encryption service with the JSTAR open-source CryptoLib library, providing a solution for spacecraft command encryption, which is required per NASA standard NASA-STD-1006-A. This paper will focus on its design, usage, and operation for two SmallSat missions, along with its future expanded functionality of end-to-end spacecraft encryption.

command encryption↗

Capability Enhancements for System-level thermal Hydraulic Modeling of Lead Fast Reactors

This project has focused on the use, assessment, and development of the SAS4A/SASSYS-1 (SAS) safety analysis software. Although SAS was originally intended as a safety analysis tool for Liquid Metal cooled Fast Reactors (LMFRs), which includes both Sodium Fast Reactors (SFRs) and Lead Fast Reactors (LFRs), the vast majority of its recent development and customization has been tailored to SFRs. In general, enhancements that are made to the software for SFRs are applicable to LFRs, however, the fuel composition and corrosive nature of lead requires careful consideration when performing safety analysis of an LFR. In this project an emphasis was placed on closing gaps that are associated with modeling LFRs using SAS. The principal objective of the project was to enhance the ability of SAS as a licensing tool for LFRs. This objective was to be accomplished through three tasks: 1) Enhance the ability of SAS to couple with external software; 2) Improve the underlying physics models in SAS, with priority given to models that are highly relevant to LFRs; 3) Extend the Verification and Validation (V&V) basis of the software

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Maintaining the Health of Software Monitors

Software health management (SWHM) techniques complement the rigorous verification and validation processes that are applied to safety-critical systems prior to their deployment. These techniques are used to monitor deployed software in its execution environment, serving as the last line of defense against the effects of a critical fault. SWHM monitors use information from the specification and implementation of the monitored software to detect violations, predict possible failures, and help the system recover from faults. Changes to the monitored software, such as adding new functionality or fixing defects, therefore, have the potential to impact the correctness of both the monitored software and the SWHM monitor. In this work, we describe how the results of a software change impact analysis technique, Directed Incremental Symbolic Execution (DiSE), can be applied to monitored software to identify the potential impact of the changes on the SWHM monitor software. The results of DiSE can then be used by other analysis techniques, e.g., testing, debugging, to help preserve and improve the integrity of the SWHM monitor as the monitored software evolves.

Runtime Monitor↗

Translating expert system rules into Ada code with validation and verification

The purpose of this ongoing research and development program is to develop software tools which enable the rapid development, upgrading, and maintenance of embedded real-time artificial intelligence systems. The goals of this phase of the research were to investigate the feasibility of developing software tools which automatically translate expert system rules into Ada code and develop methods for performing validation and verification testing of the resultant expert system. A prototype system was demonstrated which automatically translated rules from an Air Force expert system was demonstrated which detected errors in the execution of the resultant system. The method and prototype tools for converting AI representations into Ada code by converting the rules into Ada code modules and then linking them with an Activation Framework based run-time environment to form an executable load module are discussed. This method is based upon the use of Evidence Flow Graphs which are a data flow representation for intelligent systems. The development of prototype test generation and evaluation software which was used to test the resultant code is discussed. This testing was performed automatically using Monte-Carlo techniques based upon a constraint based description of the required performance for the system.

Becker, Lee↗

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IV&V) Program, with Software Assurance Research Program support, extracted FM architectures across the IV&V portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IV&V projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management. The identification of particular FM architectures, visibility, and associated IV&V techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. Additionally, the role FM has with regard to strengthened security requirements, with potential to advance overall asset protection of flight software systems, is being addressed with the development of an adverse conditions database encompassing flight software vulnerabilities. Capitalizing on the established framework, this TR suite provides assurance capability for a variety of FM architectures and varied development approaches. Research results are being disseminated across NASA, other agencies, and the software community. This paper discusses the findings and TR suite informing the FM domain in best practices for FM architectural design, visibility observations, and methods employed for IV&V and mission assurance.

Fitz, Rhonda↗

SU-E-T-608: Performance Comparison of Four Commercial Treatment Planning Systems Applied to Intensity-Modulated Radiotherapy

Purpose: To compare the performances of four commercial treatment planning systems (TPS) used for the intensity-modulated radiotherapy (IMRT). Methods: Ten patients of nasopharyngeal (4 cases), esophageal (3 cases) and cervical (3 cases) cancer were randomly selected from a 3-month IMRT plan pool at one radiotherapy center. For each patient, four IMRT plans were newly generated by using four commercial TPS (Corvus, Monaco, Pinnacle and Xio), and then verified with Matrixx (two-dimensional array/IBA Company) on Varian23EX accelerator. A pass rate (PR) calculated from the Gamma index by OminiPro IMRT 1.5 software was evaluated at four plan verification standards (1%/1mm, 2%/2mm, 3%/3mm, 4%/4mm and 5%/5mm) for each treatment plan. Overall and multiple pairwise comparisons of PRs were statistically conducted by analysis of covariance (ANOVA) F and LSD tests among four TPSs. Results: Overall significant (p>0.05) differences of PRs were found among four TPSs with F test values of 3.8 (p=0.02), 21.1(>0.01), 14.0 (>0.01), 8.3(>0.01) at standards of 1%/1mm to 4%/4mm respectively, except at 5%/5mm standard with 2.6 (p=0.06). All means (standard deviation) of PRs at 3%/3mm of 94.3 ± 3.3 (Corvus), 98.8 ± 0.8 (Monaco), 97.5± 1.7 (Pinnacle), 98.4 ± 1.0 (Xio) were above 90% and met clinical requirement. Multiple pairwise comparisons had not demonstrated a consistent low or high pattern on either TPS. Conclusion: Matrixx dose verification results show that the validation pass rates of Monaco and Xio plans are relatively higher than those of the other two; Pinnacle plan shows slight higher pass rate than Corvus plan; lowest pass rate was achieved by the Corvus plan among these four kinds of TPS.

60 APPLIED LIFE SCIENCES↗

Test Harness Framework

The code facilitates running tests and then validating the results. The tests are normally attacks on a system and the verification is normally to validate protection software detected the attack, however the framework can be used in any area.

McCarty, MichaelV↗

An evaluation of superminicomputers for thermal analysis

The use of superminicomputers for solving a series of increasingly complex thermal analysis problems is investigated. The approach involved (1) installation and verification of the SPAR thermal analyzer software on superminicomputers at Langley Research Center and Goddard Space Flight Center, (2) solution of six increasingly complex thermal problems on this equipment, and (3) comparison of solution (accuracy, CPU time, turnaround time, and cost) with solutions on large mainframe computers.

Storaasli, O. O.↗

Shuttle automatic landing system

The Shuttle automatic landing system design requirements are discussed, the approach and landing flight phase is described, and the hardware and software subsystems are functionally described. Emphasis is placed on the complexity, flexibility, and criticality of the software function. The software structure, critical computational problems, and verification process as a subsystem are discussed. Finally, the hardware/software verification activities required before flight test of the autoland system are described, along with the results from two flight tests and the planned system certification to the operational flight boundaries.

Tsikalas, G.↗

Software control and system configuration management: A systems-wide approach

A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.

Petersen, K. L.↗

Software control and system configuration management - A process that works

A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.

Petersen, K. L.↗

Proceedings of the 3rd Annual Conference on Aerospace Computational Control, volume 1

Conference topics included definition of tool requirements, advanced multibody component representation descriptions, model reduction, parallel computation, real time simulation, control design and analysis software, user interface issues, testing and verification, and applications to spacecraft, robotics, and aircraft.

Bernard, Douglas E.↗