model driven development -...

Real-Time Computing and Communications Lab., Hanyang Universityhttp://rtcc.hanyang.ac.kr

Real-Time Computing and Communications Lab., Hanyang Universityhttp://rtcc.hanyang.ac.kr

Model Driven Development

Minsoo Ryu

Hanyang University

[email protected]

2Real-Time Computing and Communications Lab., Hanyang University

http://rtcc.hanyang.ac.kr 2Real-Time Computing and Communications Lab., Hanyang Universityhttp://rtcc.hanyang.ac.kr

Contents

MDA ConceptsModel TransformationMetamodel and MOF



Model-Driven Engineering

Model-driven engineering (MDE) is the systematic use of models as primary engineering artifacts throughout the engineering lifecycle MDE can be applied to software, system, and data

engineering Models are considered as first class entities

The best known MDE initiative is the Object Management Group (OMG) called Model-Driven Architecture (MDA), which is a registered trademark of OMG Another related acronym is Model-Driven Development

(MDD) which is also an OMG trademark



OMG Model-Driven Architecture

The Model Driven Architecture (MDA) is a framework for software development defined by the Object Management Group (OMG) Key to MDA is the importance of models in the software

development process Within MDA the software development process is driven by

the activity of modeling your software system



Traditional Approach vs. MDA

Traditional Approach MDA Approach



Platform

A platform is a set of subsystems and technologies that provide a coherent set of functionality through interfaces and specified usage patterns, which any application supported by that platform can use without concern for the details of how the functionality provided by the platform is implemented

Examples include language, OS, and middleware platforms Language: Java, C, C++ OS: Linux, Windows, Solaris Middleware: CORBA, Java 2 Enterprise Edition (J2EE),

Microsoft .NET



Platform Independent Model (PIM)

PIM The first model that MDA defines is a model with a high level

of abstraction that is independent of any implementation technology

A PIM describes a software system that supports some business Within a PIM, the system is modeled from the viewpoint of

how it best supports the business Whether a system will be implemented on a mainframe with a

relational database or on an EJB application server plays no role in a PIM



Platform Specific Model (PSM)

PSM Is used to specify the system in terms of the implementation

constructs that are available in one specific implementation technology

For example, an EJB PSM is a model of the system in terms of EJB structures

• It typically contains EJB-specific terms like "home interface," "entity bean," "session bean," and so on

A relational database PSM includes terms like "table," "column," "foreign key," and so on

A PIM is transformed into one or more PSMs For each specific technology platform a separate PSM is

generated Most of the systems today span several technologies, therefore

it is common to have many PSMs with one PIM



Contents




Model Transformation

Generic transformations Implement best practices,

architectural and design patterns, technology patterns, optimizations, etc.

Additional information Adjust the transformation globally Similar to compiler options

Model markup Direct the transformation of

particular model elements Not part of the PIM Different platform mappings may

require different markup Similar to compiler pragmas



Model Transformation

The basic pattern of model transformation can be applied multiple times

PIMs and PSMs are relative notions “Someone’s PIM can be someone else’s PSM”

Platform independence is relative, too It’s a scoping issue It’s a strategic decision



Automatic Model Transformation

Traditionally, the transformations from model to model, or from model to code, are done mainly by hand

Now, many tools can generate some code from a model, but that usually goes no further than the generation of some template code, where most of the work still has to be filled in by hand

The eventual goal of MDA is to generate complete code from a model via model compilers



MDA Benefits

Raising the level of abstraction Raising the level of reuse Design-time interoperabilityModels as reusable assets



Consequent Benefits

Productivity Developers can focus on the development of PIMs They can work independently of details and specifics of the

target platforms These technical details will be automatically added by the

PIM to PSM transformation Portability

The same PIM can be automatically transformed into multiple PSMs for different platforms

Maintenance and documentation The PIM fulfills the function of high-level documentation that

is needed for any software system 100% traceability from specification to implementation



Contents




OMG Standards for MDA

Modeling: UMLMetamodeling: MOF Action semantics: UMLModel interchange: XMI Diagram interchange: UML



Metamodel

Metamodel Model of a modeling language Definition of syntax and semantics

MOF provides a set of concepts to define metamodels; in particular Class diagrams to define abstract syntax and OCL to define semantics of a modeling language

Example: UML metamodel Semantics is defined using a mixture of OCL and informal

text



Four-Layer Metamodel Hierarchy



Overview of MOF 1.4 Metamodel



Model Transformation and MOF



Discussions on MOF

Benefits Standard way to define modeling languages “MOF is not just for OO”

• i.e., can be used to define non-OO modeling languages Caveats

No means to declare concrete syntax and editing behavior• Abstract syntax: • Concrete syntax:

Scoped not just for creating modeling languages, but also for metadata management Eclipse provides a simple, proprietary metamodeling

framework – Eclipse Modeling Framework (EMF); the centerpiece of EMF is Ecore, which corresponds to MOF

model driven development -...

Documents