170 likes | 177 Views
Agenda for the SysML-Modelica Integration Working Group Meeting in San Antonio, TX on 9/17/2009, including introductions, recap of current status, feedback on RFC approach, review of remaining issues in transformation specification, and responsibilities and timeline.
E N D
SysML Modelica IntegrationWorking Group Meeting(SE DSIG Meeting, San Antonio, TX, 9/17/2009) Chris Paredis Georgia Tech
Agenda • 8:30: Introductions • 8:45: Recap of current status • 9:00: meeting Andrew Watson • Feedback on RFC approach • 10:00: Break • 10:30: Review of remaining issues in transformation specification • 11:30: Responsibilities and timeline
Remaining Issues: Current Phase • Substantive: • When to use profile? When to use parametrics? • «modelicaType» • Express constraints on stereotypes more formally (preferably in OCL) • Inheritance and redeclaration of packages; packages contained in models • Part III: Modelica meta-model • Part IV: Correspondence
Remaining Issues: Current Phase • Editorial: • Fill in gaps in Part I • Replace figures with jpg and fix capitalization on stereotypes • Reformat information in Part II to updated structure
Remaining Issues: Longterm • Arrays • Local Type Modifications
Modelica: Dynamic Systems Modeling motor torque
Simple Example ModelicaModel SysML Descriptive Model SysML Analytical Model
SysML4Modelica Formal mapping Modelica
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
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)
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
Request for Comments (RFC): Process • Possible Timeline • Finalize Transformation Specification(December 2009) • Reference Implementation (January 2010) • Submit RFC proposal (March 2010 meeting) • AB approval (March or June 2010 meeting) • Comment period (Summer 2010) • TF approval (September 2010 meeting) • Submission for adoption (December 2010 meeting)
Request for Comments (RFC): Summary • Seems appropriate for this non-controversial specification • Requires vendor implementation and active user community • SysML and Modelica communities are very active • Initial discussions with tool vendors: • NoMagic, InterCAx, Sparx? • OpenModelica, Dynasim (DassaultSystemes) • Is faster than the other options • Would be the (first?) formal definition of an MDA transformation specification