Diagrams
A UML diagram provides a visual representation of an aspect of a system. A UML diagram illustrates the aspects of a system that can be described visually such as relationships, behavior, structure and functionality. Depending on the content of a diagram it can provide information about the design and architecture of a system from the lowest level to the highest level. UML provides thirteen types of diagrams that let the user capture, communicate, and document all aspects of an application.
The individual diagrams can be categorized into three main types: Static, dynamic, and functional. Each type represents a different view of an application.
| Static-Diagrams of this type show the static aspects of a system. This includes the things from which the application is constructed for example the classes and how the things are related to each other. This type of diagram does not show changes which occur in the system over time. Examples of this type of diagram are the component diagram, the class diagram, and the deployment diagram. |
|
| Dynamic-Diagrams of this type show the dynamic aspects of a system. They document how an application responds to requests or otherwise evolves over time by showing the collaborations that take place between objects and the changes to the internal states of objects. Objects in a system achieve nothing unless they interact or collaborate. Examples of this type of diagram are the sequence diagram and the communication diagram. |
|
| Functional-Diagrams of this type of show the functional requirements of a system. Examples of this type of diagram are the use case diagram. |
Additional information about UML can be found at:
http://www-01.ibm.com/software/rational/uml
|
ibm.com/redbooks |