The Future of Model Driven Development RRS feed

  • General discussion

  • Hello, developers. I'd love to gauge your current feelings on where you see Model Driven Development as a viable technology? Gartner of course still sees MDD as an emerging technology, still climbing in the hype cycle. Rumors aboundt that MDD will even eventually get its own "quadrant." That being said, I've found that the target group t that is pushing back the most against the rise of MDD are developers.

    Mostly the objections seem to be that MDD platforms are regarded as too "lite" or "DIY" to be taken seriously by developers, while others fear that MDD could kill the developer role in the lifecycle altogether. At Novulo, our MDD platform, The Novulo Architect, was really designed for developers; although its user-friendly GUI can be easily discerned by business users, it has to be wielded by developers. We also avoided using executable models and instead feature a transformational model that outputs into C#. The nice thing about this approach is that, anything that you cannot model, you can write into the program as custom code.

    That being said, I'd love to get your take on where you think MDD is. Also, feel free to check out our MDD platform at www.novulo.com. we have a free, full-featured trial. It would be great to receive some comparative feedback.

    Kind Regards.
    Wednesday, September 16, 2009 8:13 PM

All replies

  • Well I think MDD though in intial stages, it do provide a high efficieny and some good time same against the Model to Code cycle. Tools like SPARX EA have some really good forward engineering techniques which provide substantial savings in terms of generation of boiler plate code. Besides MS push with OSLO and Modelling tools being supported through VS 2010 there should be greater traction in this area. Having said that MDD is not for killing programmer, the tool can generate stubs and not logic which is what the programmer is required for. Ultimately this is about abstraction and the more you are able to abstract the more efficient one is going to be. Modelling is a abstraction which should make life easy of programmer and not vice-a-versa.
    Wednesday, September 30, 2009 8:24 AM
  • We at Xomega think that Model Driven Development is actually gaining momentum. There is UML-based MDA by OMG, Microsoft's long support of DSLs and a new Oslo platform for modeling.

    One of the simplest, yet very powerful approaches we find to be is XML-based modeling with XSLT-based model transformations, which anyone can easily start using at very low cost. Xomega provides a structure for XML object modeling to make it simple and intuitive and at the same time highly flexible and extensible. We have a Visual Studio plug-in that helps you hit the ground running with XML-based object modeling. You can download an evaluation copy or learn more about Xomega at http://www.xomega.net

    Good developers should be happy when MDD tools can automate the generation of the plumbing code and let them focus on the domain structure and the business logic. MDD also makes the system designs much more clean, consistent and robust, which reduces the maintenance costs as well. Let alone improving portability from one platform to another and thus future-proofing your investment.

    The major issue with MDD developers seem to be having right now is the ability to regenerate the code from the models and keeping the models in sync with the code. Hopefully the tool vendors will be able to address this better in the future.

    Best regards,
    Xomega Team
    Monday, November 9, 2009 5:52 AM