UML Diagrams
Unified Modeling Language (UML) diagrams are the object-oriented system of notation. UML is the accepted standard for modeling object-oriented programs.
Behavior Diagrams:
| A use case is something that can be done by the system/application. An actor is someone or something that will affect or interact with the system/application. |
| The activity diagram describes the sequencing of activities (workflow), with support for both conditional and parallel behaviors. The activity diagram is a variation of a state diagram as the activity is a state of doing something. |
| A sequence diagram has the controlling and collaborating objects across the top. Messages are passed between objects. |
| A narrative diagram clarifies a use case and documents how the application is intended to be used. |
| A collaboration diagram or interaction diagram illustrates the interaction among two or more classes. |
| A state diagram shows how a single object behaves across many use cases. |
Structural Diagrams:
| In a class diagram only the name of the class is required. Additionally there may be the attributes, perhaps attribute types and default values. There may be a list of the operations, methods or responsibilities of the class. |
| An object diagram is a snapshot of the objects in a system at a point in time. Since it shows instances rather than classes, an object diagram is often called an instance diagram. |
| A component diagram shows the various components (physical modules of code/software) in a system and their dependencies, including source code, run-time (binary) code, and executables. Component and deployment diagrams may be combined. |
| A deployment diagram shows the physical layout of components on hardware nodes. Component and deployment diagrams may be combined. |
More sites for UML:
Smart Draw,
Borland,
Visual Paradigm
