University of Southern California Center for Systems and Software Engineering SoS Engineering and the ICM Workshop Overview Jo Ann Lane USC CSSE Gary Hafen Lockheed Martin Judith Dahmann Mitre

University of Southern California Center for Systems and Software Engineering July 2008©USC-CSSE2 Systems of Systems Issues Quality factor tradeoffs –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 SoS- specific cost estimation proxies for SoS critical path scheduling Requirements –Wide/deep/long rapid requirements renegotiation Competitive prototyping –What is the role of CP in an SoS –When would you use it Topic-specific –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

University of Southern California Center for Systems and Software Engineering July 2008©USC-CSSE3 Core Elements of SoS SE New SoS SE role SoS upgrade process Persistent SoS overlay framework External influences Translating capability objectives Translating capability objectives Translating capability objectives Addressing new requirements & options Addressing new requirements & options Addressing requirements & solution options Understanding systems & relationships (includes plans) Understanding systems & relationships (includes plans) Understanding systems & relationships External Environment Developing, evolving and maintaining SoS design/arch Developing, evolving and maintaining SoS design/arch Developing & evolving SoS architecture Assessing (actual) performance to capability objectives Assessing (actual) performance to capability objectives Assessing performance to capability objectives Orchestrating upgrades to SoS Orchestrating upgrades to SoS Orchestrating upgrades to SoS Monitoring & assessing changes Monitoring & assessing changes Monitoring & assessing changes

University of Southern California Center for Systems and Software Engineering July 2008©USC-CSSE4 ICM HSI Levels of Activity for Complex Systems Need to add mapping to SoS SE “trapeze chart”

University of Southern California Center for Systems and Software Engineering July 2008©USC-CSSE5 03/19/2008 ©USC-CSSE The Incremental Commitment Life Cycle Process: Overview Stage I: DefinitionStage II: Development and Operations Developing & evolving SoS architecture Translating capability objectives Understanding systems & relationships Monitoring & assessing changes Addressing requirements & solution options Orchestrating upgrades to SoS Assessing performance to capability objectives

University of Southern California Center for Systems and Software Engineering July 2008©USC-CSSE6 Hybrid Agile/Plan-Driven Development Process for Single Software-Intensive Systems Agile Rebaselining for Future Increments Short, Stabilized Development of Increment N Verification and Validation (V&V) of Increment N Deferrals ArtifactsConcerns Rapid Change High Assurance Future Increment Baselines Increment N Transition/ Operations and Maintenance Future V&V Resources Increment N Baseline Current V&V Resources Unforeseeable Change (Adapt) Short Development Increments Foreseeable Change (Plan) Stable Development Increments Continuous V&V