« SOA Ontology | Home | DSL and MDE, necessar… »

8 Reasons Why Model-Driven Approaches (will) Fail

29 July 2008

If you want to build model-driven software you'll need to devise a methodology based on ideas and experiences from others. I've written an article for InfoQ sharing 8 gotchas of Model Driven Engineering (MDE). I hope it will start discussions and information sharing about MDE!

I've stated the following 8 reasons why model-driven approaches can (or will) fail. Or formulated in a positive way: 8 points to pay attention to when developing an MDE methodology:

  • Not targeting all goals of Model-Driven Engineering
  • Only using one modeling dimension: the dichotomy between PIM and PSM
  • Focusing on generating new artifacts
  • Using general purpose languages
  • Using custom defined domain specific languages
  • Using model transformations which are not fully executable
  • Not testing the model
  • Insufficient tooling
I'm happy to receive your comments and I hope to learn from others (you?) sharing their experiences!

Did you like this post?
Subscribe to the article RSS feed or get articles by email and follow @JohanDenHaan on Twitter!

Read more about: , , ,


Share on LinkedIn Share on Facebook Post to del.icio.us Post to Google Buzz

Be the first to comment!

Be nice. Keep it clean. Stay on topic. No spam.

  
Remember personal info?

Emoticons / Textile

To prevent automated commentspam we require you to answer this silly question
 

  (Register your username / Log in)

Notify:
Hide email:

Small print: All html tags except <b> and <i> will be removed from your comment. You can make links by just typing the url or mail-address.

Powered by Pivot - 1.40.4: 'Dreadwind'