By Dean ~ December 10th, 2008. Filed under: Best Practices, Modeling.
I am intrigued by this article (PDF)from Markus Völter on a number of levels. First, it’s eminently approachable. He writes clearly and concisely, a trait not shared by many of our compatriots. Second, he makes strong pragmatic points about solving real world problems. Third, I’m totally in love with the way that he has surveyed his colleagues to come up with a rating for each of his recommendations. Fourth, although Domain Specific Languages are his stated topic, many of his points are dead on with regards to some of our general purpose modeling language “discussions.” The material is especially relevant to those of us in tool development roles. Finally, he points out that “the emperor has no clothes” when it comes to some of the names that we’ve chosen to use for our little corner of the technology world:
“Some notes on terminology. I use MD* as a common moniker for MDD, MDSD, MDE, MDA, MIC, and all the other abbreviations for basically the same approach. Models can be processed in many ways.”
If I wanted to pile on, I could add MBSE and MDSE…
If you have any interest in the subject of MD*, and specifically modeling languages, I strongly encourage you to take a look at this article. While I don’t agree with everything he says, and I recognize that we’re not necessarily concerned about exactly the same issues, I found his presentation, with a bit of extrapolation, both useful and thought provoking.
Nicely done Markus! If you’re ever in the Silicon Valley, look me up and I’ll buy you a beer.