1 / 22

Overview of meta-modeling works for multi-clocked environments

Overview of meta-modeling works for multi-clocked environments. Christian Brunette IRISA/INRIA Rennes – ESPRESSO Synchron 2005. Motivations. Generalize the use of Polychrony SystemC  SSA  Signal Be able to operate in popular frameworks  Metamodeling approach

jewel
Download Presentation

Overview of meta-modeling works for multi-clocked environments

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. Overview of meta-modeling works for multi-clocked environments Christian Brunette IRISA/INRIA Rennes – ESPRESSO Synchron 2005

  2. Motivations • Generalize the use of Polychrony • SystemC  SSA  Signal • Be able to operate in popular frameworks  Metamodeling approach • OPENEMBEDD & TOPCASED projects • Definition of a UML profile for real-time and embedded systems (MARTE) • Develop a front-end for different multi-clocked environments

  3. Outline • What is GME ? • Signal-Meta • A new front-end for Polychrony • Some extensions • And then…

  4. Generic Modeling Environment • Configurable UML toolkit that supports the creation of : • domain-specific modeling • program synthesis environments • Free and Open-Source • Defines modeling paradigms as metamodels • Describes concepts and relations in UML-like class diagrams

  5. Generic Modeling Environment • MetaGME: modeling paradigm for specifying metamodels: • Offers specific stereotypes: FCO, Atom, Model, Reference… • Relation: containment, inheritance (classical and interface/implementation), Connection classes • Offers a ‘separation of concerns’ concept (Aspect): specify visibility + way to use FCO • OCL constraints + OCL functions

  6. GME tools • MetaGME interpeter • OCL constraint checker • Plug-in generator: • COM language • Builder Object Network (BON) API

  7. Outline • What is GME ? • Signal-Meta • A new front-end for Polychrony • Some extensions • And then…

  8. 1st version

  9. 1st version: example started ^= sec ^+ go started := true when go default started$ count := (count$) + 1 when started

  10. Signal-Meta • Meta-model close to SIGNAL grammar v4 • An Atom per SIGNAL operator (arithmetic, boolean, clock relation, scheduling,…) • An Atom for signal/constant declaration • A Model for process declaration, module, type declaration, sub-process, iteration • A Reference per process instantiation, for signals • 3 Aspects: interface, dataflow, and clock relations

  11. A Signal-Meta paradigm sheet

  12. Example of modeling: watchdog Dataflow Aspect Clock relations Aspects

  13. Outline • What is GME ? • Signal-Meta • A new front-end for Polychrony • Some extensions • And then…

  14. Interpreter • Instantiation of graphical objects into BON2 objects • Check & build SIGNAL equations • Write into files

  15. Interpreter • Build equations by recursive analysis on FCOs • Start/End on end-statements (signals, constants,…) • Checked • Signal/constant references • Validity of FCO attribute values • Detect cyclic definition • Not checked: • Type • Clock constraints

  16. Outline • What is GME ? • Signal-Meta • A new front-end for Polychrony • Some extensions • And then…

  17. Mode Automata • States contains SIGNAL “equations” • Only weak preemption for transitions • Priority attribute of transitions  determinism • INRIA RR-5728

  18. MIMAD • Model for Integrated Modular Avionics Design • Models for IMA systems, modules, partitions, and processes (standard ARINC653) • Describe mainly IMA Process and Module levels • References for Blocks (APEX services) • User-defined services described in SIGNAL • Represents scheduling of blocks as a mode automaton • Extension of the Signal-Meta Interpreter • INRIA RR-5715

  19. Signal-Meta on Eclipse • Use ATL (ATLAS Transformation Language) • Transformation of • MetaGME  AMMA (EMF) • AMMA  EMF • Current problem: lost graphical information • Bridging the Generic Modeling Environment and the Eclipse Modeling Framework, 4th workshop of Best Practice for MDSD, OOPSLA 2005.

  20. Outline • What is GME ? • Signal-Meta • A new front-end for Polychrony • Some extensions • And then…

  21. Conclusions • A new front-end for Polychrony • Modeling • Code generation • Foundation for several multi-clock modeling paradigms • Signal-Meta will be available on Eclipse • Too few interactivity during the modeling: no type or clock constraint checking

  22. Future works • Polychrony as a GME Addon • Check dynamically types and clock constraints • Interactivity during modeling • Integration in OPENEMBEDD and/or TOPCASED platform • Improvement of transformations MetaGME  EMF

More Related