A UML activity diagram represents what happens and how the process flows from one action to another.
Before adding decisions, begin with the three basic parts of a straight process:
For a simple soccer process:
The diagram gives the reader a clear path to follow.
A UML activity diagram uses a start node to show where the activity begins.
There should be a clear point where the reader can enter the process.
In plain language:
The start node does not describe an action by itself.
It marks the beginning of the flow.
An action node represents something that happens.
Examples in a soccer system might include:
Action labels should describe meaningful work.
A vague label such as:
does not help the reader understand the process.
A stronger label tells what action occurs.
Connections between nodes show which action follows another.
For example:
The arrows communicate sequence.
They tell the reader:
A diagram with correct actions but incorrect arrows communicates the wrong process.
An end node shows where the modeled activity is complete.
For a small process:
The end tells the reader that no additional action is part of this modeled path.
The real software may continue doing other things outside the scope of the diagram.
The end node marks the end of this activity model, not necessarily the end of the entire application.
An action node should usually describe one meaningful step.
Compare:
with:
The second version makes the flow easier to follow because each action has a focused role.
An activity diagram is still an abstraction.
If the purpose is to show how the program displays a roster, the diagram does not need to include every event in the soccer club.
It may not need to show:
Include the actions needed to communicate the process being modeled.
A basic activity diagram can represent one path:
That is enough to show sequence.
Soon, you will add a point where the path can change based on a Boolean condition.
Before doing that, make sure the straight portions of the process are clear.
A decision is easier to understand when the actions before and after it already make sense.
When reading an activity diagram:
Do not jump around the page based on which box looks closest.
The connectors define the flow.
For a simple process, keep this mental model:
Start → Action → Action → End
The start establishes entry.
Actions describe the work.
Arrows establish order.
The end establishes completion.
The next activity adds a new kind of node that allows the flow to choose between different paths.