MDD/MDA and the role of the Development Process

MDD tends often to underestimate the impact of the software factory: in details, the role of the process. The organization of work and the hierarchy changes, it is not the usual software engineering process with Analysis-design-code-test, but a rather different approach where test happens in either a PIM environment, where the design happens is an parallel task out of the streamlined production process.

Under-estiamating the role of the process can reduce the advantage of MDD/MDA.

The development process when working with in MDD/MDA has been devided between different groups, testing and technology mapping have to be considered.

MDD can push the development process at a speed where the planning is postponed and will create obstacle and difficoulties in further phases of the project like it happended with 4GL. Planning as well as an accurate requirement capture and a proper analisys modeling greatlny contribute to the success of and MDD based development process.

Embracing the usual software engineeting process when applying MDD is overlookin the problem and increases the risk of the project.