Author of “UML2 for Dummies“, Michael Jesse Chonoles talks about the history and memories of UML and also shares some essential aspects of Modeling.
Kenji (CTO of Astah): Hi Michael. How are you?
How UML was made?
Michael: Yeah, it’s a long story, I’ve been involved from the very beginning. In fact, I was the person who seconded the motion to approve UML 1.1 which is really the first UML. I was working for General Electric at that time and General Electric was using the modeling technique called “Object Modeling Technique – OMT” – sometimes called the “Rumbaugh Tequnique”. And I had used it and we started an organization within General Electric to teach OMT to the rest of the world. So I went to banks and all the companies besides the General Electric to teach it.
Then what happened was, OMT and the “Booch method” and “Jacobson’s Method” which is something objectory which with UseCases they started to work together to unify to bring their methods into compliance with each other. So as soon as they started to talk about that, I who was the leader of OMT inside of General Electric at the time said “Well, we need to have a standardization of this.” and Jacobson went to OMG and said “Can we make a proposal to standardize an unified method?” and OMG eventually said “Well, unified method is too aggressive, so how about a unified notation?“
So they changed their unified method to unified notation.
Kenji: So “a unified notation” does not include the “method” part?
Michael: I am good at finding little things that need to be fixed. And in the process, in between, I got to write a book on the OMT method then afterwords, after 2.1 came out I wrote a book on a dummy’s book that you mentioned the “UML2 for Dummies” on UML 2. Now I am thinking about writing the next one UML 2.5.
So model the stuff.. that’s new to you, more challenging and more difficult.
Kenji: So we don’t have to stick to “model and execute”. Just “Model to Communicate” is good?
Michael: That’s okay. That’s enough! There are times that model and execute is good. But if you are short on money, short on time, short on resources – which every project is. You might want to model stuff where you get the most bang for your buck – the most return on your investment.
That’s the stuff that’s hard. That’s the stuff that’s not known. That’s the stuff that’s hard. That’s it.