 |  |  | Know-how
|  |  |
 |
A glance back |  |
The Unified Modeling Language (UML) is used for the modeling, documentation, specification, and visualization of complex software systems, no matter where they're used or how they're implement. The UML provides notation elements for static and dynamic models of analysis, design and architecture, on top of that it supports procedures specific to object orientation. By combining several approaches of object oriented methods, UML version 0.9 was created in 1997/98. Since then it has constantly been improved and adjusted to suit end-user needs and areas of application. |  |  |
 |
A glance ahead |  |
Well, here it is - the UML 2.0. Surely not complete yet, but good enough. What does it have to offer, this "new" UML? 13 different types of diagrams, of which three are completely new. Other diagrams, such as the activity diagram, were "overhauled". These changes alone could fill a book. If you would like to know, without lengthily sifting through various pieces of literature, which diagram suits which problem and/or situation best, have a look at chapter 2 "Process Suggestions" in UML 2 Glasklar (in German only). |  |  |
 |  |  |
There is more to the UML than just the notation elements of individual diagrams. Would you like to have more information on the UML and its uses? Then be welcome to have a look at our "whitepapers" which we will be publishing periodically in the near future.
|  |  |