Category: Model Driven Engineering

MDA/MDD: Model is not code!?

Following my post on round-tripping, a discussion raised again on “what is model?” on Think in models. Here I try to focus on why “model is not code” in an MDA/MDD context. First of all, let’s define the investigation field: MDA/MDD: using models to generate (parts of) code with generators Model (in this context): a formal

MDA/MDD: don’t round-trip!

In MDE life-cycle, round-trip engineering means ability to update a model based on source code reverse modeling. Funny practice: as the source code is issued from this model during the generation step, it’s a kind of “shoe is on the other foot”! More precisely, round-tripping is a way to work indifferently on model or source

Should MDA be the Holly Grail of Agile Manifesto?

OK, I’m in a teasing mood… But let’s take the four Agile Manifesto values and have a look on MDA(*)  through these values. Individuals and interactions over processes and tools The fact is that tools have a huge importance in MDA. Individuals, even interacting well, will not succeed if MDA tools don’t work (modeler and model-to-code

Path from ADM to MDA

The Architecture Driven Modernization (ADM)(*) approach to migration projects follows a three steps workflow: Full source code reverse modeling, Model transformation from source architectural  model to target architectural model, Target code generation combining target architectural model generation and algorithmic source code conversion to target programming language. The Model-Driven Architecture (MDA) approach to application development projects

1 2