![]() ![]() 9.4 Pre Conditions The User must possess an ATM card or a credit/debit card. 9.3 Alternate Flow Even after reinserting the card, if the card is invalid ATM (Card reader) gives a receipt indicating that the card is invalid. Customer must re-insert (swipe) the card again. ATM (Card reader) validates the card is invalid. Customer inserts card in ATM or swipes in Card reader. In those situations it is requested for re-insert. The card may not be inserted properly or it may be out of date or it can be an invalid for specific bank. Invalid card - Use case specifications 9.1 Brief Description The card inserted will be checked for validation. 8.4 Pre Conditions The User must possess an ATM card or else a debit/credit card. On success user can precede the transaction 8.3 Alternate Flow If the card is invalid, ATM ejects the card or then it may be taken back from Card reader and gives a receipt indicating the error number. Customer inserts card in ATM or Card reader 2. Once the transaction is over card is spelled out Flow of Events 8.2 Basic flow 1. Insert card - Use case specifications 8.1 Brief Description The customer is requested to insert (swipe) card and the card is taken in and kept inside for the whole transaction time. 7.4 Pre Conditions The User must possess an ATM card 7.5 Post Conditions The user must take the receipt. 7.3 Alternate Flow If in the basic flow, the card or pin is invalid a receipt ejects out from ATM in response to the error. On success employee must enter pin and select from his list of services appeared on the screen. If there are less funds the transaction is sustained. The customer may have transactions like checking balance, draw amount and donation. And then pin validation is done if the pin is invalid the transaction is doesn’t allowed. Invalid Login- Use case specifications 5.1 Brief Description transaction continues. 4.4 Pre Conditions The user should have been logged in already. 4.3 Alternate Flow If in the basic flow, if the internet connection is lost user must refresh the page again. All the transactions he performed are reflected in the bank database. The vendor provided for communication is now closed from database. Logout- Use case specifications 4.1 Brief Description The person who ever logged in to the system or bank database has to logout after all the work is over. 3.4 Pre Conditions The user must possess a login id and password. 3.3 Alternate Flow If in the basic flow, the details specified by user are invalid the he is informed that his login is failed. On success user can precede the transaction. A user may be an invalid user so the system has to prompt the person appropriately. A vendor is provided for communication with bank’s database and this vendor provides safety and atomicity. ![]() Login- Use case specifications 3.1 Brief Description The online customer or a bank employee has to login to access their accounts from bank database. 2.5 Post Conditions The account database is modified after transaction. 2.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. 2.3 Alternate Flow If in the basic flow, the details specified by employee are invalid the he is informed that his login is failed. On success employee can withdraw or deposit money, issue loans and DD/cheque to the customers. Employee enters his username and password. And the intended services are provided to the customers. Bank employee is allowed to modify the database accordingly. Download Uml diagrams for bank management and more Java Programming Study notes in PDF only on Docsity! BANK MANAGEMENT (Mini-project) By G.SHAKIR Use Case Modeling Use Case diagram for Banking System: An employee can have operations like withdrawal of money, giving loans, furnishing the DD/cheque and customers may want to deposit money. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |