Define the static part of the model. They represent the physical and conceptual elements.
CLASS
Class represents a set of objects having similar responsibilities.
INTERFACE
Interface defines a set of operations, which specify the responsibility of a class.
COLLABORATION
Collaboration defines an interaction between elements.
USE CASE
Use case represents a set of actions performed by a system for a specific goal.
COMPONENT
Component describes the physical part of a system.
NODE
A node can be defined as a physical element that exists at run time.
BEHAVIORAL THINGS
Consists of the dynamic parts of UML models.
INTERATION
Interaction is defined as a behavior that consists of a group of messages exchanged among elements to
accomplish a specific task.
STATE MACHINE
State machine is useful when the state of an object in its life cycle is important. It defines the sequence
of states an object goes through in response to events. Events are external factors responsible for state
change
GROUPING THINGS
Can be defined as a mechanism to group elements of a UML model together.
PACKAGE
Package is the only one grouping thing available for gathering structural and behavioral things.
ANNOTATIONAL THINGS
Can be defined as a mechanism to capture remarks, descriptions, and comments of UML model
elements.
NOTE
It is the only one Annotational thing available. A note is used to render comments, constraints, etc. of an
UML element.
RELATIONSHIPS
Is another most important building block of UML. It shows how the elements are associated with each
other and this association describes the functionality of an application.
DEPENDENCY
Dependency is a relationship between two things in which change in one element also affects the
other.
ASSOCIATION
Association is basically a set of links that connects the elements of a UML model. It also describes how
many objects are taking part in that relationship.
GENERALIZATION
Generalization can be defined as a relationship which connects a specialized element with a
generalized element. It basically describes the inheritance relationship in the world of objects.
REALIZATION
Realization can be defined as a relationship in which two elements are connected. One element
describes some responsibility, which is not implemented and the other one implements them. This
relationship exists in case of interfaces.
UML DIAGRAMS
UML diagrams are the ultimate output of the entire discussion. All the elements, relationships are
used to make a complete UML diagram and the diagram represents a system.
STRUCTURAL MODELING
Represents the framework for the system and this framework is the place where all other components
exist.
Classes diagrams
Objects diagrams
Deployment diagrams
Package diagrams
Composite structure diagram
Component diagram
BEHAVIORAL MODELING
Behavioral model describes the interaction in the system. It represents the interaction among the
structural diagrams. Behavioral modeling shows the dynamic nature of the system.
Activity diagrams
Interaction diagrams
Use case diagrams
ARCHITECTURAL MODELING
Architectural model represents the overall framework of the system. It contains both structural and
behavioral elements of the system. Architectural model can be defined as the blueprint of the entire
system. Package diagram comes under architectural modeling.