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 "MDT/Papyrus/Reviews/v0.7.0"
(→Communities) |
(→Overview) |
||
| Line 3: | Line 3: | ||
== Overview == | == Overview == | ||
| − | Papyrus is | + | Papyrus is a graphical modeler for both the Unified Modeling Language (UML2) and the System Engineering Language (SysML) OMG standards. Specially, it provides: |
| − | + | ||
| − | + | ||
* Provides graphical editors for the UML2. | * Provides graphical editors for the UML2. | ||
* Provides a support for UML profiles. | * Provides a support for UML profiles. | ||
| − | * Provides specific graphical editors for SysML. | + | * Provides specific graphical 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 == | == Features == | ||
Revision as of 10:43, 8 November 2010
This page provides the required docuware for the MDT Papyrus 0.7.0 Release Review.
Contents
Overview
Papyrus is a graphical modeler for both the Unified Modeling Language (UML2) and the System Engineering Language (SysML) OMG standards. Specially, it provides:
- Provides graphical editors for the UML2.
- Provides a support for UML profiles.
- Provides specific graphical 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 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
- This is the first release of the Papyrus component.
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 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.
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 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.
End-of-Life
Nothing has been deprecated.
Bugzilla
Bugzilla snapshot for Helios as of 28 May 2010:
Standards
MDT Papyrus 0.7.0 is mostly compliant with [UML OMG 2.2 standard | http://www.omg.org/spec/UML/2.2/].
UI Usability
MDT Papyrus is conforming to the user interface guidelines.
Schedule
MDT Papyrus plans to be a “+1” component in the simultaneous release.
M1 08/06/2010 3.7M1 M2 09/17/2010 3.7M2 M3 10/29/2010 3.7M3 M4 12/10/2010 3.7M4 M5 01/28/2011 3.7M5 M6 03/11/2011 3.7M6 (API Freeze) M7 04/29/2011 3.7M7 (Feature Freeze)
Communities
- 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
No commiter change.
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 http://www.eclipse.org/projects/ip_log.php?projectid=modeling.mdt.papyrus
Project Plan
The current project plan is available from http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/mdt/papyrus/project-info/plan_helios.xml&component=Papyrus.
Draft development plan for MDT Papyrus 0.8.0 is not yet available.