Project Plan For Papyrus, version 0.10.0

Introduction

This document lays out the feature and API set for the incoming release of the Eclipse Papyrus (MDT Papyrus) Project, version 0.10.0 This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan. In addition to the detailled items listed below, the papyrus team will ensure the maintenance of its existing plug-ins.

Release Deliverables

The release deliverables have the same form as is found in most Eclipse projects, namely:
  • MDT Papyrus source code release, available as versions tagged "0.10.0" in the project's SVN repository.
  • MDT Papyrus SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
  • MDT Papyrus runtime binary distribution (downloadable and update site).
  • MDT Papyrus stand-alone binary distribution (downloadable).
  • MDT Papyrus tests (downloadable)
  • MDT Papyrus examples (downloadable)

Table of Contents

Release Milestones

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 3 day; that is, until the final 4.3 release of the Platform, upon which Papyrus and other projects will release simultaneously. As Papyrus is a dependency of numerous other projects, Papyrus will deliver its milestones within three days of the Eclipse Platform. It is anticipated that Papyrus will synchronize its milestones with the Kepler milestone schedule.
M108/22/2012
M210/03/2012
M311/14/2012
M412/19/2012
M502/06/2013
M603/20/2013
API Freeze
M705/07/2013
Feature Freeze
RC105/22/2013
RC205/29/2013
RC306/05/2013
RC406/12/2013
Kepler06/26/2013
Papyrus will produce maintenance releases to align with the Kepler SR releases, that includes the Eclipse Platform 4.3.1 and 4.3.2 releases. Papyrus may produce interim maintenance releases in addition to these in order to satisfy clients requests.
  • Friday, September 28, 2012 - Papyrus 0.10.1 maintenance release (Kepler Service Release 1)
  • Friday, February 22, 2013 - Papyrus 0.10.2 maintenance release (Kepler Service Release 2)

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The Eclipse Papyrus project depends upon on the Platform and other projects, which are mostly "pure" Java. The 4.3 release of the Eclipse Platform Project is written and compiled against version 5.0 of the Java Platform APIs, and targeted to run on version 5.0 of the Java Runtime Environment, Standard Edition. Papyrus will target the same Java version as EMF and UML2, which currently require Java 5. Eclipse Platform SDK 4.3 will be tested and validated on a number of reference platforms. MDT Papyrus will be tested and validated against a subset of those listed for the platform.

Internationalization

The Eclipse Platform is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. As a result, the Papyrus project will provide English strings in its default bundles and be localized to a subset of those locales offered by the Platform. This plan will be updated to indicate which locales will be provided and the time frame for availability.

Table of Contents

Compatibility with Previous Releases

The Papyrus 0.10.0 project will be developed in parallel, and released simultaneously, with the following projects. As stated above, each milestone release of the Papyrus 0.10.0 project will be compatible with the corresponding milestones for each of these projects, and delivered the appropriate offset.
  • Eclipse Platform SDK version 4.3
  • Eclipse Modeling Framework (EMF) version 2.9
  • Model Development Tools (MDT) UML2 version 4.1
  • Graphical Modeling Framework (GMF) version 2.5

Table of Contents

Themes and Priorities

A list of project requirements and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to indicate what major set of functionalities is to be concentrated on for each. These themes are presented below, while the requirements document and associated Bugzilla entries are left to those wanting more detailed information on each.

Editors

This theme addresses issues related the diagram editors of Papyrus. It concerns more precisely all generic features related any kind of Papyrus diagram editor. For the UML2, it concerns following diagram editors: [Class diagram], [Package diagram], [Composite structure diagram], [Component diagram], [Profile diagram], [Use case diagram], [State machine diagram], [Protocol state machine diagram], [Activity diagram], [Sequence diagram], [Communications diagram], [Interactions overview Diagram], [Timing diagram]. For the SysML, it concerns following specific diagram editors: [Activity diagram], [Block definition diagram], [Internal block diagram], [Package diagram], [Parametric diagram], [Requirements diagram], [Sequence diagram], and [State machine diagram].
  • Committed

    • [Customization] Papyrus shall enable to customize the creation policy of views [399860] (target milestone: M7)
    • [Editors] Papyrus shall enable to define both context and ownership of a view [399861] (target milestone: M7)
    • [Composite Diagram] Composite structure diagram editor shall support both UML2 notations for ports. [399862] (target milestone: M7)
    • [Composite Diagram] Composite structure diagram editor shall support the behavior port notation. [399865] (target milestone: M7)
    • [All Diagrams] The "shape" compartment should not be created asynchronously [402235] (target milestone: M7)

Extensibility

This theme addresses the need for extensiblity improvements of the MDT Papyrus implementation and APIs. It concerns more precisely all features related to following concerns: [Backbone] and [Metatooling].
  • Committed

    • [All Diagrams] Papyrus shall provide configurable modelling assistants [399871] (target milestone: M4)

Scalability

This theme addresses the need for scalability and performance improvements of the MDT Papyrus implementation and APIs.
  • Committed

    • [Tests - Performances] Papyrus shall provide a test bench for performance evaluation [399874] (target milestone: M4)

Usability

This theme addresses the need for usability improvements of the MDT Papyrus implementation and APIs. It concerns more precisely all features related to following concerns: [Palette], [Property View], [Model Explorer], [Sash Editor], and [Team Working].
  • Committed

    • [CDO] Support for CDO model repository [290952] (target milestone: M7)
    • [Hyperlinks] Papyrus shall allow the creation of hyperlinks via Drag and Drop [399852] (target milestone: M4)
    • [Search] Papyrus shall provide model-aware search capability [399856] (target milestone: M5)
    • [Hyperlinks] Papyrus shall enable to navigate between model elements shown in views [399857] (target milestone: M6)
    • [Model Explorer] The Model Explorer customizations should be persisted [399866] (target milestone: M7)
    • [Widgets] Papyrus shall implement extension filters on the “import…” UI [399869] (target milestone: M7)
    • [ModelExplorer] Papyrus shall enable navigation between typed model elements shown in views and the model explorer [399882] (target milestone: M7)

Documentation

This theme addresses the need for documentation of the MDT Papyrus implementation and APIs. It concerns more precisely all features related to following concerns: [Documentation - User], and [Documentation - Developer].
  • Committed

    • [Comments] Papyrus shall enable to reference model elements within free-text of comments. [399855] (target milestone: M6)

Miscellaneous

This theme addresses all tasks that may not be included in one of the previous theme.
  • Committed

    • [Trace] Papyrus shall enable to navigate between the model and its execution traces [399879] (target milestone: M7)

Eclipse Compatibility

this theme adresses the support and compatibility with platform 4.X and 3.X

Table of Contents

Appendix Legal Notices

  • Java is a trademark or a registered trademark of Sun Microsystems, Inc.
  • UML, SysML and OMG are trademarks or registered trademark of the Object Management Group, Inc.
  • All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"