Skip to main content

Project Plan For EATOP [archived], version 0.5.0

Introduction

EATOP is an open source project under the Eclipse Modeling project to provide an infrastructure platform implementation of common base functionality for design tools that enable an effective usage of the architecture description language EAST-ADL in software and systems development.

This document lays out the feature and API set for the EATOP release 0.5.0. Comments on this plan can be can be posted on the forum or sent to the mailing list .

Release Deliverables

This release will be delivered via a p2 repository including SDK (runtime, sources and documentation), non-SDK (runtime only), examples and test utilities.

Table of Contents

Release Milestones

EATOP milestones follow the Eclipse release milestones by an offset of +3 as set by the Kepler release schedule. This table lists all completed milestones and planned releases:

M1mm/dd/2014
M2mm/dd/2014
RC1mm/dd/2014
RC2mm/dd/2014
0.5.0 Finalmm/dd/yyyy

Table of Contents

Target Environments

The EATOP 0.5 targets a defined set of other Eclipse components (e.g. platform, EMF, etc.) originating from the following release trains:

  • Kepler (Eclipse 4.3)
  • Luna (Eclipse 4.4)

EATOP builds and testing will always be based on latest available milestone build or service release of Eclipse (e.g. Eclipse 4.4M3, 4.4.1).

EATOP will work with Java 6 or higher.

Internationalization

The EATOP plug-ins are prepared for internalization using the usual Eclipse plugin.properties mechanism. Default language is English. Currently no other translations exist.

Table of Contents

Themes and Priorities

A list of project goals 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 expected to be the focus of each. These themes are presented below, while the goals of the associated Bugzilla entries are available for more detailed information.

Reusability, Interoperability and Performance

Initially driven by automotive functionality as such is generic and the EATOP is meant to enable the reuse of this infrastructure for model-driven tool environments in others domains like aerospace, finance, etc.

Table of Contents

Back to the top