Experiences with object oriented model-driven development

Model-driven development finds its origin in a reframed version of Zachman's Information Systems Architecture. This framework recognises levels of abstraction, which is not the same as levels of derail, in the systems development process. If the model-driven approach is applied in addition to object oriented analysis concepts, significant benefits are to be expected on the side of maintenance cost. Indeed, one of the main benefits of the model-driven development process is the perfect modular structure of the developed systems. This facilitates maintenance dramatically. However, in order to prove such a statement it is necessary to wail until sufficient experience is gained in the maintenance of systems developed according to this approach. M.E.R.O.DE. is an object oriented development based on two principles: model-driven development and specification by contract. The method was developed around 1988 and has been used by customers since 1991. This paper presents the result of a small scale and informal inquiry amongst the M.E.R.O.DE. users. As many systems they developed have been subject of maintenance, their experiences should allow us to asses or reject the hypothesis that model-driven development facilitates maintenance dramatically. Although the results presented here pertain to one particular method, the model-driven approach can be adopted by users of any object oriented analysis method.