SysML Modelica Integration Working Group Report (SE DSIG Meeting, San Antonio, TX, 9/15/2009) Chris Paredis Georgia Tech 1

Agenda Introduction Status update Path forward: Roadmap Discussion 2

Modelica: Dynamic Systems Modeling 3 motor torque

WG Focus and Scope Objective: – Leverage the strengths of both SysML and Modelica by integrating them to create a more expressive and formal MBSE language. Focus: – Reuse Modelica syntax by integrating Modelica into SysML as a profile – Define a formal Transformation Specification Scope: – Cover the Modelica constructs needed for the Modelica Standard Library to be used in SysML – Generate corresponding SysML constructs that fit within the profiling mechanism 4

Simple Example 5 Modelica Model SysML Analytical Model SysML Descriptive Model

6 Modelica SysML4Modelica Formal mapping

WG Activities Weekly conference call – Wed, 10-11AM Eastern Definition of Transformation Specification Reference implementations Working meeting on Thursday – 8: noon – Andrew Watson – Specification document (remaining issues, responsibilities) Current Members – Manas Bajaj – Roger Burkhart – Hans-Peter de Koning – Peter Fritzson – Sandy Friedenthal – Nerijus Jankevicius – Alek Kerzhner – Chris Paredis – Russell Peak – Nicolas Rouquette – Wladimir Schamai – Miyako Wilson 7

Progress Since San Jose Mappings for algorithm and equation sections – Algorithm sections  (opaque) behaviors – Equation sections  constraints Revision of the Mapping Document into a Transformation Specification: 1.Introduction 2.SysML profile 3.Modelica meta-model 4.Transformation Note: not limited to Modelica — transformations to other languages (e.g., SimScape) may be feasible. 8

Roadmap – Past (1) SysMLSysML-ModelicaModelica September Specification 1998— —1.4 Specifications March 2003 SysML RFP 2002— —2.2 Specifications December 2005 Initial Modelica-SysML presentation at SE DSIG (Kobi, Paredis) July 2006 Adopted Specification September 2006 Types in the Modelica Language (Broman, Fritzson, Furic) July 2007 Towards Unified Systems Modeling with the ModelicaML UML Profile (Pop, Akhvlediani, Fritzson) 9

Roadmap – Past (2) SysMLSysML-ModelicaModelica September Specification September Specification November 2007 Modeling Continuous System Dynamics in SysML (Johnson, Paredis, Burkhart) August 2007 INCOSE MBSE Project Phase 1 (Lockheed, Deere, Georgia Tech) November Specification December 2008 SysML-Modelica Working Group January st Face-to-face meeting (Fritzson, Schamai, Paredis) May Specification 10

Roadmap – Current Status SysMLSysML-ModelicaModelica March, June 2009 Intermediate Reports to SE DSIG Summer 2009 TGG implementation (Kerzhner) June 2009 ModelicaML Technical Report (Schamai) September 2009 ModelicaML Paper at Modelica Conference (Schamai, Fritzson, Paredis, Pop) Summer 2009 SysML-Modelica Transformation Specification TBD Specification ParaMagic implementation with OpenModelica Solver Future Modelica Version ? Future Directions? 11

Options for Future: SysML – Modelica Transformation Specification 1.Request for Comments (RFC) 2.Request for Proposals (RFP) 3.SysML v2.0 – Fold SysML-Modelica profile into SysML language 4.Not standardize Working Group has decided to explore the RFC option further 12

Request for Comments (RFC): Definition Any Contributing, Domain or Platform Member with technology that: – is relevant to a current Task Force adoption plan; – conforms to all applicable OMG Specifications; and – is available in a commercially-available implementation may make an unsolicited Submission to the TFC of the relevant Task Force for presentation to that TF for consideration through a Request for Comments. (Section 4.3, OMG Policies and Procedures, v2.8) 13

Request for Comments (RFC): Process 1. Submit to the TFC of the relevant Task Force an unsolicited proposal for adoption through RFC 2.The Task Force which received the proposal may recommend its issuance by its parent TC as an RFC. 3.The TC obtains AB approval and may then, by majority vote, cause OMG to issue the Submission as an RFC. 4.The comment period opens. Any party (including non-members) may send comments. Typically lasts 60 days. 5.TF considers comments and decides, by majority vote, whether to recommend the Submission to its parent TC for adoption 6.If the TF recommends adoption, the parent TC shall obtain AB approval before making a final decision on whether to recommend the Submission for adoption by the Board of Directors, using an electronic poll needing a 2/3 majority to pass 14

Request for Comments (RFC): Process Possible Timeline – Finalize Transformation Specification (December 2009) – Reference Implementation (January 2010) – Submit RFC proposal (March 2010 meeting) – AB approval (June 2010 meeting) – Comment period (Summer 2010) – TF approval (September 2010 meeting) – Submission for adoption (December 2010 meeting) 15

Request for Comments (RFC): Summary For non-controversial specifications Requires vendor implementation and active user community – SysML and Modelica communities are very active – Initial discussions with tool vendors: NoMagic, OpenModelica, Dynasim (Dassault Systemes) Is faster than the other options Would be the (first?) formal definition of an MDA transformation specification 16

Questions -- Discussion Feedback on options? 1.Request for Comments (RFC) 2.Request for Proposals (RFP) 3.SysML v2.0 4.Not standardize Which Task Force? Team members? 17

Reminder Working meeting on Thursday – 8: noon – Andrew Watson – Specification document (remaining issues, responsibilities) 18