1 / 20

SysML-Modelica Integration Working Group Report (SE DSIG meeting, San Jose, CR 6/23/2009)

SysML-Modelica Integration Working Group Report (SE DSIG meeting, San Jose, CR 6/23/2009). Chris Paredis Georgia Tech. Presentation Overview. Objectives, Focus, Scope Activities Illustrative Example Reference Implementations Remaining Issues Summary. Modelica: Dynamic Systems Modeling.

matthewrichards
Download Presentation

SysML-Modelica Integration Working Group Report (SE DSIG meeting, San Jose, CR 6/23/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 Jose, CR 6/23/2009) Chris ParedisGeorgia Tech

  2. Presentation Overview • Objectives, Focus, Scope • Activities • Illustrative Example • Reference Implementations • Remaining Issues • Summary

  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 • 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. WG Activities • Weekly conference call • Wed, 10-11AM Eastern • Creation of mapping • Reference implementations • Working meeting on Thursday • Room: Itabo • 9-12noon and 1-3PM • 3-5PM QUDV discussion • 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

  6. Current Status: Mapping Document(70-page working document)

  7. Simple Illustrative Example

  8. Dynamics Behavior

  9. SysML4Modelica Formal mapping model Spring "Linear 1D translational spring" extends Translational.Interfaces.PartialCompliant; parameter SI.TranslationalSpringConstant c "spring constant "; parameter SI.Distance s_rel0=0 "unstretched spring length"; equation f = c*(s_rel - s_rel0); end Spring;` Modelica

  10. Link Dynamics Model to Descriptive Model

  11. Establish Detailed Parametric Relationships

  12. Dynamics Behavior

  13. Alternate Mapping to Parametrics

  14. Alternate Mapping to Parametrics

  15. Reference Implementations • Goal: • Demonstrate use of SysML and Modelica • Validate the mapping through complex examples • Convert Modelica Standard Library into equivalent SysML library • Two parallel efforts • Wladimir Schamai (EADS) • Alek Kerzhner (Georgia Tech)

  16. PapyrusUML to Modelica • Wladimir Schamai • PhD research at Linköping University, Sweden • Advised byPeter Fritzson and Chris Paredis Modelica code generation using eclipse Acceleoplugin Generated (textual) Modelica code

  17. Acceleo Code Generation Template Example

  18. Triple Graph Grammar Mapping between MagicDraw and OpenModelica • Alek Kerzhner • PhD student at Georgia Tech • Advised by Chris Paredis and Nicolas Rouquette (during JPL internship) (Note: My interpretation of work by Andy Schürr)

  19. Remaining Issues • On the agenda for Thursday: • type • extends • equation/algorithm, connect • function • Longer term issues – to be revisited: • Modifications and Redeclarations • Arrays • Implementation, demonstration, validation

  20. Summary • Objective: • Leverage the strengths of both SysML and Modelica by integrating them to create a more expressive and formal MBSE language. • Getting close to a full initial mapping definition • Two reference implementations underway • Next Steps: • Complete initial mapping document • Revisit the more complex constructs • Validation with complex example • Expect a live demo at the next meeting…

More Related