1 Independent Verification and Validation Current Status, Challenges, and Research Opportunities Dan McCaugherty IV&V Program Manager Titan Systems Corporation.

Slides:



Advertisements
Similar presentations
Program Management Office (PMO) Design
Advertisements

The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
University of Southern California Center for Systems and Software Engineering Risk Calculation Case Studies CS 510 Software Engineering Supannika Koolmanojwong.
Alternate Software Development Methodologies
NEES Project Management Workshop June 16 June 18 1 Segment 2.
How to: Design and Develop an Application to Ensure its Quality James Hippolite Senior.NET Developer Telecom New Zealand Limited James Hippolite Senior.NET.
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
Verification and Validation: A Quick Introduction 1-2 Lectures.
Verification and Validation: A Quick Introduction Authors Massood Towhidnejad Massood Towhidnejad Mike Rowe Mike Rowe David Dampier David Dampier Sponsored.
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Software Fault Injection Kalynnda Berens Science Applications International Corporation NASA Glenn Research Center.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
IV&V Facility Model-based Design Verification IVV Annual Workshop September, 2009 Tom Hempler.
NASA IV&V Facility Software Independent Verification and Validation (IV&V) NASA IV&V Facility Fairmont, West Virginia Judith N. Bruner Acting Director.
INCOSE 1 st reactions. One other area that struck me has the sheer number of levels of proficiency—in ours we are going with 5 and the first one is limited.
Release & Deployment ITIL Version 3
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
Effective Methods for Software and Systems Integration
Chapter : Software Process
Managing a Training Program Why train? Who will attend the training? What are the learning objectives? Strategies? Coverage? How will the training program.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
CLEANROOM SOFTWARE ENGINEERING.
1 Reconfigurable Environment For Analysis and Test of Software Systems (REATSS) Dan McCaugherty /19/2004.
Software Project Failure Software Project Failure Night Two, Part One CSCI 521 Software Project Management.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.
S Q A.
Using Business Scenarios for Active Loss Prevention Terry Blevins t
Chapter 2 Process: A Generic View
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.
『华东师范大学』 课程名称: 软件开发实践 Software Development Practice 课程类型: 实践课 第二讲: 项目管理 Lect_02: Manage the Project 主讲 : 软件学院 周勇 副 教授 日期 :
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
IT Requirements Management Balancing Needs and Expectations.
Change Management: Getting User Buy-In Karen Coffman Katie Lutes.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
Software Engineering - I
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Core Banking Transformation: A Roadmap to a Successful Core Banking Product Implementation - PMI Virtual Library | | © 2008 Kannan S. Ramakrishnan.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
1 V&V Needs for NextGen of 2025 and Beyond A JPDO Perspective Maureen Keegan JPDO Integration Manager October 13, 2010.
Lesson 1: Examining Professional Project Management Topic 1A: Identify Project Management Processes.
PPTTEST 12/26/ :41 1 IT Ron Williams Information Technology Management Project Management.
1 Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3.
Illuminating Britelite’s Internal Services for Success Strategy for Process Improvement.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Object-Oriented and Classical Software Engineering Eighth Edition, WCB/McGraw-Hill Stephen R. Schach 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
What has been accomplished at the end of MSD 1 & 2?
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Driving Value from IT Services using ITIL and COBIT 5 July 24, 2013 Gary Hardy ITWinners.
Shared Services Initiative Summary of Findings and Next Steps.
PROJECT MANAGEMENT Software Engineering CSE
Software Verification and Validation
Identify the Risk of Not Doing BA
IEEE Std 1074: Standard for Software Lifecycle
Software Independent Verification and Validation (IV&V)
Baisc Of Software Testing
Quality and reliability management in projects
Presentation transcript:

1 Independent Verification and Validation Current Status, Challenges, and Research Opportunities Dan McCaugherty IV&V Program Manager Titan Systems Corporation 5 September, 2001

2 Agenda Where we are today Developer challenges observed by IV&V IV&V challenges Opportunities for R&D

3 Where we are today

4 IV&V Gaining Acceptance IV&V is gaining acceptance as a mechanism for mitigating software risk IV&V is naturally evolving to also include programmatic assessments such as cost/schedule performance analysis Recent NASA IV&V policy presents an opportunity for wider application and understanding of IV&V

5 IT Project Success Factors Gartner Institute study identified the following essential areas as critical to IT project success 1 –Risk Management –Communications –Resource Management –Lessons Learned Additional areas based on professional experience –Project planning –Requirements!!! Projected that implementation of sound project management approach emphasizing these key areas can reduce number of failed projects by 30% 1 1 GartnerGroup

6 IT Project Success Rates Odds for Success 1&2 –> 80% of IT projects are late, over budget, lack essential functionality, or are never delivered –28% of IT projects just flat fail representing more than $81 Billion in losses –Of 15,000 data migration projects started in 1999, as many as 88 percent either overran or failed Leading causes for project failure 1 –poor project planning –failure to manage scope and change –failure to manage risk 1 GartnerGroup 2 The Standish Group

7 Developer Challenges Observed by IV&V

8 Incremental Delivery Definition “Build a Little, Test a Little” approach can avoid major development failures, but creates other challenges, such as: –Maintaining end state specifications concurrent with increment specifications –Implementing the right requirements in the right builds to meet testable increment specific capabilities –Understanding the cost/schedule effects of pushing requirements into later builds

9 Early Definition of Interfaces and Key Architectural Concepts Late interface or architecture changes or problems create significant re-work or are unmanageable Distributed computing stresses system engineering efforts for early definition of –API’s, remote procedures, and reused objects –Redundancy Management, –Fault Detection, Isolation, and Recovery –Exception handling

10 Use of New Technologies A great way to attract and keep highly skilled professionals Majority of focus on what the technology can do, not enough focus on what it can not do or was never designed to do Limited skill base for new technologies If COTS, may not have future support

11 Measuring Progress or Quality Measurable definitions for “Done” are needed. Metrics efforts and collection mechanisms need to be part of the process from day one Optimism (a good thing) must be tempered with facts

12 IV&V Challenges

13 IV&V Technical Challenges Adapting IV&V methods to developer environments Understanding system dynamic behavior Convincing a project that the process is too risky Validating Non-Development-Items Reverse engineering incompletely specified systems

14 IV&V Managerial and Business Challenges Demonstrating that selected IV&V tasks and scope are appropriate for the Project’s acceptable levels of risk Appropriate IV&V integration into project Demonstrating IV&V ROI Accounting for IV&V data needs within developer contracts.

15 Opportunities for R&D

16 Opportunities for R&D Research IV&V ROI –Past case study 3 shows 1.25 < IV&V ROI < 1.82 –Recommend a study of many projects with varying amounts and types of IV&V –Correlate overall project success to IV&V effort types Continue development of code reverse engineering tools and interface V&V tools –Software and Interface Analysis Tool (SIAT) –Interface Management System (IMS) Develop Reconfigurable engineering simulation for Space Craft –Improve early “validation” analyses 3 Rogers

17 Opportunities for R&D Develop a guidebook identifying sets of IV&V tasks for certain types of systems and acceptable levels of mission risk. –Research history of IV&V method application and results Develop a guidebook for developer managers on how to realize benefits of IV&V. –Contracts and agreements –Integration of IV&V into different types of projects –Reporting and issue resolution

18 Summary

19 Summary There are many software challenges/risks out there –Many can be managed through use of accepted engineering practices IV&V can help mitigate risk if used/applied correctly We need to better quantify the effects of IV&V and the ROI Recommended areas of R&D –Research IV&V ROI, effects of IV&V use –Develop tools that are needed today –Develop guidance for future IV&V'ers and IV&V users.