2. Unified OO becomes commonly used in the late 1980s Various analysis and design methods The “three amigos” join forces in Rational Software Also include ideas from other methodologies 1991 Jim Rambaugh OMT (object modeling technique) Grady Booch OOD (Booch Method) Ivar Jacobson Objectory 1994 1995 Rational hires Rambaugh Rational hires Jacobson 1997 UML 1.0 1992 1990

3. Modeling Simplified representation of the real world where the software will operate – Objects in this world (structure) – Business processes (dynamic behavior) Use multiple perspectives – Even with some redundancy Not directly executable, but can be used to generate code template

4. Language A visual/graphical notation to express the models Has precise semantics! – Not just pretty pictures – But sometimes abused by those who don’t know Not a development process – Later we’ll see the Rational Unified Process that uses UML

5. The Diagrams

6. Why Use It Framework to foster discussion and discovery – Conceptual: the underlying structure and ideas – Specification: the layout of the software and the interfaces – Implementation: the details Documentation of what you learned and the resulting design A medium for communication – A standard: everyone knows it