ICM and Software Sub-Systems
Transcript of ICM and Software Sub-Systems
© 2005-07 AWBrown BES/MSEE & USC Center for Software Engineering 1 of 16 03/25/082/9/20092/9/2009
University of Southern California
Center for Systems and Software Engineering
ICM and Software Sub-Systems
A Winsor Brown [email protected]
Feb. 2, 2009
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 2 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
Systems Development Life Cycle
MBASE/RUP -- ICM for software systems
ICM for Software Intensive Systems & Systems of Systems
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 3 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
RUP/MBASE Application Development Model1 I
R
R
L
C
A
I
O
C
P
R
R
L
C
O
C
C
D
1 (efforts not to scale)
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 4 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
ICM LC Processes For Systems (Hw, Sw & Pw)
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 5 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
Why Multiple Build Software Systems Simplest: Early Functionality in the hands of ALL users
• Architecture/Core plus some funcitonality
• Implies Full Qualification/Acceptance Testing each cycle
Increasingly Complex
• Multiple, diverse "platforms"
• Different "foci" of funcitonality
• Network Centric Systems Operation
−−−− Evolution/federation of legacy systems
−−−− System of Systems by design
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 6 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
Overlaps Across Software Builds
Inception Elaboration Construction Transition
Inception Elaboration Construction Transition
Evolve During Transition [After Sw IOC]
Evolve After Architecture Complete
Incept. Elaboration Construction Transition
Inception Elaboration with Evol. Req. Construction Transition
I. Elab. Construction Transition
. . .
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 7 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
ICM Showing Multi-Build Software in Systems
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 8 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
COINCOMO Direction
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 9 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
ICM Showing Multi-Build Software in DSOSystems
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 10 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 11 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
Background
WinWin Spiral Model (WWSM)
WWSM: CSCI577 Unrolled with Repeated Cycles
ICM & CSCI577ab (2007-2008): Much easier for students and clients to understand
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 12 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
Background and Definitions (cont.) WinWin Spiral Model
• Risk Driven Selection, Execution and Validation of Activities and Products
• Feasibility "demonstration" needed to proceed
• Stakeholder concurrence to proceed at major milestones
• Life Cycle Process(s) Model Generator: Select and document/plan for next "rounds" a specific "Development Process Model".
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 13 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
Stylized WinWin Spiral with Activities Mapped to Original Spiral[radial dimension (cost) not to scale]
2a. EvaluateAlternativeswith respect toOC&Ps
1b. StakeholdersIdentify SystemObjectives, Constrains,& Priorities (OC&Ps)Alternatives SolutionsElements
1a. IdentifySuccess-CriticalStakeholders
2b.Assess,AddressRisks
3. ElaborateProduct andProcessDefinition4. Verify and Validate
Product and ProcessDefinitions
Stakeholders’
Commitment4
5
6
8
2
1
Stakeholders’Review
7
3
L COL CACC DI OC
Progress Through Steps
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 14 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
WWSM: CSCI577 Unrolled With Repeated Cycles
EOCDInc. Cycle
already
doneI & E
Key: IRR - Inception Readiness Review LCO - Life Cycle Objective
LCA - Life Cycle Architecture RLCA- Rebaselined LCA
L
C
A
R
L
C
A
C
CD
Time Line
SemesterBreak
StartOf Fall
Semester
SpringSemester
Ends
Inc. Elaboration Construction Transition
LC
O
IRR
R
RR
2
IOC
T
RR
1
T R
R RR R
2 1
EOCD
I E C T
Fall Elab. Cycle Const. Cycle Prelim. Trans.
SummerSemester
Ends
CCD- Core Capability Demo. IOC- Initial Operational CapabilityTRR- Transition Readiness ReviewPRR - Product Release Review
Enhancement Cycle?
ICM and Software Sub-Systems
© 2005 AWBrown BES/MSEE & USC Center for Software Engineering 15 of 16 2/9/2009
University of Southern California
Center for Systems and Software Engineering
577ab Software ICM