The Bank Management System Use Case Diagram is used to show the processes involved when users invoke the software. It depicts the structure of the system behavior.
Additionally, the diagram consists of processes (use cases) and users or “actors”. It uses defined symbols to describe the overall flow of the system.
Explore our Suggested and Related Articles for further reading material and more educational ideas.
- Use Case Diagram for Blood Bank Management
- Blood Bank Management Project Use Case Diagram
- Blood Bank Management System UML Diagrams
- Activity Diagram for Blood Bank System
- ER Diagram for Blood Bank Management
- Online Blood Bank Management System Class Diagram
- Component Diagram for Blood Bank Management
- Deployment Diagram for Blood Bank Management
- Blood Bank Management System Sequence Diagram
Project Overview
| Name: | Bank Management System Use Case Diagram in UML |
| Users: | Bank Admin, Employees, and Clients (Customers). |
| Tools Used: | Any Diagram tools that provide use case diagram symbols. |
| Designer: | ITSourceCode.com |
What is a Use Case Diagram?
The use case diagram for bank management system shows the sample behavior of the software. It includes the project functions using use cases, actors, and their connections.
Moreover, the diagram assists you to define and organize project needs. This also provides a clear picture of the user and system relationships. Therefore, this diagram depicts the complex functions of a system including how the user reacts to it.
What is the Importance of UML Use Case Diagram?
Helping the developers and businesses with system management is one of the importance of the UML use case diagram. It includes the procedures from the viewpoint of users.
Furthermore, the diagram is the analysis method used to identify, clarify, and manage project needs. This diagram works best with other UML Diagrams for Bank Management System. Other UML diagrams include activity, class, sequence, deployment, and component diagrams.
How the Bank Management Use Case Diagram works?
The designed bank management system use case diagram has two main illustrations. These illustrations describe the system’s general and specific processes using include and extend.
Bank Management System General Use Case Diagram
The general use case diagram for bank management system shows the main functions of the system. It is based on the transactions done during student management.
The general use case is the most common application of a use case diagram. The use case diagrams depict the system’s main components as well as the flow of information between them.
Use Case Diagram using Include and Extend
The use case diagram using include and extend is used to elaborate the proceeding diagrams. The terms include and extend in the use case diagram are known as indicators.
The label include indicates that the sub-processes of the main processes must be included to complete the task. Extend, on the other hand, declares that the sub-processes can only be performed when needed.
Manage Customers’ Information and Status Use Case Diagram
This is where the admin handles the important client information which serves as the basis for student transactions. It is also the place where the admin can update client’s information (transaction).
Manage Withdrawing and Saving Transaction Use Case Diagram
This process is where the bank users encode and validate the applicant’s application. It is done to grant applicants access to their bank accounts. Admin updates the applicants’ information as soon as their records are valid.
Manage Applicant’s Account Information
It is the process where the admin gathers the instructors’ information and profiles. The admin will also manage their credentials for teaching and assign them to the subjects that suits their qualifications.
You can add more to this illustration and it is up to you how will you create your diagram. But make sure to have precise information and consider the included use cases.
Use Case Diagram for Bank Management System Pdf
How to draw a Use Case Diagram?
Time needed: 2 minutes
Here’s the complete guide on how to draw a use case diagram for bank management system.
- Step 1: Familiarize Use Case Diagram Symbols
For beginners, you need to familiarize first with use case symbols to be used.
- Step 2: Determine the system processes
The next step is to determine the system’s processes. They will be the use cases of your project.
You may ask the users about the typical activities done in bank management.
- Step 3: Analyze the use cases included
The gathered information from the users needs to be evaluated to know the general use cases.
From the general use cases, you will see the sub-cases that are included. But, only include the useful processes related to the bank management system.
- Step 4: Plot the Use Case Diagram
To plot the diagram you will need the users, use cases, container (scope), and their indicators (association). You will base the flow of use cases on the evaluated information from the users.
Your first move is to place the users involved.
Next, put the container in the plotted diagram to separate the objects (users and system) scope.
Then place the use cases of the bank management.
Finally, you need to map out the association of the use cases to show the interactions between the user/s and the system.
Conclusion:
One of the methods that contribute to bank management system development is the UML use case diagram. It helps developers know the possible inputs that the project should process and perform.
Furthermore, you will discover the needed processes and connect them to the other UML Diagrams. The diagram is also applicable in modeling the software’s use cases (processes). It captures the system’s flow from one process to the next.
Inquiries
If you have concerns about the Bank Management System Use Case Diagram, just leave us your comments below.
How to read a use case diagram
A use case diagram has 3 main elements: actors (stick figures outside the system), use cases (ovals inside the system boundary), and relationships between them.
- Actor. A role played by a human or external system that interacts with the system.
- Use case. A specific goal the actor accomplishes with the system.
- System boundary. The rectangle around the use cases marks what is inside vs outside.
- Association. Line between an actor and a use case they perform.
Use case relationships
- Include. Dashed arrow with “<<include>>” — one use case ALWAYS calls another (e.g., Login is included in Place Order).
- Extend. Dashed arrow with “<<extend>>” — an optional add-on to a base use case (e.g., Apply Discount extends Place Order).
- Generalization. Solid arrow with hollow triangle — one actor or use case is a specialized form of another.
Common capstone mistakes to avoid
- Too granular. Do not create a use case for each button. Focus on business goals like “Manage Inventory.”
- Missing actors. Every use case must be associated with at least one actor.
- Confusing include vs extend. Include is mandatory; Extend is optional.
- System actors as human. External payment gateways, email servers, etc. are actors too.
- No system boundary. Missing rectangle is a common panel critique.
Where the use case diagram fits in Chapter 3
- Section 3.1 (System Overview) or 3.2 (Functional Requirements).
- List each use case with a brief description in a table alongside the diagram.
- Reference each use case when explaining the workflow in later sections.
Official documentation
Working source code for this system
Download the actual implementation of this system in your preferred language. Each project includes source code, database, and setup instructions for BSIT capstone use.
- PHP: Online Blood Bank Management System in PHP with Source Code
- Java: Bank Management System Project In Java NetBeans Source Code
- Python: Bank Management System Project in Django with Source Code
- Django: Bank Management System Project in Django with Source Code
- Laravel: Online Banking Management System Project in Laravel with Source Code
Frequently asked questions
What is a use case diagram used for in BSIT capstone?
A use case diagram shows what the system does from the user’s perspective: actors, use cases, and their relationships (include, extend, generalization). It goes in Chapter 3 and communicates the functional requirements of the system.
What tool should I use to draw the use case diagram?
Free options: draw.io, Lucidchart free tier, PlantUML, StarUML 30-day trial, Visual Paradigm Community Edition. Paid options: Microsoft Visio, Lucidchart pro, Enterprise Architect. For BSIT capstones, draw.io is the most commonly used free tool.
How detailed does the use case diagram need to be for capstone defense?
Panel members expect the diagram to match the actual system implementation. Include every major class/use case/entity relevant to the system. Omit trivial helper classes. Every diagram element should have a clear justification.
Should I use black-and-white or colored diagrams?
Black-and-white is standard for capstone documentation to match the thesis format. Use color only if it improves clarity. Ensure text is readable at printed size (10pt minimum for labels).
Where does this diagram go in the capstone documentation?
Chapter 3 (System Design and Methodology) typically holds all UML diagrams. Introduce each diagram with a 1-paragraph description explaining what it shows and how to read it.
Mary Grace G. Patulada
Programmer & Technical Writer at PIES IT Solution
Mary Grace G. Patulada (pen name ‘Nym’) is a programmer and writer at PIES IT Solution with a BSIT background from Carlos Hilado Memorial State College, Binalbagan Campus. Authored 370+ UML diagram tutorials and capstone documentation guides at itsourcecode.com. Specializes in UML (class, use case, activity, sequence, component, deployment), DFD, and ER diagrams for BSIT capstone projects.
Expertise: UML Diagrams · DFD · ER Diagrams · Use Case Diagrams · Activity Diagrams · Capstone Documentation · PHP
· View all posts by Mary Grace G. Patulada →