Skip to main content

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.

Jump to: navigation, search

MDT/OCL/Reviews/Helios

< MDT‎ | OCL

This page provides the required docuware for the MDT OCL 3.0.0 Release Review, as part of the upcoming Helios Simultaneous Release.

Overview

OCL is an implementation of the Object Constraint Language (OCL) OMG standard for EMF-based models.

The OCL component provides the following capabilities to support OCL integration:

  • Defines APIs for parsing and evaluating OCL constraints and queries on EMF models.
  • Defines an Ecore implementation of the OCL abstract syntax model, including support for serialization of parsed OCL expressions.
  • Provides a Visitor API for analyzing/transforming the AST model of OCL expressions.
  • Provides an extensibility API for clients to customize the parsing and evaluation environments used by the parser.

Features

New in this release

  • Elimination of many deviations from the OMG standard.
  • Internal improvements and upgrade to the newest LPG parser version.
  • OCL annotations are supported in Ecore models
  • OCL Editor support in examples.

See http://wiki.eclipse.org/MDT/OCL/New_and_Noteworthy/Helios.

Accordance with project plan themes and priorities

  • Compliance - 5 committed, 4 deferred
  • Release Currency - 6 committed, 0 deferred
  • Usability - 3 committed, 1 deferred

See http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/mdt/ocl/project-info/plan_helios.xml&component=OCL.

Non-Code Aspects

APIs

This release has made breaking changes to the API. See http://wiki.eclipse.org/MDT/OCL/New_and_Noteworthy/Helios, http://wiki.eclipse.org/MDT/OCL/MDT-OCL_3.0.0_Migration_Guide.

  • 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

  • Upgrade to the newest version of the LPG parser.
  • OCL model-based library approach is in progress.
  • Extensibility features in Helios are inherited from Galileo.

Tool Usability

  • OCL is used for model validation as a constraint definition language as well as in downstream projects like QVTO were it is used for model navigation and extended for model updates.
  • OCL-based annotations in Ecore models increase applications of OCL.
  • OCL editors increase the usability of OCL.

End-of-Life

The legacy MDT OCL 1.1.x (org.eclipse.emf.ocl) deprecated for 3 years is no longer supported. A few API have been deprecated. See migration guide: http://wiki.eclipse.org/MDT/OCL/MDT-OCL_3.0.0_Migration_Guide.

Bugzilla

Bugzilla snapshot for Helios as of 28 May 2010:

Bugzilla snapshot Helios.png

Standards

MDT OCL 3.0 is mostly compliant with [OCL OMG 2.2 standard | http://www.omg.org/technology/documents/modeling_spec_catalog.htm#OCL].

UI Usability

MDT OCL is conforming to the user interface guidelines.

Schedule

MDT OCL is a “+1” component in the simultaneous release.

M1	08/17/2009	
M2	09/28/2009	
M3	11/09/2009	
M4	12/14/2009	
M5	02/01/2010	
M6	03/15/2010	API freeze
M7	05/03/2010	Feature Freeze
RC1	05/17/2010	
RC2	05/24/2010	
RC3	05/31/2010	
RC4	06/07/2010	
RC5	06/14/2010	
Helios	06/23/2010	

Communities

  • Interaction in Bugzilla
  • Activity on the OCL newsgroup: roughly 450 messages from June 2009 to May 2010
  • Collaboration with other projects at Eclipse

Commiter Changes

No commiter change.

IP Issues

The MDT OCL 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.ocl

Project Plan

The current project plan is available from http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/mdt/ocl/project-info/plan_helios.xml&component=OCL.

Draft development plan for MDT OCL 4.0.0 is not yet available.

Back to the top