Before I want to explain about the model driven development strategy I want to go through the definition that I have learnt about it. And here it goes:
A system development strategy that emphasizes the drawing of the system models to help visualize and analyze problems, define business requirements and design the information systems.
I hope you got the definition. What I know about it is that based on the system modeling this strategy is oldest and still in practice to design the information system. So here comes the new thing what is system model? One has to know that it is the visualization for the final system which represents the reality. Not only this, the final system developed can provide the proper and also the improved communication between the users, analysts, designers and builders. This is not different from the basic phases. One more thing about it is that the after the system is implemented the models can be served as documentation for any changes that may be required during the support stage and operation.
why model driven strategy? why to use it? the answer is that the specifications all seems to more detailed and more informative. The requirements for the business and the designs for the systems can be easily expressed in pictures rather than the words. Moreover, being the model driven approaches it becomes easier to identify the problems and for the solution there can be alternative. System designs becomes more and stable and flexible as due to their pre analysis before the build process. So it happens to be stable system if the clear model is given in the first time.
Having these advantages it is more time consuming as the time is wasted to draw the clear view of the models. This happens when the user are really confused with their systems. Before the design the requirements must be clearly provided and such designs must be well documented with the technical stuffs which may be a hard work sometimes.