Table of Contents

• Introduction
• Release Deliverables
• Release Milestones
• Target Environments
• Compatibility with Previous Releases
• Themes and Priorities

This is the project plan for Tigerstripe 1.0.0

While our goal is to be ready graduate out of incubation by the end of the plan, we acknowledge that we have quite a bit of work ahead of us, so the detailed content of some of the future release may be adjusted and certainly very much influenced by community requirements.

At the time of writing of this plan, version 0.4 has just been released and includes a significant refactoring of the framework to enable more customization of Tigerstripe as a Model-Driven-Engineering environment for the Telecommunication Industry.

We are going to continue working towards graduation throughout the years and will focus on removing all the remaining legacy code and continue building our user and adopter communities.

Our key drivers for this year are:

• Making Tigerstripe a robust, scalable environment for Model-Driven-Engineering with special focus on the Telecommunication Industry.
• Provide a customizable modeling end-user framework, as we acknowledge that multiple domains within the Telecom Industry have different modeling requirements.
• Leverage all existing Eclipse project where applicable (Modeling, buckminster, etc.) and remove redundant legacy code.
• Build our communities of Users and Adopters
• Aim for project graduation

The release deliverables will be split across an intermediary 0.x release (0.5 'Bora') which will will be the last build of Tigerstripe with its legacy core.
Starting with the 1.0 stream, the legacy core will be completely removed and we will be relying solely on EMF objects

In order to accomplish this transition, we have already started building a and EMF-based version of the Tigerstripe model elements, which will be available in the late maintenance releases of 0.4 'Alize'.

For 0.5 'Bora' we will focus on end-user customizations for the modeling environment and address some of the long standing bugs in Bugzilla

As of 1.0, Tigerstripe will provide a complete MDE framework, that can be customized into specific domains with Telecom Industry and possibly others.

Our aim is to first to address some known issues in 0.4 with a few quick maintenance release.
The first couple of milestone builds for 0.5 will focus on stabilization and bug fixes, in order to set up a clean slate for the final EMF transition.
The 0.5 release will deliver a user-configurable (as opposed to 0.4 which is driven by ext. points and programming only) modeling environment.
1.0 will mainly focus on replacing the legacy core with an EMF based core, and address bugs. No major feature enhancement is currently planned.

Versions 0.4.x and 0.5 will be based on Eclipse 3.4.x.

Version 1.0 will target Eclipe 3.5

Java5 to remain the minimum requirement for Tigerstripe

Compatibility at the model level will be fully supported from 0.4 to 1.0 (and going forward).

Existing Tigerstripe generators will require changes to accomodate migration to EMF. Migration tutorial will be provided

APIs will remain stable between 0.4 and 0.5. However, due to EMF migration the legacy core APIs will change with 1.0. Tutorial for existing code migration will be provided

This year will be focused on maturation and graduation for Tigerstripe. So, while we will be putting efforts in the code base, we will also actively work on developing our user community

The TeleManagement Forum has adopted Tigerstripe to build next generation Telecommunication standards.

We will work with TMF member companies to strengthen the position of Tigerstripe and develop its use across the industry

We will promote Tigerstripe through online and face-2-face events as often as possible.

Tigerstripe is intended to enable Model-Driven Engineering based on large models for mission critical production systems. We focus on 2 key aspects:

• Extensibility: allowing users and adopters to customize the modeling environment to meet their specific needs. This is accomplish through a series of documented extensions points allowing to decorate models, work with different meta-models, etc.
• Scalability: with built-in features to ensure that large models can be handled across geographically distributed teams, with a high level of granularity.

As part of this effort, we are working towards making Tigerstripe seamlessly integrated with other existing Modeling projects.

Tigerstripe aims at providing both an Eclipse Framework for adopters to build upon, but also a end-user workbench that doesn't require any programming and yet allows organization to adopt MDE quickly.

For every release we provide 3 features that can installed/downloaded separatly:

• Tigerstripe Annotation Framework: a framework to annotate any resource or java element in the Eclipse workspace. Definitions for the content of the annotations is done through EMF's Ecore. This framework is independent of the rest of Tigerstripe code, yet the Tigerstripe we provide a direct integration allowing to annotation Tigerstripe model elements.
• Tigerstripe Core Framework: offering all the model access/edit, generation and auditing capabilities found in the Tigerstripe workbench, without the UI
• Tigerstripe Workbench: the end-user MDE environment, including model editing, Class diagrams, Instance diagrams, Facets, generation, etc.