SEARCH · Engineering Papers

Results for “verification and validation”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 793 records · Page 44

All sources NASA NTRS DOE OSTI

NASA NTRS2019

Agile Approach to Assuring the Safety-Critical Embedded Software for NASA's Orion Spacecraft

Human-rated missions like NASA's Exploration Mission - 1 (EM-1) and the Orion Multi-Purpose Crew Vehicle are becoming exceedingly complex in terms of software's contribution to achieving mission objectives. The increasing complexity and inherent safety critical nature of the embedded flight software imposes a unique resource challenge to assurance providers responsible for affirming that the mission is going to fly safely. Another challenge NASA and other Government agencies are facing is that more and more software is being developed using an agile development methodology, which is divergent from the typical waterfall, iterative, and incremental development methodologies assurance providers generally observe in the development of safety-critical embedded software. Orion Independent Verification and Validation (IV&V) has addressed these challenges by providing focused assurance results of critical mission capabilities prioritized by a dynamic assessment of risk level. Prior to this approach, Orion IV&V evaluated areas of risk in much broader, and more static, terms. Due to the agile software development life cycle that Orion follows, IV&V findings were often reported months out of phase with the developer thereby imposing increased rework costs. As a result of evolving the approach to adding assurance on Orion, IV&V is able to incrementally deliver high-priority assurance conclusions and more impactful issues more in phase with the developer activities, thereby increasing the value of the findings to the project. The agile IV&V approach employed by the Orion IV&V team strives to achieve a cadence of delivery that matches the pace of development. This agile approach provides increased flexibility for the assurance provider to become more efficient in reporting assurance conclusions and issues. This paper and presentation will discuss the principles which drive the design of our approach, results to date, and stimulate thinking for groups looking to add assurance to software being developed using an agile methodology.

Justin Smith↗

NASA NTRS2018

IV&V Planning & Execution Initiative

Independent verification and validation (IV&V) is a systems engineering discipline which seeks to provide confidence that mission-critical software-dependent systems will operate safely and achieve all mission objectives. In order to optimize application of IV&V resources, it is necessary to identify specific assurance objectives that are most likely to reveal difficulty and therefore to increase confidence. Software assurance literature deals predominantly with the code itself. However, our experience is that the most significant software-related issues are discovered via analysis of other system artifacts such as operations concepts, requirements and design. Consequently, it is desirable to, when assessing risk and defining assurance objectives, consider all facets of the software system architecture. We describe in this presentation progress and lessons learned from an IV&V capability development initiative to enhance the IV&V project planning process using all available architecture information.

Risk↗

NASA NTRS2015

Proposal for a Sample Pilot Response Model

Regulations to establish operational and performance requirements for unmanned aircraft systems (UAS) are being developed by a consortium of government, industry and academic institutions. Those requirements will apply to the new detect and avoid (DAA) systems and other equipment necessary to integrate UAS with the National Airspace System (NAS) and are determined according to their contribution to the overall safety case for such an integration. In order to perform end-to-end verification and validation of DAA requirements, a committee accepted pilot response model is needed to emulate UAS pilots in closed-loop Monte Carlo fast-time simulations. This briefing focuses on background of the pilot model used in previous Airspace Concept Evaluation System studies, identification of strengths and weaknesses in that model, and proposals on model improvements. The briefing also looks to build consensus around a common architecture and assumptions for modeling the pilot for UAS DAA systems.

Santiago, Confesor↗

NASA NTRS2017

A Fuzzy Logic Approach for Separation Assurance and Collision Avoidance for Unmanned Aerial Systems

In the coming years, operations in low altitude airspace will vastly increase as the capabilities and applications of small Unmanned Aerial Systems (sUAS) continue to multiply. Therefore, solutions to managing sUAS in highly congested airspace must be explored. In this study, a Fuzzy Logic based approach was used to help mitigate the risk of collisions between aircraft using separation assurance and collision avoidance techniques. The system was evaluated for its effectiveness to mitigate the risk of mid-air collisions between aircraft. This system utilizes only current state information and can resolve potential conflicts without knowledge of intruder intent. The avoidance logic was verified using formal methods and shown to select the correct action in all instances. Additionally, the Fuzzy Logic Controllers were shown to always turn the vehicles in the correct direction. Numerical testing demonstrated that the avoidance system was able to prevent a mid-air collision between two sUAS in all tested cases. Simulations were also performed in a three-dimensional environment with a heterogenous fleet of sUAS performing a variety of realistic missions. Simulations showed that the system was 99.98 effective at preventing mid-air collisions when separation assurance was disabled (unmitigated case) and 100 effective when enabled (mitigated case).

Verification & Validation of a Fuzzy Logic Control↗

NASA NTRS2019

Flight Servicing of Robotic Refueling Mission 3

The Robotic Refueling Mission 3 (RRM3) payload launched aboard a SpaceX rocket en route to the International Space Station on December 5th, 2018. The Goddard Space Flight Center designed payload carried approximately 50 liters of liquid methane onboard, with a mission to demonstrate long term storage and transfer of the cryogenic fluid in microgravity. Kennedy Space Center (KSC) was tasked to design, fabricate, test, and operate a system equipped to fill an RRM3 dewar with liquid methane prior to launch. Though KSC has a rich history of fueling rockets and payloads, no such operations had previously been accomplished using liquid methane. As such, all of the hardware and processes had to be developed from scratch. The completed ground system design, along with the verification and validation testing will be outlined in this paper. Several challenges that were met and overcome during procurement of the high purity methane are described. In addition, budget restrictions prohibited fueling operations from occurring in traditional processing facilities. The unique and creative solutions which were required to maintain payload cleanliness during cryogenic servicing are also detailed.

Cryogenics↗

NASA NTRS2019

Flight Servicing of Robotic Refueling Mission 3

Thermal Conductivity↗

NASA NTRS2019

Flight Servicing of Robotic Refueling Mission 3

Cryogenics↗

NASA NTRS2016

V&V on a NASA Technology Demonstration Project: Low Density Supersonic Decelerator

Given their smaller budgets, but higher allowed risk posture, technology demonstration missions face different Verification and Validation (V&V) challenges than typical NASA missions. Despite these challenges, the Low Density Supersonic Decelerator (LDSD) project, managed by NASA’s Jet Propulsion Laboratory (JPL), has been extremely successful in testing new supersonic atmospheric decelerator technologies. A contribution to the project’s success is the unique V&V program that emphasized efficiency and flexibility. This paper will provide an overview of LDSD test objectives, Supersonic Flight Dynamics Tests (SFDT) performed so far, unique requirements structure and V&V processes implemented. The paper will focus on the V&V of the SFDT test architecture. Furthermore, lessons learned will also be presented at the end of the paper to aid future technology demonstration projects.

Murry, Michael L.↗

NASA NTRS2018

Study of Laminar-Turbulent Transition Modeled by Amplification Factor Transport Within the LAVA Solver

The Amplification Factor Transport (AFT) transition model proposed by Coder and Maughmer is implemented in the unstructured and curvilinear Reynolds-Averaged Navier-Stokes (RANS) solvers of the Launch Ascent and Vehicle Aerodynamics (LAVA) platform. It is coupled to the Spalart-Allmaras (SA) turbulence model through a modified intermittency variable. As part of the model verification and validation phase, laminar-turbulent transition is studied over 2D flat plates, wind turbine and general aviation airfoils, as well as a 3D inclined prolate spheroid and the JAXA Standard Model (JSM). This work will analyze the sensitivity of the results to grid refinement, grid paradigm, flow conditions and numerical schemes. The numerical efficiency of the unstructured and curvilinear solvers will be compared and convergence acceleration techniques will be explored to address a broad range of aerodynamics applications.

Denison, M. F.↗

NASA NTRS2018

Systems Health Monitoring and Prognostics Using Model Based Approach

In order to tackle and solve the prediction problem, it is essential to have awareness of the current state and health of the system, especially since it is necessary to perform condition-based predictions. To be able to accurately predict the future state of any system, it is required to possess knowledge of its current and future operations. Given models of the current and future system behavior, the general approach of model-based prognostics can be employed as a solution to the prior stated prediction problem. In case of electric aircrafts, computing remaining flying time is safety-critical, since an aircraft that runs out of power (battery charge) while in the air will eventually lose control leading to catastrophe. In order to tackle and solve the prediction problem, it is essential to have awareness of the current state and health of the system, especially since it is necessary to perform condition-based predictions. To be able to predict the future state of the system, it is also required to possess knowledge of the current and future operations of the vehicle. Our research approach is to develop a system level health monitoring safety indicator which runs estimation and prediction algorithms to estimate remaining useful life predictions at system as well as subsystem levels. Given models of the current and future system behavior, a general approach of model-based prognostics can be employed as a solution to the prediction problem and further for decision making. In addition a digital twin concept is being implemented in the framework to demonstrate verification and validation of developed algorithms.

Electronics Prognostics↗

NASA NTRS2019

Overview of Electric Propulsion Projects at NASA Glenn Research Center

NASA Glenn Research Center (GRC) is currently leading the development of multiple electric propulsion systems to flight readiness. The Advanced Electric Propulsion System is a 12.5 kW Hall thruster system that is being developed by the Solar Electric Propulsion Technology Demonstration Mission (SEP TDM) project, under the sponsorship of the Space Technology Mission Directorate. NASA's Evolutionary Xenon Thruster-Commercial (NEXT-C) is 7 kW class gridded ion thruster system that being developed under the sponsorship of the Science Mission Directorate. NASA GRC is also providing electric propulsion discipline support to the Power and Propulsion Element and the Double Asteroid Redirection Test (DART) missions, which will be the first applications for these technologies, respectively. Lower technology readiness level (TRL) projects are underway for applications including CubeSats, small spacecraft and Mars exploration vehicles. Under the sponsorship of the Small Spacecraft Technology Program, NASA GRC has performed numerous independent verification and validation tests of CubeSat class electric propulsion systems in support of a growing number of small US businesses that are developing these systems. Lastly, three technology development efforts focused on 100 kW EP strings led by Aerojet Rocketdyne, Ad Astra and MSNW were recently completed.

Smith, Bryan K.↗

NASA NTRS2019

Agile Approach to Assuring Software for NASA's Orion Spacecraft

Agile software development is prevalent throughout the Government, and NASA is no exception. NASA's Orion spacecraft is being developed to return Astronauts to the moon in the next 5 years, and the role of software in achieving the ambitious mission objectives has expanded dramatically in the last few decades. This presentation is the story of how the Independent Verification and Validation team for Orion adapted to the Agile approach that the Orion Program was using to develop the flight software. Consider attending this session if you are working with software developers utilizing Agile development approaches, or are interested in learning about Agile and Lean principles that could help improve communication within your own team.

Smith, Justin↗

NASA NTRS2019

Mars Small-Spacecraft Human Exploration Resource Prospector with Aero-braking (SHERPA): Demonstrating an End-to-End Mission to Phobos Distant Retrograde Orbit

This paper summarizes an end-to-end mission design concept exploring the feasibility of using small satellites together with aero-capture technology to achieve Mars orbit insertion, and subsequent injection into a Phobos-stabilized (or distant retrograde) orbit. The science and mission objectives are to carry out a survey of the mineralogy and morphology of Phobos, to answer basic questions concerning its origin and formation, to test the cohesiveness of Phobos regolith, and to search for potential landing sites for future human or robotic spacecraft. The Mars Small-Spacecraft Human Exploration Resource Prospector with Aero-braking (SHERPA) spacecraft is based on a combination flight-tested prototype vehicle and instruments, and first principle sizing of consumables. The resulting system is fitted with an inflatable aerodynamic decelerator to effect aero-capture into a Mars elliptical orbit, on its way to achieving Phobos orbit. A computational fluid dynamics tool is used to analyze the flow-field and identify potential hot spots during aerodynamic flight. This work advocates for the use of small satellites to test out technologies and operational concepts used in sustained human exploration of Mars, and to carry out scientific exploration of the Mars system. Consistent with a systems engineering approach, this work combines elements of the NASA Human Exploration and Operations Mission Directorate, the Space Technology Mission Directorate, and the Science Mission Directorate, and proposes a scenario for science acquisition, technology verification, trajectory validation, and in-situ resource exploration. We believe these type of missions are essential forerunners to human crewed missions to Mars.

Mission Design↗

NASA NTRS2019

Independent Optical Navigation Processing for the Osiris-Rex Mission Using the Goddard Image Analysis and Navigation Tool

The OSIRIS-REx mission to the asteroid(101955) Bennu heavily relies on optical navigation to provide relative state information between the asteroid and the spacecraft. These measurements enable determination of the spacecraft's orbit to the tight requirements needed to meet the science goals of the mission. In this document we describe the algorithms and techniques used by the Goddard independent verification and validation navigation effort to extract these measurements from the images taken by the spacecraft during the mission.We also demonstrate the capabilities of the techniques by showing the high accuracy of the results when used in an orbit determination solution.

Liounis, Andrew↗

NASA NTRS2019

Static Analysis Using Abstract Interpretation

Lecture about abstract interpretation. This lecture starts with a brief introduction to validation and verification using formal methods. It then demonstrates IKOS (Inference Kernel for Open Static Analyzers), a static analyzer for C/C++ based on Abstract Interpretation. Then, it describes in details the theory of Abstract Interpretation, a mathematical framework to over-approximate the reachable states of a program.

Arthaud, Maxime↗

NASA NTRS2019

MARGInS Model-Based Analysis of Realizable Goals in Systems

The high complexity of modern aircraft and spacecraft requires elaborate Verification and Validation (V&V) approaches to make sure that such complex systems work properly and reliably. MARGInS is a framework for the analysis, understanding, and prediction of the behavior of a complex, hybrid system. MARGInS contains a set of machine learning and statistical algorithms for multivariate clustering, treatment learning, critical factor determination, time-series analysis, event prediction, and safety-boundary detection and characterization. The framework supports system testing and can be configured to find novel features in test suites, determine classes of behavior, propose new experiments that can efficiently explore and characterize the boundaries between classes of system behavior, and to create visualizations and reports.

He, Yuning↗

NASA NTRS2020

Is Structured Agile an Oxymoron? Tales from Implementing and Executing Agile in a US Government Environment

To paraphrase a famous quote, "No plan survives contact with the reality." Software (SW) development is often a classic example of this: whatever the plan was for a particular development, it often does not survive contact with technical realities, budget realities, program realities and schedule realities. Traditionally, SW development has followed a waterfall methodology with requirements being rigorously specified before the design, which was completed before the coding and unit testing started, which were in turn finished before validation and verification started. This model of SW engineering derives much from the HW engineering of large systems, and has been the standard methodology used in US government software acquisitions and systems for decades, with highly variable results. US Government SW requirements are built around Waterfall concepts, which assume that the plan will survive contact with reality, or at least that modifications to the plan are relatively small, and relatively few.Because of the inefficiencies and difficulties inherent in Waterfall, the commercial SW world started using a different SW development methodology called Agile more than 20 years ago. Agile believes that a plan should evolve and learn rapidly in response to the realities encountered. At its core, there are a few key elements of Agile:- A small team of people which is highly flexible and adaptive. The team collaborates and interoperates through sophisticated development architectures and release environments- An iterative, incremental development and release approach which is based upon the concept that knowledge comes from experience within the team, and that the team makes decisions based upon what it knows- A team culture which prizes transparency, inspection and adaptation. These values are necessary so that the team experience and decision making is transparent and responsive to the realities encountered during development and testingSo, how to use Agile in a US Government environment? GMSEC (Goddard Mission Services Evolution Center) develops satellite ground system software for NASA and other US Government agencies. The SW developed by the team contains a large code base of many applications used within satellite mission operations centers. It spans the full gamut of SW development types: from SW which is in a classic maintenance and sustainment mode, to new developments with a fairly well understood scope and approach, to new developments whose scope and approach are quite unclear and which require significant research and prototyping. Team members move between all of these different types of SW development. Waterfall was inadequate to the programmatic and technical needs of the team, as well as the various types of SW development being done. The software plan was not surviving contact with the technical and programmatic realities experienced by the team. To address this, the team started a small pilot project in 2016 to test the use of Agile within a small subset of the team for a new web services application. In early 2018, the use of Agile was expanded to the whole team and all the software, but we had to fulfill the NASA SW development requirements. And we needed to do this while still remaining true to the key Agile elements of transparency, inspection and adaption. In order to do this, the team worked very closely with the Software Process Improvement (SPI) team at NASA Goddard, as well as NASA engineering manageme

Beech, Theresa W.↗

NASA NTRS2019

Recommendation for a Medical System Concept of Operations for Gateway Missions

NASA’s exploration missions to cis-lunar space will establish a permanent gateway to future transport missions to Mars. These missions mandate a significant paradigm change for mission planning, spacecraft design, human systems integration, and in-flight medical care due to constraints on mass, volume, power, resupply, and medical evacuation capability. These constraints require medical system development to be tightly integrated with mission and habitat design to provide a sufficient medical infrastructure and enable mission success. This concept of operations provides a vision of medical care needs that will be used to guide the development of a medical system for the cis-lunar Gateway Habitat. This medical system will serve as the precursor to what is implemented in future exploration missions to Mars. This concept of operations documents an overview of the stakeholder needs and system goals of a medical system and provides examples of the types of activities for which the system will be used during the mission. This concept of operations informs the ExMC systems engineering effort to define the Gateway Habitat Medical System by documenting the medical activities and capabilities relevant to Gateway missions, as identified by the ExMC clinician community. In addition, this concept of operations will inform the subsequent systems engineering process of developing technical requirements, system architectures, interfaces, and verification and validation approaches for the medical system. This document supports the closure of ExMC Gap Med01: We do not have a concept of operations for medical care during exploration missions, corresponding to the ExMC-managed human system risk: Risk of Adverse Health Outcomes & Decrements in Performance due to Inflight Medical Conditions.

Rubin, David↗