After Ivar Jacobson it is now Grady Booch who gives his opinion on the UML as part of this interview .
Let me just highlight the best modeling-related comments in the interview for those that prefer not to read it full (comments mine):

• When we began with the UML, we never intended it to become a programming language . I agree, modeling makes sense when the abstraction level is higher than that of programming languages. However, I'd say that most people do not use UML as a programming language (except,maybe, for those following the ExecutableUML approach). I think it is just the opposite, UML is used more as a sketch .
• I think that there's a fairly narrow domain for which model-driven development makes sense : I disagree, I think the combination of UML and/or DSLs (depending on the domain) allows model-driven to be beneficial in many domains
• we should return to the roots of the UML : assuming that he means that UML has become too complex, I think we all agree with this and, fortunately, even the OMG has realized about it
• one should only use a graphical notation for those things that cannot easily be reasoned about in code... most important artifact any development team produces is raw, running, naked code. Everything else is secondary : again, here Grady seems to completely disregard the whole field of model-driven development. I wonder why. True, we don't have many empirical studies proving the benefits of model-driven development (I'm collecting those I've found so far for a future post) but I don't think going back to code-centric development process is the solution (but, of course, I'm not Grady Booch so I don't expect you to believe me :-D )

If you enjoyed this post you can subscribe to this Software Modeling blog and/or follow me on twitter or through the portal's mailing list . And if you really liked it help me pass it on to others by bookmarking and sharing the post using the links below: