Sterilization Assembly Development Laboratory - Quality assurance program Plan
Quality control program plan for sterilization assembly development laboratory
Paquin, L. A.↗
SEARCH · Engineering Papers
Results for “Development assurance”
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.
Status of SPCA-ANL Software Development, Software Quality Assurance, and Application (FY2025)
SPCA-ANL is a simulation tool used to perform deterministic analyses of sodium spray and pool fires. Development of the SPCA-II (Spray Pool Combustion Analysis) code began in the mid- 1980s as part of the Clinch River Breeder Reactor (CRBR) Project. At that time, development of SPCA-II, which was led by Rockwell International, was focused on treatment of large-scale sodium spray, stream, and pool fires that were anticipated to be prototypic of the steam generator building cells in CRBR. Under more recent DOE NE programmatic activities, the SPCA-II code was recovered from existing literature and underwent minor modifications to generate a stable executable. This recovered version of the code was not formally released. As part of the Versatile Test Reactor (VTR) Project in the 2010s, the SPCA-II code underwent key modifications to improve stability, address modeling deficiencies, improve consistency between the code manual and software, and address numerous bugs. At this point, SPCA-II was renamed SPCA-ANL. Given that SPCA-II served as the original basis for SPCA-ANL, both codes share an integrated history. Following termination of the VTR Project, the DOE NE Fast Reactor Program resumed support of the software with the goal of building and maintaining software infrastructure that can enable commercial-grade dedication of SPCA-ANL by an end user. Version 1.0, the first external release of SPCA-ANL, was generated in June 2024. This report summarizes the development and maintenance activities completed for SPCAANL in FY2025. This year’s work was focused on improving quality and usability of the code. The provisional Software Quality Assurance (SQA) program has been established and was used to test the procedures for infrastructure improvements, code development, bug fixes, and code releases, as described in the following sections of this report. A code Version 1.0.1 was released in FY25, as described in Chapter 4.
97 MATHEMATICS AND COMPUTING↗
Assurance Issues in Developing AI/ML Components (and their Standards) for Civil Aviation
Standards development activities require a keen and deep understanding of the problem being solved by the standard as well as the technologies being deployed in any reference implementation of the solution. It is important to understand the mechanisms and limits of the fundamental, underlying science of implementation and verification technologies used to realize and assure systems. We need to understand the limits of what current process and metrics can provide with respect to new technologies. US leadership is important in this endeavor, and it is vital that we have a measured approach that yields sound results. We wish to start with simple, well-defined, non-safety critical applications and then progress to functions which have (1) clearly defined requirements, (2) means of checking the answer/output, and (3) means of intervention and mitigation of incorrect answers/outputs.
Aviation Safety↗
Product assurance policies and procedures for flight dynamics software development
The product assurance policies and procedures necessary to support flight dynamics software development projects for Goddard Space Flight Center are presented. The quality assurance and configuration management methods and tools for each phase of the software development life cycles are described, from requirements analysis through acceptance testing; maintenance and operation are not addressed.
Perry, Sandra↗
Fuel Quality Assurance Research and Development and Impurity Testing in Support of Codes and Standards [Slides]
Abstract not provided.
08 HYDROGEN↗
International Cooperation on Model Based Development for Spaceflight Assurance: The Trilateral Assurance CubeSat (TACS) Test Case
Explore the source record for details and available documents.
Model Based System Engineering↗
Development of TID Hardness Assurance Methodologies to Capitalize on Statistical Radiation Environment Models
We develop methods for bounding part-to-part variation in TID data. When used in conjunction with statistical radiation environment models, these methods allow development of RHA that deliver estimated piece part reliability for any desired confidence level, moving beyond risk avoidance methodologies based on radiation design margin. Two methods are developed, and their results compared for realistic data.
Total Ionizing Dose↗
Development of TID Hardness Assurance Methodologies to Capitalize on Statistical Radiation Environment Models
We develop methods for bounding part-to-part variation in TID data. When used in conjunction with statistical radiation environment models, these methods allow development of RHA that deliver estimated piece part reliability for any desired confidence level, moving beyond risk avoidance methodologies based on radiation design margin. Two methods are developed, and their results compared for realistic data.
Total ionizing dose↗
Overview of the OECD-NEA Working Party on International Nuclear Data Evaluation Cooperation (WPEC)
The OECD Nuclear Energy Agency (NEA) Working Party on International Nuclear Data Evaluation Cooperation (WPEC) was established in 1989 to facilitate collaboration in nuclear data activities. Over its thirty year history, different Subgroups have been created to address topics in nearly every aspect of nuclear data, including: experimental measurements, evaluation, validation, model development, quality assurance of databases and the development of software tools. WPEC has recently completed activities on fission yield evaluation, the general nuclear database structure (GNDS) to replace the ENDF-6 format, methods to provide feedback to evaluation, studies of specific capture cross sections, new methods in thermal scattering kernel evaluation and the Collaborative International Evaluated Library Organisation (CIELO) Pilot Project. Ongoing activities in GNDS application programming interface (API) development, methods for covariance evaluation and quality assurance in nuclear data validation using the International Criticality Safety Benchmark Evaluation Project (ICSBEP) database are complemented by the work of two Expert Groups that oversee the High-Priority Request List (HPRL) for Nuclear Data and the continuous development of the GNDS. New activities on the use of integral experiments for nuclear data validation and adjustment, as well as the use of the Shielding Integral Benchmark Archive and Database (SINBAD) for validation have begun and will be coordinated alongside future Subgroups. After three decades we will review the status of WPEC, how it integrates other collections and activities organised by the NEA and how it dovetails with the initiatives of the IAEA and other bodies to effectively coordinate international activities in nuclear data.
73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗
Application of Objectives-Driven Assurance Cases to System Development in an Evolving Acquisition Model
System properties such as “safety” and “dependability” cannot, in practice, be proven, and must be argued in an “assurance case” aimed at supporting risk-acceptance decisions that have to be made by system acquirers and/or regulatory authorities. The paper is concerned with applications of the “assurance case” idea early in design and development of new systems, when (apart from dedicated testing) the only available operating experience information derives from previous (non-identical) systems. Much of the discussion is based on an evolving acquisition model at the US National Aeronautics and Space Administration; previously, most major systems were developed in-house, but some major systems will now be developed by and acquired from commercial providers. Key points discussed include the following. (1) By promoting a particular kind of focused discussion between acquirers and providers, the use of assurance cases should be particularly valuable under the new acquisition model. (2) In principle, objectives-driven (sometimes called “performance-based”) approaches to assurance of performance have significant advantages in cases where they are applicable. (3) For truly novel systems, completeness of the safety analysis is a significant issue; it is important for the assurance case to include a commitment by the provider (or applicant) to seriously pursue analysis of operating experience, so that previously unrecognized hazards can be identified and addressed. (4) Inquiries into major accidents often point to deficiencies in management oversight in all parts of the life cycle; management processes need to be addressed in the formulation and the implementation of an assurance case. Under the new acquisition model, these considerations imply a serious reconsideration of the way in which the development process is managed by both providers and acquirers.
Objectives-driven↗
APPLICATION OF OBJECTIVES-DRIVEN ASSURANCE CASES TO SYSTEM DEVELOPMENT IN AN EVOLVING ACQUISITION MODEL
System properties such as “safety” and “dependability” cannot, in practice, be proven, and must be argued in an “assurance case” aimed at supporting risk-acceptance decisions that have to be made by system acquirers and/or regulatory authorities. The paper is concerned with applications of the “assurance case” idea early in design and development of new systems, when (apart from dedicated testing) the only available operating experience information derives from previous (non-identical) systems. Much of the discussion is based on an evolving acquisition model at the US National Aeronautics and Space Administration; previously, most major systems were developed in-house, but some major systems will now be developed by and acquired from commercial providers. Key points discussed include the following. (1) By promoting a particular kind of focused discussion between acquirers and providers, the use of assurance cases should be particularly valuable under the new acquisition model. (2) In principle, objectives-driven (sometimes called “performance-based”) approaches to assurance of performance have significant advantages in cases where they are applicable. (3) For truly novel systems, completeness of the safety analysis is a significant issue; it is important for the assurance case to include a commitment by the provider (or applicant) to seriously pursue analysis of operating experience, so that previously unrecognized hazards can be identified and addressed. (4) Inquiries into major accidents often point to deficiencies in management oversight in all parts of the life cycle; management processes need to be addressed in the formulation and the implementation of an assurance case. Under the new acquisition model, these considerations imply a serious reconsideration of the way in which the development process is managed by both providers and acquirers.
99 GENERAL AND MISCELLANEOUS↗
Application of Objectives-Driven Assurance Cases to System Development in an Evolving Acquisition Model
System properties such as “safety” and “dependability” cannot, in practice, be proven, and must be argued in an “assurance case” aimed at supporting risk-acceptance decisions that have to be made by system acquirers and/or regulatory authorities. The paper is concerned with applications of the “assurance case” idea early in design and development of new systems, when (apart from dedicated testing) the only available operating experience information derives from previous (non-identical) systems. Much of the discussion is based on an evolving acquisition model at the US National Aeronautics and Space Administration; previously, most major systems were developed in-house, but some major systems will now be developed by and acquired from commercial providers. Key points discussed include the following. (1) By promoting a particular kind of focused discussion between acquirers and providers, the use of assurance cases should be particularly valuable under the new acquisition model. (2) In principle, objectives-driven (sometimes called “performance-based”) approaches to assurance of performance have significant advantages in cases where they are applicable. (3) For truly novel systems, completeness of the safety analysis is a significant issue; it is important for the assurance case to include a commitment by the provider (or applicant) to seriously pursue analysis of operating experience, so that previously unrecognized hazards can be identified and addressed. (4) Inquiries into major accidents often point to deficiencies in management oversight in all parts of the life cycle; management processes need to be addressed in the formulation and the implementation of an assurance case. Under the new acquisition model, these considerations imply a serious reconsideration of the way in which the development process is managed by both providers and acquirers.
99 GENERAL AND MISCELLANEOUS↗
Developing a Nuclear Quality Assurance Compliant Design Methodology for Neutronic Analysis of Xe-100 Design
The primary objective of this work is to develop a design methodology compliant with nuclear quality assurance standards for the Xe-100 neutronic design verification studies. To achieve this, a Monte Carlo model of the Xe-100 reactor was constructed using the exclusion principle, transformation technique, and universe-based level specification following Idaho National Laboratory (INL) NQA level-1 compliant standards and an NQA-1 compliant version of MCNP6. The model encompasses the entire reactor core structures, including the upper plenum, core region, and lower plenum sections, along with all sub-components. The active core section was represented using the spectral regions, each comprising a particular fuel composition and temperature averaged over the considered zone, calculated by X-energy using Very Superior Old Programs (VSOP). Additionally, a component-wise temperature map was implemented into the model, not only for the core region but also for the structural components. Temperature-dependent cross-section libraries, along with thermal scattering law libraries, generated using INL NQA-1 compliant version of NJOY21, were utilized for each isotope in the burnt fuel and the structural materials. Furthermore, the volume of each modeled component was estimated using a stochastic approach with the ray tracing method in MCNP and criticality calculations were performed.
22 GENERAL STUDIES OF NUCLEAR REACTORS↗
The ERSDT Software Quality Assurance Plan Practices and Development Environment Setup for RASCAL 5
This document includes the information pertaining to the practices of the Emergency Response Software Development Team (ERSDT) for the RASCAL software project. The content includes information regarding: 1) Software Quality Assurance. 2) Project Management. 3) Configuration Management. 4) Development Standards. 5) Third-Party Software. 6) Verification and Validation. The information contained in this report is considered living documentation. The information contained in this report was assembled from multiple documents and content management systems.
97 MATHEMATICS AND COMPUTING↗
Demonstrating Assurance of Model-Based Fault Diagnosis Systems on an Operational Mission
Developers of robotic scientific and commercial spacecraft are trending towards use of onboard autonomous capabilities for responding quickly to dynamic environments and rapidly changing situations. These capabilities need to know the state of the spacecraft’s health. Model-based fault diagnosis (MBFD) is an approach to estimating health by continuously verifying accurate behavior and diagnosing off-nominal behavior. Proper functioning of MBFD depends on 1) the quality of the diagnostic system model that is analyzed and compared to commands and onboard measurements to estimate a system’s health state, and 2) the correct functionality of the diagnosis engine interrogating the model and comparing its analyses to observed system behavior. Our goal is to develop Verification and Validation (V&V) techniques for MBFD to provide future missions sufficient confidence in its functionality and performance to deploy it on the systems they develop. Our work has been focused on infusing the techniques we developed earlier to an operational mission. First, we are constructing diagnostic models of a spacecraft attitude control system and updating our diagnostic engine so they can be demonstrated aboard the Arcsecond Space Telescope Enabling Research in Astrophysics (ASTERIA) mission, an operational spacecraft for which experiments in autonomy are being planned and executed, using the V&V techniques we have previously developed to assure they are both correct and complete. Since it is nearing the end of its life, ASTERIA provides a unique opportunity to demonstrate MBFD since the monitored components are expected to fail. Our demonstration will give system developers additional confidence to make timely, informed MBFD deployment decisions. Second, we will be completing performance assessments of the diagnostic engine/diagnostic model ensemble both on the flight system and ground-based testbeds to gain confidence in MBFD’s ability to run successfully in a spacecraft’s resource-constrained environment without adversely affecting other on-board activities. Finally, we are capturing our experience in preparing this demonstration in a set of checklists and guidance documents. Current practice includes high-level institutional guidance documents and standards, but at a high level of abstraction that does not necessarily address specific MBFD concerns. The purpose of the new checklists is to provide future mission developers clear, unambiguous, procedure-oriented guidance on assuring MBFD. This paper describes our work in these areas. For the first area, we describe the diagnostic models and updated diagnostic engine that will be used for the on-board demonstration. We describe how the V&V techniques we developed earlier are used to assure model and engine correctness and completeness. For the second area, we identify the performance measurement and assessment techniques used to characterize the diagnostic engine and diagnostic models, and discuss the effect of measured performance on overall mission operation. Finally, we present the checklist and guidance documents and describe how they meet the goals of providing system developers with clear, unambiguous, procedure-oriented guidance on MBFD assurance. We show how the techniques we have developed map into those artifacts.
Nikora, Allen↗
Developing A Dependable Multi-Agent Rover Swarm Using cFS
The future of space exploration lies in cooperative autonomous systems. Ensuring their high integrity remains a challenge. The Robust Software Engineering group at NASA Ames Research Center has been developing the Troupe project to explore the challenges with developing and assuring high integrity of cooperative autonomous robotic systems. In particular, Troupe aims to develop a swarm of autonomous rovers capable of mapping unknown terrain and assure their high integrity using the advanced V&V tools developed in the group. In this paper, we present the evolution of the design of Troupe. We focus on the lessons learned in developing and assuring the rover swarm using core Flight System (cFS). In particular, we discuss the benefits and challenges in applying model-based development to develop the rover swarm.
space systems↗
Developing A Dependable Multi-Agent Rover Swarm Using cFS
The future of space exploration lies in cooperative autonomous systems. Ensuring their high integrity remains a challenge. The Robust Software Engineering group at NASA Ames Research Center has been developing the Troupe project to explore the challenges with developing and assuring high integrity of cooperative autonomous robotic systems. In particular, Troupe aims to develop a swarm of autonomous rovers capable of mapping unknown terrain and assure their high integrity using the advanced V&V tools developed in the group. In this paper, we present the evolution of the design of Troupe. We focus on the lessons learned in developing and assuring the rover swarm using core Flight System (cFS). In particular, we discuss the benefits and challenges in applying model-based development to develop the rover swarm.
space systems↗
Application of Risk Informed Decision Making to Highly Reliable Three Dimensionally Woven Thermal Protection System for Mars Sample Return
The NASA Risk Informed Decision Making process is used to assess a trade space of three dimensionally woven thermal protection systems for application to the Mars Sample Return Earth Entry Vehicle. Candidate architectures are assessed based on mission assurance, technical development, cost, and schedule risk. Assessment methodology differed between the architectures, utilizing a four-point quantitative scale for mission assurance and technical development and highly tailored PERT techniques for cost and schedule. Risk results are presented, in addition to a review of RIDM effectiveness for this application.
Needels, J.↗