Model-driven software development (English Model Driven development, MDD) is a procedural model for the development of software.

see also Model Driven Architecture (MDA)

Definition

Model Driven development makes possible to describe software systems constantly by models. One differentiates thereby between:

1. technical models (PIM)

2. technical models (PSM)

The models form an abstraction hierarchy developing one on the other. The Abstaktionsniveau is lowest in the programming language level and rises then over the technical and technical model. A further abstraction level is the Business Process Modeling (see also BPMN, BPEL).

The model serves as starting point for the software development process. If changes arise, first the model is changed. Technical model and code are kept by automatic transformations synchronous to the changed model. Information concerning application or the system environment is maintained in the model instead of in the code.

Since models are understandable also for non--developers, as for example specialized divisions, all Stakeholder can be taken part in the development process.

Advantages of MDD

The technical models of MDD (PIM) are platform independent by definition. Models can be used on different technology. From the independent model in the follow-up a platform-specific model (PSM) is generated.

MDD increases the development speed. By suitable tools an automatic transformation from PIM to PSM and PSM takes place to code. Thus the manual modelling and coding of artifacts stereotypedly which can be produced are substantially reduced as for example model elements or code fragments, avoided ideally completely.

By the higher degree of abstraction from models the expenditure for changes of system becomes and - maintenance in models reduces.

Models can become simply administered and secured. Conceivable is even the introduction of model libraries, which make re-use possible on level of the technical modelling.

Tools for MDD

One differentiates:

1. pure modelling tools: These serve only for the diagram and support no automatic transformations. The model is exported here into an exchange format (XMI) and further processed with separate transformers.

2. pure transformers: These serve excluding the transformation of models and contain no graphic modelling functionalities. Models are imported, transformed in an exchange format like XMI into an internal model format and exported to it again.

. MDD of tools integrated 3: These offer modelling, model transformations and generation of code in a tool. Redundant export and import procedures, compatibility problems with data exchange and preparation expenditure concerning integration are avoided. The navigation barness and synchronisation between technical and technical model and implementation code are optimally supported.

Examples of integrated MDD tools

• ObjectiF (microTOOL)
• Together Architect (boron country)
• Rationally Application Developer (IBM)

Articles in category "Model-driven software development"

We found here 2 articles.

Related Websites

We found here 5 related websites.

• Abstract
  In the approach we call Model-Driven Software Development (MDSD) we combine ... Model-Driven Software Development. need to be built, and only in some cases ...


• Best Practices for Model-Driven Software Development
  The workshop focuses on generative techniques that can be used to realize Model Driven Architecture (MDA)


• Best Practices for Model-Driven Software Development
  The workshop focuses on generative techniques that can be used to realize Model Driven Architecture (MDA)


• Model-Driven Software Development
  Model-Driven Software Development. ... Core Values. Values for the Development of Model-Driven Software. History of Model-Driven Software Development ...


• voelter.de - Services :: Model-Driven Software Development Tutorial
  home · mail · back · search · impressum · go back · go up Services :: Model-Driven Software Development Tutorial. dotted Line. dotted Line ...