GMF Tooling 3.0 Vision, Architecture, Roadmap

Transcription

1 GMF Tooling 3.0 Vision, Architecture, Roadmap , OMG/Eclipse Symposium, Reston VA Michael Golubev, GMF Tooling lead Montages AG

2 GMF Tooling - Overview Vision: Support creation of graph syntax (diagrams) for arbitrary Ecore based metamodels Approach: Model Driven Architecture (MDA) 1.Capture the domain of Diagram Editors as platform independent model (PIM) 2.Take domain models of the content as input 3.Map PIM of Diagram Editors to platform specific model (PSM) 4. Generate code from the PSM Implementation: Reuse of OMG standards as implemented by Eclipse

3 GMF Tooling MDA approach

4 GMF-T Technical Achievements Diagram structure: Nodes: shapes & pure labels & border items Links: EClass- & EReference-based, link decorations Labels: external & fixed, custom parsers, EReference- and OCL-based Compartments: list-based & free-form Graphical representation: All basic shapes, polygons, polylines, access to Draw2D properties Borders, layouts, link decorations, raster and vector images Custom counterparts for everything as an escape for existing code Advanced behavior Audits, metrics, validation

5 GMF-T 5 years of user history Adopted inside Eclipse community Papyrus (for UML 2, SysML diagrams) Bonita Open Solution (BPMN diagrams) Multiple full featured commercial products A lot of small & medium sized diagram products Expertise spreads out across the community

6 After 5 years user reaction Much easier to deal with first 80% of user diagram requirements... but still difficult to implement the other 20% Common complaints: Complicated models, multiple attempts to simplify input Difficult to extend Integration between custom and generated code Issues of maintainability of the generated code

7 GMFT 2.4 lessons learned User changes go directly to code, why? Mistakes early at the project life: Retreat from MDA Usage of the non-standard technologies

8 GMFT 3.0 back to MDA Transformation Map Gen in QVTo OMG standardized technology for M2M Native features: debugger, tracibility User tweaks are stored as QVTo scripts too Generation of QVTo from model comparision (provisional) Direct back references PSM PIM PSM model & bridge simplified, data deduplication 1 stage codegen, no code stored in model Cooperative codegen for Draw2D and GEF More use of the OCL Back to standard template language (3.0+)

9 Battling the size of domain Forces: Simplify models vs. Add new features Feature request PIM/PSM changes templates changes Model growth and facet-ness Solution: Stack of separate mini-mda add-ons (diaglets) PIM ext (bridge ext ) PSM ext Templates ext code ext Automatic discovery of add-ons Static & runtime analysis of compatibility Enables exchange between GMFT extenders From forum to add-ons repository Separate release cycle

10 GMFT 3.0 improvements GMF-Map additions: Derivation for nodes containment and link ends (OCL-based & blackbox) GMF-Graph additions: Buttons, checkboxes, drop-downs, rotated labels Definition of dynamic visual capabilities Custom attributes for default figures GMF-Tooling additions: Modeling of semantic updates triggered by menus, palette, or buttons Modeled binding between semantic and graphical properties Composite & customized elements creation Customisation for link handles

11 GMFT 3.0 solutions