National Aeronautics and Space Administration SAS08_Classify_Defects_Nikora1 Software Reliability Techniques Applied to Constellation Allen P. Nikora,

Slides:



Advertisements
Similar presentations
Testing Workflow Purpose
Advertisements

Technology readiness levels in a nutshell
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Risk Assessment & Risk Management at GSFC
Establishing IV&V Properties Steve Raque, NASA IV&V Facility Dr. Doron Drusinsky, Naval Postgraduate School 9/4/20091Establishing IV&V Properties.
The Experience Factory May 2004 Leonardo Vaccaro.
Project Management Methodology (PMM)
Automation for System Safety Analysis: Executive Briefing Jane T. Malin, Principal Investigator Project: Automated Tool and Method for System Safety Analysis.
Civil Government Services Group 1 Return on Investment of Independent Verification and Validation: Indirect Benefits James B. Dabney, Gary Barber, Don.
SAS_06_STOL_Tool_Cooper Automated Systems Test and Operations Language (STOL) Analysis Tool Jason G. Cooper July 20, 2006.
Organizational Execution Capability Assessment Framework
PMSS Final SOW May 22 nd, Statement of Work 2 GLENN RESEARCH CENTER PROJECT MANAGEMENT SUPPORT SERVICES (PMSS) The Contractor shall provide expert.
National Aeronautics and Space Administration SAS08_Classify_Defects_Nikora1 Software Reliability Techniques Applied to Constellation Allen P. Nikora,
CS527: (Advanced) Topics in Software Engineering Overview of Software Quality Assurance Tao Xie ©D. Marinov, T. Xie.
How To Apply Quality Management
SAS_08_AADL_Exec_Gluch MAC-T IVV Model-Based Software Assurance with the SAE Architecture Analysis & Design Language (AADL) California Institute.
Chapter 6 Software Implementation Process Group
Risk management in Software Engineering T erm Paper By By Praveenkumar Sammita Praveenkumar Sammita CSC532 CSC532.
Research Heaven, West Virginia Verification and Validation of Adaptive Systems Online Failure Detection and Identification for IFCS through Statistical.
OSMA2003 Center for Reliability Engineering 1 Integrating Software into PRA Presented by C. Smidts Center for Reliability Engineering University of Maryland.
1PBI_SAS_08_Exec_ShullSeptember 2008MAC-T IVV Dr. Forrest Shull, FCMD Kurt Woodham, L-3 Communications OSMA SAS 08 Infusion of Perspective-Based.
WHAT IS SYSTEM SAFETY? The field of safety analysis in which systems are evaluated using a number of different techniques to improve safety. There are.
Management & Development of Complex Projects Course Code - 706
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
7 th Continual Improvement & Innovation Symposium 2015 CASE STUDY COMPETITION: INNOVATION TEMPLATE [ Name of the Organization ] [ Innovation Title ]
1 Human Performance in Reactor Safety George E. Apostolakis Massachusetts Institute of Technology Presented at the Quality Colloquium,
Testing Workflow In the Unified Process and Agile/Scrum processes.
1 Software Reliability Assurance for Real-time Systems Joel Henry, Ph.D. University of Montana NASA Software Assurance Symposium September 4, 2002.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
Georgia Institute of Technology CS 4320 Fall 2003.
SAS ‘05 Reducing Software Security Risk through an Integrated Approach David P. Gilliam, John D. Powell Jet Propulsion Laboratory, California Institute.
California Institute of Technology Formalized Pilot Study of Safety- Critical Software Anomalies Dr. Robyn Lutz and Carmen Mikulski This research was carried.
11th International Symposium Loss Prevention 2004 Prague Ľudovít JELEMENSKÝ Department of Chemical and Biochemical Engineering, STU BRATISLAVA, SLOVAKIA.
California Institute of Technology Formalized Pilot Study of Safety- Critical Software Anomalies Dr. Robyn Lutz and Carmen Mikulski Software Assurance.
California Institute of Technology Estimating and Controlling Software Fault Content More Effectively NASA Code Q Software Program Center Initiative UPN.
Software Architecture Risk Assessment (SARA) Tool Khader Shaik, Wallid Abdelmoez, Dr. Hanny Ammar Lane Department of Computer Science and Electrical Engineering,
Reusing Modeling Elements in IV&V Thomas Otani Naval Postgraduate School 2009 NASA Independent Verification and Validation (IVV) Annual Workshop John Ryan.
National Aeronautics and Space Administration SAS08_Classify_Defects_Nikora1 Classifying Software Faults to Improve Fault Detection Effectiveness Allen.
Presented to Managers. INTERNAL CONTROLS are the integration of the activities, plans, attitudes, policies and efforts of the people of an organization.
New Products from NASA’s Software Architecture Review Board
1 Technology Infusion of the Software Developer’s Assistant (SDA) into the MOD Software Development Process NASA/JSC/MOD/Brian O’Hagan 2008 Software Assurance.
Smart Home Technologies
Contents 1 Description of 1 Description of Initiative Initiative 3 Defining Inspection 3 Defining Inspection Perspectives Perspectives 2 Overview of 2.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
SAS_05_Contingency_Lutz_Tal1 Contingency Software in Autonomous Systems Robyn Lutz, JPL/Caltech & ISU Doron Tal, USRA at NASA Ames Ann Patterson-Hine,
Swedish Risk Management System Internal management and control Aiming to Transport Administration with reasonable certainty to.
California Institute of Technology 1 Operationalization and Enhancement of the Advanced Risk Reduction Tool (ARRT) Presentation to the 2 nd Annual NASA.
SAS_08_Legacy_Safety_Hill Assurance and Recertification of Safety Critical Software In Legacy Systems Janie Hill NASA Kennedy Space Center, Florida
Quality Assurance and Risk Management Services, Inc. 
1 SAS ‘04 Reducing Software Security Risk through an Integrated Approach David P. Gilliam and John D. Powell.
1 Recommended Next Steps For Improving Quantitative Information California Water Plan Advisory Committee Meeting August 17, 2005.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Organizations of all types and sizes face a range of risks that can affect the achievement of their objectives. Organization's activities Strategic initiatives.
Failure Modes, Effects and Criticality Analysis
Cs498dm Software Testing Darko Marinov January 24, 2012.
Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2.
The Project Infrastructure
Project Integration Management
Please highlight one choice only
Project Management Processes
ISO 9001:2015 Quality Management System
Goal, Question, and Metrics
Classifying Software Faults to Improve Fault Detection Effectiveness
Knowing When to Stop: An Examination of Methods to Minimize the False Negative Risk of Automated Abort Triggers RAM XI Training Summit October 2018 Patrick.
Please highlight one choice only
Project Lifecycle and IT Product Life Cycle
An Assessment of Space Shuttle Flight Software Development Processes
8th Continual Improvement & Innovation Symposium 2016 CASE STUDY COMPETITION: INNOVATION TEMPLATE [ Name of the Organization ] [ Innovation Title ]
Jeff Dutton/NASA COR August 26, 2019
Presentation transcript:

National Aeronautics and Space Administration SAS08_Classify_Defects_Nikora1 Software Reliability Techniques Applied to Constellation Allen P. Nikora, JPL/Caltech This research was carried out at the Jet Propulsion Laboratory, California Institute of Technology under a contract with the National Aeronautics and Space Administration. The work was sponsored by the NASA Office of Safety and Mission Assurance under the Software Assurance Research Program led by the NASA Software IV&V Facility. This activity is managed locally at JPL through the Assurance and Technology Program Office Executive Briefing NASA OSMA Software Assurance Symposium September 9-11, /09/2008

National Aeronautics and Space Administration 09/09/2008SAS08_CxP_SWRel_Nikora2 Agenda Problem/Approach Relevance to NASA Accomplishments and/or Tech Transfer PotentialAccomplishments and/or Tech Transfer Potential Next Steps

National Aeronautics and Space Administration 09/09/2008SAS08_CxP_SWRel_Nikora3 Problem/Approach Software-related failures responsible for more than half of NASA major space mission losses or malfunctions between 1996 and 2007 –Large majority due to system conditions not been anticipated or fully understood in the system / software specification and design process –As NASA space missions are increasingly controlled by software, probability of mission failure due to software may increase if no action is taken –Minimizing loss of crew/loss of mission requires appropriate techniques to evaluate reliability of on- board and ground-based support software during all development phases.

National Aeronautics and Space Administration 09/09/2008SAS08_CxP_SWRel_Nikora4 Problem/Approach (cont’d) Modeling of a software system in its anticipated operational context is an important aspect of assuring software reliability. –Recognized in concept of “operational profile”, software reliability model assumptions –Many techniques for modeling software reliability treat software in isolation from the hardware on which it runs and which it controls. Goals: –Demonstrate feasibility of applying Context-based Software Risk Modeling (CSRM) technique to CxP applications/scenariosContext-based Software Risk Modeling Focus on mission-critical applications such as GN&C, Safety and Health Monitoring, Launch Abort –Develop guidelines for use of context-based techniques –Infuse context-based SW reliability modeling techniques to other NASA SW development efforts

National Aeronautics and Space Administration 09/09/2008SAS08_CxP_SWRel_Nikora5 Relevance to NASA Reliability of software component depends on operating environment. CSRM explicitly includes context in system/software models. Unlike traditional software reliability modeling techniques, CSRM helps guide software testing CSRM can be used to evaluate risk of software failure during specification and design phases as well as during implementation and test. –Identify risk-prone areas earlier in development  reduced number of defects passed through to test and operations –Earlier identification of risk-prone areas  more effective management of development resources

National Aeronautics and Space Administration 09/09/2008SAS08_CxP_SWRel_Nikora6 Accomplishments and/or Tech Transfer Potential Selected PA-1 as initial scenario to be modeled Acquired relevant artifacts from Windchill, JSC contacts Analysis of PA-1 software specifications/design in progress

National Aeronautics and Space Administration 09/09/2008SAS08_CxP_SWRel_Nikora7 Next steps Complete development of PA-1 model(s) Analyze models; evaluate software failure risk Review models, results Refine models Select further applications to model

National Aeronautics and Space Administration Backup Information

National Aeronautics and Space Administration 09/09/2008SAS08_CxP_SWRel_Nikora9 CSRM Highlights From “Risk-Informed Software Assurance for NASA Space Missions”, Sergio Guarro, ASCA Inc., November, 2007 Approach PRA-style development of mission and risk scenario models Uses traditional event-tree / fault-tree logic models at top modeling level to capture the basic aspects of mission scenarios Uses Dynamic Flowgraph Methodology (DFM) models to capture dynamic and logically complex aspects of system/software interactions –DFM analytical and quantitative results are fully compatible and can be integrated with PRA tool binary models and results (SAPHIRE, CAFTA) Modeling and quantification framework is also compatible with / can incorporate risk and assurance info from other tools and sources –Traditional test results –SW-process-quality based information –SW defect / reliability model output