MDT/Papyrus/Reviews/v0.8.0

This page provides the required docuware for the MDT Papyrus 0.8.0 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 second release

• Xtext has been integrated within Papyrus to embed textual editors inside the tool and edit partially UML models, such as properties or Ports.
• A generic tabular editor has been introduced inside Papyrus. This generic tabular editor can custumized to specific needs, as examplified in the SysML version of Papyrus for allocation and deployment modeling.
• For UML2, Papyrus provides two new diagram editors respectively for component and deployment.
• Stability nd usability of Papyrus has been improved.
• The frameworks for custumizing the palette and the property view have refactorized in order to be EMF-based. The property view framework of Papyrus is now based on the
• For SysML, Papyrus has improved its editors for IBD, and BDD and added two tabular editors for requirements and allocations modeling.

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.8.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/index.php/papyrus]

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 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.

End-of-Life

Nothing has been deprecated.

Bugzilla

Bugzilla tasks resolved for this second release: [2]

Standards

MDT Papyrus 0.8.0 is compliant with both following OMG standards:

• [UML 2.2 standard | http://www.omg.org/spec/UML/2.2/]
• [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/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)
RC1 05/18/2011 0.8.0RC1
RC2 05/25/2011 0.8.0RC2
RC3 06/01/2011 0.8.0RC3
RC4 06/08/2011 0.8.0RC4
Release 06/22/2011 0.8.0

Communities

• Interactions in Bugzilla
• Activity on the Papyrus newsgroup
• Collaboration with other projects at Eclipse (e.g., Modisco, XText and EMF Facet)
• Planned integration in the TopCASED environment in Q3 2011: [3]
• Used as basis for the Scade System Designer for providing the system view on top of SCADE: [4].
• 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:

• Arnaud CUCCURU(CEA)

Following committers have been decommitterized:

• Tatiana Fesenko

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 next release will be decided this summer.