IV&V and Software Risk Management
|
|
|
- Abraham Barker
- 10 years ago
- Views:
Transcription
1 IV&V and Software Risk Management The Role of IV&V in Software Risk Management NASA Risk Management Conference IV Kenneth A. Costello, NASA IV&V Chief Engineer NASA IV&V Facility Fairmont, West Virginia 1
2 Discussion Outline Software Risk What is IV&V at NASA? IV&V and Software Risk Management 2
3 Software Risk Risk The possibility of suffering damage or harm The likelihood of an event along with the consequences of it occurring Software risk The risk inherent in the development of software Poor estimating Personnel shortfalls Requirements creep/inadequate requirements The risk associated with software failure Hazardous event not controlled Incorrect command execution Erroneous navigation calculations Software Risk Management Active process Identify and address risks as early as possible Relate them to the software and the system/mission as a whole 3
4 IV&V Overview What is the goal of IV&V analysis? Provide a higher level of confidence that the software will be fit for operation and satisfy its requirements for safety, availability, quality and function Reduce the risk associated with development and operation What is Independent Verification and Validation? A set of engineering tasks executed throughout the development process Performed at the unit, module, integration and system levels (as required) Consists of system domain and software experts Focused approach to assessing software for high-criticality risks/issues What is the output from IV&V? Generally analysis summary reports and issues The issues can either be errors in a development artifact or errors (risks) in the development process 4
5 IV&V Execution NASA s definition of Independent Verification and Validation Independent managerial, technical, financial Verification Is the product built right? Validation Are we building the right product? IV&V at NASA is treated as a system level activity that starts by assessing the role of software within a system We want to answer the following questions within a system context What role does the software play in the system? Is it critical to mission success or have safety implications? Does it provide only information? Does it control other components? How does the development approach fit within the overall system development? A set of engineering analysis tasks are then performed against the software/system based upon the assessment (the answers to the questions) 5
6 IV&V Execution (2) Once the IV&V Team understands the role of the software, the team then employs techniques, processes and methods of varying levels of rigor to evaluate the correctness and quality of the software throughout the project life cycle It is important to note that the approach taken is throughout the life cycle IV&V is not viewed nor applied as a test only approach to software risk identification/mitigation at NASA Proper application of IV&V provides Analysis of the software within the context of the system being developed Greater insight into the software development status Early insight into potential problem areas allows problems to be fixed sooner 6
7 IV&V Life Cycle System Requirements Review Nominal Software Development Life Cycle Preliminary Design Review Critical Design Review S/W FQT System Test Mission Readiness Review System Retirement Launch Initial IVVP signed Execution IVVP Signed - IV&V provides support and reports for Project milestones - Technical Analysis Reports document major phases - IVVP is updated to match changes in Project IV&V Provides CoFR IV&V Final Report Concept 2.0 Requirements 3.0 Design 4.0 Implementation 5.0 Test 6.0 Operations & Maintenance 7.0 Formulation Execution Nominal IV&V Life Cycle Close-out Note: numbers correspond to IV&V WBS 7
8 IV&V and Software Risk Management The IV&V Team provides early identification of issues/risks Software and system level Issues may affect the development process Issues may affect the operation of the system While independent, the IV&V Team results should be integrated into the risk management process Development project needs to work with IV&V Team to address issues found Communication is important to ensure critical issues are addressed as early as possible Need to understand definition of risk on both sides 8
SOFTWARE SAFETY STANDARD
NOT MEASUREMENT SENSITIVE National Aeronautics and NASA-STD-8719.13B w/change 1 Space Administration July 8, 2004 SOFTWARE SAFETY STANDARD NASA TECHNICAL STANDARD REPLACES NASA-STD-8719.13A DATED SEPTEMBER
The Application Readiness Level Metric
The Application Readiness Level Metric NASA Application Readiness Levels (ARLs) The NASA Applied Sciences Program has instituted a nine-step Application Readiness Level (ARL) index to track and manage
Space Flight Project Work Breakdown Structure
APPENDIX G. (WBS) Space Flight Project Work Breakdown Structure G.1 Introduction G.1.1 The Project Work Breakdown Structure (WBS) is a key element of project management. The purpose of a WBS is to divide
HHS OCIO Policy for Information Technology (IT) Enterprise Performance Life Cycle (EPLC)
Office of the Chief Information Officer Office of the Assistant Secretary for Resources and Technology Department of Health and Human Services HHS OCIO Policy for Information Technology (IT) Enterprise
SOFTWARE ASSURANCE STANDARD
NOT MEASUREMENT SENSITIVE National Aeronautics and NASA-STD-8739.8 w/change 1 Space Administration July 28, 2004 SOFTWARE ASSURANCE STANDARD NASA TECHNICAL STANDARD REPLACES NASA-STD-2201-93 DATED NOVEMBER
The Key to a Successful KM Project
Introduction An integrated PKM methodology enables organizations to maximize their investments by ensuring initiatives are on time and within budget, while sharing project challenges and successes that
Mastering Microsoft Project 2013
Course 55054: Mastering Microsoft Project 2013 Page 1 of 9 Mastering Microsoft Project 2013 Course 55054: 2 days; Instructor-Led Introduction This two-day, instructor-led course is intended for individuals
Mastering Microsoft Project 2013 Course: 55054A Course Length: 3 Days
3 Riverchase Office Plaza Hoover, Alabama 35244 Phone: 205.989.4944 Fax: 855.317.2187 E-Mail: [email protected] Web: www.discoveritt.com Mastering Microsoft Project 2013 Course: 55054A Course Length:
The!Art!and!Science of!systems!engineering *
The!Art!and!Science of!systems!engineering * The!Scope!of!Systems!Engineering The!Personal!Characteristics!of!Good!Systems!Engineer Summary This! work! culminates! years! of! experience! in! systems! engineering!
THE ROLE OF IV&V IN THE SOFTWARE DEVELOPMENT LIFE CYCLE
1 THE ROLE OF IV&V IN THE SOFTWARE DEVELOPMENT LIFE CYCLE by: The IV&V Group for: ASQ Section 509 Section 509 - NOV 2007 2 2 INTRODUCTION Overview Phase-Related IV&V Activities IV&V Implementation Summary
INDEPENDENT VERIFICATION AND VALIDATION OF EMBEDDED SOFTWARE
PREFERRED RELIABILITY PRACTICES PRACTICE NO. PD-ED-1228 PAGE 1 OF 6 INDEPENDENT VERIFICATION AND VALIDATION OF EMBEDDED SOFTWARE Practice: To produce high quality, reliable software, use Independent Verification
Project Risk Management: IV&V as Insurance for Project Success
Project Risk Management: IV&V as Insurance for Project Success Introduction Software development projects can be expensive and risky: Ever more complex mission-critical requirements lead to increasingly
An approach to Return on Investment (ROI) for Independent Verification and Validation (IV&V) at NASA
An approach to Return on Investment (ROI) for Independent Verification and Validation (IV&V) at NASA Bob Hunt September 2012 1 NASA IV&V The NASA IV&V Program was established in 1993 as part of an Agency-wide
Risk. Risk Categories. Project Risk (aka Development Risk) Technical Risk Business Risk. Lecture 5, Part 1: Risk
Risk Lecture 5, Part 1: Risk Jennifer Campbell CSC340 - Winter 2007 The possibility of suffering loss Risk involves uncertainty and loss: Uncertainty: The degree of certainty about whether the risk will
Software-based medical devices from defibrillators
C O V E R F E A T U R E Coping with Defective Software in Medical Devices Steven R. Rakitin Software Quality Consulting Inc. Embedding defective software in medical devices increases safety risks. Given
A Methodology for Safety Critical Software Systems Planning
A Methodology for Safety Critical Software Systems Planning EHAB SHAFEI 1, IBRAHIM F. MOAWAD 2, HANY SALLAM 1, ZAKI TAHA 3, MOSTAFA AREF 3 1 Operation Safety and Human Factors Department, 2 Information
Overview of Florida Information Technology Project Management and Oversight Standards. Jason M. Allison, Executive Director
Overview of Florida Information Technology Project Management and Oversight Standards Jason M. Allison, Executive Director AGENCY FOR STATE TECHNOLOGY Statutory duties and responsibilities of AST: Establish
U.S. Department of Education Federal Student Aid
U.S. Department of Education Federal Student Aid Lifecycle Management Methodology Stage Gate Review Process Description Version 1.3 06/30/2015 Final DOCUMENT NUMBER: FSA_TOQA_PROC_STGRW.NA_001 Lifecycle
CHARACTERISTICS OF SUCCESSFUL MEGAPROJECTS
Chapter Six CHARACTERISTICS OF SUCCESSFUL MEGAPROJECTS Bibliographic Information: Committee to Assess the Policies and Practices of the Department of Energy to Design, Manage, and Procure Environmental
The Program Managers Guide to the Integrated Baseline Review Process
The Program Managers Guide to the Integrated Baseline Review Process April 2003 Table of Contents Foreword... 1 Executive Summary... 2 Benefits... 2 Key Elements... 3 Introduction... 4 IBR Process Overview...
PgMP Credential. Christopher Talmont, PMP, PMI-RMP. February 23, 2011
PgMP Credential Christopher Talmont, PMP, PMI-RMP February 23, 2011 A b o u t M e 7 years of experience as an instructor and consultant of project scheduling software and best practices 4 years of experience
MM Agile: SCRUM + Automotive SPICE. Electronics Infotainment & Telematics
MM Agile: SCRUM + Automotive SPICE Electronics Infotainment & Telematics 20 Novembre, 2010 INDEX Introduction Why MM Agile Approach? How did we align classical and agile approach? How do we implement SCRUM?
Estimating Software Reliability In the Absence of Data
Estimating Software Reliability In the Absence of Data Joanne Bechta Dugan ([email protected]) Ganesh J. Pai ([email protected]) Department of ECE University of Virginia, Charlottesville, VA NASA OSMA SAS
NASA TECHNICAL STANDARD SOFTWARE SAFETY STANDARD
NASA TECHNICAL STANDARD NASA-STD-8719.13C National Aeronautics and Space Administration Approved: 05-07-2013 Washington, DC 20546-0001 Superseding NASA-STD-8719.13B SOFTWARE SAFETY STANDARD MEASUREMENT
Dallas IIA Chapter / ISACA N. Texas Chapter. January 7, 2010
Dallas IIA Chapter / ISACA N. Texas Chapter Auditing Tuesday, October Project 20, 2009 Management Controls January 7, 2010 Table of Contents Contents Page # Project Management Office Overview 3 Aligning
VDI 2206 Prof. Dr. Magdy M. Abdelhameed
Course Code: MDP 454, Course Name:, Second Semester 2014 VDI 2206 Mechatronics System Design The mechatronic design methodology is based on a concurrent (instead of sequential) approach to discipline design,
The Mental Health Care Patient Management System (Mentcare)
The Mental Health Care Patient Management System (Mentcare) The Mentcare system ² This system (not its real name but a real system) is a generic medical information system that is configured for use in
Appendix B: Work Breakdown Structure (WBS)
: Work Breakdown Structure (WBS) B.1. Introduction The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. In accordance with
Project Managing Microsoft Dynamics CRM Implementations
Workshop 80054A: Project Managing Microsoft Dynamics CRM Implementations with Microsoft Dynamics Sure Step Length: 2 Day(s) Published: November 12, 2008 Language(s): Audience(s): English Developers Level:
<Project Name> Software Quality Assurance (SQA) Plan. <Document Control Number>
Software Quality Assurance (SQA) Plan Date: CHECK THE AT< WEBSITE Address> TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. General Tailoring Guidelines This
Software Quality Assurance: II Software Life Cycle
Software Quality Assurance: II Software Life Cycle Room E 3.165 Tel. 60-3321 Email: [email protected] Outline I Introduction II Software Life Cycle III Quality Control IV Infrastructure V Management VI Standards
V&V and QA throughout the M&S Life Cycle
Introduction to Modeling and Simulation and throughout the M&S Life Cycle Osman Balci Professor Department of Computer Science Virginia Polytechnic Institute and State University (Virginia Tech) Blacksburg,
FEMA Grant Programmes and the Role of Elizabeth Harman
STATEMENT OF ELIZABETH M. HARMAN ASSISTANT ADMINISTRATOR GRANT PROGRAMS DIRECTORATE FEDERAL EMERGENCY MANAGEMENT AGENCY U.S. DEPARTMENT OF HOMELAND SECURITY BEFORE THE HOUSE COMMITTEE ON HOMELAND SECURITY
PHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The Planning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
Criteria for Flight Project Critical Milestone Reviews
Criteria for Flight Project Critical Milestone Reviews GSFC-STD-1001 Baseline Release February 2005 Approved By: Original signed by Date: 2/19/05 Richard M. Day Director, Independent Technical Authority
A Study on Software Metrics and Phase based Defect Removal Pattern Technique for Project Management
International Journal of Soft Computing and Engineering (IJSCE) A Study on Software Metrics and Phase based Defect Removal Pattern Technique for Project Management Jayanthi.R, M Lilly Florence Abstract:
Risk/Issue Management Plan
Risk/Issue Management Plan Centralized Revenue Opportunity System November 2014 Version 2.0 This page intentionally left blank Table of Contents 1. Overview... 3 1.1 Purpose... 3 1.2 Scope... 3 2. Roles
Introduction to Risk Management for Software Projects. Peter Kolb. Distributed and Outsourced Software Engineering, - 1 - ETH Zurich
Introduction to Risk Management for Software Projects Peter Kolb Distributed and Outsourced Software Engineering, - 1 - ETH Zurich Purpose of Presentation To provide an Overview of the Risk Management
A Characterization Taxonomy for Integrated Management of Modeling and Simulation Tools
A Characterization Taxonomy for Integrated Management of Modeling and Simulation Tools Bobby Hartway AEgis Technologies Group 631 Discovery Drive Huntsville, AL 35806 256-922-0802 [email protected]
Using Static Code Analysis Tools for Detection of Security Vulnerabilities
Using Static Code Analysis Tools for Detection of Security Vulnerabilities Katerina Goseva-Popstajanova & Andrei Perhinschi Lane Deptartment of Computer Science and Electrical Engineering West Virginia
Project Management with Clarity PPM using Microsoft Project
Project Management with Clarity PPM Using Microsoft Project Five (5) Day Virtual Learning Environment Comprehensive Course by Digital Celerity Digital Celerity offers innovative training on all CA Clarity
Goddard Procedural Requirements (GPR) TABLE OF CONTENTS
Goddard Procedural Requirements (GPR) DIRECTIVE NO. GPR 8710.2B APPROVED BY Signature: Original signed by Arthur F. Obenschain NAME: Robert Strain TITLE: Director COMPLIANCE IS MANDATORY Responsible Office:
V-Sept CRM Integration Setup
V-Sept CRM Integration Setup 1 Contents V-SEPT CRM INTEGRATION SETUP... 1 ENABLING YOUR V-SEPT/50 BELOW INTEGRATION... 3 GENERATING A LOGIN AND PASSWORD FOR THE FIRST TIME... 3 Integration Manager... 3
Get Confidence in Mission Security with IV&V Information Assurance
Get Confidence in Mission Security with IV&V Information Assurance September 10, 2014 Threat Landscape Regulatory Framework Life-cycles IV&V Rigor and Independence Threat Landscape Continuously evolving
PHASE 1: INITIATION PHASE
PHASE 1: INITIATION PHASE The Initiation Phase begins when agency management determines that a business function requires enhancement through an agency information technology (IT) project and investment
NASA PROCUREMENT TENETS
NASA PROCUREMENT TENETS Introduction: The goal of procurement is to ensure the Agency executes its mission successfully by effectively and efficiently managing the acquisition process. NASA spends approximately
EXECUTIVE SAFETY POLICY
EXECUTIVE SAFETY POLICY SAFETY AT VIRGINIA FLIGHT SCHOOL The concept or word safety when used at Virginia Flight School, written, spoken or implied shall mean: The freedom from, or minimal exposure to,
SAPHIRE 8 Software Configuration Management Plan
INL/EXT-09-16696 Rev. 1 SAPHIRE 8 Software Configuration Management Plan January 2010 The INL is a U.S. Department of Energy National Laboratory operated by Battelle Energy Alliance INL/EXT-09-16696 Rev.
Handbook for Software Cost Estimation
JPL D-26303, Rev. 0 Handbook for Software Cost Estimation Prepared by: Karen Lum Michael Bramble Jairus Hihn John Hackney Mori Khorrami Erik Monson Document Custodian: Jairus Hihn Approved by: Frank Kuykendall
Analytical Program Management: Integrating Cost, Schedule, and Risk. Graham Gilmer Eric Druker
Analytical Program Management: Integrating Cost, Schedule, and Risk Graham Gilmer Eric Druker Analytical Program Management (APM) Outline Integration of Cost, Schedule, and Risk Management Activities NASA
Mastering Microsoft Project 2013
This three-day, instructor-led course is intended for individuals who are interested in expanding their knowledge base and technical skills about Microsoft Project. The course begins with the basic concepts
Human-Automation Interaction Design and Evaluation Tools. Michael Feary, PhD
Human-Automation Interaction Design and Evaluation Tools Michael Feary, PhD Outline Human Automation interaction Research Challenges Research Approach Understanding Work domain analysis Visualization Prediction
Information Technology Solutions at Work
Information Technology Solutions at Work Company Overview Established in 2000, E Quality Corporation is a privately held company headquartered in Dallas, Texas with regional offices in Springfield, Virginia.
An Introduction to the ECSS Software Standards
An Introduction to the ECSS Software Standards Abstract This introduces the background, context, and rationale for the creation of the ECSS standards system presented in this course. Addresses the concept
ESA s Data Management System for the Russian Segment of the International Space Station
iss data management system ESA s Data Management System for the Russian Segment of the International Space Station J. Graf, C. Reimers & A. Errington ESA Directorate of Manned Spaceflight and Microgravity,
U.S. DEPARTMENT OF THE INTERIOR SENIOR LEVEL AND SCIENTIFIC AND PROFESSIONAL PERFORMANCE AGREEMENT AND APPRAISAL SYSTEM.
` U.S. DEPARTMENT OF THE INTERIOR SENIOR LEVEL AND SCIENTIFIC AND PROFESSIONAL PERFORMANCE AGREEMENT AND APPRAISAL SYSTEM Table of Contents Page Section I. Authority and Purpose 1 Section II. Coverage
NASA Financial Management Requirements Volume 9, Chapter 4 April 2005 CHAPTER 4 RISK ASSESSMENTS
CHAPTER 4 RISK ASSESSMENTS 0401 GENERAL 040101. Purpose. This chapter provides detailed guidance on National Aeronautics and Space Administration s (NASA) financial management internal control program
POSITION DESCRIPTION ATTACHMENT A MERCER CED EVALUATION: 157 ASCO: 2211 ANZCO: 2211 POSITION NUMBER: Position Holder: Signature: / /
ATTACHMENT A POSITION DESCRIPTION POSITION TITLE: STATUS: Accounting Officer Full-time MERCER CED EVALUATION: 157 ASCO: 2211 ANZCO: 2211 POSITION NUMBER: Position Holder: FU0027 Vacant Signature: / / Position
Project Closure. ProPath. Office of Information and Technology
Project Closure ProPath Office of Information and Technology Table of Contents Project Closure Process Map... 1 Process: Project Closure... 2 Project Closure Description and Goals... 3 Description... 3
NMMSS Upgrade Progress
NMMSS Upgrade Progress Dan Farmer Technical Manager NMMSS Upgrade WSRC May 23, 2007 Document Number: WSRC-CP-2006-00027 Outline Project Organization Project Methodology Current Status of Software Development
--Hydrographic Survey (GS-1301) Competency Model--
--Hydrographic Survey (GS-1301) Competency Model-- --Hydrographic Survey (GS-1301) Competency Model-- KNOWLEDGE AREAS Bureau-specific mission, vision, goals, and values Bureau-specific policies and procedures
HACCP Manager Certification Training Version 3.0 Center for Public Health Education
HACCP Manager Certification Training Version 3.0 Center for Public Health Education Developed by the NSF Center for Public Health Education HACCP Training Manual Table of Contents CHAPTER 1 1.0 What is
PROJECT AUDIT METHODOLOGY
PROJECT AUDIT METHODOLOGY 1 "Your career as a project manager begins here!" Content Introduction... 3 1. Definition of the project audit... 3 2. Objectives of the project audit... 3 3. Benefit of the audit
UNITED HEALTHCARE NEW YORK STATE HEALTH INSURANCE PROGRAM - OVERPAYMENTS FOR SERVICES AT THE EYE SURGERY CENTER OF WESTCHESTER.
Thomas P. DiNapoli COMPTROLLER OFFICE OF THE NEW YORK STATE COMPTROLLER DIVISION OF STATE GOVERNMENT ACCOUNTABILITY Audit Objective... 2 Audit Results - Summary... 2 UNITED HEALTHCARE Background... 2 Audit
CMS Testing Framework Overview
Department of Health and Human Services Centers for Medicare & Medicaid Services Office of Information Services CMS Framework Overview Version 1.1 May 18, 2011 Table of Contents 1. Introduction... 1 1.1
The Role and Task of the System Architect
- Blah Blah V4aa Idea IO think, analyze listen, talk, walk around design, assist project leader brainstorm, with work breakdown, explain schedule, risks present, meet, teach, discuss travel to write, customer,
Lecture 10: Managing Risk" Risk Management"
General ideas about Risk" Risk Management" Identifying Risks" Assessing Risks" Case Study:" Mars Polar Lander" Lecture 10: Managing Risk" 2012 Steve Easterbrook. This presentation is available free for
Intland s Medical Template
Intland s Medical Template Traceability Browser Risk Management & FMEA Medical Wiki Supports compliance with IEC 62304, FDA Title 21 CFR Part 11, ISO 14971, IEC 60601 and more INTLAND codebeamer ALM is
USGS EOS SYSTEMS ENGINEERING MANAGEMENT PLAN (SEMP)
Department of the Interior U.S. Geological Survey USGS EOS SYSTEMS ENGINEERING MANAGEMENT PLAN (SEMP) September 2013 Executive Summary This Systems Engineering Management Plan (SEMP) outlines the engineering
The 9 Things in the PMBOK
The 9 Things in the PMBOK 9/15/2011 The PMBOK Project Body of Knowledge sum of knowledge within the profession of project management used dto document and standardize di generally accepted project management
ITIL: Service Transition
Management of IT Environment (6) Riadenie IT prostredia ITIL: Service Transition Martin Sarnovský Department of Cybernetics and AI, FEI TU Košice 1 Content Service Transition Goal, inputs and outputs,
Goddard Procedures and Guidelines
Goddard Procedures and Guidelines DIRECTIVE NO. APPROVED BY Signature: Original signed by NAME: A. V. Diaz TITLE: Director Responsible Office: Title: Code 300 / Office of Systems Safety and Mission Assurance,
Systems Engineering Essentials (in Aerospace)
Systems Engineering Essentials (in Aerospace) March 2, 1998 Matt Sexstone Aerospace Engineer NASA Langley Research Center currently a graduate student at the University of Virginia Executive Summary Boeing
Project Management. The Art of Getting Things Done Herding Cats. January,2015
Project Management The Art of Getting Things Done Herding Cats January,2015 What is a Project? A project is a temporary endeavor undertaken to create a unique product or service. It implies: A specific
Software Defined Radio Architecture for NASA s Space Communications
From July 2007 High Frequency Electronics Copyright 2007 Summit Technical Media Software Defined Radio Architecture for NASA s Space Communications By Maximilian C. Scardelletti, Richard C. Reinhart, Monty
GENERAL RECORDS SCHEDULE 3.1: General Technology Management Records
GENERAL RECORDS SCHEDULE 3.1: General Technology Management Records This schedule covers records created and maintained by Federal agencies related to the general management of technology. It includes
How To Write An Slcm Project Plan
SLCM 2003.1 Artifacts in a Nutshell ( as of 01/21/2005) Project Development Phases Pension Benefit Guaranty Corporation s (PBGC) System Life Cycle Methodology (SLCM) is comprised of five project development
