Create a use case diagram for an online banking system with customer and teller actors
About the framework
This banking example connects Customer to Check Balance, Transfer Funds, Pay Bills, View Statements, and Open Account. Teller connects to Open Account, Process Loan, and Generate Reports. Seven function boxes and eight connections show where the roles differ and where they meet.
Open Account is the only shared function in the sample. That can start a discussion about whether customers initiate an application while tellers review it, or whether both roles complete the same task. The diagram itself does not make that distinction.
Use the layout to review functional scope before adding detailed workflows. Authentication, notifications, external networks, and a system boundary are absent. Add those only where they fit your application, and document permission checks separately from these role-to-function connections.
What's included
Use Case Diagram - Online Banking System
✦ Free preview · Sign in to use
Frequently asked questions
No. Process Loan connects only to Teller. Add a separate customer application function if your system supports that journey.
It identifies role participation at a high level. You still need explicit permission rules and checks for each action and account; a connection is not an implemented authorization policy.
No external payment network or credit bureau appears in the sample. Add the relevant system and specify which banking function interacts with it.
Free to start. No credit card required.