🎓 Free Capstone Projects with Full Documentation, ER Diagrams & Source Code — Updated Weekly for 2026
👨‍💻 Free Source Code & Capstone Projects for Developers

Activity Diagram for Online Banking System

Online Banking System Activity Diagram

The Activity Diagram for Online Banking System is an important part of the banking management system. This designed activity diagram shows the panel and reader how the banking system would …

Read more

Activity Diagram for ATM Management System

ATM Management System Activity Diagram

Activity Diagram for ATM Management System – is an illustration of the ATM management software’s behavior towards its users. This depicts the flow of the proposed Capstone Project from the …

Read more

Frequently Asked Questions

What is the difference between Activity Diagram and Flowchart?
A flowchart shows control flow with general-purpose symbols (decision diamond, process rectangle, terminator oval). An Activity Diagram is a UML-standardized flowchart with specific UML symbols (filled-circle initial node, rounded-rectangle activity, diamond decision, thick-bar fork/join, circled-dot final node) and the ability to show parallel activities (fork/join) which classic flowcharts cannot. For capstone Chapter 3, use Activity Diagram if your school requires UML; use flowchart if they accept general diagrams.
What is the difference between Activity Diagram and Sequence Diagram?
Activity Diagram focuses on WORKFLOW — what happens, in what order, with what decisions. No specific objects called out. Sequence Diagram focuses on OBJECT INTERACTION — which object calls which method on which other object, and in what order. Activity = "how does the process flow?" Sequence = "which objects do what?" Capstones usually need both.
What are fork and join nodes for?
Fork (thick black horizontal bar) splits one flow into multiple parallel flows that happen simultaneously. Join (also a thick black bar) merges parallel flows back into one. Useful when actions happen in parallel: e.g., after a user pays, your system simultaneously (1) updates the database, (2) sends SMS confirmation, (3) emails the receipt. Fork from "Process Payment," join before "Show Success Screen."
How detailed should my Activity Diagram be?
For BSIT capstone Chapter 3, draw 1-3 Activity Diagrams covering your most important workflows (Login + main user flow + admin flow). Each diagram should have 5-15 activities. More than 20 activities means the workflow is too complex — split into sub-diagrams. Less than 5 means the workflow is too trivial to need a diagram.
What free tool should I use to draw an Activity Diagram?
draw.io / diagrams.net — free, web-based, has UML Activity shapes built in (initial, activity, decision, fork, final). Lucidchart Free — prettier output. Visual Paradigm Community — full UML support. PlantUML — text-based, version-controllable, great for technical docs. Pick draw.io for fastest capstone iteration.
Should I include swimlanes in my Activity Diagram?
Swimlanes (vertical columns labeled with actor/department names) clarify WHO performs each activity. Use them when your workflow crosses multiple roles (Customer / Cashier / Admin / Inventory Clerk all participate). Skip swimlanes for single-actor workflows. Many BSIT capstones include swimlanes for the main workflow but omit them in simpler sub-flows.
How often is this Activity Diagram collection updated?
New Activity Diagrams are added regularly. Existing diagrams are revised when UML 2.5.x notation updates. Last refreshed: May 2026.