Embed Size (px)
DESCRIPTION
The demand for integrated environments to support model-driven development based on standardized or domain-specific modeling languages is on the rise. When setting out to develop such environments, toolsmiths must frequently use, buy, or build the same handful of common building blocks to support things like model exploration, property description, resource management, validation, compare/merge, search, index, etc.. While they can certainly benefit from the wide range of existing modeling frameworks and tools at Eclipse, experience has shown that there is still a significant gap between these existing components and what users expect to see in an industrial strength environment. This has resulted in a growing number of increasingly redundant modeling technologies and overlapping consumer-driven modeling components at Eclipse. We owe it to our communities to do better than this.Just as the Eclipse e4 project has a set of composeable application services, also referred to as the "twenty things", the Modeling project should have its own list of essential services - the "twenty modeling things". Efforts are already underway to put some of these things into practice by creating higher level modeling tool platforms. Among these are the Papyrus project, where reusable parts that comprise UML tooling are being refactored into a generic backbone, and the Artop project (www.artop.org), where an AUTOSAR modeling tool platform has been built atop an AUTOSAR-independent layer of generic services. This talk will propose a core set of modeling services and APIs (based on industry experience and community input), discuss whether/how existing efforts support each service, and speculate as to how any remaining gaps might be filled by the upcoming Sphinx project, where Papyrus and Artop committers will join forces to create an integrated modeling tool platform at Eclipse.
Citation preview
The Twenty Modeling Things
Stephan Eberle, GeensysKenn Hussey, Zeligsoft
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
About
Stephan Eberle– Development manager at Geensys in Paris, France– Lead of Artop Core and Validation– Coming soon: Sphinx project co-lead
Kenn Hussey– MDT project lead– Committer on EMF, UML2, BPMN2, MST, …
EclipseCon 2010 2
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 33
Outline
Quo vadis, Eclipse Modeling Project?
What are the twenty modeling things?
How do we put them into practice?
What next?
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 4
Quo vadis, Eclipse Modeling Project?
Missing overall vision!
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 5
Outline
Quo vadis, Eclipse Modeling Project? What are the twenty modeling things?
How do we put them into practice?
What next?
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 6
20 Modeling Things
Essential Things
Typical Things
Advanced Things
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 7EclipseCon 2010 © 2010 Geensys, Zeligsoft. Made available under Eclipse Public License v1.0. 7
1.Metamodel
Management
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 8
2. Scoping
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 9
3. Lifecycle
Management
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 10
4. Navigation
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 11
5. Editor
Management
Demo
EclipseCon 2010
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 13EclipseCon 2010 © 2010 Geensys, Zeligsoft. Made available under Eclipse Public License v1.0. 13
6. Complex Operations
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 14
7. Query & Indexing
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 15
8. Persistence
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 16
Typical Things
9. Organization & Distribution10. Compare & Merge11. Search & Replace12. Validation13. Transformation14. Code Generation15. Documentation & Report Generation
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 17
Advanced Things
16. Version Management17. Access Control18. Task-focused Modeling19. Dynamic Modeling & Scripting20. Workflow, Execution, Build System
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 18
Outline
Quo vadis, Eclipse Modeling Project?
What are the twenty modeling things? How do we put them into practice?
What next?
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 19
Mission of Sphinx
To make sure that things exist by– Reusing and integrating existing modeling
components– Providing missing pieces in Sphinx
To make sure that things fit together by– Helping to enhance existing modeling components– Implementing additional glue in Sphinx
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 20
Mission Impossible?
Integrated modeling tool platform
© 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0EclipseCon 2010 21
What next?
2O modeling things presented here are not meant to be final – tell us what you think [1]
Check out Sphinx project proposal [2] - become an “Interested Party”
Further discussion at Modeling Panel and BOF [3], [4]?
Don’t miss the Papyrus talk [5]!
[1] eclipse.modeling.mdt
[2] http://www.eclipse.org/proposals/sphinx/
[3] http://www.eclipsecon.org/2010/sessions?id=1528
[5] http://www.eclipsecon.org/2010/sessions/sessions?id=1385
[4] http://www.eclipsecon.org/2010/sessions?id=1631
