Worth a look - A process for MDD (Model Driven Development)

A post by lispy entitled "Why UML Fails to Add Value to the Design and Development Process" reminded me of an existing methodology put together by IBM.

Lispy wrote (I cut a lot out) -
"The modeling language must be a first-class citizen of the development process rather than just make-work for architects and project managers... There are two linguistic abstraction barriers that must be implemented in order to make this work: 1) the modeling language between the models and the generated code and 2) the framework between the generated code and the target libraries. You must build up from your core code components to the framework… and you must build down from the models to the generated code. If the code generation process is too complicated, you may need better abstractions at the framework level. If the code generation process is impossible, then the modeling language may not be providing a detailed enough description of the requirements. If there is too much repetition in the models, then the modeling language will need to be extended to cover additional concepts."


What I was reminded of was "Patterns: Model-Driven Development Using IBM Rational Software Architect", by the way you don't have to use IBM's products. You can go off and the whole thing, but chapter 4 is where the meat is and Figure 4.2 on pg 47 and the related descriptions on the following pages put it all in place. It really lays out a process which in my mind covers some of Lispy's concerns.

A short post just to share an interesting modeling process I learned about sometime ago.

Comments

Popular posts from this blog

Configuring Javascript SyntaxHighligher 3+ in a Blogger site

Reference Cards, Cheat Sheets, Posters, whatever they are called.

The Technology Architect Organization Quiz - 7 questions to ask before taking the job