1 / 18

SysML Modelica Integration Working Group Report (SE DSIG Meeting, San Antonio, TX, 9/15/2009)

This report provides an overview of the goals, scope, and progress of the SysML-Modelica Integration Working Group, including discussions on the integration of SysML and Modelica, transformation specifications, and future roadmap.

perryz
Download Presentation

SysML Modelica Integration Working Group Report (SE DSIG Meeting, San Antonio, TX, 9/15/2009)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Agenda • Introduction • Status update • Path forward: Roadmap • Discussion

  3. Modelica: Dynamic Systems Modeling motor torque

  4. 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

  5. Simple Example ModelicaModel SysML Descriptive Model SysML Analytical Model

  6. SysML4Modelica Formal mapping Modelica

  7. WG Activities • Weekly conference call • Wed, 10-11AM Eastern • Definition of Transformation Specification • Reference implementations • Working meeting on Thursday • 8:30 - 12noon • Andrew Watson • Specification document (remaining issues, responsibilities) • Current Members • Manas Bajaj • Roger Burkhart • Hans-Peter de Koning • Peter Fritzson • Sandy Friedenthal • NerijusJankevicius • AlekKerzhner • Chris Paredis • Russell Peak • Nicolas Rouquette • WladimirSchamai • Miyako Wilson

  8. 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: • Introduction • SysML profile • Modelica meta-model • Transformation • Note: not limited to Modelica — transformations to other languages (e.g., SimScape) may be feasible.

  9. Roadmap – Past (1)

  10. Roadmap – Past (2)

  11. Roadmap – Current Status

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

  13. 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)

  14. Request for Comments (RFC): Process • Submit to the TFC of the relevant Task Force an unsolicited proposal for adoption through RFC • The Task Force which received the proposal may recommend its issuance by its parent TC as an RFC. • The TC obtains AB approval and may then, by majority vote, cause OMG to issue the Submission as an RFC. • The comment period opens. Any party (including non-members) may send comments. Typically lasts 60 days. • TF considers comments and decides, by majority vote, whether to recommend the Submission to its parent TC for adoption • 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

  15. 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)

  16. 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

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

  18. Reminder • Working meeting on Thursday • 8:30 - 12noon • Andrew Watson • Specification document (remaining issues, responsibilities)

More Related