Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

ModelingPlatform/EclipseConEuropeNov2 2011

Eclipse Modeling Ecosystem Face to Face Meeting at EclipseCon Europe

9h00 - 12h00, Wednesday November 2nd, 2011

Conference room Herzog Eberhard Ludwig at the Nestor Hotel, Ludwigsburg, Germany


  • 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 (UAL) / Action Language for Foundational UML (ALF)
      • 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
    • Modeling for System / Software specification and design (embedded and ground)
    • UML, SysML, SAM (Structure Analysis Modeling language based on SA/RT concepts), AUI (Abstract User Interface), ECORE
    • Requirements handling in models (texts and model fragments)
    • Scripting on models (Jython / Javascript)
    • Generation of documents, test plans, proof obligations to validate partial / complete products
    • Behavioral simulation (graphical animation, headless simulation for non-regression tests)
    • Prove structual properties using OCL
    • Connection between modeling and ALM tools
    • Seamless migration from classical process to Model Based process
    • 2012
      • Contribute all valuable TOPCASED components to Eclipse / Polarsys (collaboration with Atos)
        • OCL checker
        • Gendoc 2
        • Scripting
        • Metrics
        • Textual Requirements editor in models
        • Various modelers / languages (SAM, AUI, obsolete UML / SysML modelers)
      • Go on with our current effort on MDT Papyrus (SysML and UML)
      • Improve Gendoc 2 (useability, better HTML support, maturation)
      • Generation of proof obligations from UML / SysML / SAM to FramaC (targeting C code)
    • Beyond 2012
      • Converge with ReqIF / RMF and improve requirement management tools
      • Integration of behavioral provers
      • Improve generic/specific simulators (UI, debug capability, maturation)
      • Integrate Gendoc2 script editor (aka M2M Acceleo) within LibreOffice / OpenOffice / Microsoft Word
      • Use UML/MARTE for dynamic design
      • Qualify M2M / M2T transformations (vs DO-178)
      • Traceability and M2M / M2T transformations
      • Improve requirement tools to compete with DOORS features
  • Robert Blust, UBS AG
    • Importance of customizability of the modeling toolset
    • The modeling platform gathers enterprise knowledge in models: Requirements, Processes, Applications, Components, etc.
    • Projects are transient, leverage existing knowledge and create new knowledge.
    • CDO as a repository.
    • Merging and diffs of models: Ok with large models? Use EMF compare on the model level.
    • Features going in production in November:
      • Computes KPI of complexity of the system
      • Manage projects domains.
    • Issue : Get information back from projects models to enterprise models
    • Import repository wizard: Review the new knowledge before accepting it in the repository
    • CDO allows to have other applications on top of it like for example a web site for enterprise knowledge visualization
    • Idea to leverage REQiF standard for requirements engineering.
    • Link to Presentation
  • Benjamin Kamphausen BMW
    • Begin to be involved in Auto IWG
    • Aim to improve the Eclipse Modeling platform for BMW specific usages

Possible Synergies Between Eclipse Working Group
Modeling synergies between:

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 are their current initiatives, etc.

  • Stephan Eberle, itemis update
    • Improvement in Xtext/Xtend 2.1
    • Xtend is now based on Xtext
    • Xcore is a new feature providing an ECORE textual syntax using Xtend as an action language. Driven by Ed Merks.
    • RMF: implements ReqIF in ECORE + a basic editor (going nevertheless beyond the default EMF tree editor).
    • Link to Presentation
  • Remi Schnekenburger, CEA LIST
    • Papyrus status and plans for Juno
      • Evaluation of MDT Papyrus vs e4 in progress
      • Improvement of table editors
      • stabilization of the architecture
      • bug fixes in progress
      • Improvement of customizability
      • Development of ALF support
      • Migration to the latest UML version being studied
  • Raphaël Faudou, AtoS
    • Papyrus industrial usage
      • Feedback on intensive usage for customers (report bugs, tune performance on large models, suggest improvements,…)
      • Bug fixes on diagrams and model explorer
      • Improvement of collaborative work to support CDO-based approach
      • Provide extended enterprise management for model (extract sub models and manage interfaces with parent model)
      • Migrate TOPCASED Abstract User Interface editor to Papyrus technology
      • Provide SPEM editor based on Papyrus technology
    • Contribute several TOPCASED components to Eclipse / Polarsys :
      • Model simulation engine (UML state machine and activity interpreter), aligned on fUML specification
      • Requirement traceability engine, aligned with ReqIF specification and RMF Eclipse project (in collaboration with Airbus)
      • Gendoc 2 engine and tag libraries (in collaboration with Airbus)
      • UML2EC code generator for embedded C code
    • Integrate contract modeling and C code generator
      • Provide a transformation able to capture functional contracts expressed at model level (with OCL or other formalism) and translate them into ACSL (ANSI C Specification Language) properties at C code level so that they can be processed by FRAMA-C tooling

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 Polarsys (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

Copyright © Eclipse Foundation, Inc. All Rights Reserved.