In a UML activity diagram, you represent the control flow from one activity to another in software system (like a levels in video game). You can consider activities as actions that further the flow of execution in a system. They are actions, that when completed, cause another action to execute. For example these actions can alter objects or create new objects. These changes/actions drive the application forward.
The purpose of the activity diagram is to capture the dynamic behaviour of the system. The activity diagram allows you to map out the branching into alternative flows.
When creating the diagram, firstly have to identify the activities.
Activity diagram have 2 major parts, the start and end nodes:
The intermediate activities are shaped as a pill. They describe all of the activities that change the game state before the game ends.
Ivan's Blog 