1. INCOSE (MBSE) Model Based System Engineering (SoS) System of Systems/Enterprise Activity Introduction
Ron Williamson, PhD
Raytheon
Jan 21-22, 2012
INCOSE IW12 MBSE Workshop
MBSE Wiki page:
MBSE SoS/Enterprise Modeling Wiki page:

2. Outline MBSE and SoS/Enterprise Vision Introduction
Mind Map Summary for SoS
Concept Representations
MBSE SoS Challenges
Systems Language Models for SoS
SysML (System Modeling Language)
Architecture Framework (AF) Models for SoS
UPDM (UML(Unified Modeling Language) Profile for DoDAF/MODAF
MBSE SoS Case Study
UPDM and DoDAF 2.0 DM2
UPDM and SysML, SoaML, BPMN, BMM, etc.
Questions…hold for the end of the session

3. Integrated Systems Engineering Vision
Automatic Cruise Control <FAULT>
Thermal/Heat Dissipation: 780°
Ergonomic/Pedal Feedback: 34 ERGS
Hydraulic Pressure: 350 PSI
Sensor MTBF: 3000 hrs
Power Rating: 18 Amps
Hydraulic Fluid: SAE 1340 not-compliant
Integrated Systems Engineering Vision
If we can pull this off we can achieve this ultimate vision for integrated requirements…, visualizing where requirements go and how they interact with various systems… For example, …starting with the car, what are the requirements associated with the front end of this vehicle.
Shows current requirements by graphically clicking on the car…
What about changing a requirement…stopping distance
Show the potential impact of changing stopping distance including…
Thermal/heat problems with brakes
Ergonmic feedback problems with brake pedal
Hydraulic fluid rating violation
Failure modes/MTBF rating problems with sensors
Hydraulic pressure problems
Electrical fault problems
Zooming into the electrical box, highlights a fuse
Clicking into the fuse brings up the schematic and highlights a fuse link
Clicking into the schematic zooms in on the wire harness that has the problem—including the signal for a failed sensor that in this particular failure mode causes the short.
…which allows us to go look at the Failure Modes document and update appropriately.
Updating the software to handle that fault
…and even seeing the impact on our safety rating and insurance costs.
Minimum Turn Radius: 24 ft.
Dry Pavement Braking Distance at 60 MPH : 110 ft. 90 ft
Minimum Turn Radius: 24 ft.
Dry Pavement Braking Distance at 60 MPH : 110 ft.

4. A Vision: Intelligent Regional Highway SoS/Enterprise
Capability : Communications, Sensing, Command, Control
Tolling, Transporting, …
Condition : Safety, Security, Efficiency, Reliability, …
Measure : Vehicle delays, Vehicle throughput,
Revenue Generation, …
Comms
Who What When Where Why How
Comms
Sensing
Sensing
Comms
Building on the MBSE vision for systems…..the SoS Vision example takes the individual automobile example into the context of a regional “intelligent” highway of the future where each of the automobiles is “connected” in a network, has local traffic sensing capabilities, has local semi-autonomous operations capabilities, and local navigation/traffic warning features. The regional highway has sensing, communications and tolling capabilities that are all controlled via a regional command and control facility, whose role is to balance safe, secure, efficient and reliable transportation on the regional highways.
Sensing the average segment transit times, the scenario walks through how a model based approach to defining, engineering and eventually managing the system of systems for the regional enterprise could be envisioned.
SoS and Enterprise meta models include concepts such as Capability, Condition, Measure and the six interogatives from the Zachman Framework.
Control
Command & Control
Tolling
$1 Toll Lane
Comms
Dry Pavement Braking Distance : 110 ft.
Avg Segment Transit Time : mins
Toll Pricing: $1 per segment

5. A Vision: Intelligent Regional Highway SoS/Enterprise
SocioEconomic
Performers
Performance Model
Communications
Model
Comms
Dynamic
Network Model
Location
Comms
Sensing
Activity
Communications
Model
Sensing
Communications
Model
Comms
Building on the core concepts used in modeling the regional highway enterprise (Activity, Resources, Performance, Location, etc.) and domain specific models for communications, dynamic network models, resource / performer models and socio economic models….the combination of all of these modeled factors can help determine how to control the features of the highway to get the transit time delays reduced from say 15 minutes to 5 minutes, perhaps simply by eliminating the tolling price all together for a short period of time.
Control
Performers
Command & Control
Tolling
Resources
$1 Toll Lane
Comms
Guidance
Dry Pavement Braking Distance : 110 ft.
Avg Segment Transit Time : mins
Toll Pricing: $1 per segment
Dry Pavement Braking Distance : 110 ft.
Avg Segment Transit Time : mins
Toll Pricing: $1 per segment
$0 ////

6. Introduction MBSE System of Systems /Enterprise
System of Systems (SoS)…one of many definitions/characterizations
A class of problems that have unique characteristics, distinguishing them for “classic” systems.
For example, unbounded context and usage, potentially emergent behaviors, large number of complex interactions, costly to fully verify and validate a priori,…
Enterprise (ref Merriam-Webster)
A project or undertaking that is especially difficult, complicated or risky
Readiness to engage in daring or difficult action
A systematic purposeful activity
SoS/Enterprise Engineering
Best Practices in Analysis, Architecture, Design, Development, Integration, Testing, Deployment and Maintenance
Modeling is increasingly critical to understanding, managing and validating
SoS/Enterprise Architecting
Architecture Frameworks (DoDAF, MODAF, FEAF, Zachman, TOGAF,….)
Model Based Frameworks (e.g. UPDM - Unified Profile for DoDAF/MODAF)
Provide some basic definitions and examples related to the SoS / Enterprise modeling context.

7. Introduction SoS Engineering Key Concepts
Legacy Systems
Dynamic Reconfiguration of Architecture
Service Oriented Architecture Enabler
Protocols and Standards to Enable Interoperable Systems
Added “ilities” or Quality Attributes
Federated Acquisition
Independent Systems
Concept of Operations Critical
Ongoing Experimentation
Converging Spirals
Discuss the core results from the 2005 study by the US AFSAB and discuss the SoS engineering key concepts leading to the SoS Modeling Implications on the next slide.
SoS / Enterprise
Modeling
Implications 
Saunders, T. et al, “United States Air Force Scientific Advisory Board Report on System-of-Systems Engineering for Air Force Capability Development,” SAB-TR-05-04, July 2005

8. Introduction …SoS MBSE Implications
Legacy Systems 
Models for behavior, interfaces, requirements, performance, e.g. SysML, Modelica, MARTE
Dynamic Reconfiguration of Architecture
Dynamic Reconfigurable models of architecture, e.g. UPDM with UML/SysML model version management
Service Oriented Architecture Enabler
SOA modeling language, e.g. SoaML, SOA Patterns
Protocols and Standards to Enable Interoperable Systems
Models for protocols, standards, interoperability, e.g. UPDM, DoDAF 2 MetaModel
Added “ilities” or Quality Attributes
Specialty Engineering models, e.g assurance
Federated Acquisition
Models for acquisition project synergy, e.g. UPDM, MODAF, DoDAF 2 MetaModel
Independent Systems
Models for independence in system functionality, e.g. Agent Based, federated models
Concept of Operations Critical
Models for CONOPs including Mission, Objectives, Courses of Action, etc. e.g. UPDM Operational Viewpoint, BPMN Business Processes
Ongoing Experimentation
Analysis of Alternatives models for all viewpoints and model versioning
Quickly discuss each of the key points,….picking one or two major differences from classic systems engineering…..e.g. the SOA enabler, Independent systems and the idea of ongoing experimentation/agile development.

9. MBSE SoS/Enterprise IDEAS Group Meta Model (example)
Use the DoDAF DM2 (metamodel) summary to emphasize some of the key concepts for SoS and Enterprise modeling.

10. Some MBSE SoS/Enterprise Challenges
Core Concepts have a wide range of interpretations and definitions across modeling languages
Duality: System of Systems and Model of Models
OMG Initiative: “Ecosystem” of Languages/Models
Methodology / Discipline differences expand into SoS Engineering
Object Oriented vs Structured/Functional
Enterprise vs SoS vs System
Business vs Engineering Models (BPMN vs UML vs SoaML vs SysML)
Enterprise, Business and Technical Architecture Models (pick your favorite Architecture Frameworks)
“Fit for Purpose” Descriptions
Definition
Examples
Best Practices
Framework “Ecosystems”
US Federal Government Frameworks
Commercial Frameworks
International Frameworks

11. Systems Language Models for SoS/Enterprise
SysML Core Concepts Apply to SoS/Enterprise
Structure, Behavior, Requirements, Parametrics
View, Viewpoint, Block, Part, Role, Connector, Interface, Item, ItemFlow, Activity, State, Transition, Requirement, Constraint Block,…
SoS Core Concepts
View, Viewpoint, Enterprise, Mission, Projects, Milestone, Vision, Goal, Policy, Capability, Node, Configuration, Resource, System, Information, Data, Technology, Standard, Organization, Task, Activity, Measures of Effectiveness, Key Performance Parameters, “ilities”, Scenario, Workflow…
SysML/SoS/Enterprise Mapping Example (one of several approaches)
Structure (Block,…)
Enterprise, Capability, Configuration, Resource, Systems, Information, Data, Technology, Organization, Milestone, Vision, Goal, Node, …
Behavior (Activity, State,…)
Function, Task, Activity, Scenario, Workflow,
Requirement
Policy, Constraint, Standard,…
Parametrics
MoE’s, KPP’s, “ilities”…
See UPDM and DoDAF Meta model
References for mapping standards efforts
at :

12. Architecture Framework (AF) Models for SoS/Enterprise
Zachman Framework
Perspectives, Interrogatives, Checklist
TOGAF 9 (The Open Group AF)
Architecture Development Model
FEAF (Federal Enterprise AF)
Reference Models (Business, Technical, Information, …)
DoDAF 2 / MODAF / NATO AF /…
Viewpoints, Products for Capability, Operational, System, Service, Technology Standards, Information, … Views
…and many additional variants of various combinations of the above frameworks

13. MBSE SoS/Enterprise Case Studies
UPDM 2.0 and DoDAF 2.02
UPDM 2.0 official OMG standard
Co-Chairs
Daniel Brookshier, NoMagic
Graham Bleakley, IBM
Matthew Hause, Atego
DoD
Walt Okon, DoD OSD
Len Levine, DoD DISA
UPDM and SysML, SoaML, BPMN, BMM, etc
Common Language vs Domain Specific Languages
Common Core Concept Definitions
Expand on the Core with well defined “profiles”
OMG has tried this with UML…but with many lessons learned
Rethinking the concept of “extending a core language”
Key enablers exist in the Ontology work
Back to the UPDM, DoDAF 2.x and IDEAS Group work for examples

15. INCOSE IW12 MBSE Workshop
INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario
Ron Williamson, PhD
Raytheon
Jan 21-22, 2012
INCOSE IW12 MBSE Workshop

16. Integration & Verification Scenario Breakout Session Agenda
Logistics
85 minutes Total
15 minutes intros, level setting, recommendations
50 minutes brainstorming
20 minutes capturing the out brief topic conclusions
Level Setting
Setting the stage for: Integration and Verification Scenario
System Vee
Role of Modeling in the System Vee
Specification
Synthesis
Verification and Validation
Questions / Recommendations…
Out brief topics
Key Practices
Feedback….
Integration Challenges
Feedback…
Recommendations

17. Integration & Verification Scenario
Concept of Operations
Word document  Scenarios Model (Behavior/Structure)
Requirements & Architecture
Word Document  Requirement Objects, Architecture Framework Languages
Design and Implementation
Diagrams and Word document  SW and HW Models (Form & Function)
Test
Plans  Test Models
Integration
Model Integration
Verification
Model Verification
Operation and Maintenance
Operational Models

18. Integration & Verification Scenario
Project Modeling
Operational Parameters
Operations &
Maintenance
Concept of
Operations
Model
Model Verify & Validate
Model
Synch
Model vs Implementation
Project
Definition
Requirements
& Architecture
Models
Constraints & Viewpoints
System Verif &
Validation
Model Verify & Validate
Model vs Impl.
Model
Synch
Project
Test &
Integration
Structure & Behaviors
Detailed Design
Models
Integration, Test
& Verification
Model Verify & Validate
Model
Synch
Model vs Impl.
Implementation
Time