Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative

1. Modeling Standards Activity TeamModel-based Systems Engineering (MBSE) Initiative Roger Burkhart MBSE Workshop Opening Plenary 30 January 2011

2. MBSE Builds on Standards • Languages and frameworks to express and communicate models • For understanding and interpretation by people • For analysis and processing by computer programs • Integration of models across multiple domains and communities • Mappings across multiple sources and forms of models • Problem-specific frameworks, models, reference data • Generated and shared by user communities for specificsystem and problem types

3. MBSE Standards in INCOSE • INCOSE has been driving development of needed standards for MBSE since 2001 • Memorandum of Understanding with OMG and ISO TC184/SC4 (STEP), which led directly to SysML and AP233 • Model-Driven System Design Working Group (MDSDWG) • With this meeting, the activities of MDSD are merginginto the Activity Teams of the MBSE Initiative, includingthe Modeling Standards Activity Team

4. Model Driven System Design (MDSD) WGIW 2010 “Quad Chart” MDSD WG Chairs: Phil Spiby Phil.Spiby@incose.org Roger Burkhart Roger.Burkhart@incose.org Number of Members: 100+ INCOSE Connect address: https://connect.incose.org/tb/MnT/mdsd/default.aspx INCOSE Web page: http://www.incose.org/practice/techactivities/wg/mdsd/ • MDSD Charter: • Enable effective and efficient use of models throughout the systems engineering life cycle. • Published Products: • Requirements, evaluation, & user feedback for AP233, SysML, & other modeling frameworks • White paper on AP233 & SysML relationship • SE Conceptual Model originally used to provide requirements to AP233 and SysML • - Neutral terminology and structure to support content across languages, models, and tools • - To be republished using semantic modeling technologies to define valid usage and structure • Portfolio of mappings across MBSE languages and models (AP233, SysML, Modelica, OPM, ...) • Planned Work: • Organize electronic communications and work sites • Develop and publish products, examples, inputs to support MBSE Initiative • Publish mapping specification to define AP233 and SysML relationship • Develop roadmap for progressive coverage of model-driven methods, including PLM support of MBSE • Interacting with OMG, ISO, ECCMA, and other modeling standards organizations IW 2010 4 Technical Operations

5. Modeling Standards Wiki Page • Key goals of the Modeling Standards MBSE Activity include: • Maintain a taxonomy and roadmap of modeling standards of importance for MBSE. • Identify gaps in the roadmap which still need to be filled by new standards development projects. • Work with the INCOSE Standards Initiative to maintain liaisons and agreements with organizations that develop standards within the taxonomy and roadmap. • Serve as a voice of the Systems Engineering user community to provide requirements to new modeling standards and to evaluate them during their development process. • Encourage cross participation, communications, and collaboration across the MBSE community and standards development organizations and projects.

6. Taxonomy and Roadmap ofStandards for MBSE • Modeling Languages and Frameworks • SysML, AP233, Ontologies, … • Mappings, integration, interoperability • AP233-SysML, SysML-Modelica, … • Problem-specific frameworks, models, reference data • UPDM, AADL, DocBook, Modelica, … • Start populating this list, including existing projects and organizations, and gaps that need new efforts to fill them. Reach out to groups who can develop and maintain the needed standards.

7. Neutral Modeling Infrastructure Shared SemanticModels UML/SysML OWL STEP/Express

8. Taxonomy and Roadmap • Catalog of Classifications for Modeling Standards • Modeling Languages and Frameworks • Modeling Language, Metamodel, Model Exchange Format, Constraint Language, Query Language, Transformation/Mapping Language, Representation Model (Diagrams, Documents),Model Management Service, … • Mapping Specifications • Problem-specific frameworks, models, reference data • Architecture Modeling Language, Hardware/Software Systems,Continuous System Dynamics, … • Catalog of Standards Development Organizations (SDOs) • Catalog of Standards Projects/Specifications • Schedules, Contacts, Liaisons • Placeholder if no project exists

9. Example: Object Management Group • Standards Development Organization: OMG • Modeling Language: SysML • Metamodel: Meta Object Facility (MOF) • Model Exchange Format: XMI • Constraint Language: OCL • Transformation/Mapping Language: QVT • Representation Model: Diagram Definition • Model Management Service: MOF Versioning • Mapping Specification: SysML-Modelica Transformation • Mapping Specification: Ontology Definition Metamodel (ODM) • Architecture Modeling Language: UPDM • Business Modeling Language: BPMN • Real-Time Software: MARTE

10. Breakout Session Plan • Inputs to Catalog from all other Challenge and Activity Teams • Wrapup session at 2:45 PM after input from all other teams • Additional discussion and identification of catalog inputs • Contacts and assignments to establish links to other projects,or to address gaps • Status updates and overviews of existing work-in-progress