return to: MBSE Wiki Start

• SoS Architecture Framework Standards
  • OMG UPDM Specifications
  • OMG UPDM 3.0 RFP
  • UPDM 3.0 Human View Modeling Discussion Topics
• Related Research Efforts
  • COMPASS - Correctness, Modeling and Performance of Aerospace Systems
  • DANSE - Designing for Adaptability and evolutioN in System of systems Engineering
  • Purdue University System of Systems Laboratory
• Sos/EA Best Practice and Challenge Problem Areas
  • DARPA - Adaptive Vehicle Make Challenge

Welcome to the SoS/Enterprise Modeling Activity Wiki page sponsored by the INCOSE MBSE initiative.

Please also join us in the LinkedIn group for INCOSE MBSE SoS Enterprise Architecture discussions at: MBSE SoS EA LinkedIn Group

Note: This is an open group, but requires LinkedIn registration…to gain access as a new member please register with LinkedIn (free basic membership) and link to the group above.

The purpose of this activity is to foster interest and participation in the continuing efforts to model enterprise and system of systems level architecture specifications and frameworks. The focus areas include the DoD DODAF 2.0 MetaModeling, NATO NAF Modeling, UK MOD MODAF modeling, OMG UPDM 2.0, the BPMN and BPEL, SOAML, NDIA System of Systems committee efforts and NCOIC Network Centric patterns efforts.

Similar to the Systems Engineering initiatives to evolve away from document based descriptions of systems to a model base descriptions of systems, the SoS/Enterprise modeling focus is on the efforts underway to evolve from a document only description of Architectures, Capabilities, Programmatics, etc. to a more rigorous model based representation of all the perspectives involved in engineering at the SoS and Enterprise levels of abstraction.

As discussed in the Architecting Principles for System of Systems reference, not all System of Systems are alike and come in three broad categories Directed, Collaborative, Virtual with five principal characteristics:

• Operational Independence of the Elements
• Managerial Independence of the Elements
• Evolutionary Development
• Emergent Behavior
• Geographic Distribution

Engage the stakeholders, capture the stakeholder expectations and define the measures of success.

Some Examples of measures for our focus area:

There are many definitions and interpretations of Systems of Systems and Enterprise level analysis, architecting and engineering. For example, one definition of System of Systems includes: “ a class of problems that have unique characteristics, distinguishing them from “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 Systems Engineering and Architecting community to investigate new languages and frameworks to help better define these key System of Systems characteristics.

T. Saunders, et al, in “United States Air Force Scientific Advisory Board Report on System of Systems Engineering for Air Force Capability Development” SAB-TR-05-04, July 2005 included the follow table:

• 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

Some of the key efforts underway related to SoS/Enterprise modeling including,

• OMG Unified Profile for DoDAF/MODAF (UPDM) standards UPDM Group
• OMG Architecture Ecosystem Special Interest Group AE SIG
• Business Process Modeling BPMN
• Service Oriented Architecture modeling SOAML
• IDEAS Group IDEAS Group Website
• DoD DODAF 2.0 Meta Model DM2 Website
• UK MOD MODAF 1.2 Meta Model M3 Website
• NCOIC Netcentric Patterns Netcentric Patterns Website

• SoS SE Guide v1.0
• What are the differences between a vocabulary, a taxonomy, a thesaurus, an ontology, and a meta-model? http://infogrid.org/wiki/Reference/PidcockArticle
• Early Systems Engineering - A Level of Analytical Fidelity to Support MDD and MS A Decisions

Link to related items such as related organizations, related articles, …

• 2011 INCOSE SoS-Enterprise Modeling Workshop Agenda 2011
• 2011 INCOSE MBSE SoS-Enterprise Modeling Introduction
• 2011 MBSE UPDM Introduction

• 2012 INCOSE MBSE SoS-Enterprise Modeling Introduction

• 2013 INCOSE MBSE SoS-Enterprise Modeling Introduction

• Coordination with SoS Working Group…deferred until SoS WG interest in MBSE identified beyond current academic focus of the WG
• Coordination with Architecture Working Group…added to 2014 WG follow up tasks with Charles Dickerson as Arch WG POC for MBSE liaison
• Coordination with Human Systems Integration Working Group…possible interest on Human View Modeling for Architecture Frameworks

• INCOSE MBSE Initiative Wiki Home Page
• INCOSE Architecture Working Group
• INCOSE Agile Systems & Systems Engineering Working Group
• INCOSE System of Systems Working Group
• INCOSE Human Systems Integration Working Group
• MBSE SoS/EA Model Examples
• MBSE SoS/EA Group Exchanges

• Challenge Teams

• MBSE Methodology

• MBSE Ontology

• Modeling Standards

• MBSE Usability

• Object Management Group Home Page
• OMG Architecture EcoSystem Wiki Page
• OMG Unified Profile for DoDAF/MODAF (UPDM) Wiki Page
• OMG UPDM 2.0 Specificiations

• NDIA Home Page
• NDIA SoS Engineering Committee
• NDIA Architecture Committee

• Georgia Tech
• Stevens Institute
• Old Dominion University
• Purdue University
• CMU
• USC
• UCLA

• Georgia Tech - ME/ISyE 8803 MBSE with SysML, McGinnis , ME 6105 M&S in Design, Paredis
• Loyola Marymount Los Angeles - SELP 530 & 675 Systems Architecting & Modeling I & II, Ghashghai, Tang & Williamson
• USC - SAE 547 Model Based Systems Architecting and Engineering, Madni & Rosenberg

• NCOIC: Network Centric Operations Industry Consortium
• NCOIC Network Centric Assessment Tool
• NCOIC SCOPE
• System of Systems Engineering Cemter of Excellence
• IEEE System of Systems Engineering
• System of Elements Patent

• Form core membership and initiate active participation
• Define baseline for focus areas
• Wiki updates by membership
• Reachout to other INCOSE Working Groups
• Reachout to other organizations (NDIA, NCOIC, etc.)
• Define common terms
• Build a list of references and bibliography

• Crossley, W.A., System-of-Systems:, Introduction of Purdue University Schools of Engineering's Signature Area.
• DeLaurentis, D. “Understanding Transportation as a System of Systems Design Problem,” 43rd AIAA Aerospace Sciences Meeting, Reno, Nevada, January 10-13, 2005. AIAA-2005-0123
• Held, J.M., The Modelling of Systems of Systems, PhD Thesis, University of Sydney, 2008
• Rechtin, E, System Architecting: Creating and Building Complex Systems, Prentice Hall, 1991
• Yaneer Bar-Yam and others, The Characteristics and Emerging Behaviors of System-of-Systems in: NECSI: Complex Physical, Biological and Social Systems Project, January 7, 2004.

• IBM The Internet of Things

• IBM System of Systems Video
• M61 System of Systems Video
• UPDM - IBM Rhapsody Part 1
• UPDM - IBM Rhapsody Part 1

• Architecture: The activity of designing any kind of system
• Architecture Framework: An architecture framework establishes a common practice for creating, interpreting, analyzing and using architecture descriptions within a particular domain of application or stakeholder community
• Enterprise Architecture: Enterprise Architecture is the continuous practice of describing the essential elements of a sociotechnical organization, their relationships to each other and to the environment, in order to understand complexity and manage change
• Meta Model: Defines the language and processes from which to form a model
• Meta Model: A model is a representation containing the essential structure of some object or event in the real world
• System: A group of interacting, interrelated, or interdependent elements forming a complex whole
• System of Systems: a class of problems that have unique characteristics, distinguishing them from “classic” systems, for example, unbounded context and usage, potentially emergent behaviors, large number of complex interactions, costly to fully verify and validate a priori