UML Diagram
UML Diagram
What is UML? UML stands for Unified Modeling Language. UML is a way of
visualizing a software program using a collection of diagrams. The
notation has evolved from the work of Grady Booch, James Rumbaugh,
Ivar Jacobson, and the Rational Software Corporation to be used for
object-oriented design, but it has since been extended to cover a wider
variety of software engineering projects. Today, UML is accepted by
the Object Management Group (OMG) as the standard for modeling
software development.
The original UML specified nine diagrams; UML 2.x brings that
number up to 13. The four new diagrams are called: communication
diagram, composite structure diagram, interaction overview
diagram, and timing diagram. It also renamed statechart diagrams to
state machine diagrams, also known as state diagrams.
The current UML standards call for 13 different types of diagrams: class,
activity, object, use case, sequence, package, state, component,
communication, composite structure, interaction overview, timing, and
deployment.
These diagrams are organized into two distinct groups: structural
diagrams and behavioral or interaction diagrams.
Structural UML diagrams
Class diagram
Package diagram
Object diagram
Component diagram
Deployment diagram
Activity diagram
Sequence diagram
State diagram
Communication diagram
Timing diagram
Class Diagram
Class diagrams are the backbone of almost every object-oriented method,
including UML. They describe the static structure of a system. Learn more
Package Diagram
Package diagrams are a subset of class diagrams, but developers
sometimes treat them as a separate technique. Package diagrams
Object Diagram
Object diagrams describe the static structure of a system at a particular
time. They can be used to test class diagrams for accuracy.
Activity Diagram
Activity diagrams illustrate the dynamic nature of a system by modeling
the flow of control from activity to activity. An activity represents an
operation on some class in the system that results in a change in the state
of the system. Typically, activity diagrams are used to model workflow or
business processes and internal operation. Learn more
Sequence Diagram
Sequence diagrams describe interactions among classes in terms of an
exchange of messages over time. Learn more
Component Diagram
Component diagrams describe the organization of physical software
components, including source code, run-time (binary) code, and
executables.Learn more.
Deployment Diagram
Deployment diagrams depict the physical resources in a system, including
nodes, components, and connections.