University of Southern California Center for Systems and Software Engineering A Process Decision Table for Integrated Systems and Software Engineering Barry Boehm and Jo Ann Lane USC CSSE Presented by Marilee Wheaton University of Southern California Center for Systems and Software Engineering ICM Nature and Origins Integrates hardware software and human factors elements of systems engineering Concurrent exploration of needs and opportunities Concurrent engineering of hardware software human aspects Concurrency stabilized via anchor point milestones Developed in response to DoD related issues Clarify spiral development usage in DoD Instruction 5000 2 Initial phased version 2005 Explain Future Combat System of systems spiral usage to GAO Underlying process principles 2006 Provide framework for human systems integration National Research Council report 2007 Integrates strengths of current process models But not their weaknesses USC CSSE March 2008 2 University of Southern California Center for Systems and Software Engineering Process Model Principles Principles trump diagrams 1 2 3 Commitment and accountability Success critical stakeholder satisficing Incremental growth of system definition and stakeholder commitment 4 5 Concurrent iterative system definition and development cycles Cycles can be viewed as sequential concurrentlyperformed phases or spiral growth of system definition 6 Risk based activity levels and anchor point commitment milestones Used by 60 80 of CrossTalk Top 5 projects 2002 2005 March 2008 USC CSSE 3 University of Southern California Center for Systems and Software Engineering The Incremental Commitment Life Cycle Process Overview Stage I Definition Stage II Development and Operations Anchor AnchorPoint Point Milestones Milestones Synchronize Synchronize stabilize stabilizeconcurrency concurrencyvia viaFEDs FEDs Risk Riskpatterns patterns determine determinelife life cycle cycleprocess process March 2008 03 19 2008 USC CSSE 4 University of Southern California Center for Systems and Software Engineering Common Risk Driven Special Cases of the ICM Special Case Example Size Complexity Change Rate Month Criticality NDI Support 1 Use NDI Small Accounting 2 Agile E services Low 1 30 Low Med Good in place 3 Architected Agile Business data processing Med 1 10 Med High 4 Formal Methods Security kernel Safety critical LSI chip Low 0 3 5 HW component with embedded SW Multi sensor control device Low 6 Indivisible IOC Complete vehicle platform 7 NDI Intensive Org Personnel Capability Key Stage I Activities Incremental Definition Key Stage II Activities Incremental Development Operations Acquire NDI Use NDI Agile ready Med high Skip Valuation Architecting phases Scrum plus agile methods of choice 1 day 2 6 weeks Good most in place Agile ready Med high Combine Valuation Architecting phases Complete NDI preparation Architecture based Scrum of Scrums 2 4 weeks 2 6 months Extra High None Strong formal methods experience Precise formal specification Formally based programming language formal verification 1 5 days 1 4 weeks 0 3 1 Med Very High Good In place Experienced med high Concurrent HW SW engineering CDRlevel ICM DCR IOC Development LRIP FRP Concurrent Version N 1 engineering SW 1 5 days Market driven Med High 0 3 1 High Very High Some in place Experienced med high Determine minimum IOC likely conservative cost Add deferrable SW features as risk reserve Drop deferrable features to meet conservative cost Strong award fee for features not dropped SW 2 6 weeks Platform 6 18 months Supply Chain Management Med High 0 3 3 Med Very High NDI driven architecture NDI experienced Med high Thorough NDI suite life cycle costbenefit analysis selection concurrent requirements architecture definition Pro active NDI evolution influencing NDI upgrade synchronization SW 1 4 weeks System 6 18 months 9 Hybrid agile plan driven system C4ISR Med Very High Mixed parts 1 10 Mixed parts Med Very High Mixed parts Mixed parts Full ICM encapsulated agile in high change low medium criticality parts Often HMI external interfaces Full ICM three team incremental development concurrent V V nextincrement rebaselining 1 2 months 9 18 months 9 Multi owner system of systems Net centric military operations Very High Mixed parts 1 10 Very High Many NDIs some in place Related experience medhigh Full ICM extensive multi owner team building negotiation Full ICM large ongoing system software engineering effort 2 4 months 1824 months 10 Family of systems Medical Device Product Line Med Very High 1 3 Med Very High Some in place Related experience med high Full ICM Full stakeholder participation in product line scoping Strong business case Full ICM Extra resources for first system version control multistakeholder support 1 2 months 918 months Complete Time per Build per Increment C4ISR Command Control Computing Communications Intelligence Surveillance Reconnaissance CDR Critical Design Review DCR Development Commitment Review FRP Full Rate Production HMI Human Machine Interface HW Hard ware IOC Initial Operational Capability LRIP Low Rate Initial Production NDI Non Development Item SW Software March 2008 USC CSSE 5 University of Southern California Center for Systems and Software Engineering Case 1 Use NDI Exploration phase identifies NDI opportunities NDI risk opportunity analysis indicates risks acceptable Product growth envelope fits within NDI capability Compatible NDI and product evolution paths Acceptable NDI volatility Some open source components highly volatile Acceptable usability dependability interoperability NDI available or affordable Example Small accounting system Size complexity Low Anticipated change rate per month Low Criticality Low NDI support Complete Organization and personnel capability NDI experienced Key Stage I activities Acquire NDI Key Stage II activities Use NDI Time build Driven by time to initialize tailor NDI Time increment Driven by NDI upgrades March 2008 USC CSSE 6 University of Southern California Center for Systems and Software Engineering Case 2 Pure Agile Methods Exploration phase determines Low product and project size and complexity Fixing increment defects in next increment acceptable Existing hardware and NDI support of growth envelope Sufficient agile capable personnel Need to accommodate rapid change emergent requirements early user capability Example E services Size complexity Low Anticipated change rate per month 1 30 Criticality Low to medium NDI support Good in place