Your SlideShare is downloading. ×
The Twenty Modeling Things
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

The Twenty Modeling Things

2,528
views

Published on

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, …

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.

Published in: Technology

1 Comment
6 Likes
Statistics
Notes
No Downloads
Views
Total Views
2,528
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
110
Comments
1
Likes
6
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. The Twenty Modeling Things
    Stephan Eberle, Geensys
    Kenn Hussey, Zeligsoft
  • 2. 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
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    2
  • 3. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    3
    3
    Outline
    • Quo vadis, Eclipse Modeling Project?
    What are the twenty modeling things?
    How do we put them into practice?
    Whatnext?
  • 4. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    4
    Quo vadis, Eclipse Modeling Project?
    • Missing overall vision!
  • EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    5
    Outline
    Quo vadis, Eclipse Modeling Project?
    • What are the twenty modeling things?
    How do we put them into practice?
    Whatnext?
  • 5. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    6
    20 Modeling Things
    Essential Things
    TypicalThings
    Advanced Things
  • 6. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    7
    1.Metamodel Management
    EclipseCon 2010
    © 2010 Geensys, Zeligsoft. Made available under Eclipse Public License v1.0.
    7
  • 7. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    8
    2. Scoping
  • 8. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    9
    3. Lifecycle Management
  • 9. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    10
    4. Navigation
  • 10. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    11
    5. Editor Management
  • 11. Demo
    EclipseCon 2010
  • 12. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    13
    EclipseCon 2010
    © 2010 Geensys, Zeligsoft. Made available under Eclipse Public License v1.0.
    13
    6. Complex Operations
  • 13. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    14
    7. Query & Indexing
  • 14. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    15
    8. Persistence
  • 15. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    16
    Typical Things
    Organization & Distribution
    Compare & Merge
    Search & Replace
    Validation
    Transformation
    Code Generation
    Documentation & Report Generation
  • 16. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    17
    Advanced Things
    Version Management
    Access Control
    Task-focused Modeling
    Dynamic Modeling & Scripting
    Workflow, Execution, Build System
  • 17. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    18
    Outline
    Quo vadis, Eclipse Modeling Project?
    What are the twenty modeling things?
    • How do we put them into practice?
    Whatnext?
  • 18. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    19
    Mission of Sphinx
    To make sure that things existby
    Reusing and integrating existing modeling components
    Providing missing pieces in Sphinx
    To make sure that things fit togetherby
    Helping to enhance existing modeling components
    Implementing additional glue in Sphinx
  • 19. EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    20
    Mission Impossible?
    • Integrated modeling tool platform
  • EclipseCon 2010
    © 2010 by Geensys and Zeligsoft; made available under Eclipse Public License v1.0
    21
    Whatnext?
    2O modelingthingspresentedhere are not meant to befinal – tell us whatyouthink [1]
    Check out Sphinx project proposal [2] - become an “Interested Party”
    Furtherdiscussion atModelingPanel 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
    [4] http://www.eclipsecon.org/2010/sessions?id=1631
    [5] http://www.eclipsecon.org/2010/sessions/sessions?id=1385