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


< MDT‎ | Papyrus

This page provides the required docuware for the MDT Papyrus 0.7.0 Release Review.


Papyrus is a graphical modeler for both the Unified Modeling Language (UML2) and the System Engineering Language (SysML) OMG standards. Specially, it provides:

  • Editors for the UML2.
  • One editor for UML profiles.
  • Specific editors for SysML.

In addition, Papyrus is also a framework to build specific graphical modelers for any UML profiles or EMF metamodels and a runtime platform to host those editors.


Content of the first release

  • For UML2, Papyrus provides graphical editors for class, composite, package, use case, statemachine, sequence, communication and activity diagrams.
  • Papyrus provides also a graphical support for modeling UML2 profiles.
  • For SysML, Papyrus provides graphical editors for IBD, BDD, parametric diagrams and requirements diagrams.
  • Papyrus provides facililties for custumizing its UI for specific usages of UML2 and SysML.

Accordance with project plan themes and priorities

MDT Papyrus is the result of the merge of two open-source projects: Papyrus developped by CEA ( and TopCASED UML. Our plan for this first release was to provide a version of the new Papyrus at least providing the same features as its original projects. This pupose has not yet been achieved through this version 0.7.0 Papyrus, but is already very promising. This goal will be achieved in the context of the next realease, version 0.8.0. The version 0.7.0 provides already following features:

  • For UML2, Papyrus supports: Class, Composite, Package, Use case, Communication, Statemachine, Activity, Sequence and Profile Diagram editors.
  • For SysML, Papyrus supports preliminary versions of: Block Definition, Internal Block, Requirements and Parametric Diagram editors.

Non-Code Aspects


This release is the first release of the Papyrus component.

  • The project lead certifies that the requirements for Eclipse Quality APIs have been met for this release.
  • Metamodel definitions and corresponding implementations are considered APIs.
  • Non-API classes are separated from the exposed API through an internal package in the namespace.
  • API Tooling is activated on all plugins to mark exceptions within the exposed API.


  • Papyrus graphical editors are based on the GMF framework and are been generated using the GMF tooling.
  • Papyrus architecture is based on a component called the backbone that enable Papyrus to support various kinds of editors designed with different technologies. Currentlty, Papyrus provides adaptors for EMF-based or GMF-based editors.

Tool Usability

  • Papyrus may be used to denote UML2 or SysML models.
  • Papyrus may be used to design and apply UML profiles.
  • Papyrus UI may be custumized in order to fit specific domain needs.


Nothing has been deprecated.


Bugzilla snapshot for Helios as of 28 May 2010:



MDT Papyrus 0.7.0 is compliant with both following OMG standards:

UI Usability

MDT Papyrus is conforming to the user interface guidelines.


MDT Papyrus plans to be a “+3” component in the simultaneous release.

M1 08/06/2010 0.8.0M1
M2 09/17/2010 0.8.0M2
M3 10/29/2010 0.8.0M3 
M4 12/10/2010 0.8.0M4 
M5 01/28/2011 0.8.0M5 
M6 03/11/2011 0.8.0M6 (API Freeze) 
M7 04/29/2011 0.8.0M7 (Feature Freeze)


  • Interactions in Bugzilla
  • Activity on the Papyrus newsgroup
  • Collaboration with other projects at Eclipse (e.g., Modisco)
  • Planned integration in the TopCASED environment in Q3 2011: [1]
  • Used as basis for the Scade System Designer for providing the system view on top of SCADE: [2].
  • Large diffusion in the academics community using UML2 (e.g., hudge presence at the international conference MODELS 2010 in Oslo)

Commiter Changes

Following committers have been wellcome:

  • Tristan FAURE (ATOS)
  • Tatiana Fesenko (CEA)
  • Vincent Hemery (ATOS)
  • Vincent Lorenzo (CEA)
  • Ansgar Radermacher (CEA)
  • Mathieu Velten (ATOS)

Following committers have been decommitterized:

  • Etienne Julio
  • Jerome Benoit
  • Francisco Javier Cano
  • David Carlson

IP Issues

The MDT Papyrus component leadership verifies that:

  • the about files and use licenses are in place as per the Guidelines to Legal Documentation.
  • all contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
  • all significant contributions have been reviewed by the Foundation's legal staff.
  • all non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff.
  • all Contribution Questionnaires have been completed.
  • the "provider" field of each plug-in is set to "Eclipse Modeling Project“.
  • the "copyright" field of each feature is set to the copyright owner (the Eclipse Foundation is rarely the copyright owner).
  • any third-party logos or trademarks included in the distribution (icons, help file logos, etc) have been licensed under the EPL.
  • any fonts or similar third-party images included in the distribution (e.g. in PDF or EPS files) have been licensed under the EPL.

The MDT Project IP log in located at

Project Plan

Draft development plan for MDT Papyrus 0.8.0 is available:

Back to the top