INCOSE MBSE Model Based System Engineering So S

INCOSE (MBSE) Model Based System Engineering (So. S) System of Systems Activity Introduction Ron Williamson, Ph. D. Raytheon ron. williamson@incose. org Jan 30 -31, 2011 INCOSE IW 11 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 11 MBSE Workshop 1

Outline • • • Introduction Conceptual Model Summary for So. S Concept Representations – Languages – Frameworks – Patterns • • 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 Studies – Architecture Eco-System Efforts – UPDM and Do. DAF 2. 0 DM 2 – UPDM and Sys. ML, Soa. ML, BPMN, BMM, etc. • • • Conclusions / Recommendations References and Related Initiatives Questions… INCOSE IW 11 MBSE Workshop 2

Introduction MBSE System of Systems • 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, … – These unique characteristics have lead the SE and Architecting community to investigate new languages and frameworks to help better define these key So. S characteristics • So. S Engineering – Best Practices in Analysis, Architecture, Design, Development, Integration, Testing, Deployment and Maintenance – Modeling is increasingly critical to understanding, managing and validating – So. S modeling (e. g. Sys. ML, MARTE, Modelica, e. Xtend, Simu. Link, …) • So. S Architecting – Architecture Frameworks (Do. DAF, MODAF, FEAF, Zachman, TOGAF, …. ) – Model Based Frameworks (e. g. UPDM - Unified Profile for Do. DAF/MODAF) INCOSE IW 11 MBSE Workshop 3

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 11 MBSE Workshop So. S Modeling Implications 4

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 Concept of Operations Critical Ongoing Experimentation 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 INCOSE IW 11 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 5

MBSE So. S Conceptual Model (partial) specifies Viewpoint representation of provides perspective on Arch Desc has described by member of Stakeholder Enterprise Multiplicity default: 0. . * visions for enterprise defines Architecture Constrains Policy So. S Vision contributes to vision Information represents abstract exchanges requires standardizes composed of deployed to Function Resource carries to Connection Mission accomplish realizes Performed by Activity conducts Competence System So. S employs has from Goal fulfills goal performs Hosted on Interaction of Capability Configuration includes Standard Asset goals of vision fulfills capability realized as Node Technology realized as Domain So. S Node requires Role standardizes carries Data INCOSE IW 11 MBSE Workshop 6

Some MBSE So. S 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 – – • Example Concepts with several interpretations – – – • 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) Capability Function Activity Requirement Viewpoint Example Languages with overlap – BPMN and UML (Sys. ML, UPDM) INCOSE IW 11 MBSE Workshop UML/BPMN Integration Straw Poll (source OMG) They remain separate standards 3 BPMN is a UML profile with notation 6 Create a unified model encompassing both 13 Semantic models with UML and BPMN viewpoints 9 BPMN replaces UML activity diagrams 4 BPMN grows to make UML not required 0 BPMN and UML are separate models, mapped with QVT 2 There are ways to make links between them 3 7

Systems Language Models for So. S • Sys. ML Core Concepts – 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 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 11 MBSE Workshop See UPDM and Do. DAF Meta model References for mapping standards efforts 8

Architecture Framework (AF) Models for So. S • 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 11 MBSE Workshop 9

MBSE So. S Case Studies • Architecture Eco-System Efforts – Special Interest Group at OMG – Co-Chairs: • Jim Amsden (IBM) • Cory Casanave (Model Driven Solutions) • UPDM and Do. DAF 2. 0 – UPDM 1. 0 official OMG standard • Co-Chairs – Jim Rice, No. Magic – Graham Bleakley, IBM – Matthew Hause, Atego (aka Artisan Software+Aonix) • Do. D – Walt Okon, OSD – Len Levine, DISA INCOSE IW 11 MBSE Workshop 10

Architecture Eco-System Efforts • The set of architectural languages defined in the ecosystem should, together, create a complete architectural environment – – Advantages of unified tools – integrated Without the coupling of monolithic tools Full life-cycle Integrating the same information about the same enterprise from multiple viewpoints – Well defined meaning – Flexible for extension and new viewpoints – Models as data – repurpose, query, mash-up • The goal of the architectural ecosystem is to figure out how to do this – to architect our architectures • Identify real or perceived problems and find solutions INCOSE IW 11 MBSE Workshop 11

Architecture Eco-System Efforts • Current Integrated Modeling Efforts – – – – Do. DAF DM 2 FEA/FSAM Proprietary tool models BPDM & IMM Nasa NEx. IOM (Proposed) Business Modeling Framework Unified Process Model (NIST) Others…. INCOSE IW 11 MBSE Workshop 12

UPDM and Do. DAF 2. 0 • UPDM: Four+ year effort to standardize Do. DAF 1. 5 architecture description models using UML and Sys. ML • UPDM 1. 0 Official OMG standard in 2009 • UPDM 2. 0 RFP issued late 2009 to extend to Do. DAF 2. 0, MODAF, NAF, etc. updates • At least one team responding and coordinating with Do. D sponsored Do. DAF 2. 0 Meta Modeling efforts INCOSE IW 11 MBSE Workshop 13

Do. DAF 2. 0 Viewpoints INCOSE IW 11 MBSE Workshop 14

Do. DAF 2 Metamodel Summary Ontology Capturing fundamental semantics (Meaning) and relationships among key concepts Models Provide “choices” based on decision maker needs Fit for Purpose Describes an architecture that is appropriately focused and directly supports customer needs INCOSE IW 11 MBSE Workshop 15

UPDM Summary INCOSE IW 11 MBSE Workshop 16

UPDM Summary (cont. ) • Viewpoints and Concept Stereotypes – – – – All Views (Metadata, Measurement. Set, Definition, …) Strategic Capability (Enterprise. Phase, Vision, Goal, Mission, Capability, …) Operational (Node, Role, Needline, Activity, State, Organization, Competence, Information, Rule, Policy…) System (Capability. Configuration, Resource, System, Data, System. Function, …) Service-Oriented (Service, Service. Interface, …) Acquisition (Project, Milestone, …) Tech Standard (Standard, Protocol, …) Source: MODAF Overview, Version 1. 0, 2005 INCOSE IW 11 MBSE Workshop 17

References for some MBSE So. S Related Initiatives • OMG’s Architecture Ecosystem Special Interest Group – http: //www. omgwiki. org/architecture-ecosystem/doku. php • OMG’s Unified Profile for Do. DAF/MODAF 2. 0 – http: //www. updm. com • Do. D’s Do. DAF 2. 0 Meta Modeling efforts – http: //cio-nii. defense. gov/sites/dodaf 20/DM 2. html • IDEAS Group (US, UK, Canada, Sweden) – http: //www. ideasgroup. org/ • OMG’s Sys. ML – http: //omgsysml. org/ INCOSE IW 11 MBSE Workshop 18

INCOSE IW 11 MBSE Workshop 19