MDT/Papyrus/Reviews/v0.9.0

This page provides the required docuware for the MDT Papyrus 0.9.0 (Juno) Release Review.

Overview

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.

Features

Content of the release 0.9.0

• Model explorer has a better support of the EMF Facet framework
• Bug fixes on diagrams (SysML and UML) editors: 70+ bugs on SysML diagram editors for example
• Bug fixes on the model explorer (22 bugs fixed)
• Better support of table editors: 11 bugs fixed

Accordance with project plan themes and priorities

MDT Papyrus is the result of the merge of two open-source projects: Papyrus developped by CEA (www.papyrusuml.org) and TopCASED UML. The 0.9.0 release of Papyrus has partially realized its plan as denoted in : [1]

Non-Code Aspects

• User documentation hosted at [Papyrus Web site | http://www.eclipse.org/modeling/mdt/papyrus/usersCorner/usersCornerIndex.php]
• Developer documentation on the Papyrus [Wiki | http://wiki.eclipse.org/Papyrus_Developer_Guide]

APIs

This release is the second 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.

Architecture

• 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, GMF-based, or XText-based or EMF-Facet-based editors.
• Model explorer relies on the EMF Facet [1] customization framework
• Papyrus 0.9.0 has also been refactored in order to create dependency layers. For example, Papyrus 0.9.0 provides a core framework, some extensions or generic services on top of GMF, on top of EMF, etc. Finally, some diagram and table layers for each UML and SysML diagram implementation

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 customized in order to fit specific domain needs.

End-of-Life

Nothing has been deprecated.

Bugzilla

Bugzilla snapshot for Juno as of May 22nd, 2012.

Standards

MDT Papyrus 0.9.0 is compliant with both following OMG standards:

• [UML 2.4.1 standard | http://www.omg.org/spec/UML/2.4.1/]
• [SysML 1.2 standard | http://www.omg.org/spec/SysML/1.2/].

UI Usability

MDT Papyrus is conforming to the user interface guidelines.

Schedule

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

• M1 08/17/2011 0.9.0M1
• M2 09/28/2011 0.9.0M2
• M3 11/09/2011 0.9.0M3
• M4 12/14/2011 0.9.0M4
• M5 02/01/2012 0.9.0M5
• M6 03/14/2012 0.9.0M6 - API Freeze
• M7 05/09/2012 0.9.0M7 - Feature Freeze
• RC1 05/23/2012 0.9.0RC1
• RC2 05/30/2012 0.9.0RC2
• RC3 06/06/2012 0.9.0RC3
• RC4 06/13/2012 0.9.0RC4
• Juno 06/29/2012 0.9.0 - Release
• SR1 11/26/2012 0.9.1 - Service Release 1
• SR2 02/26/2013 0.9.2 - Service Release 2

Communities

• Interactions in Bugzilla
• Activity on the Papyrus newsgroup
• Collaboration with other projects at Eclipse (e.g., Modisco, XText and EMF Facet)
• Integration done in the TopCASED environment 5.2: [2]
• Used as basis for the Scade System Designer for providing the system view on top of SCADE: [3].
• Large diffusion in the academics community using UML2 (e.g., huge presence at the international conference MODELS 2010 in Oslo)
• Demo at the 3rd OMG - Eclipse Symposium in Washington [4]

Commiter Changes

Following committers have been welcome since 0.8.0:

• Arthur Daussy (ATOS): 08/25/2011
• Olivier Melois (ATOS): 05/18/2012

Following committers have been decommitterized:

• David Servat (CEA LIST): 05/15/2012
• Thibaut Landre (ATOS): 05/15/2012

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 Papyrus IP log in located at http://www.eclipse.org/projects/ip_log.php?projectid=modeling.mdt.papyrus

Project Plan

Plan for juno version of Papyrus (0.9.0) can be found here: [5].