INSTANCE MODEL BUS

Juan Carlos Castrejón - ITESM CCM

1

• Traditional Software Development

INTRODUCTION (1/5)

A. Kleppe, J. Warmer, and W. Bast, MDA Explained: The Model Driven Architecture: Practice and Promise: Addison- Wesley Professional, 2003.

2

INTRODUCTION (2/5)

• Model-Driven Software Development (MDSD)

Model-Driven Architecture (OMG)

3

INTRODUCTION (3/5)

• Eclipse Modeling Framework (EMF)

• Unify Java, XML and UML

• Its core meta-model is named Ecore

4

INTRODUCTION (4/5)

5

INTRODUCTION (5/5)

• Productivity tool for building enterprise applications

• Web applications are automatically built with a set of architecture patterns and best practices

6

PROBLEM

• Each environment provides its own:

• Model definition (UML, Ecore, DSL, etc.)

• Instance repository technology and access mechanisms (DB, XML Files, etc.)

• Model instances are tied to particular combinations of models and generation tools

• If these combinations are to be changed, the data associated to the model instances is at risk of being lost

7

INSTANCE MODEL BUS (1/2)

• General approach

8

INSTANCE MODEL BUS (2/2)

• Implementation for Java based systems

Eclipse Plugin

Spring Roo add-on

9

EXAMPLE APPLICATION (1/3)

10

EXAMPLE APPLICATION (2/3)

Application Bus

Bus Application

11

EXAMPLE APPLICATION (3/3)

Spring Roo client

Eclipse client

Spring Roo bus

12

REFERENCES

• Stahl, T., Völter, M.: Model-Driven Software Development. Wiley, New York (2006)

• Steinberg, D., Budinsky, F., Paternostro, M.: EMF: Eclipse Modeling Framework. Addison-Wesley Professional, Boston (2008)

• Spring Roo, http://www.springsource.org/roo

• Instance Model Bus, http://code.google.com/p/instance-model-bus

13