University of Southern California Center for Software Engineering CSE USC MBASE Essentials Planning and control Milestone content Process models Life cycle Anchor Points; Risk management Key practices Success models Business case IKIWISI Stakeholder win-win Product models Evaluation and analysis Process entry/exit criteria Product Evaluation criteria Domain models; Requirements; Architecture; Code; Documentation Property models Cost Schedule Performance Reliability …

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE2 Waterfall Misconceptions

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE3 Outline Spiral Model Life Cycle Anchor Points MBASE/RUP Activity/Process ModelMBASE/RUP Activity/Process Model COCOTS: Development ModelCOCOTS: Development Model MBASE Integration Framework & ProcessMBASE Integration Framework & Process MBASE ModelsMBASE Models a lecture on the philosophy behind MBASE, the types of things MBASE does and why, and an overview of OCD and SSRD

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE4 Spiral Model Original spiral and common misinterpretations Six spiral essentials –Examples and counterexamples –Relation to CMMI Hazardous spiral lookalikes to avoid

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE5 Original Spiral and Misinterpretations? Common Misinterpretations –Hack some prototypes –Fit spiral into waterfall –Incremental waterfalls –Suppress risk analysis –No concurrency, feedback –One-size-fits-all model

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE6 “Spiral Development” Definition A risk-driven process model generator Used to guide concurrent engineering Two distinguishing features: –Cyclic approach for growing system definition –Anchor point stakeholder-commitment milestones

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE7 Six Spiral Model Essentials 1. Concurrent determination of artifacts in each cycle 2. Each cycle addresses objectives, constraints, alternatives, risks, artifact elaboration, stakeholders’ commitment 3. Risk-driven activity level of effort 4. Risk-driven artifact degree of detail 5. Managing stakeholder commitments via anchor-point milestones 6. Emphasis on system and life-cycle issues - vs. software and development issues

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE8 Life Cycle Anchor Points Common System/Software stakeholder commitment points –Defined in concert with Government, industry affiliates –Coordinated with the Rational Unified Process Life Cycle Objectives (LCO) –Stakeholders’ commitment to support architecting –Like getting engaged Life Cycle Architecture (LCA) –Stakeholders’ commitment to support full life cycle –Like getting married Initial Operational Capability (IOC) –Stakeholders’ commitment to support operations –Like having first child

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE9 MBASE/RUP Activity/Process Model

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE10 2. COTS Tailoring 1. COTS Assessment 3. Glue Code Development 4. System Effort due to COTS Volatility New System Development Not Involving COTS Components Time Staffing LCO (Requirements Review) LCA (PDR) IOC (SAR) LCO – Lifecycle Objectives LCA – Lifecycle Architecture IOC – Initial Operational Capability COCOMO II Effort Estimate COCOTS Effort Estimate Elaboration (RR) Construction COCOTS: Development Model

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE11 (Risk-driven level of detail for each element) *WWWWWHH: Why, What, When, Who, Where, How, How Much Milestone ElementLife Cycle Objectives (LCO)Life Cycle Architecture (LCA) Definition of Operational Concept Top-level system objectives and scope - System boundary - Environment parameters and assumptions - Evolution parameters Operational concept - Operations and maintenance scenarios and parameters - Organizational life-cycle responsibilities (stakeholders) Elaboration of system objectives and scope of increment Elaboration of operational concept by increment Top-level functions, interfaces, quality attribute levels, including: - Growth vectors and priorities - Prototypes Stakeholders’ concurrence on essentials Elaboration of functions, interfaces, quality attributes, and prototypes by increment - Identification of TBD’s( (to-be-determined items) Stakeholders’ concurrence on their priority concerns Top-level definition of at least one feasible architecture - Physical and logical elements and relationships - Choices of COTS and reusable software elements Identification of infeasible architecture options Choice of architecture and elaboration by increment - Physical and logical components, connectors, configurations, constraints - COTS, reuse choices - Domain-architecture and architectural style choices Architecture evolution parameters Elaboration of WWWWWHH* for Initial Operational Capability (IOC) - Partial elaboration, identification of key TBD’s for later increments Assurance of consistency among elements above All major risks resolved or covered by risk management plan Identification of life-cycle stakeholders - Users, customers, developers, maintainers, interoperators, general public, others Identification of life-cycle process model - Top-level stages, increments Top-level WWWWWHH* by stage Assurance of consistency among elements above - via analysis, measurement, prototyping, simulation, etc. - Business case analysis for requirements, feasible architectures Definition of System Requirements Definition of System and Software Architecture Definition of Life- Cycle Plan Feasibility Rationale System Prototype(s) Exercise key usage scenarios Resolve critical risks Exercise range of usage scenarios Resolve major outstanding risks Win Win Spiral Anchor Points

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE12 Where do objectives, constraints, alternatives come from? –Win Win extensions Lack of intermediate milestones –Anchor Points: LCO, LCA, IOC –Concurrent-engineering spirals between anchor points Need to avoid model clashes, provide more specific guidance –MBASE Spiral Model Refinements

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE13 MBASE Model Integration Framework Process models Life cycle anchor points Risk management Key practices Success models Business case IKIWISI Stakeholder win-win Property models Cost Schedule Performance Reliability Product models Domain model Requirements Architecture Code Documentation Planning and control Milestone content Evaluation and analysis Process entry/exit criteria Product evaluation criteria

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE14 MBASE Invariants and Variants 1. Use of particular success, process, product, or property models. 2. Choice of process or product representation. 3. Degree of detail of process, product, property, or success modeling. 4. Number of spiral cycles or builds between anchor points. 5. Mapping of activities onto Inception-Elaboration-Construction- Transition phases. 6. Mapping of staff levels onto activities. 1. Defining and sustaining a stakeholder win-win relationship through the system's life-cycle. 2. Using the MBASE Model Integration Framework. 3. Using the MBASE Process Integration Framework. 4. Using the LCO, LCA, and IOC Anchor Point milestones. 5. Ensuring that the content of MBASE artifacts and activities is risk- driven. VariantsInvariants

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE15 MBASE Model Integration Process

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE16 MBASE Process Framework

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE17 MBASE Model Integration: LCO Stage Domain Model WinWin Taxonomy Basic Concept of Operation Frequent Risks Stakeholders, Primary win conditions WinWin Negotiation Model IKIWISI Model, Prototypes, Properties Models Environment Models WinWin Agreements, Shared Vision Viable Architecture Options Updated Concept of Operation Life Cycle Plan elements Outstanding LCO risks Requirements Description LCO Rationale Life Cycle Objectives (LCO) Package Anchor Point Model determines identifies determines situatesexercise focus use of focus use of determines guides determination of validate inputs for provides initializeadoptidentify update achieveiterate to feasibility, consistency determines exit criteria for validates readiness of initializesinitializes

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE18 MBASE Models* Iterations Release Description Test Plan Test Results Peer Review Report Users Manual CTS OCD Shared Vision System Capabilities Key Stakeholders System Boundary & Environment Top-Level Business Case Domain & Organization Description Proposed System Prototyping Proj. Reqts. Capability Reqts. System Interface Level of Service Reqts. Evolution Reqts. SSRD SSAD System Analysis Architecture Design & Analysis Implementation Design LCP Milestones and Products Responsibilities Approach, Resources FRD/CTS Business Case Reqts. Satisfaction Process Rationale Risk Assessment Iteration Plan Quality Plan * Not exhaustive

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE19 Operations Model` Object Model Capability Requirements System Definition Class Model Project Requirements Statement of Purpose Project Goals Organization Goals System Capabilities Component Model Organization Entities Behavior Model Enterprise model Domain DescriptionSystem AnalysisSystem Design Operational Concept Description (OCD) System and Software Requirements Definition (SSRD) System and Software Architecture Description (SSAD) Organization Background Organization Activities Interaction Model Levels of Service Goals LOS Requirements Coverage/Traceability of MBASE Product Models* * Does not include all MBASE models Release Description Reqts. Satisfaction Capability Tests Data Structures Methods/functions LOS Tests Implementation Construction,Transition,Support (CTS) External to MBASE

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE Project Activities

University of Southern California Center for Software Engineering CSE USC 4/30/01©USC-CSE21 CS577 MBASE Documents