Storify by Adrian Kuhn

3 Reasons on why UML is the worst thing that ever happened to MDE.

William Cook @w7cook
UML is the worst thing to ever happen to MDD. Fortunately many people now realize this ... should I list the reasons?
Wed, Jun 20 2012 12:31:52
Reply Retweet Favorite
William Cook @w7cook
UML was created to model OO designs. It effect you are modeling the code of a system, not the system's behavior. UML is at wrong level.
Wed, Jun 20 2012 13:00:19
Reply Retweet Favorite
William Cook @w7cook
2) the idea that 7 (or 13) diagram formats in UML can cover everything is crazy. What about GUIs, web wireframes, authorization, etc. ???
Wed, Jun 20 2012 13:47:48
Reply Retweet Favorite
William Cook @w7cook
3) UML has encouraged the idea that models must be graphical. Ridiculous! Text and graphic models are both useful and often interchangeable
Wed, Jun 20 2012 14:15:22
Reply Retweet Favorite
Since I’ve created this story, William added two more reasons …
William Cook @w7cook
4) UML is at once too large and complex and at the same time very limiited. Stereotype and profiles are not effective for usable extensions.
Wed, Jun 20 2012 15:05:29
Reply Retweet Favorite
William Cook @w7cook
5) The PIM/PSM distinction is misguided. The purpose of high-level models is not platform independence. It is about "what" versus "how".
Wed, Jun 20 2012 15:53:08
Reply Retweet Favorite
And this discussion between William and Rafael sparked off …
Rafael Chaves @abstratt
@w7cook all that being said, I'd be happy to use something better, don't know of any alternatives abstratt.com/blog/2010/02/0…
Wed, Jun 20 2012 15:03:17
Reply Retweet Favorite
William Cook @w7cook
@abstratt It must be a meta-environment for creating, integrating and extending modeling languages. We are trying: enso-lang.org
Wed, Jun 20 2012 15:33:54
Reply Retweet Favorite
Rafael Chaves @abstratt
@w7cook "Behavioral semantics defined using model interpreters written in Ruby" << is Ensō's "spec" tied to Ruby? Or is that an impl detail
Wed, Jun 20 2012 15:41:54
Reply Retweet Favorite
William Cook @w7cook
@abstratt It's an implementation detail. But having a real reference implementation is a good thing. There is very little dependence on Ruby
Wed, Jun 20 2012 15:48:55
Reply Retweet Favorite

Did you find this story interesting? like or comment as 2 already did!

Liked!

#Ricardoand that is why we have eXtreeme Programming, and all of the RAD methodologies2012-06-23T03:04:16.154Z
dmdevito1) UML is about too much graphical notations, and too little precise and/or valuable meaning (for code generation), but IMHO the strongest argument is the...1) UML is about too much graphical notations, and too little precise and/or valuable meaning (for code generation), but IMHO the strongest argument is the following: 2) while the UML platform has quite very slowly evolved, the targeted platforms (for code generation) have much more progressed (so the gap is narrowing, and UML is not the winner). You can put a "Web Service" stereotype on a class in a UML diagram (using any of the annoying and cumbersome UML editors out there), but you can also put a @WebService annotation on a Java class (using any pleasant Java editor out there, with code completion), and put it running. That's quite a difference! In some sense, UML was expected to supersede the code generation's targeted platforms, but these platforms have replaced themselves "executable UML", and quite UML too.more2012-06-22T11:36:18.123Z