Search NASA⌕ Search

SEARCH · Search NASA

Results for “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.

At least 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Software Safety Assurance of Programmable Logic

Programmable Logic (PLC, FPGA, ASIC) devices are hybrids - hardware devices that are designed and programmed like software. As such, they fall in an assurance gray area. Programmable Logic is usually tested and verified as hardware, and the software aspects are ignored, potentially leading to safety or mission success concerns. The objective of this proposal is to first determine where and how Programmable Logic (PL) is used within NASA and document the current methods of assurance. Once that is known, raise awareness of the PL software aspects within the NASA engineering community and provide guidance for the use and assurance of PL form a software perspective.

Berens, Kalynnda↗
NASA NTRS2004

Software Quality Assurance Metrics

Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

McRae, Kalindra A.↗
NASA NTRS2006

Safety and Mission Assurance Knowledge Management Retention: Managing Knowledge for Successful Mission Operations

Knowledge Management is a proactive pursuit for the future success of any large organization faced with the imminent possibility that their senior managers/engineers with gained experiences and lessons learned plan to retire in the near term. Safety and Mission Assurance (S&MA) is proactively pursuing unique mechanism to ensure knowledge learned is retained and lessons learned captured and documented. Knowledge Capture Event/Activities/Management helps to provide a gateway between future retirees and our next generation of managers/engineers. S&MA hosted two Knowledge Capture Events during 2005 featuring three of its retiring fellows (Axel Larsen, Dave Whittle and Gary Johnson). The first Knowledge Capture Event February 24, 2005 focused on two Safety and Mission Assurance Safety Panels (Space Shuttle System Safety Review Panel (SSRP); Payload Safety Review Panel (PSRP) and the latter event December 15, 2005 featured lessons learned during Apollo, Skylab, and Space Shuttle which could be applicable in the newly created Crew Exploration Vehicle (CEV)/Constellation development program. Gemini, Apollo, Skylab and the Space Shuttle promised and delivered exciting human advances in space and benefits of space in people s everyday lives on earth. Johnson Space Center's Safety & Mission Assurance team work over the last 20 years has been mostly focused on operations we are now beginning the Exploration development program. S&MA will promote an atmosphere of knowledge sharing in its formal and informal cultures and work processes, and reward the open dissemination and sharing of information; we are asking "Why embrace relearning the "lessons learned" in the past?" On the Exploration program the focus will be on Design, Development, Test, & Evaluation (DDT&E); therefore, it is critical to understand the lessons from these past programs during the DDT&E phase.

Johnson, Teresa A.↗
NASA NTRS2010

GSFC Safety and Mission Assurance Organization

This viewgraph presentation reviews NASA Goddard Space Flight Center's approach to safety and mission assurance. The contents include: 1) NASA GSFC Background; 2) Safety and Mission Assurance Directorate; 3) The Role of SMA-D and the Technical Authority; 4) GSFC Mission assurance Requirements; 5) GSFC Systems Review Office (SRO); 6) GSFC Supply Chain Management Program; and 7) GSFC ISO9001/AS9100 Status Brief.

Kelly, Michael P.↗
NASA NTRS2011

Asset Analysis and Operational Concepts for Separation Assurance Flight Testing at Dryden Flight Research Center

A preliminary survey of existing separation assurance and collision avoidance advancements, technologies, and efforts has been conducted in order to develop a concept of operations for flight testing autonomous separation assurance at Dryden Flight Research Center. This effort was part of the Unmanned Aerial Systems in the National Airspace System project. The survey focused primarily on separation assurance projects validated through flight testing (including lessons learned), however current forays into the field were also examined. Comparisons between current Dryden flight and range assets were conducted using House of Quality matrices in order to allow project management to make determinations regarding asset utilization for future flight tests. This was conducted in order to establish a body of knowledge of the current collision avoidance landscape, and thus focus Dryden s efforts more effectively towards the providing of assets and test ranges for future flight testing within this research field.

Costa, Guillermo J.↗
NASA NTRS2005

Safety and Mission Assurance Performance Metric

The safety and mission assurance (S&MA) performance metric is a method that provides a process through which the managers of a large, complex program can readily understand and assess the accepted risk, the problems, and the associated reliability of the program. Conceived for original use in helping to assure the safety and success of the International Space Station (ISS) program, the S&MA performance metric also can be applied to other large and complex programs and projects. The S&MA-performance-metric data products comprise one or more tables (possibly also one or more graphs) that succinctly display all of the information relevant (and no information that is irrelevant) to management decisions that must be made to assure the safety and success of a program or project, thereby facilitating such decisions.

Holsomback, Jerry↗
NASA NTRS2011

Evaluation of High Density Air Traffic Operations with Automation for Separation Assurance, Weather Avoidance and Schedule Conformance

In this paper we discuss the development and evaluation of our prototype technologies and procedures for far-term air traffic control operations with automation for separation assurance, weather avoidance and schedule conformance. Controller-in-the-loop simulations in the Airspace Operations Laboratory at the NASA Ames Research Center in 2010 have shown very promising results. We found the operations to provide high airspace throughput, excellent efficiency and schedule conformance. The simulation also highlighted areas for improvements: Short-term conflict situations sometimes resulted in separation violations, particularly for transitioning aircraft in complex traffic flows. The combination of heavy metering and growing weather resulted in an increased number of aircraft penetrating convective weather cells. To address these shortcomings technologies and procedures have been improved and the operations are being re-evaluated with the same scenarios. In this paper we will first describe the concept and technologies for automating separation assurance, weather avoidance, and schedule conformance. Second, the results from the 2010 simulation will be reviewed. We report human-systems integration aspects, safety and efficiency results as well as airspace throughput, workload, and operational acceptability. Next, improvements will be discussed that were made to address identified shortcomings. We conclude that, with further refinements, air traffic control operations with ground-based automated separation assurance can routinely provide currently unachievable levels of traffic throughput in the en route airspace.

Prevot, Thomas↗
NASA NTRS2012

Safety Assurance in NextGen

The generation of minimum operational, safety, performance, and interoperability requirements is an important aspect of safely integrating new NextGen components into the Communication Navigation Surveillance and Air Traffic Management (CNS/ATM) system. These requirements are used as part of the implementation and approval processes. In addition, they provide guidance to determine the levels of design assurance and performance that are needed for each element of the new NextGen procedures, including aircraft, operator, and Air Navigation and Service Provider. Using the enhanced Airborne Traffic Situational Awareness for InTrail Procedure (ATSA-ITP) as an example, this report describes some limitations of the current process used for generating safety requirements and levels of required design assurance. An alternative process is described, as well as the argument for why the alternative can generate more comprehensive requirements and greater safety assurance than the current approach.

HarrisonFleming, Cody↗
NASA NTRS2012

Surveillance and Datalink Communication Performance Analysis for Distributed Separation Assurance System Architectures

This study investigates the effects of two technical enablers: Automatic Dependent Surveillance - Broadcast (ADS-B) and digital datalink communication, of the Federal Aviation Administration s Next Generation Air Transportation System (NextGen) under two separation assurance (SA) system architectures: ground-based SA and airborne SA, on overall separation assurance performance. Datalink performance such as successful reception probability in both surveillance and communication messages, and surveillance accuracy are examined in various operational conditions. Required SA performance is evaluated as a function of subsystem performance, using availability, continuity, and integrity metrics to establish overall required separation assurance performance, under normal and off-nominal conditions.

Chung, William W.↗
NASA NTRS2012

Design and Evaluation of Nextgen Aircraft Separation Assurance Concepts

To support the development and evaluation of future function allocation concepts for separation assurance systems for the Next Generation Air Transportation System, this paper presents the design and human-in-the-loop evaluation of three feasible function allocation concepts that allocate primary aircraft separation assurance responsibilities and workload to: 1) pilots; 2) air traffic controllers (ATC); and 3) automation. The design of these concepts also included rules of the road, separation assurance burdens for aircraft of different equipage levels, and utilization of advanced weather displays paired with advanced conflict detection and resolution automation. Results of the human-in-the-loop simulation show that: a) all the concepts are robust with respect to weather perturbation; b) concept 1 (pilots) had highest throughput, closest to assigned spacing, and fewest violations of speed and altitude restrictions; c) the energy of the aircraft during the descent phase was better managed in concepts 1 and 2 (pilots and ATC) than in concept 3 (automation), in which the situation awareness of pilots and controllers was lowest, and workload of pilots was highest. The paper also discusses further development of these concepts and their augmentation and integration with future air traffic management tools and systems that are being considered for NextGen.

Johnson, Walter↗
NASA NTRS2013

A Concept of Operations for an Integrated Vehicle Health Assurance System

This document describes a Concept of Operations (ConOps) for an Integrated Vehicle Health Assurance System (IVHAS). This ConOps is associated with the Maintain Vehicle Safety (MVS) between Major Inspections Technical Challenge in the Vehicle Systems Safety Technologies (VSST) Project within NASA s Aviation Safety Program. In particular, this document seeks to describe an integrated system concept for vehicle health assurance that integrates ground-based inspection and repair information with in-flight measurement data for airframe, propulsion, and avionics subsystems. The MVS Technical Challenge intends to maintain vehicle safety between major inspections by developing and demonstrating new integrated health management and failure prevention technologies to assure the integrity of vehicle systems between major inspection intervals and maintain vehicle state awareness during flight. The approach provided by this ConOps is intended to help optimize technology selection and development, as well as allow the initial integration and demonstration of these subsystem technologies over the 5 year span of the VSST program, and serve as a guideline for developing IVHAS technologies under the Aviation Safety Program within the next 5 to 15 years. A long-term vision of IVHAS is provided to describe a basic roadmap for more intelligent and autonomous vehicle systems.

Hunter, Gary W.↗
NASA NTRS2016

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 (IVV) Program, with Software Assurance Research Program support, extracted FM architectures across the IVV portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IVV 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.

Fitz, Rhonda↗
NASA NTRS2016

Challenges in High-Assurance Runtime Verification

Safety-critical systems are growing more complex and becoming increasingly autonomous. Runtime Verification (RV) has the potential to provide protections when a system cannot be assured by conventional means, but only if the RV itself can be trusted. In this paper, we proffer a number of challenges to realizing high-assurance RV and illustrate how we have addressed them in our research. We argue that high-assurance RV provides a rich target for automated verification tools in hope of fostering closer collaboration among the communities.

Goodloe, Alwyn E.↗
NASA NTRS2015

Analysis of Aviation Safety Reporting System Incident Data Associated with the Technical Challenges of the System-Wide Safety and Assurance Technologies Project

The Aviation Safety Program (AvSP) System-Wide Safety and Assurance Technologies (SSAT) Project asked the AvSP Systems and Portfolio Analysis Team to identify SSAT-related trends. SSAT had four technical challenges: advance safety assurance to enable deployment of NextGen systems; automated discovery of precursors to aviation safety incidents; increasing safety of human-automation interaction by incorporating human performance, and prognostic algorithm design for safety assurance. This report reviews incident data from the NASA Aviation Safety Reporting System (ASRS) for system-component-failure- or-malfunction- (SCFM-) related and human-factor-related incidents for commercial or cargo air carriers (Part 121), commuter airlines (Part 135), and general aviation (Part 91). The data was analyzed by Federal Aviation Regulations (FAR) part, phase of flight, SCFM category, human factor category, and a variety of anomalies and results. There were 38 894 SCFM-related incidents and 83 478 human-factorrelated incidents analyzed between January 1993 and April 2011.

Withrow, Colleen A.↗
NASA NTRS2017

Assurance Arguments for the Non-Graphically-Inclined: Two Approaches

We introduce and discuss two approaches to presenting assurance arguments. One approach is based on a monograph structure, while the other is based on a tabular structure. In today's research and academic setting, assurance cases often use a graphical notation; however for people who are not graphically inclined, these notations can be difficult to read. This document proposes, outlines, explains, and presents examples of two non-graphical assurance argument notations that may be appropriate for non-graphically-inclined readers and also provide argument writers with freedom to add details and manipulate an argument in multiple ways.

Heavner, Emily↗
NASA NTRS2018

Quality Assurance Surveillance Tool Designed for SLS EM-1 Certificate of Flight Readiness

Exploration Mission-1 (EM-1) is an uncrewed mission that is launching on the Space Launch System (SLS) Block 1 vehicle. This is a critical flight test for the agency's human deep space exploration goals. Exploration Ground Systems (EGS) Quality (SA-F2) is responsible for providing Quality Assurance Surveillance Plans (QASPs) for NASA contracts and facilities. A QASP assures products and services are provided to EGS in accordance with the contract requirements. In order to encapsulate the multiple KSC Safety and Mission Assurance surveillance and audit activities that need to be accomplished specifically for EM-1 Certificate of Flight Reediness (CoFR), a QASP tool needed to be implemented. This tool would be able to intuitively track Work Authorization Documents (WADs) under development by Test Operations Support Contract (TOSC), reviewed and accepted WADs, Government Mandatory Inspection Points (GMIPs), Nonconformances (NCs), Material Review Board (MRB) Status, Corrective Actions, Alterations, Deviations, and Waivers for flight hardware and Ground Support Equipment (GSE). This would help ensure that all SLS EM-1 flight hardware and related GSE surveillances and requirements are being recognized and completed with zero constraints identified for the mission.

Morris, Patrick↗
NASA NTRS2017

Mission Assurance: A Model-Based Approach

The purpose of Safety and Mission Assurance (SMA) at NASA’s Jet Propulsion Laboratory is to ensure mission safety and success. As the complexity of technical systems increases, the tools, processes, and infrastructure used to facilitate SMA activities must evolve. A transition from a document-centric approach to a data-driven, model-based architecture is critical in allowing SMA efforts to grapple with complex system designs. This work describes how a sample subset of existing SMA processes can be executed in a model-based environment, while also describing ways in which a model-based architecture can further augment SMA efforts. One key aspect is supporting the complex interplay between the different SMA processes and the systems engineering effort to provide additional insight into the system from an SMA perspective. The proposed architecture for model-based mission assurance provides an avenue for assuring mission safety and success in increasingly complex systems.

Schreiner, Samuel S.↗