COSOSIMO* Workshop Outbrief 14 March 2006 Jo Ann Lane University of Southern California Center for Software Engineering CSE Annual Research Review – March 2006 © USC CSE 2006 *COSOSIMO: Constructive System of Systems Integration Cost Model

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR Agenda Workshop objectives Review of scope of COSOSIMO Review of last workshop discussions COSOSIMO cost model parameters –Updated definitions –One more survey Case Study: View of COSOSIMO within the COCOMO Suite (if time permits)

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR Objective of March 2006 COSOSIMO Workshop To converge upon a relevant and complete set of parameters for the COSOSIMO model that –Are easily discerned in the early stages of SoS development –Minimal overlap with each other –Can be used to start cost model data collection activities

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR Attendees George Hulling, Disciplined Software Engineering Suzanne Dawes, Aerospace Josh Wilson, Price Systems Karen Owens, Aerospace Bettina Babbitt, Aerospace Tony Jordano, SAIC Peter Hantos, Aerospace Ed Casey, Raytheon Gary Thomas, Raytheon Garry Roedler, Lockheed Martin Anthony Peterson, Raytheon Miles Nesman, Boeing Jim Cain, BAE Systems David Seaver, Price Systems Marilee Wheaton, Aerosapce Linda Hwang, Northrop Grumman Dan Ligett, Softstar Systems Ali Nikolai, SAIC Ricardo Valerdi, MIT Rosalind Lewis, Aerospace Barry Boehm, USC Jo Ann Lane, USC 22 attendees from 11 organizations

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR Scope of COSOSIMO Designed to estimate Lead System Integrator (LSI) effort associated with the development of net-centric systems-of- systems (SoS) Initial model to focus on first increment/evolution of SoS Covers LSI types of EIA 632 activities with special emphasis on –Concurrent SoS scoping, planning, requirements, architecting –Source selection –Teambuilding, re-architecting, feasibility assurance with selected suppliers –Incremental acquisition management Development Integration and test –Continuous change, risk, and opportunity management

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR What is a “System-of-Systems”? Very-large systems developed by creating a framework or architecture to integrate –Existing systems –Systems currently under development –New systems to be developed SoS system components independently developed and managed Business Domain: enterprise-wide integration and sharing of core business information across functional and geographical areas Military Domain: dynamic communications infrastructure to support operations in a constantly changing, sometimes adversarial, environment SoS activities often planned and coordinated by a Lead System Integrator (LSI) Net-Centric SoSNet-Centric SoS

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR What is a “Lead System Integrator”? Organization (or set of organizations) selected to oversee the definition, development and integration of an SoS Typical activities –Lead concurrent engineering of requirements, architecture, and plans –Identify and evaluate technologies to be integrated –Conduct source selection –Coordinate supplier activities and validate SoS architecture feasibility –Integrate and test SoS-level capabilities –Manage changes at the SoS level and across the SoS-related IPTs Typically do not develop system components to be integrated (possible exception: SoS infrastructure)

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR COSOSIMO Parameter Discussion and Survey Parameters Reviewed –Current COSYSMO parameters, some tailored for SoS/LSI environment –All proposed COSOSIMO parameters Goals –To determine if some set/calibration of COSYSMO is sufficient to estimate LSI effort for developing an SoS –To determine comprehensive set that can be used to start data collection activities Aspects discussed –How applicable parameter is to LSI effort –How easily discerned in early design phase –Reasonable discriminators in high-to-low spectrum? –Are LSIs honest when evaluating parameter—or are their political aspects that hinder usefulness of parameter?

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR COSOSIMO Parameter Discussion Size Drivers –# of SoS requirements –# of system interfaces –# of SoS interface protocols –# of algorithms –# of operational scenarios –# of independent system component organizations –# of unique system components Cost Drivers –Requirements understanding –Architecture understanding –Architecture maturity –Level of service requirements –Migration complexity –Technology risk Cost Drivers (continued) –Documentation –# and diversity of installations/platforms –# of recursive levels in the design –Stakeholder team cohesion –Personnel/SoS team capability –Personnel experience/continuity –Process capability/maturity of LSI’s processes –Multi-site coordination –Tool support –Cost/schedule compatibility –SoS risk resolution –Component system maturity and stability –Component system readiness

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR Survey “Quick Look” Results 10 completed survey forms submitted (more expected) Size drivers: average rating of High-to-Medium for all except # of algorithms which was Low-to-n/a Cost drivers –Two-thirds or more of respondents rated most cost drivers High-to- Medium –Exceptions: Documentation, # of Recursive Levels in the Design, Tool Support 5 out of 10 respondents had some LSI experience –No significant difference in LSI responses except for Tool Support which was rated Medium by 4 of 5 respondents Several recommendations provided to –Combine some cost drivers –Remove overlap from drivers

COSOSIMO Workshop Outbrief © USC CSE 2006 CSE ARR Next Steps Collect additional inputs from LSIs on selected SoS programs Attempt to identify and model higher-impact drivers to simplify cost model