UML

Unified Modeling Language (UML) is a standard language to specify, visualize, and document the artifacts of software systems.

Use Case Diagram
- A use case is a set of scenarios that describe the interaction between a actor (user or another system) and the system being modeled.
- A use case diagram displays the relationship among actors and use cases.

Class Diagram
- A Class is composed of a name, a set of attributes, and a set of operations.
- Class diagrams model class structure and contents at three different levels - classes, packages and objects.
- Class diagrams have three different perspectives - conceptual, specification, and implementation.
- Class diagrams display relationships such as containment, inheritance, associations and others.

Interaction Diagrams
- Interaction diagrams model the behavior of use cases by describing the way groups of objects interact to complete the task. The two kinds of interaction diagrams are sequence and collaboration diagrams.
- Sequence diagrams demonstrate the behavior of objects in a use case by describing the objects and the messages they pass.
- Collaboration diagrms show the relationship between objects and the order of messages passed between them.

State Diagrams
- State diagrams describe all of the possible states of an object as events occur.
- Each diagram usually represents objects of a single class and track the different states of its objects through the system.

Activity Diagrams
- Activity diagrams describe the workflow behavior of a system.
- The diagrams describe the state of activities by showing the sequence of activities performed. - Activity diagrams can show activities that are conditional or parallel.

Physical Diagrams
- There are two types of physical diagrams: deployment diagrams and component diagrams.
- Deployment diagrams show the physical relationship between hardware and software in a system.
- Component diagrams show the software components of a system and how they are related to each other. These relationships are called dependencies.
- Many times the deployment and component diagrams are combined into one physical diagram.

-- Kennesaw State University