1. Status of SysML v2 Planning & Requirements Berlin, Germany June 16, 2015 http://www.omgwiki.org/OMGSysML/doku.php?id=sysml- roadmap:sysml_assessment_and_roadmap_working_group Sandy Friedenthal Eldad Palachi

2. System Modeling Assessment & Roadmap WG  Sponsored by OMG SE DSIG  Develop roadmap for SysML and related modeling standards  Current focus on requirements and concepts for SysML v2  Prepared INCOSE article for June ‘15 on the capabilities, effectiveness measures, and driving requirements for a systems modeling environment 2

3. Product Support Software Models Mechanical & Electrical Models Q Q SET CLR S R Verification Models Performance, RMA, SWaP, Cost, etc.  G(s)U(s) Analytical Models Manufacturing Program Management System Architectural Model Test Plan Analysi s Spec System Engineering Development Environment To measure SysML effectiveness we need to understand the context of how it is used Customer © 2014 Lockheed Martin Corporation. All Rights Reserved. MBSE Use Cases Source: John Watson

4. System Modeling Environment (SME)  Used by system modelers to perform MBSE in the broader context of Model-Based Engineering (MBE)  Provide basic capabilities that include: –model construction –model visualization –model analysis –model management –model exchange and integration –support for MBSE collaboration and workflow  Impose requirements on both the modeling language and the tools 4

5. System Modeling Environment Basic Functionality in Support of MBSE 5

6. Effectiveness Measures  Improve systems engineering productivity, quality, and management of complexity and risk –Expressive: Ability to express the system concepts –Precise: Representation is unambiguous and concise –Presentation/communication: Ability to effectively communicate with diverse stakeholders –Model construction: Ability to efficiently and intuitively construct models –Interoperable: Ability to exchange and transform data with other models and structured data –Manageable: Ability to efficiently manage change to models –Usable: Ability for stakeholders to efficiently and intuitively create, maintain, and use the model –Adaptable/Customizable: Ability to extend models to support domain specific concepts and terminology 6

7. Driving Requirements 7  Driving requirements for the next-generation system modeling language and tools have been identified as highlighted below. 1.Express the core systems engineering concepts. 2.Include precise semantics that avoid ambiguity and enable a concise representation of the concepts. impact assessment of a requirement or design change integrate with equation solvers, execution environments, & capture quantitative data. 3.Provide flexible and rich visualization and reporting capabilities to support a broad range of model users. 4.Enable much more intuitive and efficient model construction. 5.Integrate across discipline-specific engineering tools, including hardware and software design, analysis and simulation, and verification.

8. 8 6.Provide a standard application program interface (API) to provide dynamic access to the model. 7.Capable of being managed in a heterogeneous and distributed modeling environment. 8.Enable efficient and intuitive use by a broad range of users with diverse skills. 9.Must be highly adaptable and customizable to multiple application domains. 10.Support the migration of existing models with minimum information loss. 11.Enable evolution of the above capabilities that take advantage of on-going advances in technologies, concepts, methods, and theories. Driving Requirements (cont.)

9.  Develop concepts for each driving requirement  Capture in a System Modeling Environment concept white paper  Vet among the community  Derive requirements for SysML v2 RFP 9 Next Steps

10. ROADMAP APPROACH 10

11.  For each capability area –Assess the current state to identify capabilities and limitations –Develop the concept and requirements and refine the moe’s that reflects the vision for how this can and should be done in the future –Determine near term, mid term, and long term improvements that can be realized Identify and leverage current activities, research, and initiatives where practical –Develop a follow-up plan on how to move forward  Integrate the concepts from each task area into an overall system modeling environment concept and roadmap that supports MBSE in the context of Virtual Engineering 11 Systems Modeling Environment Roadmap Approach

12.  Develop MBSE Use Cases  Update System Engineering Concept Model  Assess current state and develop concepts and requirements for each capability area –Model Construction –Model Visualization –Model Analysis –Model Interoperability –Model Management –Workflow Management –Collaboration Management  Evolve system modeling environment –Requirements, concepts, and prototype implementations –Implementation plans for near term, mid term, long term RTF, RFI’s, RFP’s 12 Systems Modeling Environment Roadmap Summary

13. BACKUP 13

14. Status  Regularly scheduled WG telecons hosted by Eldad Palachi  Developed conceptual framework  Prepared draft INCOSE article for June ‘15 on the capabilities, effectiveness measures, and driving requirements for a systems modeling environment (SME)  Initiated work on the SE Concept Model –Captured original UML for SE RFP in a model –Started work on the Systems Engineering Concept Model (SECM) for System v2 14

15. Today’s Agenda  Introduction and Driving Req’ts - Sandy Friedenthal - 15 min  SE Use Cases - John Watson - 10 min  PLM/MBSE Integration - Uwe Kaufman - 10 min  SE Concept Model for UML for SE RFP- Rick Steiner - 10 min  SE Concept Model - Chas Galey - 20 min  Geometric Modeling Concept- Michael Pfenning - 20 min  Model Injestion & Construction Concepts - Ron Williamson - 20 min  Model Management Concepts- Laura Hara - 20 min  Model Interoperability Concepts - Axel Reichwein - 15 min  Model Analysis Concepts presented by Manas Bajaj  MBEE Open Source Update - Chris Delp – 15 min  Plan Forward - 15 min  Open Discussion 15

16. Systems Modeling Environment 16 Source: A Practical Guide to SysML, 3 rd Edition Figure 18.5. High level information exchange between the system modeling tool and other tools.

17. Systems Modeling Environment Conceptual Architecture 10/06/14 17

18. System Modeling Environment 18