Acquisition Perspectives on the Incremental Commitment Model Dr. Peter Hantos Senior Engineering Specialist The Aerospace Corporation © 2007. The Aerospace.

Slides:



Advertisements
Similar presentations
Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Advertisements

Integrated Product Team (IPT) Process Training
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
1 Lecture 1.4: Life Cycle Models Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
CS 325: Software Engineering January 15, 2015 Software Process & Methodology Prototyping Process Model Evolutionary Process Model Spiral Process Model.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 4: Phase Management - Elaboration.
1 Business (Agency) Process Discovery and Documentation Workshop PeopleSoft Phase II Tuesday, October 23, :00 AM to 12:00 Noon Concourse Theatre.
Small Projects & Tailoring Using the PPA 1:15 – 2:15 Teresa Kinley, OPHPR With Panelists: Susan Wilkin, NCCDPHP Andy Autry, NCBDDD Carol Waller, NCEH/ATSDR.
© The Aerospace Corporation 2010 An Application of COCOMO and COSYSMO in Acquisition Research Dr. Peter Hantos and Nancy Kern The Aerospace Corporation.
Anchoring Concurrent Engineering Processes
University of Southern California Center for Software Engineering C S E USC Barry Boehm, USC USC-CSE Executive Workshop March 15, 2006 Processes for Human.
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
DoD Systems and Software Engineering A Strategy for Enhanced Systems Engineering Kristen Baldwin Acting Director, Systems and Software Engineering Office.
Object-oriented Analysis and Design
CS 501: Software Engineering
© The Aerospace Corporation 2010 Life Cycle Alignment Concerns in Acquisition of Software-Intensive Systems Dr. Peter Hantos and Nancy Kern The Aerospace.
Iterative development and The Unified process
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Chapter 3: The Project Management Process Groups
COMP 350: Object Oriented Analysis and Design Lecture 2
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
May 4, Establish an Acquisition process that produces: Required, Affordable, Timely Products Big “A” Acquisition Resources Acquisition Requirements.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
RUP Fundamentals - Instructor Notes
EMIS 7307 T&E Part 2 1 Documents in flux. MNS - Mission need statement –Non system specific, a needed capability. Being replaced by Initial Capabilities.
NIST Special Publication Revision 1
The Challenge of IT-Business Alignment
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
New 5000 Documents 14 May 2001 New 5000 Documents 14 May 2001 Defense Systems Management College Acquisition Policy Department.
Government Procurement Simulation (GPSim) Overview.
The Defense Acquisition Management System 2009 Implementing DoDI 5000
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 5 Project Integration Management.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
1 1 Nunn-McCurdy Legislation/Program Impacts Della McPhail Chief Financial Officer 308 ARSW DISTRIBUTION STATEMENT A: Approved for public release; distribution.
Develop Project Charter
Practical Investment Assurance Framework PIAF Copyright © 2009 Group Joy Pty. Ltd. All rights reserved. Recommended for C- Level Executives.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Introducing Project Management Update December 2011.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Verification and Validation — An OSD Perspective — Fred Myers Deputy Director, Test Infrastructure Test Resource Management Center November 4, 2009.
Lecture 2.1b: DoD Acquisition Process (SEF Ch 2)
Contracting in a Changing Environment Leslie Deneault Defense Acquisition University
Dan Luttrell, Northrop Grumman USC Agile Experiences Workshop March 17-19, 2004 Agile Process in a DOD Environment - One Project’s.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Software Project Management Iterative Model & Spiral Model.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
Business Case Ganesh Botcha, Ajoy Chatterjee 16 Nov ’15, Monday.
CCA LSS Support Slides1 Draft The Defense Acquisition Management Framework. Post Implementation Review (PIR) Capability Needs Satisfaction & Benefits.
Systems/Software ICM Workshop Acquisition and Process Issues Working Group Rick Selby and Rich Turner Systems/Software ICM Workshop July 14-17, 2008 Washington.
Chapter 3: The Project Management Process Groups: A Case Study Information Technology Project Management, Fourth Edition Project Execution & Closing Thursday,
© 2004 Tangram Hi-Tech Solutions Project Management According to the CMMI1 Project Management according to the Capability Maturity Model (CMMI)
Iterative development and The Unified process
TK2023 Object-Oriented Software Engineering
Camera PDR/CD1 Planning 19 September 2008
MNS - Mission need statement
Competitive Prototyping – the New Reality
The Project Infrastructure
MDD to Milestone A Requirements Management Activities
Milestone A to Milestone B Requirements Management Activities
V-Shaped SDLC Model Lecture-6.
Chapter 3: The Project Management Process Groups: A Case Study
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger Joanne M. Atlee 4th Edition.
ICM_Sw Essentials for CS510
ICM-Sw Essentials for 577 Process models Success models Product models
Baisc Of Software Testing
Comparison between each special case
The Department of Defense Acquisition Process
Presentation transcript:

Acquisition Perspectives on the Incremental Commitment Model Dr. Peter Hantos Senior Engineering Specialist The Aerospace Corporation © The Aerospace Corporation. All Rights Reserved. Integrating Systems and Software Engineering 2007

USC/ISSE 2007 – Peter Hantos Slide 2 Acknowledgements This work would not have been possible without the following:  Reviewers –Suellen Eslinger, Software Engineering Subdivision –Dr. Leslie J. Holloway, Software Acquisition and Process Department –Mary A. Rich, Software Engineering Subdivision  Sponsor –Michael Zambrana, USAF Space and Missile Systems Center, Engineering & Architecture Directorate  Funding source –Mission-Oriented Investigation and Experimentation (MOIE) Research Program (Software Acquisition Task)

USC/ISSE 2007 – Peter Hantos Slide 3 Agenda Objectives Incremental Commitment Model (ICM) – The 10,000 Foot View ICM and DOD (Department of Defense) Acquisition Life Cycle Model Phases Evolutionary Acquisition Selected Evolutionary Acquisition and Spiral Development Challenges Renaming Anchor Points in ICM Conclusions Acronyms References

USC/ISSE 2007 – Peter Hantos Slide 4 Objectives Identify strengths and weaknesses of the new Incremental Commitment Model Explore to what extent the new model will mitigate known problems of the defense acquisition system

USC/ISSE 2007 – Peter Hantos Slide 5 ICM - The 10,000-Foot View* Based on and inherits most characteristics of the Spiral Model  Risk-driven spiral planning is the most significant element The uncoiled spiral metaphor replaces spiral  Every spiral cycle maps into a life cycle phase  For depicting concurrency, builds on the well-known IBM/RUP ® diagram of core process work flows Major emphasis on formalized stakeholder commitment  Anchor Point (AP) reviews are renamed to Commitment Reviews (CR)  The new Commitment Reviews emphasize life cycle phase- entry instead of phase-exit Most CRs are aligned with DOD Acquisition Life Cycle Milestones (See next slide) ____________________ * Discussion is based on [Pew 2007] ® RUP is registered in the U.S. Patent and Trademark Office by IBM/Rational Corporation

USC/ISSE 2007 – Peter Hantos Slide 6 DCR Valuation Commitment Review Development Commitment Review Architecture Commitment Review ICM and DOD Acquisition Life Cycle Model Phases System Development & Demonstration Approval Technology Development Approval A B C Production & Deployment Operations & Support Low-Rate Initial Prod Initial ProdApproval Design Readiness Review Review Concept Refinement Technology Development System Development & Demonstration DODI (12 May 2003) Full Rate Production Approval IOCFOC Concept Decision Pre-Systems Acquisition Systems AcquisitionSustainment ValuationArchitecting Development 1 Architecting 2 Exploration Operations 1 Development 2 Architecting 3 Operations 2 Development 3 Architecting 4 ICM Exploration Commitment Review ECRVCRACRDCR Operations Commitment Review OCR 1 Initial Operational Capability Final Operational Capability … DCR OCR 2

USC/ISSE 2007 – Peter Hantos Slide 7 Evolutionary Acquisition Current DOD direction embraces Evolutionary Acquisition (EA) and Spiral Development (SD)  EA is an acquisition strategy, and SD is a development process –Note that unique life cycle models are associated with both  Per DOD , SD is preferred because (supposedly) it supports EA Current state  EA is well understood and widely practiced  SD is still not well understood, sporadically practiced, and many times misrepresented The following discussion is highly relevant, since ICM is a successor of the Spiral Model

USC/ISSE 2007 – Peter Hantos Slide 8 Selected EA-SD Challenges Uncoiling the spiral and mapping it into DOD phases have been a concern from the beginning  Common interpretation is that spiral increments are mapped into DOD phases –This notion is reinforced by the fact that DOD requires risk- identification and risk-reduction activities in every phase

USC/ISSE 2007 – Peter Hantos Slide 9 Spiraling After Milestone B is Problematic ____________________ Legend: JROC: Joint Requirements Oversight Council PPBE: Planning, Programming, Budgeting, and Execution. For details see [DODP 2003] After Milestone B, system requirements must be agreed to; this is needed to secure funding for the first acquisition increment. Spending of funds is highly constrained.

USC/ISSE 2007 – Peter Hantos Slide 10 Bogeyman – The Nunn-McCurdy Breach Reporting Thresholds“Significant”“Critical” Current Baseline Estimate Is exceeded by +15%+25% Original Baseline Estimate Is exceeded by +30%+50% Congress is very closely monitoring cost growth. Program re-baselining cannot be taken lightly.

USC/ISSE 2007 – Peter Hantos Slide 11 “Conventional” Risk Management vs. Risk-driven Spiral Planning in ICM Spirals Conventional risk management (required by DOD )  Fundamental characteristics –Assigns a likelihood and impact value to the risk to facilitate prioritization –Simple monitoring is an acceptable way of handling risks –Most of the time a risk “burn-down” plan is put in place for risk mitigation  In all cases the contractor is supposed to have the costs associated with risk mitigation in the baseline –Alternative development paths and experiments might be chosen to deal with risks, but the contracted cost and schedule must not be impacted Risk-driven spiral planning  All parameters of upcoming increments are “up for grab”  Number of spirals should not be administratively limited –In fact, spinning-off iterations with engineering objectives, even without delivering any additional, useful functionality is an essential characteristic of iterative development Iteration represents a sensible engineering approach, but might be incompatible with the overarching acquisition structure.

USC/ISSE 2007 – Peter Hantos Slide 12 The Previously Shown Spiral Mapping Does Not Support EA The previously shown mapping of spiral increments has nothing to do with EA; those spirals are localized, internal matters of a single acquisition increment Spirals shown in the earlier mapping are far removed from the upgrade decision that triggers the creation of the new acquisition increment A more reasonable interpretation is as follows:

USC/ISSE 2007 – Peter Hantos Slide 13 Renaming Anchor Points to Commitment Reviews in ICM CR equivalents of key Anchor Points  LCO (Life Cycle Objectives)  ACR (Architecture Commitment Review)  LCA (Life Cycle Architecture)  DCR (Development Commitment Review)  IOC (Initial Operational Capability)  OCR (Operations Commitment Review) The new naming conventions emphasize the importance of stakeholder commitment at the entry to the next phase  Pros and cons: –The positive impact is the reinforcement and codification of the principles that were used to create the Win-Win extension of the Spiral Model –The negative impact is that – inadvertedly – the Anchor Point objectives got deemphasized

USC/ISSE 2007 – Peter Hantos Slide 14 Conclusions Strengths:  ICM is a promising, new, development life cycle model  Recent ICM publications do contribute to the better understanding of spiral development principles  In ICM the original spiral graphical metaphor has been replaced with the uncoiled spiral, making the model’s use easier for project managers  ICM emphasizes the importance of gaining stakeholder commitment before progressing to the next life cycle phase Weaknesses:  The renaming of APs to CRs deemphasized the earlier, important notion in the Spiral Model that all activities in a spiral increment are focusing on the satisfaction of the objectives of the upcoming Anchor Point  The mapping of ICM Anchor Points into the DOD milestones is artificial and not supportive of either the DOD Instruction in general, or its preferred, Evolutionary Acquisition strategy in particular

USC/ISSE 2007 – Peter Hantos Slide 15 Acronyms

USC/ISSE 2007 – Peter Hantos Slide 16 References

USC/ISSE 2007 – Peter Hantos Slide 17 Contact Information Peter Hantos The Aerospace Corporation P.O. Box M1/112 Los Angeles, CA Phone: (310)

USC/ISSE 2007 – Peter Hantos Slide 18 All trademarks, service marks, and trade names are the property of their respective owners