Model Driven Development
Description
mix between 2 technologies:
- apache ant,
- freemarker
Mix very well:
- declarative
- versionnable
There are many detractors of MDD approach because a lot of projects have failed because of using code generation. But there are also a lot of projects that failed because of an artisanal approach that have more and more side effects while it grows.
unbilievable apps
This page is not a article to speak about pro or cons MDD. see: Todo. It is a pragmatic solution I developped for my needs, nothing more, nothing less.
There are also a lot of other solutions, like :
-
…
-
complexity increase
-
unmaintanable
-
repetitive development
-
human errors
-
faster
-
explicit (vs complex implicit models)
-
increase quality
-
error tolerant
-
homogen
-
Manual changes must NOT be applied to generated code
-
Manual changes must be applied to specific code, even if it can be generated once at the first time
-
Conception and separation between generic (and generated) code and specific (manual) code is important
-
technical vs business layer
-
http://en.m.wikipedia.org/wiki/Model-driven_software_development
-
http://martinfowler.com/bliki/ModelDrivenSoftwareDevelopment.html
-
fr : http://fr.m.wikipedia.org/wiki/Ing%C3%A9nierie_dirig%C3%A9e_par_les_mod%C3%A8les
Pro
Cons
See also
- http://www.google.fr/search?q=advantages+of+model+driven+development&revid=1524550206&sa=X&ei=fjTiU-DZAdTZ0QXpzIGgBg&ved=0CEgQ1QIoAA
- http://www.google.fr/search?q=agile+model+driven+development&revid=1524550206&sa=X&ei=fjTiU-DZAdTZ0QXpzIGgBg&ved=0CEkQ1QIoAQ
- http://www.google.fr/search?q=the+pragmatics+of+model+driven+development&revid=1524550206&sa=X&ei=fjTiU-DZAdTZ0QXpzIGgBg&ved=0CEoQ1QIoAg