INCOSE MBSE Model Based System Engineering So S

INCOSE (MBSE) Model Based System Engineering (So. S) System of Systems/Enterprise Activity Introduction Ron Williamson, Ph. D Raytheon ron. williamson@incose. org Jan 21 -22, 2012 INCOSE IW 12 MBSE Workshop MBSE Wiki page: http: //www. omgwiki. org/mbse MBSE So. S/Enterprise Modeling Wiki page: http: //www. omgwiki. org/MBSE/doku. php? id=mbse: enterprise INCOSE IW 12 MBSE Workshop 1

Outline • MBSE and So. S/Enterprise Vision • Introduction • • Mind Map Summary for So. S Concept Representations • MBSE So. S Challenges • Systems Language Models for So. S – Sys. ML (System Modeling Language) • Architecture Framework (AF) Models for So. S – UPDM (UML(Unified Modeling Language) Profile for Do. DAF/MODAF • MBSE So. S Case Study – UPDM and Do. DAF 2. 0 DM 2 – UPDM and Sys. ML, Soa. ML, BPMN, BMM, etc. • Questions…hold for the end of the session INCOSE IW 12 MBSE Workshop 2

Integrated Systems Engineering Vision Hydraulic Fluid: SAE 1340 notcompliant Power Rating: 18 Amps Thermal/Heat Dissipation: 780° Ergonomic/Pedal Feedback: 34 ERGS Hydraulic Pressure: 350 PSI Sensor MTBF: 3000 hrs Automatic Cruise Control <FAULT> Minimum Turn Radius: 24 ft. Dry Pavement Braking Distance at INCOSE IW 12 MBSE Workshop 60 MPH : 110 ft.

A Vision: Intelligent Regional Highway So. S/Enterprise Comms Capability : Communications, Sensing, Command, Control Tolling, Transporting, … Condition : Safety, Security, Efficiency, Reliability, … Measure : Vehicle delays, Vehicle throughput, Revenue Generation, … Who Control Sensing Comms What When Where Why How Comms Sensing Tolling Command & Control $1 T oll L e an Comms Dry Pavement Braking Distance : 110 ft. Avg Segment Transit Time : 30 mins INCOSE IW 12 MBSE Workshop Toll Pricing: $1 per segment 4

A Vision: Intelligent Regional Highway So. S/Enterprise Socio. Economic Communications Model Comms Performance Model Performers Dynamic Network Model Activity Control Comms Sensing Communications Comms Model Location Sensing Tolling Performers Command & Control $1 Resources Communications Model T oll L e an Dry Pavement Braking Distance : 110 ft. Avg Segment Transit Time : 5 30 15 mins INCOSE IW 12 MBSE Workshop $0 $1 //// per Toll Pricing: segment Comms Guidance 5

Introduction MBSE System of Systems /Enterprise • System of Systems (So. S)…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 • So. S/Enterprise Engineering – Best Practices in Analysis, Architecture, Design, Development, Integration, Testing, Deployment and Maintenance – Modeling is increasingly critical to understanding, managing and validating • So. S/Enterprise Architecting – Architecture Frameworks (Do. DAF, MODAF, FEAF, Zachman, TOGAF, …. ) – Model Based Frameworks (e. g. UPDM - Unified Profile for Do. DAF/MODAF) INCOSE IW 12 MBSE Workshop 6

Introduction So. S Engineering Key Concepts • So. S 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 Saunders, T. et al, “United States Air Force Scientific Advisory Board Report on Systemof-Systems Engineering for Air Force Capability Development, ” SAB-TR-05 -04, July 2005 INCOSE IW 12 MBSE Workshop So. S / Enterprise Modeling Implications 7

Introduction …So. S MBSE Implications Legacy Systems Dynamic Reconfiguration of Architecture Service Oriented Architecture Enabler SOA modeling language, e. g. Soa. ML, SOA Patterns Protocols and Standards to Enable Interoperable Systems Models for protocols, standards, interoperability, e. g. UPDM, Do. DAF 2 Meta. Model Added “ilities” or Quality Attributes Federated Acquisition Specialty Engineering models, e. g assurance Independent Systems Models for acquisition project synergy, e. g. UPDM, MODAF, Do. DAF 2 Meta. Models for independence in system functionality, e. g. Agent Based, federated models Models for CONOPs including Mission, Objectives, Courses of Action, etc. e. g. UPDM Operational Viewpoint, BPMN Business Processes Analysis of Alternatives models for all viewpoints and model versioning Concept of Operations Critical Ongoing Experimentation INCOSE IW 12 MBSE Workshop Models for behavior, interfaces, requirements, performance, e. g. Sys. ML, Modelica, MARTE Dynamic Reconfigurable models of architecture, e. g. UPDM with UML/Sys. ML model version management 8

MBSE So. S/Enterprise IDEAS Group Meta Model (example) INCOSE IW 12 MBSE Workshop 9

Some MBSE So. S/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 So. S Engineering – – • Object Oriented vs Structured/Functional Enterprise vs So. S vs System Business vs Engineering Models (BPMN vs UML vs Soa. ML vs Sys. ML) 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 INCOSE IW 12 MBSE Workshop 10

Systems Language Models for So. S/Enterprise • Sys. ML Core Concepts Apply to So. S/Enterprise – Structure, Behavior, Requirements, Parametrics • View, Viewpoint, Block, Part, Role, Connector, Interface, Item. Flow, Activity, State, Transition, Requirement, Constraint Block, … – So. S 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… • Sys. ML/So. S/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 • Mo. E’s, KPP’s, “ilities”… INCOSE IW 12 MBSE Workshop See UPDM and Do. DAF Meta model References for mapping standards efforts at : http: //www. omgwiki. org/mbse 11

Architecture Framework (AF) Models for So. S/Enterprise • Zachman Framework – Perspectives, Interrogatives, Checklist • TOGAF 9 (The Open Group AF) – Architecture Development Model • FEAF (Federal Enterprise AF) – Reference Models (Business, Technical, Information, …) • Do. DAF 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 INCOSE IW 12 MBSE Workshop 12

MBSE So. S/Enterprise Case Studies • UPDM 2. 0 and Do. DAF 2. 02 – UPDM 2. 0 official OMG standard • Co-Chairs – Daniel Brookshier, No. Magic – Graham Bleakley, IBM – Matthew Hause, Atego • Do. D – Walt Okon, Do. D OSD – Len Levine, Do. D DISA • UPDM and Sys. ML, Soa. ML, 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, Do. DAF 2. x and IDEAS Group work for examples INCOSE IW 12 MBSE Workshop 13

INCOSE IW 12 MBSE Workshop 14

INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario Ron Williamson, Ph. D Raytheon ron. williamson@incose. org Jan 21 -22, 2012 INCOSE IW 12 MBSE Workshop 15

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 • Feedback… INCOSE IW 12 MBSE Workshop 16

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 INCOSE IW 12 MBSE Workshop 17

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