Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "ModelingPlatform/EclipseConEuropeNov2 2011"
(→Attendees) |
|||
| Line 1: | Line 1: | ||
== '''Eclipse Modeling Ecosystem Face to Face Meeting at EclipseCon Europe''' == | == '''Eclipse Modeling Ecosystem Face to Face Meeting at EclipseCon Europe''' == | ||
| − | |||
9h00 - 12h00, Wednesday November 2, 2011 | 9h00 - 12h00, Wednesday November 2, 2011 | ||
'''Conference room [http://en.nestor-hotel-ludwigsburg.de/conferences-meetings/conference-rooms/room-Herzog-Eberhard-Ludwig-45-qm-maximum-25-persons Herzog Eberhard Ludwig] at the Nestor Hotel''', Ludwigsburg, Germany | '''Conference room [http://en.nestor-hotel-ludwigsburg.de/conferences-meetings/conference-rooms/room-Herzog-Eberhard-Ludwig-45-qm-maximum-25-persons Herzog Eberhard Ludwig] at the Nestor Hotel''', Ludwigsburg, Germany | ||
| − | |||
=== Attendees === | === Attendees === | ||
| Line 24: | Line 22: | ||
<br> | <br> | ||
'''End-User Companies'''<br> | '''End-User Companies'''<br> | ||
| − | End-user companies to give a summary of what is missing in Eclipse open source modeling, e.g. feature, support, documentation, migration, training, etc. | + | End-user companies to give a summary of what they do with and what is missing in Eclipse open source modeling, e.g. feature, support, documentation, migration, training, etc. Includes also what are their current initiatives if applicable. |
*Dominique Toupin, Ericsson | *Dominique Toupin, Ericsson | ||
| + | ** Modeling for System specification and design | ||
| + | ** Large scale Modeling: large & distributed teams, big models | ||
| + | ** Using many (open source or not) tools | ||
| + | ** Plan to start using Eclipse Modeling tools in 2012 | ||
| + | ** Need to have target observability from the model point of view | ||
| + | ** Using UML and other modeling languages | ||
| + | ** Focus in 2011: Modeling support in Mylyn, EGit, EMF Compare for MDT Papyrus | ||
| + | ** Main improvement topics: | ||
| + | *** Logical model merge | ||
| + | *** Connection to various VCS | ||
| + | *** Advanced / Flexible M2T / M2M engines and tools | ||
| + | *** Good implementation of UML standard | ||
| + | *** UML Action Language | ||
| + | *** Modeling Team work (bringing Git to models) | ||
| + | *** Simulation capabilities | ||
| + | *** Traces / debug aware of code generation | ||
| + | *** Performances on large models repositories | ||
| + | *** Import from legacy tools | ||
| + | *** Review tools: enhance Mylyn code review tool (RE4) to support models (connection to Gerrit ?) | ||
*Pierre Gaufillet, Airbus | *Pierre Gaufillet, Airbus | ||
*Robert Blust, UBS AG | *Robert Blust, UBS AG | ||
Revision as of 07:18, 10 November 2011
Contents
Eclipse Modeling Ecosystem Face to Face Meeting at EclipseCon Europe
9h00 - 12h00, Wednesday November 2, 2011
Conference room Herzog Eberhard Ludwig at the Nestor Hotel, Ludwigsburg, Germany
Attendees
- Dominique Toupin, Ericsson
- Gaël Blondelle, Obeo
- Robert Blust, UBS AG
- Stephan Eberle, itemis
- Tanya Fesenko, Modelsolv
- Martin Flügge, MFTechnologies
- Pierre Gaufillet, Airbus
- Benjamin Kamphausen, Fraunhofer ESK
- Alvaro Sanchez, Ericsson
- Remi Schnekenburger, CEA LIST
- Bran Selic, Malina Software
Agenda Items
End-User Companies
End-user companies to give a summary of what they do with and what is missing in Eclipse open source modeling, e.g. feature, support, documentation, migration, training, etc. Includes also what are their current initiatives if applicable.
- Dominique Toupin, Ericsson
- Modeling for System specification and design
- Large scale Modeling: large & distributed teams, big models
- Using many (open source or not) tools
- Plan to start using Eclipse Modeling tools in 2012
- Need to have target observability from the model point of view
- Using UML and other modeling languages
- Focus in 2011: Modeling support in Mylyn, EGit, EMF Compare for MDT Papyrus
- Main improvement topics:
- Logical model merge
- Connection to various VCS
- Advanced / Flexible M2T / M2M engines and tools
- Good implementation of UML standard
- UML Action Language
- Modeling Team work (bringing Git to models)
- Simulation capabilities
- Traces / debug aware of code generation
- Performances on large models repositories
- Import from legacy tools
- Review tools: enhance Mylyn code review tool (RE4) to support models (connection to Gerrit ?)
- Pierre Gaufillet, Airbus
- Robert Blust, UBS AG
- Benjamin Kamphausen BMW
Possible Synergies Between Eclipse Working Group
Modeling synergies between Automotive Working Group, OPEES (PolarSys) Working Group, Multicore
Implementer Companies
What is the view of implementer companies, their core expertise, what implementation can have a big impact on open source modeling next year, low hanging fruit, what is their current initiatives, etc.
- Stephan Eberle, itemis update
- Remi Schnekenburger, CEA LIST
End-User Companies Business Case Brainstorming
Review first version of Modeling slides for end user companies, identify additional benefits for end user companies in order to facilitate budget approval
- Gaël Blondelle, Obeo, feedback from the OPEES group
Improvements areas interesting for end user companies
- Scalable logical model merge
- Ability to connect to different physical repository technologies, e.g. Git,
- Advanced, flexible and efficient code generation. Should be simple and efficient to do M2M and M2T transforms.
- Good implementation of UML standard. Most tools implement some part well but skip others. MagicDraw is good reference tool to compare against.
- UAL/ALF implementation
- Team development capabilities across distributed models and repositories
- Model Simulation capabilities
- Trace and Debug capabilities connected to code generation feature
- Stable and clean user interface. We don't want to see a lot of Eclipse noise.
- Ability to work with fragmented models
- Good performance on large model repositories.
- Ability to import from existing tools without information loss. A huge bonus with be to preserve all diagram information.
- Traceability with requirements and text cases