Search NASA⌕ Search

SEARCH · Search NASA

Results for “assurance case”

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 73 records · Page 4

The Friendly Argument Notation (FAN)

This document defines and explains through examples the Friendly Argument Notation (FAN). FAN builds on previous work investigating text-based ways to express arguments [2, 3]. Its primary intended use is for creating and evaluating arguments about safety-critical systems, especially the types of arguments common within safety and assurance cases [4], but nothing in its design constrains its use to that domain. Compared to existing notations commonly used within this domain (for example [6]), FAN corresponds more closely to traditional argument concepts (for example [1]), allows greater flexibility in expression, provides for including counter-arguments, and requires less knowledge of computer-science-specific concepts. Only time and use will determine how beneficial these differences are in practice. This paper concentrates on showing how FAN looks to someone who is using it manually to develop or assess arguments. A later document will concentrate on providing the information necessary for software tools to be created for FAN.

arugment↗

Software assurance of autonomous spacecraft control

The work described addresses assurance of a planning and execution software system being added to an in-orbit CubeSat to demonstrate autonomous control of that spacecraft. Our focus was on how to develop assurance of the correct operation of the added software in its operational context, our approach to which was to use an assurance case to guide and organize the information involved.

Bocchino, Robert↗

Evolution of NASA’s Nuclear Flight Safety Program to Meet Changing Needs

Over the past 4 years, the United States (U.S.) Government has issued several new National policies that fundamentally change the approach to nuclear flight safety for aerospace applications, including the complete revision of the Federal policy for handling launch of spacecraft containing space nuclear systems. In response, the National Aeronautics and Space Administration (NASA) is updating its nuclear flight safety program while still maintaining consistency with other Federal policies, international conventions, and NASA’s own policies. To achieve this evolution, NASA is factoring in an objectives-driven and assurance case mindset to develop a risk-informed and performance-based program. NASA and others have successfully applied this mindset in other disciplines and contexts and it is being pursued here via broad cooperation within NASA and with external stakeholders. This paper will briefly describe how the NASA nuclear flight safety program is evolving to meet these changing needs.

NASA↗

The Friendly Argument Notation (FAN): 2023 Version

This document constitutes the official description of the current iteration of the Friendly Argument Notation (FAN). This new version provides several enhancements to the original 2020 instantiation, while maintaining essential compatibility with it. Specifically, the new version enables distinguishing between deductive and non-deductive arguments, removes the requirement for always providing an explicit statement of reasoning, and relaxes the rules for when labels may be used. The primary intended use of FAN is unchanged: creating and evaluating arguments about safety-critical systems, specifically the types of arguments common within safety and assurance cases.

language↗

Unlocking the Spacecraft and Human Habitat Microbiome to Enable the Next Generation of Space Exploration

Planetary protection is the discipline that prevents harmful contamination of the solar system during exploration activities. The current international guidelines and NASA policy addressing biological contamination on spacecraft surfaces contains prescriptive guidelines of spore requirements (e.g., 300 spores/m2, 5×105 spores per spacecraft) applicable to spacecraft bound for Mars. To verify these requirements spacecraft engineers sample spacecraft surfaces throughout the assembly, test and launch operations phase of the mission using damp water cotton swabs and polyester wipes. After sampling, the potential biological contamination is enumerated using a series of traditional microbiology techniques to include sonication, heat shocking at 80°C for 15min to select for spores, and growth on tryptic soy agar at 32°C for 72 hours. To enable crewed missions to Mars and robotic exploration of the Ocean Worlds a risk informed decision making / performance-based approach to assess biological contamination offers a promising solution in the trade space. Recognizing the need for a performance-based approach, NASA’s new Planetary Protection policies now incorporate the agility for missions to be able to leverage a performance or prescriptive approach. One of top contenders in the option space is a coupled quantitative, descriptive and functional based approach to be able to assess the quantity, types and capabilities of the biological contamination present on spacecraft surfaces. A tailored, mission by mission assurance case could then be formulated by building an argument around the target body, projected capabilities surrounding the types of organisms their potential for survival and proliferation, and ability to be transported on the target body to contaminate an area of biological interest. A performance-based requirement would then be used to demonstrate the mission’s compliance in protecting the planetary environment safety objectives. This symposium talk will showcase the background and need case for NASA to develop such a capability as well as provide an update on the efforts underway in developing a transparent and responsible performance-based approach to biological contamination assessments on spacecraft surfaces.

Habitat Microbiome↗

Robotic and Crewed Mars Missions Increasing the Demand for Planetary Protection Technology Needs

Planetary protection (PP) policy seeks to avoid harmful contamination by limiting biological and relevant organic contamination from spacecraft as well as preventing adverse changes to Earth’s biosphere when extraterrestial samples are brought back to Earth. The PP policy at NASA was updated in 2021 (NPR 8715.24) and 2022 (NASA-STD-8719.27) to enable missions by expanding the decades old prescriptive requirements to allow for an option of adopting performance-based requirements that are objectivesdriven, risk-informed and case-assured. In parallel, the final PP knowledge gap workshop was completed representing the international consensus on the key areas to be considered in developing crew PP policy. These knowledge gaps focused on key technology development areas in 1) microbial and human health monitoring, 2) technical and operations needed for contamination control and 3) natural transport of contamination on Mars. As robotic missions start to implement performance-based approaches and research and technology efforts commence to inform crew policy the demand for data quality driven verification and validation in relevant space environments. Examples of the types of testing that is envisioned includes test as you fly validation and verification of decontamination systems in a relevant on-orbit and Mars environment, developing lethality curves of terrestrial organisms to further our understanding of the biocidal impacts of Mars and the space environment, and particle transport model validation and verification. Thus, the PP discipline has identified the need for groundbased space environments to perform preliminary testing as validation and verification of flight systems and to advance the technology readiness level prior to further testing on-orbit or lunar environments to prepare for Mars.

J. Nick Benardini↗

Robotic and Crewed Mars Missions Increasing the Demand for Planetary Protection Technology Needs

Planetary protection (PP) policy seeks to avoid harmful contamination by limiting biological and relevant organic contamination from spacecraft as well as preventing adverse changes to Earth’s biosphere when extraterrestrial samples are brought back to Earth. The PP policy at NASA was updated in 2021 (NPR 8715.24) and 2022 (NASA-STD-8719.27) to enable missions by expanding the decades old prescriptive requirements to allow for an option of adopting performance-based requirements that are objectives-driven, risk-informed and case-assured. In parallel, the final PP knowledge gap workshop was completed representing the international consensus on the key areas to be considered in developing crew PP policy. These knowledge gaps focused on key technology development areas in 1) microbial and human health monitoring, 2) technical and operations needed for contamination control and 3) natural transport of contamination on Mars. As robotic missions start to implement performance-based approaches and research and technology efforts commence to inform crew policy the demand for data quality driven verification and validation in relevant space environments. Examples of the types of testing that is envisioned includes test as you fly validation and verification of decontamination systems in a relevant on-orbit and Mars environment, developing lethality curves of terrestrial organisms to further our understanding of the biocidal impacts of Mars and the space environment, and particle transport model validation and verification. Thus, the PP discipline has identified the need for ground-based space environments to perform preliminary testing as validation and verification of flight systems and to advance the technology readiness level prior to further testing on-orbit or lunar environments to prepare for Mars.

J Nick Benardini↗

Evolution of NASA’s Nuclear Flight Safety Program to Infuse Risk Leadership and Assurance Framework Concepts

In recent years, the United States (U.S.) Government has issued several new National policies that fundamentally change the approach to nuclear flight safety for aerospace applications, including the complete revision of the Federal policy for handling launch of spacecraft containing space nuclear systems. In response, the National Aeronautics and Space Administration (NASA) is updating its nuclear flight safety program while still maintaining consistency with other Federal policies, international conventions, and NASA’s own policies. To achieve this evolution, NASA is factoring in an objectives-driven and assurance case mindset to develop a risk-informed and performance-based program. NASA and others have successfully applied this mindset in other disciplines and contexts and it is being pursued here via broad cooperation within NASA and with external stakeholders. This paper will briefly describe how the NASA nuclear flight safety program is evolving to meet these changing needs.

Matthew J. Forsbacka↗

Towards a Formal Basis for Modular Safety Cases

Safety assurance using argument-based safety cases is an accepted best-practice in many safety-critical sectors. Goal Structuring Notation (GSN), which is widely used for presenting safety arguments graphically, provides a notion of modular arguments to support the goal of incremental certification. Despite the efforts at standardization, GSN remains an informal notation whereas the GSN standard contains appreciable ambiguity especially concerning modular extensions. This, in turn, presents challenges when developing tools and methods to intelligently manipulate modular GSN arguments. This paper develops the elements of a theory of modular safety cases, leveraging our previous work on formalizing GSN arguments. Using example argument structures we highlight some ambiguities arising through the existing guidance, present the intuition underlying the theory, clarify syntax, and address modular arguments, contracts, well-formedness and well-scopedness of modules. Based on this theory, we have a preliminary implementation of modular arguments in our toolset, AdvoCATE.

Safety↗

Overarching Properties as Means of Compliance: An Industrial Case Study

The Overarching Properties (OPs) have been created by an inter-national working group and are being evaluated by the National Aeronautics and Space Administration (NASA), the Federal Aviation Administration (FAA), industry, and other certifying agencies in an effort to streamline certification processes. Their intent is to facilitate the use of alternative approaches and to al-low flexibility to combine the system, software, and complex hardware certification. The hope is that the FAA may eventually establish an Advisory Circular that offers the OPs as a Means of Compliance (MoC) for software approval (and eventually systems and hardware) by showing the product possesses the three OPs: Intent (specification of the intended behavior), Correctness (implementation of the intended behavior) and Innocuity (safety of unintended behavior). In the certification community, there is still a concern about the practicability of using such high level properties in certification. This paper aims to address that concern by showing possession of the OPs in an industrial case study using assurance arguments. The two main contributions of this paper are: a certification process based on OPs as Means of Compliance, and a certification argument for an on-board physical model of an UAV, as industrial example. We pro-pose a hybrid approach for the certification process that combines OPs with existing certification standards. Thus, OPs can be used for parts of a system that uses technologies that are not supported by current standards or for which existing standards require additional effort without commensurate additional safety assurance.

certification↗

Dynamic Safety Cases for Through-Life Safety Assurance

We describe dynamic safety cases, a novel operationalization of the concept of through-life safety assurance, whose goal is to enable proactive safety management. Using an example from the aviation systems domain, we motivate our approach, its underlying principles, and a lifecycle. We then identify the key elements required to move towards a formalization of the associated framework.

Dynamic Safety Case↗

Retrospectively Documenting Satisfaction of the Overarching Properties: An Exploratory Prototype

Software-intensive aviation systems are typically developed in accordance with recognized development process, safety analysis, and software development standards such as SAE ARP4754A, SAE ARP4761, and RTCA DO-178C. Efforts to streamline assurance processes and make them flexible enough to handle future assurance challenges have produced the Overarching Properties (OPs) for airworthiness approval. Each of the three OPs is a property systems must possess to be certifiable. There is no mandated means of documenting possession of the OPs. To explore possible means, we have prepared retrospective documentation showing that a specimen software system possesses the OPs. The specimen system, Safeguard, enforces geofencing restrictions on unmanned aerial vehicles. Our OP-possession case for its airborne component comprises eight arguments in the Goal Structuring Notation (GSN): a main argument for each OP and five cross-cutting auxiliary arguments. We present this argument as an example for discussion and further research, e.g., into means of assessing OP possession.

safety case↗

Human Spaceflight Trajectory Operations: A Case Study from STS-132/ULF4

Prior to the launch of the STS-132/ULF4 mission, the International Space Station (ISS) Flight Control Team was alerted to the approach of a space debris with a predicted time of closest approach approximately 1 hr after Space Shuttle docking. As a result, the ISS team considered performing a collision avoidance maneuver prior to the Space Shuttle s approach. The purpose of this presentation will be to use this case study to illustrate best practices of the human spaceflight trajectory operations team. The presentation will begin with an overview of the roles of the real-time ISS and Space Shuttle trajectory flight control teams. Then, the STS-132/ULF4 case study will be used to illustrate the issues and lessons learned involved in performing Space Shuttle rendezvous maneuver planning and execution. Specific elements of the STS-132 Space Shuttle rendezvous maneuver profile that can be used to provide mission assurance in cases of trajectory uncertainty will be described and discussed. Additionally, this case study will be used to provide context for identifying lessons learned in an operational environment that requires technical and decision-making coordination between two control center teams with two potentially maneuvering space vehicles.

Cutri-Kohart, Rebecca↗

A Primer on Argument (Overarching Properties Edition)

The purpose of this document is to establish for the Overarching Properties Working Group (OPWG) a common understanding of the terms, concepts, principles, and uses of argument. It emphasizes the practical over the theoretical and the simple over the complicated.

argument↗