1. ICM_Sw Essentials for CS510
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
Domain models;
Requirements;
Architecture;
Code;
Documentation
Property models
Cost
Schedule
Performance
Reliability …

2. Six Spiral and ICM 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
8/29/08
© USC-CSSE

3. Incremental Commitment Models
The Incremental Commitment Models (ICMs) for System Life Cycle Processes
For Systems (Human, Hardware and Software)
ICM for Software Intensive Systems (ubiquitous hardware)
ICM for Software (only) Systems
ICMs solve Spiral Model problems
Use spiral principles vs. diagram
Relate to stakeholder commitments and values: Make concurrency explicit
Use risk to explicitly show go-backs and skips
Provide view for handling mini-spirals
8/29/08
© USC-CSSE

4. Incremental Commitment Model for Systems
8/29/08
© USC-CSSE

5. ICM Showing Software Systems
8/29/08
© USC-CSSE

6. ICM Showing Multi-Build Software in Systems
8/29/08
© USC-CSSE

7. ICM-LeanMBASE/RUP Activity/Process Model
8/29/08
© USC-CSSE

8. ICM P3S (nee 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
8/29/08
© USC-CSSE

9. ICM_Sw & P3S (nee MBASE) Invariants and Variants
1. Use of particular success, process, product, or property models.
  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.
Variants
Invariants
8/29/08
© USC-CSSE

10. ICM_Sw & P3S (nee MBASE) Model Integration Process
8/29/08
© USC-CSSE

11. ICM-LeanMBASE/RUP Activity/Process Model
8/29/08
© USC-CSSE