> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/system-design/system-design-methodology/diagrams/uml-diagrams/plantuml/activity-diagram.md).

# Activity Diagram

## About

An Activity Diagram represents workflow or process flow in a system, describing sequential and parallel actions. It is widely used for business logic modeling and process visualization.

{% hint style="success" %}
Refer to the official documentation for more details - <https://plantuml.com/activity-diagram-beta>
{% endhint %}

### **Key Elements**

1. **Start & End Nodes**
   * Represented by a **black circle (start)** and **encircled black dot (end)**.
2. **Actions (Activities)**&#x20;
   * Represented as **rounded rectangles**.
   * Each action represents **a step in the workflow**.
3. **Transitions (Arrows)**&#x20;
   * Show the **flow of execution** between activities.
4. **Decision Nodes**&#x20;
   * Diamond shape, used for **if-else conditions**.
5. **Fork & Join Nodes**&#x20;
   * Represent **parallel processing** (splitting/joining flows).
6. **Swimlanes**&#x20;
   * Separate **responsibilities of different entities** in the process.

## 1. User Registration Process

This represents the **User Registration Process** in a web application.

{% hint style="success" %}

* **Start (`start`)** and **End (`stop`)** nodes.
* **Decision (`if ... then ... else`)**: Validates user input.
* **Actions (`: ActionName;`)**: Represents different activities.
  {% endhint %}

```plant-uml
@startuml
title User Registration Process - Activity Diagram

start
:User Enters Details;
if (Are details valid?) then (Yes)
    :Save to Database;
    :Send Verification Email;
    if (Email Verified?) then (Yes)
        :Activate Account;
    else (No)
        :Show Error;
    endif
else (No)
    :Show Validation Errors;
endif
stop

@enduml
```

<figure><img src="https://3632859567-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPd6ktrA5pPLsZJktj2fm%2Fuploads%2Fy8XwNIT5W2YTFJi931e2%2Fplantuml-activity-diagram-1.png?alt=media&amp;token=00a26dab-1e5b-4c70-a642-1eae3451b6cf" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.pranaypourkar.co.in/the-programmers-guide/system-design/system-design-methodology/diagrams/uml-diagrams/plantuml/activity-diagram.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.