Recording Venue: Code Generation 2008
Guest(s): Bran Selic
Host(s): Laurence
In this episode we’re talking to Bran Selic of Malina Software about modelling in general and UML2 in particular. Bran covers the basics of modelling, the history of UML, and what’s new in UML2.
SE Radio 117: Bran Selic on UML
Join the discussion
You must be logged in to post a comment.
6 comments
More from this show
Matthew Skelton joins host Giovanni Asproni to talk about team topologies—an approach to organizing teams for fast flow of value. The...
Vinay Tripathi, a senior network engineer in Google Backbone Engineering and an 18-year network engineering veteran, discusses BGP...
Tim McNamara, a well-known Rust educator, author of Rust in Action (Manning), and a recipient of a Rust Foundation Fellowship in 2023...
I did not clearly understand the title of the book on foundations of meta-modelling (from the 1980s) Bran was referring to. Bran also mentions the book’s author, but searching for Doug Hofstetter on the Internet did not yield anything. Does anyone know the title of this book?
Cheers,
Frank
Dear Frank,
I believe the book Bran is referring to is “Gödel, Escher, Bach: an Eternal Golden Braid” by Doug Hofstadter. This isn’t a meta-modelling book per se – but it outlines the underlying philosophical principles.
Laurie
For me the use of UML class diagrams to specify languages is a bit strange idea. After having realized the need for domain-specific languages you apply a general purpose language to design them. I would argue that a much better choice would be using a language that actually supports language design and specification work. For instance, distinguish different languages, their composition and integration, naming rules, uniqueness etc. Now MOF (and class diagrams) don’t even have a concept of “language”.
Bran mentions the need for books on how to design domain-specific modeling languages, covering both theory and experience side. One option is Domain-Specific Modeling, Wiley, 2008 (http://www.dsmbook.com)
As an aeronautical engineer who now writes code for a living I do wish people working in the software field would stop trying to equate blueprints and UML. They are not functionally equivalent. Blueprints are executables. They are run ‘on’, or by, skilled tradesmen who operate machine tools that process the raw materials into a finished product.
Chris
I believe that using MDA, xUML (Executable UML – UML Profile to be standardized) or DSLs created using MOF people are trying to get to the state when a model will be executable as you described using some tools.
However in literature i found that “UML as a a blueprint” is more about having a good plan for the system to be developed. So maybe it will describe such an use of UML as a plan, at least in my opinion.
Great interview!