This action might not be possible to undo. Are you sure you want to continue?
Use Case Modeling
Use Case diagram for Banking System:
transaction <<include>> <<extend>> invalid card insert card user <<include>> atm transaction invalid login bank employee web merchant <<extend>> online transaction <<include>> <<include>> login <<include>> logout <<include>> invalid pin <<extend>> <<include>>
client desktop transaction
1. Online Transaction - use case specifications
1.1 Brief Description Account transaction begins when customer is successfully logged in to the site. Several menus where displayed related to profile of customer and the recent transactions and the current account balance. The main purpose of using online account transactions is to transfer cash from one account to another for this purpose the customer is provided fields
to specify the accounts to which he is transferring amount. User enters username and password.2 Basic flow 1. On success user can transfer money.4 Pre Conditions The user should have a valid account in the bank. 1. 1.5 Post Conditions The account database is modified after transaction. every transaction is added to the bank database. After every transaction a confirmation is displayed to customer. but not the user id. Client Desktop transaction.1 Brief Description Client desktop is given to each of bank employees and they are provided with account logins with a user id and a password. 3. the details specified by user are invalid then he is informed that his login is failed . The customer is also provided the possibility to change the account login password.Then the user may quit the system or he may create a new account. 2. Bank Database validates the user. Every employee switches on his desktop and login to his account through which he can communicate with bank database. . 1. Flow of Events 1.Use case specifications 2.3 Alternate Flow If in the basic flow. change his password and view his profile. 2.
Flow of Events 2. Employee issues dd/cheque to user. Bank employee is allowed to modify the database accordingly. 2. Employee enters his username and password. On success employee can withdraw or deposit money. 2.An employee can have operations like withdrawal of money. 3.5 Post Conditions The account database is modified after transaction. the details specified by employee are invalid the he is informed that his login is failed . Bank Database validates the employee. 2. Login. 3. giving loans. furnishing the DD/cheque and customers may want to deposit money. 2.Use case specifications 3.2 Basic flow 1. issue loans and DD/cheque to the customers. And the intended services are provided to the customers.3 Alternate Flow If in the basic flow.4 Pre Conditions The employee must possess a account login and password.Then the person is not employee of the bank and he is not having authority to perform those actions.1 Brief Description .
Bank Database validates the user.Use case specifications 4.1 Brief Description . 3. A user may be an invalid user so the system has to prompt the person appropriately. Logout. A vendor is provided for communication with bank’s database and this vendor provides safety and atomicity. On success user can precede the transaction. 3.3 Alternate Flow If in the basic flow. 3. 3. 4.5 Post Conditions None.4 Pre Conditions The user must possess a login id and password. Flow of Events 3.The online customer or a bank employee has to login to access their accounts from bank database. User enters username and password. the details specified by user are invalid the he is informed that his login is failed. 2.2 Basic flow 1.
if the internet connection is lost user must refresh the page again.1 Brief Description .4 Pre Conditions The user should have been logged in already. The vendor provided for communication is now closed from database.Use case specifications 5.3 Alternate Flow If in the basic flow. 4.2 Basic flow 1. 4. User clicks the logout 2. 5.5 Post Conditions None. All the transactions he performed are reflected in the bank database. Flow of Events 4. 4. Invalid Login.The person who ever logged in to the system or bank database has to logout after all the work is over.
Card transaction .4 Pre Conditions None. Bank Database validates that the login is invalid. If the user enters a valid login he must be allowed to proceed further. 5.If a person with a invalid user id or password details want login to the system. User enters username and password. customer provides the card and the merchant . 5. This service is provided by a retail institution to a card holding customer. 6. The customer may want to buy any thing form merchant.Use case specifications 6. 2.1 Brief Description Card transaction includes a credit/debit card.5 Post Conditions None. Flow of Events 5. Further he may not be allowed to proceed until enters a valid login.2 Basic flow 1. 5.3 Alternate Flow 1. 3. the system has to prompt the person about failure and should not open the vendor of communication until he furnishes valid user id & password.
After entering the pin number retailer enters amount to be paid by customer. 3.4 Pre Conditions The User must possess a debit/credit card. A debit card will be having some level of funds if the funds are over the transaction will not continue. 2. After inserting the card it is checked for validity if the card is valid . 4. Flow of Events 6. ATM transaction.stripes the card into the card reader then it is checked for validity and if the card is valid the transaction begins. 6.2 Basic flow 1. Card reader checks the card validity after that retailer asks the customer to enter pin number.3 Alternate Flow If in the basic flow. The retailer places the card in card reader. Card reader proceeds transaction after that it updates bank Database and finally gives a receipt to customer.Use case specifications 7. 7.5 Post Conditions The user has to sign in the receipt and put a copy of receipt with him for security reasons. 6. if the card or pin is invalid or the account don’t have sufficient balance the card reader ejects the card out by giving a receipt.1 Brief Description If a customer approaches an ATM. 6. A credit card will have a credit amount you can deduct amount more than that. the person is requested to insert card.
Use case specifications 8. if the pin is invalid the transaction is doesn’t allowed.3 Alternate Flow If in the basic flow. Bank Database validates the card.2 Basic flow 1.1 Brief Description . Flow of Events 7.4 Pre Conditions The User must possess an ATM card 7. 2. The customer may have transactions like checking balance. 7. 3. draw amount and donation. 8. Insert card . the card or pin is invalid a receipt ejects out from ATM in response to the error.5 Post Conditions The user must take the receipt. And then pin validation is done. User inserts card in ATM. 7. If there are less funds the transaction is sustained.transaction continues. On success employee must enter pin and select from his list of services appeared on the screen.
Use case specifications 9.The customer is requested to insert (swipe) card and the card is taken in and kept inside for the whole transaction time. Once the transaction is over card is spelled out Flow of Events 8.3 Alternate Flow If the card is invalid. Invalid card . 3. ATM ejects the card or then it may be taken back from Card reader and gives a receipt indicating the error number. On success user can precede the transaction 8.1 Brief Description . 9. 8.4 Pre Conditions The User must possess an ATM card or else a debit/credit card. 8. Customer inserts card in ATM or Card reader 2.2 Basic flow 1.5 Post Conditions None. ATM or Card reader validates the card.
Use case specifications 10. 9. In those situations it is requested for re-insert. 3. if the card is invalid ATM (Card reader) gives a receipt indicating that the card is invalid. Flow of Events 9. 9. 2. Customer inserts card in ATM or swipes in Card reader.5 Post Conditions None. The card may not be inserted properly or it may be out of date or it can be an invalid for specific bank.1 Brief Description . Customer must re-insert (swipe) the card again. Pin validation .2 Basic flow 1.The card inserted will be checked for validation.4 Pre Conditions The User must possess an ATM card or a credit/debit card. 9.3 Alternate Flow Even after reinserting the card. 10. ATM (Card reader) validates the card is invalid.
3.After inserting the card and if it is checked for validation. ATM ejects the card and gives a receipt indicating the error number.4 Pre Conditions The User must possess an ATM card. 2. 10.3 Alternate Flow If the pin is invalid. On success user can precede the transaction 10. Flow of Events 10. the user is requested for pin.Use case specifications 11. 11.5 Post Conditions None. The pin is itself present on magnetic strip on back of card and it is checked with the entered one. Customer inserts card in ATM and enter his pin number. Invalid Pin .2 Basic flow 1. 10. ATM validates the pin.1 Brief Description .
The pin entered may be wrong in that case transaction is cancelled. 2. ATM blocks the card temporarily. ATM founds that pin is invalid. 11. 11. Customer inserts card in ATM and enter his pin number.4 Pre Conditions The User must possess an ATM card. Class Diagram for Banking System: .3 Alternate Flow If customer enters a correct pin transaction proceeds further.2 Basic flow 1. 11. The number of wrong trials may be limited according to bank’s specifications. The customer requested to reinsert card or reenter the pin. Flow of Events 11.5 Post Conditions The user should not enter the pin number more than the number of trials. 3. 4. In case the number of trials exceeded. The customer is requested for re-inserting of card and re-entry of pin.
* 1 +cnctwithDB +turnon() +turnoff() 1..* 1 1 draw amount +am ount +feasibility() 0.* check bal +balance 0.* transfer of amount +am ount +toaccno +feasibility() 1 1 1 1 employee console +id&pswrd .* credit +am ount +feasibility() retail instituition +am ountadded +process() bank database network to bank +profile +balance +log +request() +profile +log +balance +procesesrequest() bank web page +bankdetails 1 +loginform +processrequest() 1 +logout() 1 login +id +pswrd +validity() 1 1 1 0.* DD/ cheque +am ount +dispensecash() 0.* 0...customer console 0..* 0..* donation +am ount +feasibility() 0.* 1 ATM +choice +processrequest() 1 client desktop +frontend +cnctwithDB +turnon() +shutdwn() 1 1 1 0..* +card +pin +request() 0....* deposit +am ount +accno +transfercash() 1 1 1 0...* 1 pin validation +pin +validity() 1 withdrawl +accno +am ount +feasible() +drawam nt() 0.* loan +am ount +feasibility() 1 logout 1 1 funds +balance debit +am ount +feasibility() card validation +accno +validity() 1 1 1 card reader 1 +cardholder 0....
Sequence Diagrams and Collaboration Diagrams Online Transaction Sequence Diagram: .
online transaction sequence diagram custom console er network to bank transaction 1 : loginRequest() 2 : validity() 3 : profileRequest() 4 : display() 5 : transferRequest() 6 : transfer() 7 : succed() 8 : acknowledgem ent() 9 : transferRequest() Online Transaction Collaboration Diagram: 1 : login request() custom console er 4 : display() 7 : succeed() 2 : validity() 5 : transfer request() 8 : acknowledgem ent() 3 : profile request() network to bank 9 : transfer request() transaction 6 : transfer() Client desktop Transaction Sequence Diagram: .
client desktop transaction sequence diagram em ployee console network to bank database transaction 1 : login request() 2 : validity() 3: m enuChoice() 4 : proceedTransaction() 5 : accountInfo() 6 : succed() 7: m enuChoice() 8 : proceedTransaction() Client desktop Transaction Collaboration Diagram: em ployee console 1 : login request() netwrk to bank db 8 : transaction proceed() 4 : proceed transaction() 3 : choice m enu() 2 : validity() 5 : account info() 6 : succeed() 7 : choice m enu() transaction Login & Logout Sequence Diagram: .
desktop front end network to bank login & logout sequence diagram 1 : enterId&Pswrd() 2 : verify() 3 : validity() 4 : logout() 5 : reqLogout() 7 : loggedout() 6 : succeded() Login & Logout Collaboration Diagram: desktop 1 : enter id pwd() 2 : verify() front end 3 : validity() network to bank 4 : logout() 7 : logged out() 5 : request logout() 6 : succeeded() ATM Transaction Sequence Diagram: .
custom console er ATM transaction sequence diagram ntwrk to bank transaction 1 : insert card() 2 : validation() 3 : verified() 4 : ChoiceMenu() 5 : selectservice() 6 : accountInfo() 7 : feasibility() 8 : give receipt() 9 : another transaction() ATM Transaction Collaboration Diagram: custom console er ntwrk to bank 9 : another trans() 8 : give receipt() 3 : verified() 7 : feasibility() 6 : account info() 4 : choice m enu() 1 : insert card() 2 : validation() 5 : select service() transaction .
Card Validation Sequence Diagram: card validation sequence diagram custom panel er atm network to bank 1 : insert card() 2 : validation() 3 : card valid() 4 : eject card() Card Validation Collaboration Diagram: custom panel er 4 : eject card() 1 : insert card() atm 3 : card valid() 2 : validation() bank network .
Pin Validation Sequence Diagram: pin validation sequence diagram custom panel er atm network to bank 1 : enterpin() 2 : pin validation() 4 : choiceMenu() 3 : validity() Pin Validation Collaboration Diagram: custom panel er 1 : enter pin() atm 2 : `pin validation() bank network 4 : choice m enu() 3 : validity() Web merchant Transaction Sequence Diagram: .
Web m erchant transaction sequence digram custom er retailer card reader network to bank 1 : gives card() 2 : insert card() 3 : validation() 4 : verified() 5 : enter am ount() 6 : update bank db() 7 : give receipt() Web merchant Transaction Collaboration Diagram: custom er 1 : give card() retailer 2 : insert card() card reader 5 : enter am ount() 7 : give receipt() 3 : validation() 4 : verified() 6 : update bank DB() bank network .
Activity Diagrams Online Transaction Activity Diagram: .
open web page create account enter id and pwd no valid login yes choice m enu furnish details no valid details yes subm it am ount transfer view details change pwd finished Client Desktop Transaction Activity Diagram: .
custom approaches officer er em ployee login no valid login yes choice m enu passbook entry deposit withdraw issue dd/cheque proceed transaction ATM Transaction Activity Diagram: .
custom approaches officer er em ployee login no valid login yes choice m enu passbook entry deposit withdraw issue dd/cheque proceed transaction Web Merchant Transaction Activity Diagram: .
insert card no card valid yes enter am ount no sufficient bal yes proceed transaction take receipt finish Component Diagram for Banking System: .
customer console ATM machine ATM transaction Account info Employee console Card reader Bank Database Webpage Client desktop webmerchant transactrion online transaction client desktop transaction Deployment Diagram for Banking System: .
Custom m be er ay ATM card holder. credit/debit card holder or an online user of a Bank ATM Machine providing services of ATM transaction Customer Console ATM Machine Bank Database keeping the details of each and every account Card Reader Bank Database Client Desktop Client Desktop providing services of banking at desks Web Page Employee Console Card reader providing services of credit/debit tranm saction Web Page providing services of online transaction Each em ployee at Bank given a desktop and provided with own id & password for login to the Bank's Database .