Benefits of Model Driven Software Development
In the previous post we outlined how we think that Model Driven Software Development (MDD) helps to bridge the gap between rapid application development and quality analysis and design. Below are some more detailed examples of the benefits of MDD.
- You can deliver visible, functional and useful solutions, faster and to a higher standard than the alternate custom-coded route. You’ll write a lot less code and have more functionality to show for it because you’re leveraging existing capabilities rather than building them from the ground up;
- You can get the best value from your analyst(s) and subject matter expert(s); they can directly participate in the design and development of the solution, providing validation and even testing through each iteration;
- You will have less code to support and maintain; generated code has been previously tested and so your technology footprint for support will largely be on the new custom code;
- You can protect your investment in IT by capturing and partitioning the knowledge (of the data, rules and processes) from the technology. In future releases you can extend your functionality or even change the technology of solution components, without requiring the same expertise as a fully custom solution would.
If you’re not persuaded and consider that every Project requires a unique solution, delivered by “guru” developers who need to work 18 hours a day to produce the world’s smartest code… then let’s agree to disagree. In the next post we will cover when we think MDD is appropriate.