2.2 Use case diagram
A use case is a graph of the steps that define the interaction between an actor (a human who interacts) and the system to be developed.
2.3 Sequence diagrams
Sequence diagrams, also known as event diagrams, depict how processes interact with each other.
UML Diagram Examples
Class diagrams
Classes are represented as a rectangular shape with three divisions. The top section shows the name, the middle section contains the attributes, and the bottom section shows the class's operations (methods).
Use lines to represent association, transfer, multiplicity, and other relationships between classes and subclasses.
Component diagrams
Represents a component with a rectangular shape. It is represented by two small rectangles on one side.
Lines are added to represent relevant relationships.
Implementation diagrams
When drawing a deployment diagram, the cambodia telegram data same notation is used for a component diagram.
Use a 3D cube to model a physical machine or virtual machine.
Behavioral Diagram Tutorial Examples
Activity diagrams
These diagrams are integrated with specialized shapes which are then connected with arrows.
The activity diagram starts with a black circle.
Use case diagram
A use case diagram starts with an oval shape in the center, indicating an action.
The actors are then represented with a human figure, and lines are drawn to indicate relationships.
Sequence diagram
The vertical lines indicate the sequence of messages in chronological order and the horizontal elements show instances in which messages are transmitted.
Draw lines between class instances, to represent the sender and receiver of messages.
Connect the circle to the first activity.
Then connect each activity to other activities with lines that show the step-by-step flow.
