Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22University of Southern CaliforniaCenter for Software Engineering C S E USCBarry Boehm, USCCS 510 Lecture Fall 2011Value-Based Software Engineering and the Incremental Commitment Spiral ModelAugust 24, 2011 1© USC-CSSEUniversity of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011 © USC-CSSE 2Outline•VBSE theory and process overview•Implementing VBSE via the Incremental Commitment Spiral Model–ICSM nature, origins, and framework–Example commercial application–Decision table for common special cases•Conclusions and referencesUniversity of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011 © USC-CSSE 3Theory W: Enterprise Success Theorem– And informal proofTheorem: Your enterprise will succeed if and only if it makes winners of your success-critical stakeholders•Proof of “if”:Everyone that counts is a winner.Nobody significant is left to complain.•Proof of “only if”:Nobody wants to lose.Prospective losers will refuse to participate, or will counterattack.The usual result is lose-lose.University of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011 © USC-CSSE 4Theory W: WinWin Achievement TheoremMaking winners of your success-critical stakeholders requires:i. Identifying all of the success-critical stakeholders (SCSs).ii. Understanding how the SCSs want to win.iii. Having the SCSs negotiate a win-win set of product and process plans.iv. Controlling progress toward SCS win-win realization, including adaptation to change.University of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011 © USC-CSSE 5Initial VBSE Theory: 4+1•Engine: Theory W (stakeholder win-win): What values are important?–Enterprise Success Theorem–Theory of Justice–Win-Win Equilibrium and Negotiation•Four Supporting Theories–Dependency Theory: How do dependencies affect value realization?–Results chains; value chains; cost/schedule/performance tradeoffs–Utility Theory: How important are the values?–Multi-attribute utility; Maslow need hierarchy–Decision Theory: How do values determine decisions?–Investment theory; game theory; statistical decision theory–Control Theory: How to monitor and control value realization–Feedback control; adaptive control; spiral risk controlUniversity of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011 © USC-CSSE 6VBSE Theory 4+1 StructureUtility TheoryTheory W:SCS Win-WinDecision TheoryDependency TheoryControl TheoryHow do dependencies affect value realization?How to adapt to change and control value realization?How do values determine decision choices?How important are the values?What values are important?How is success assured?University of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011 © USC-CSSE 7Initial VBSE Theory: 4+1 Process– With a great deal of concurrency and backtrackingUtility TheoryTheory W:SCS Win-WinDecision TheoryDependency TheoryControl Theory6a, 7c. State measurement, prediction, correction; Milestone synchronization5a. Investment analysis, Risk analysis1. Protagonist goals3a. Solution exploration7. Risk, opportunity, change management5a, 7b. Prototyping2a. Results Chains3b, 5a, 7b. Cost/schedule/performance tradeoffs2. Identify SCSs3b, 7a. Solution Analysis5a, 7b. Option, solution development & analysis4. SCS expectations management3. SCS Value Propositions(Win conditions)SCS: Success-Critical Stakeholder6, 7c. Refine, Execute, Monitor & Control Plans5. SCS Win-Win NegotiationUniversity of Southern CaliforniaCenter for Software Engineering C S E USCNeed Incremental Approach to VBSE Process •Cannot make all decisions in a single pass–Emergent technology: social networking–Emergent requirements: outdo competitors–TBD standards: information exchange; infrastructure–Evolving platforms: mobile devices–Emerging stakeholders: strategic partners, suppliers•Best to incrementally define scope, features, details–But do best-effort architecting for the future•Avoid easiest-first increments on large, critical projects•Concurrently determine requirements and solutions•Best to incrementally develop product features–Avoid obsolete deliveries–Early focus on critical infrastructure, high-value featuresAugust 24, 2011 © USC-CSSE 8University of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011The Broadening Early Cone of Uncertainty (CU)•Need greater investments in narrowing CU–Mission, investment, legacy analysis–Competitive prototyping–Concurrent engineering–Associated estimation methods and management metrics•Larger systems will often have subsystems with narrower CU’sGlobal Interactive, BrownfieldBatch, GreenfieldLocal Interactive,Some Legacy9© USC-CSSEUniversity of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 201110Rapid Change Creates a Late Cone of Uncertainty– Need incremental vs. one-shot developmentUncertainties in competition, technology, organizations, mission priorities 10© USC-CSSEUniversity of Southern CaliforniaCenter for Software Engineering C S E USCAnimated displaysSecondary application functionsUser amenitiesMain application functionsNatural speech inputTertairy application functionsBasic application functionsData management systemOperating SystemInvestment High-payoff Diminishing returnsCost of software productValue of software product to organizationSoftware Production Function August 24, 2011 11© USC-CSSEUniversity of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011 © USC-CSSE 12Outline•VBSE theory and process overview•Implementing VBSE via the Incremental Commitment Spiral Model–ICSM nature, origins, and framework–Example commercial application–Decision table for common special cases•Conclusions and referencesUniversity of Southern CaliforniaCenter for Software Engineering C S E USCAugust 24, 2011What is the ICSM?•Risk-driven framework for determining and evolving best-fit system life-cycle process•Integrates the strengths of phased and risk-driven spiral process models •Synthesizes together principles critical to successful system development–Stakeholder value-based system definition and