Scribd
Upload
163 views3 pages

F11 UseCases

The document describes the use cases for a mobile banking application. There are 11 primary use cases: Register User, Login User, Logoff User, Register Account, Unregister Account, View Accounts, View Account, Transfer Money, View Alerts, Add Alert, and Delete Alert. The use cases allow a user to register and log into their account, view account information and transaction history, transfer money between accounts, and manage alerts for their accounts.

Uploaded by

ppdudecmu
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
163 views3 pages

F11 UseCases

The document describes the use cases for a mobile banking application. There are 11 primary use cases: Register User, Login User, Logoff User, Register Account, Unregister Account, View Accounts, View Account, Transfer Money, View Alerts, Add Alert, and Delete Alert. The use cases allow a user to register and log into their account, view account information and transaction history, transfer money between accounts, and manage alerts for their accounts.

Uploaded by

ppdudecmu
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Task 06: Database and Detailed Design Use Cases for Mobile Banking Application

Mobile Banking System


RegisterUser

LoginUser

LogOffUser

RegisterAccount

User

UnregisterAccount

ViewAccounts

ViewAccount TransactionWebService

TransferMoney

AddAlert

DeleteAlert

ViewAlerts

Figure 1: UML Use Case Model for Mobile Banking System.

Primary Use Cases (Main Success Scenarios only)


UC1: Register User. The system displays a screen for the user to input their userid, password, and address information. The user inputs the required information. The system stores the data in the system. The user is redirected to the Login User use case. UC2: Login User. The system displays a screen for the user to input their userid and password. The user inputs the required information. The system validates that the userid and password are valid and correct. The user is redirected to the View Accounts use case. The screen also contains a link for the user to invoke the Register User use case, so that they may register if they dont have a login. This use case is triggered when the system first starts or the user first connects. UC3: Logoff User. The system displays a log off confirmation. The user confirms. The system exits and/or the connection is terminated. UC4: Register Account. The system displays a screen for the user to input the information about the new account they wish to register. The user inputs the information. The system confirms the information with the user. The information is stored in the system. The user is redirected to the View Account use case for the new account. UC5: Unregister Account. The system displays a confirmation screen. The user confirms. The system deletes the data associated with the deleted account. The user is redirected to the View Accounts use case. UC6: View Accounts. The system displays a menu listing the registered accounts. The user selects a particular account. The user is redirected to the View Account use case for the selected account. UC7: View Account. The system displays the current balance and a list of recent transactions for the account. When the user is done viewing the data, she selects OK and is redirected to the View Accounts use case. The user may also select Transfer, in which case she is redirected to the Transfer Money use case for the selected account. The user may also select View Alerts, in which case she is redirected to the View Alerts use case for the selected account. UC8: Transfer Money. The system prompts the user with a menu of destination accounts. The user selects the desired destination account. The system executes the appropriate transfer transaction with the TransactionWebService. The user is redirected to the View Accounts use case. UC9: View Alerts. The system displays a list of current alerts for the selected account. The user may select Add Alert to redirect to the Add Alert use case, or Delete Alert to redirect to the Delete Alert use case.

UC10: Add Alert. The system displays an input screen for the user to input the required information for the alert (type of alert, address, etc.). The user provides the required information. The system stores the data and redirects the user to the View Alerts use case. UC11: Delete Alert. The system displays a menu of the current alerts. The user selects the alert to be deleted. The system displays a confirmation screen. The user confirms. The alert data is deleted from the system. The user is redirected to the View Alerts use case.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy