1. Agile concepts in System of Systems engineering Alexey Tregubov

2. Outline What is a System of Systems (SoS)? Common problems in SoS
Kanban-based scheduling system for SoS
Comparison with ICSM

3. System of systems
System of systems is a collection of systems that together to create a new, more complex system which offers more functionality and performance than simply the sum of the constituent systems.

4. System of systems around us:
SoSs within Our Homes
Enterprise-wide SoS:
Regional Area Crisis Response SoS
National and International Defense SoS

5. System of systems: example

6. System of systems: example

7. Common problems in SoS Lack of flexibility and predictability
Bad coordination across multiple projects
Business value not delivered in time

8. Kanban-based scheduling system (KSS)
The proposed Kanban levels are:
Executive/Stakeholder Management (ESM)
Capability Engineering (CE)
Product/Domain Engineering (PDE)
The ESM level is the level that determines which proposed capabilities (or capability enhancements) are going to be approved for development.
Capability engineering level represents all capability-related SE activities, specialty SE support for product teams, including software system engineering tasks, where software is a key component in the requirements allocation.
At the PDE level, there are separate KSSs for each product or domain team in the enterprise.
The User Support Team operates at the PDE level because it primarily interfaces with the product and domain teams. There are occasions, however, when it influences the needs backlogs, or when it uncovers an issue (e.g. patient safety or privacy) that requires engagement with ESM and CE to handle the solution.

9. KSS

10. Work breakdown:
Needs -> Capabilities -> Requirements -> Features/User-stories/Bugs
Work item dependencies:
Vertical – hierarchical decomposition
Horizontal – internal work dependencies
TODO: Give an example of work breakdown from Healthcare KSS Network (Insurance Interface, Telemetry Integration, and Performance Upgrade).

11. Example
TODO: Give an example with blocking task from Healthcare KSS Network.
TODO: Explain how reprioritization of blocking task helps to push implementation of the desired capability.

12. Priority calculation Priority calculation based on the following:
Business value
Class of service (eg. Standard, Important, Date Certain, Critical Expedite)
Estimated effort
Specialties required
TODO: quickly explain each item.

13. Simulation model Static model: Dynamic model:
Describes objects (work items, backlogs, resources) and their relationships.
Dynamic model:
Describes how work items’ dependencies change over time. This includes establishing relationships with new or existing dependent task and breaking down the task into a set of subtasks.
Apply scheduling/prioritization algorithms.

14. Comparison with ICSM Value based engineering approach
Incremental commitment
Coordinate multiple levels of systems engineering activity

15. References
Turner, Richard, Lane, Jo Ann (2013) “Goal-Question-Kanban: applying lean concepts to coordinate multi-level systems engineering in large enterprises”. Conference on Systems Engineering Research 2013.
Office of the Deputy Under Secretary of Defense for Acquisition and Technology, Systems and Software Engineering. Systems Engineering Guide for Systems of Systems, Version 1.0. Washington, DC: ODUSD(A&T)SSE, 2008.
What is a System of Systems and Why Should I Care? By Jo Ann Lane Daniel J. Epstein, Department of Industrial and Systems Engineering University of Southern California.

16. Question & Answers