Optimizing NASA IV&V Benefits Using Simulation Grant Number: NAG5-12736 David M. Raffo, Ph.D College of Engineering and Computer Science School of Business.

Slides:



Advertisements
Similar presentations
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Advertisements

Designing and Developing Decision Support Systems Chapter 4.
ITIL: Service Transition
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
1 Independent Verification and Validation Current Status, Challenges, and Research Opportunities Dan McCaugherty IV&V Program Manager Titan Systems Corporation.
Some Experience With COSYSMOR At Lockheed Martin
SE 555 Software Requirements & Specification Requirements Management.
Software Project Planning CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 12, 2002.
Iterative development and The Unified process
Introduction to Systems Analysis and Design
SDLC and alternative methodologies 1/14/2015 © Abdou Illia MIS Spring 2015.
Software causes many failures - significant mission risk Hard to quantify effects on system risk of: software defects software development practices software.
Architecture Tradeoff Analysis Method Based on presentations by Kim and Kazman
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
Product Lifecycle Management Cost of Quality Pasi Kaipainen, Mika Huhta.
Cost Management Week 6-7 Learning Objectives
Effective Methods for Software and Systems Integration
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Planning Processes and Techniques
Integrated Capability Maturity Model (CMMI)
SAS_08_AADL_Exec_Gluch MAC-T IVV Model-Based Software Assurance with the SAE Architecture Analysis & Design Language (AADL) California Institute.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
UNIT 2: Planning The Planning Process and Types of Plans.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Management & Development of Complex Projects Course Code - 706
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
Reducing ITS Project Risk By using and developing consensus based regional ITS architecture and a systems engineering process Robert S. Jaffe, Ph.D., CSEP.
Acquiring Information Systems and Applications
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Software Engineering Lecture # 17
1 MultiCom, a platform for the design and the evaluation of interactive systems. MultiCom, a platform for the design and the evaluation of interactive.
Acquiring Information Systems and Applications
Common Activities Activities and Tasks in the WBS.
PROJECT MANAGEMENT. A project is one – having a specific objective to be completed within certain specifications – having defined start and end dates.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
Project Management Part 6 Project Control. Part 6 - Project Control2 Topic Outline: Project Control Project control steps Measuring and monitoring system.
Acquiring Information Systems and Applications
Software Engineering Spring (C) Vasudeva VarmaClass of 32 CS3600: Software Engineering: Process and Product* *Most of the Content drawn.
CHAPTER 13 Acquiring Information Systems and Applications.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Formal Methods in Software Engineering
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
Develop Project Charter
Lecture 2 –Approaches to Systems Development Method 10/9/15 1.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Software Architecture Risk Assessment (SARA) Tool Khader Shaik, Wallid Abdelmoez, Dr. Hanny Ammar Lane Department of Computer Science and Electrical Engineering,
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
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.
Introduction to IT investment decision-making Pertemuan 1-2 Matakuliah: A Strategi Investasi IT Tahun: 2009.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Software Engineering (CSI 321) Software Process: A Generic View 1.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
What’s New in SPEED APPS 2.3 ? Business Excellence Application Services.
Risk Management in Software Development Projects Roberto Torres Ph.D. 11/6/01.
Project Cost Management
Fundamentals of Information Systems, Sixth Edition
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Presented to the NASA OSMA SAS ‘01
TechStambha PMP Certification Training
Software Engineering (CSI 321)
Software Engineering I
HHS Child Welfare National IT Managers' Meeting
Presentation transcript:

Optimizing NASA IV&V Benefits Using Simulation Grant Number: NAG David M. Raffo, Ph.D College of Engineering and Computer Science School of Business Administration Portland State University

Problem There is a critical need allocate scarce IV&V resources in the most effective manner possible Questions –How can the economic benefit of IV&V technologies be optimized? –What is the best strategy for applying IV&V technologies? –What is the benefit of applying one combination of IV&V techniques to a given process vs another? The goal of this project is to provide NASA with a flexible decision support tool that can be applied to NASA projects and NASA IV&V to assess the benefits of various quality assurance and IV&V policies on a given NASA project.

Relevance to NASA Contributes to mission assurance & improved project management More cost effective management of IV&V Potential to be applied to multiple NASA projects at multiple NASA Centers (started project with KSC) –Develop method for rapidly tailoring simulation models in the NASA environment –Comparison of effectiveness of DES models with COCOMO & SD models –Augment DES models with SD factors

Importance/ Benefits What if a NASA project canceled due to software delays and cost overruns had this tool: –They could have assessed the benefits vs. costs of IV&V early on. They could have let IV&V in earlier or had a broader scope. –They could have had better estimates, validated those estimates, and quantified the impacts of scope and budget changes. –They could have validated processes they had or designed better processes. –They could have assessed the impacts of developer and project manager experience on productivity and its impact on the project

Approach This tool is based on Software Process Simulation techniques and the Process Tradeoff Analysis Method (PTAM) based on work originally done at the SEI. Key Advantages of using a Simulation Based Approach: –Compare alternative process scenarios and make tradeoffs –Forward looking at what is “possible” not just what has been –Extensive “What if” analyses to explore alternatives desired by management –Compute a ROI and develop a quantitative business case –Update initial plans; choose best corrective action

Approach Process Performance Cost, Quality, Schedule Project Data Process and Product Better Process Decisions Software Development Process SW Process Simulation Model

Process Analysis Tradeoff Tool Large-Scale software project planning support Rapidly deployable models dramatically reduce time to develop and modify Platform for analyzing process tradeoffs and impact of QA, IV&V or other process technologies (tools) NASA Project studying the impact of IV&V IV&V can be applied at one or more phases over the entire software development lifecycle Alternative IV&V application configurations can be compared (ROI)

Basis for Project Management X Original Plan Current Trajectory Actual Data Corrective Action

Accomplishments Delivered prototype version of simulation tool to NASA. This prototype contains: –IEEE Software Development Process Lifecycle Model that can be adapted to a variety of NASA projects –Nine potential IV&V techniques (using new IV&V WBS) Increased PF to 7 - Researchers using NASA data (2 projects) Reported work at ProSim’04

Next Steps Creating new software process life cycle models Adding more IV&V Techniques Continuing NASA data analysis with goal of developing business case scenarios Continuing tool development Joint research with KSC Continuing research in Optimization Theory –Assessing variety of techniques including: Treatment Learning,DEA, and Financial Measures

The End