In this article, the author tries to answer some of the questions that typically revolve around Model Driven Development, like, why MDD and it’s advantages.
In short, it’s all about quality, productivity and alignment. The 15 reasons, in summary are:
- Its faster
- Increased Quality
- Less Error-Prone
- Meaningful Validation
- Results in software being less sensitive to changes in personnel
- Empowers domain experts
- Lets advanced programmers focus on the hard stuff
- Bridges the gap between business and IT
- Results in software being less sensitive to changes in business requirements
- Results in software being less sensitive to changes in technology
- Really enforces architecture
- Captures domain knowledge
- Provides up-to-date documentation
- Enables to focus on business problems instead of technology
In my view, for an organization, (esp. IT service organizations) who are used to selling programming hours, their business will be affected by using MDD!! What do you think? Could this be the holy-grail of enterprise software development?
Leave your comments.
Read the entire article here.