This action might not be possible to undo. Are you sure you want to continue?
Submitted by :
Kumar Pratyush (2009202018) Mukesh KumaR (2009202029) OOSD (lab) M.C.A. (3rd sem), regular
Use - case diagram
USE CASE DIAGRAM ONLINE BANKING MANAGEMENT SYSTEM
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. After every transaction a confirmation is displayed to customer. The customer is also provided the possibility to change the account login password, but not the user id, every transaction is added to the bank database.
Flow of Events 1.2 Basic flow
1. User enters username and password. 2. Bank Database validates the user. 3. On success user can transfer money, change his password and view his profile.
1.3 Alternate Flow
If in the basic flow, the details specified by user are invalid then he is informed that his login is failed .Then the user may quit the system or he may create a new account.
1.4 Pre Conditions
The user should have a valid account in the bank.
1.5 Post Conditions
The account database is modified after transaction.
4 Pre Conditions The employee must possess a account login and password. On success employee can withdraw or deposit money. And the intended services are provided to the customers.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 Alternate Flow If in the basic flow. . An employee can have operations like withdrawal of money.2. Client Desktop transaction. 2. giving loans. Employee issues dd/cheque to user. 2. 2. Bank employee is allowed to modify the database accordingly.5 Post Conditions The account database is modified after transaction. Every employee switches on his desktop and login to his account through which he can communicate with bank database. the details specified by employee are invalid the he is informed that his login is failed . 3.2 Basic flow 1. 2. Flow of Events 2. furnishing the DD/cheque and customers may want to deposit money.Then the person is not employee of the bank and he is not having authority to perform those actions. Employee enters his username and password.Use case specifications 2. Bank Database validates the employee. issue loans and DD/cheque to the customers.
4 Pre Conditions The user must possess a login id and password. .2 Basic flow 1. 2. the details specified by user are invalid the he is informed that his login is failed. A user may be an invalid user so the system has to prompt the person appropriately.1 Brief Description The online customer or a bank employee has to login to access their accounts from bank database.5 Post Conditions None. User enters username and password.3 Alternate Flow If in the basic flow. A vendor is provided for communication with bank’s database and this vendor provides safety and atomicity. On success user can precede the transaction. Flow of Events 3.3. 3. Bank Database validates the user. Login. 3. 3. 3.Use case specifications 3.
if the internet connection is lost user must refresh the page again. 4.Use case specifications 4.5 Post Conditions None. The vendor provided for communication is now closed from database. User clicks the logout 2.2 Basic flow 1. .4. Logout. 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. Flow of Events 4. All the transactions he performed are reflected in the bank database. 4.4 Pre Conditions The user should have been logged in already.3 Alternate Flow If in the basic flow.
1 Brief Description If a person with a invalid user id or password details want login to the system.4 Pre Conditions None.Use case specifications 5. 5. 3.5. 5. User enters username and password. Flow of Events 5. .3 Alternate Flow If the user enters a valid login he must be allowed to proceed further. Bank Database validates that the login is invalid. 5. 2. Invalid Login. Further he may not be allowed to proceed until enters a valid login.5 Post Conditions None. the system has to prompt the person about failure and should not open the vendor of communication until he furnishes valid user id & password.2 Basic flow 1.
6.Use case specifications 6. This service is provided by a retail institution to a card holding customer. 4. The retailer places the card in card reader.1 Brief Description Card transaction includes a credit/debit card. .6. Card transaction . 3. Flow of Events 6.5 Post Conditions The user has to sign in the receipt and put a copy of receipt with him for security reasons.3 Alternate Flow If in the basic flow. Card reader checks the card validity after that retailer asks the customer to enter pin. A debit card will be having some level of funds if the funds are over the transaction will not continue. A credit card will have a credit amount you can deduct amount more than that.2 Basic flow 1. After entering the pin number retailer enters amount to be paid by customer. 2. 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. Card reader proceeds transaction after that it updates bank Database and finally gives a receipt to customer. 6.4 Pre Conditions The User must possess a debit/credit card. The customer may want to buy any thing form merchant. 6. customer provides the card and the merchant stripes the card into the card reader then it is checked for validity and if the card is valid the transaction begins.
5 Post Conditions The user must take the receipt.1 Brief Description If a customer approaches an ATM. draw amount and donation. ATM transaction. On success employee must enter pin and select from his list of services appeared on the screen. if the pin is invalid the transaction is doesn’t allowed. . After inserting the card it is checked for validity if the card is valid transaction continues. The customer may have transactions like checking balance.7. 7. the card or pin is invalid a receipt ejects out from ATM in response to the error.Use case specifications 7. Flow of Events 7.4 Pre Conditions The User must possess an ATM card 7. If there are less funds the transaction is sustained. 2. 3. 7. User inserts card in ATM. And then pin validation is done.3 Alternate Flow If in the basic flow. the person is requested to insert card.2 Basic flow 1. Bank Database validates the card.
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.5 Post Conditions None. ATM or Card reader validates the card.3 Alternate Flow If the card is invalid. Once the transaction is over card is spelled out Flow of Events 8. Insert card . On success user can precede the transaction 8.8. 3.Use case specifications 8.4 Pre Conditions The User must possess an ATM card or else a debit/credit card.2 Basic flow 1. Customer inserts card in ATM or Card reader 2. . 8. 8. ATM ejects the card or then it may be taken back from Card reader and gives a receipt indicating the error number.
3.5 Post Conditions None.1 Brief Description The card inserted will be checked for validation. Customer inserts card in ATM or swipes in Card reader. if the card is invalid ATM (Card reader) gives a receipt indicating that the card is invalid. The card may not be inserted properly or it may be out of date or it can be an invalid for specific bank. Flow of Events 9. 9. 2. 9.Use case specifications 9. ATM (Card reader) validates the card is invalid. Invalid card . Customer must re-insert (swipe) the card again.9. 9.4 Pre Conditions The User must possess an ATM card or a credit/debit card. .3 Alternate Flow Even after reinserting the card. In those situations it is requested for reinsert.2 Basic flow 1.
2.4 Pre Conditions The User must possess an ATM card. Flow of Events 10. Customer inserts card in ATM and enter his pin number. 10. 3. . The pin is itself present on magnetic strip on back of card and it is checked with the entered one. ATM validates the pin.Use case specifications 10.10.1 Brief Description After inserting the card and if it is checked for validation.3 Alternate Flow If the pin is invalid. On success user can precede the transaction 10. 10. Pin validation . ATM ejects the card and gives a receipt indicating the error number. the user is requested for pin.2 Basic flow 1.5 Post Conditions None.
Flow of Events 11. Invalid Pin . 2. The number of wrong trials may be limited according to bank’s specifications.2 Basic flow 1.3 Alternate Flow If customer enters a correct pin transaction proceeds further. The customer requested to reinsert card or reenter the pin. 3.4 Pre Conditions The User must possess an ATM card. 11. Customer inserts card in ATM and enter his pin number. In case the number of trials exceeded. The customer is requested for re-inserting of card and re-entry of pin. 11. 4. ATM founds that pin is invalid.Use case specifications 11. .5 Post Conditions The user should not enter the pin number more than the number of trials. 11.1 Brief Description The pin entered may be wrong in that case transaction is cancelled.11. ATM blocks the card temporarily.
class diagram .
CLASS DIAGRAM ONLINE BANKING MANAGEMENT SYSTEM .
SEQUENCE DIAGRAMS & COLLABORATION DIAGRAMS SEQUENCE DIAGRAM ONLINE TRANSACTION SYSTEM .
COLLABORATION DIAGRAM ONLINE TRANSACTION SYSTEM .
SEQUENCE DIAGRAM .
CLIENT DESKTOP TRANSACTION SYSTEM .
COLLABORATION DIAGRAM CLIENT DESKTOP TRANSACTION SYSTEM .
SEQUENCE DIAGRAM LOGIN & LOGOUT TRANSACTION SYSTEM COLLABORATION DIAGRAM LOGIN & LOGOUT TRANSACTION SYSTEM .
SEQUENCE DIAGRAM ATM TRANSACTION SYSTEM .
COLLABORATION DIAGRAM ATM TRANSACTION SYSTEM .
SEQUENCE DIAGRAM CARD VALIDATION SYSTEM .
COLLABORATION DIAGRAM CARD VALIDATION SYSTEM SEQUENCE DIAGRAM PIN VALIDATION SYSTEM .
COLLABORATION DIAGRAM PIN VALIDATION SYSTEM SEQUENCE DIAGRAM WEB MERCHANT TRANSACTION SYSTEM .
COLLABORATION DIAGRAM WEB MERCHANT TRANSACTION SYSTEM .
ACTIVITY DIAGRAMS .
ACTIVITY DIAGRAM ONLINE TRANSACTION SYSTEM .
ACTIVITY DIAGRAM CLIENT DESKTOP TRANSACTION SYSTEM .
ACTIVITY DIAGRAM ATM TRANSACTION SYSTEM .
ACTIVITY DIAGRAM WEB MERCHANT TRANSACTION SYSTEM .
COMPONENT DIAGRAM .
COMPONENT DIAGRAM ONLINE BANKING MANAGEMENT SYSTEM .
DEPLOYMENT DIAGRAM .
DEPLOYMENT DIAGRAM ONLINE BANKING MANAGEMENT SYSTEM .
PACKAGE DIAGRAM PACKAGE DIAGRAM ONLINE BANKING MANAGEMENT SYSTEM .
State chart DIAGRAM STATE CHART DIAGRAM ATM TRANSACTION SYSTEM .
CLIENT DESKTOP TRANSACTION SYSTEM ONLINE TRANSACTION SYSTEM .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.