University of Southern California
Center for Systems and Software Engineering
SoS Engineering and the ICM
Workshop Overview
Jo Ann Lane
USC CSSE
jolane@usc.edu
Gary Hafen
Lockheed Martin
gary.hafen@lmco.com
Judith Dahmann
Mitre
jdahmann@mitre.org
University of Southern California
Center for Systems and Software Engineering
Systems of Systems Issues
• Quality factor tradeoffs
• Topic-specific
– Quality of service evidence
development across
wide/deep/long combinations
of component
systems/subcontractor
levels/increments
•
Cost and risk
– Wide/deep/long risk
coordination, tracking SoSspecific cost estimation
proxies for SoS critical path
scheduling
•
– SoSE team planning,
organizing, staffing,
controlling, and directing
– What and what not to delegate
to systems developers
– How to plan and execute a
multi-owner SoS anchor point
milestone review
– Mapping the new SoSE
Guidebook to the ICM
•
Other
– How to determine the right
battle rhythm
– What to review at SoS anchor
point milestone commitment
reviews
– What are the important work
products/artifacts at the SoS
level
– What should an SoSE team pay
attention to/not pay attention to
Requirements
– Wide/deep/long rapid
requirements renegotiation
•
Competitive prototyping
– What is the role of CP in an
SoS
– When would you use it
July 2008
©USC-CSSE
2
University of Southern California
Center for Systems and Software Engineering
Core Elements of SoS SE
Translating
Translating
capability
Translating
capability
objectives
capability
objectives
objectives
Assessing
Assessing
(actual)
Assessing
(actual)
performance
performance
performance
totocapability
to capability
capability
objectives
objectives
objectives
Orchestrating
Orchestrating
Orchestrating
upgrades
upgrades
upgrades
to
toSoS
SoS
Understanding
Understanding
systems
Understanding
systems&&
relationships
relationships
systems &
(includes
(includesplans)
plans)
relationships
to SoS
Addressing
Addressing
new
Addressing
new
requirements
requirements
requirements
&
&
solution
&options
options
Developing,
Developing,
Developing
evolving
and
evolving and
maintaining
&
evolving
maintaining
SoS design/arch
SoS
SoS design/arch
architecture
options
New
SoS SE
role
Persistent
SoS overlay
framework
SoS
upgrade
process
External
influences
Monitoring
Monitoring
Monitoring
&
assessing
&changes
assessing
& assessing
changes
changes
External Environment
July 2008
©USC-CSSE
3
University of Southern California
Center for Systems and Software Engineering
ICM HSI Levels of Activity for Complex Systems
July 2008
Need to add mapping to SoS SE “trapeze chart”4
©USC-CSSE
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
Translating capability objectives
Understanding systems & relationships
Monitoring & assessing changes
Developing
& evolving SoS
architecture
Addressing requirements & solution options
Orchestrating upgrades to SoS
Assessing performance to capability objectives
July
2008
03/19/2008
©USC-CSSE
5
University of Southern California
Center for Systems and Software Engineering
Hybrid Agile/Plan-Driven Development Process
for Single Software-Intensive Systems
Unforeseeable Change (Adapt)
Future Increment Baselines
Agile
Rebaselining for
Future Increments
Rapid
Change
Foreseeable
Change
(Plan)
Short
Development
Increments
Increment N Baseline
Stable Development
Increments
High
Assurance
Current V&V
Resources
Continuous V&V
July 2008
Deferrals
Short, Stabilized
Development
of Increment N
Artifacts
Operations and Maintenance
Concerns
Verification and
Validation (V&V)
of Increment N
©USC-CSSE
Increment N Transition/
Future V&V
Resources
6