Bank Management
24
BANK MANAGEMENT (Mini-project) By G.SHAKIR Use Case Modeling Use Case diagram for Banking 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
-
Upload
rarhikrish8480 -
Category
Documents
-
view
214 -
download
0
Transcript of Bank Management
BANK MANAGEMENT(Mini-project)By G.SHAKIR
Use Case ModelingUse Case diagram for Banking System:
1. Online Transaction – use case specifications1.1 Brief DescriptionAccount 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 Events1.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.
2. Client Desktop transaction- Use case specifications2.1 Brief DescriptionClient desktop is given to each of bank employees and they are provided with account logins with a user id and a password. Every employee switches on his desktop and login to his account through which he can communicate with bank database.
An employee can have operations like withdrawal of money, giving loans, furnishing the DD/cheque and customers may want to deposit money.
Bank employee is allowed to modify the database accordingly. And the intended services are provided to the customers.
Flow of Events2.2 Basic flow
1. Employee enters his username and password.
2. Bank Database validates the employee.
3. On success employee can withdraw or deposit money, issue loans and
DD/cheque to the customers.
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 .Then the person is not employee of the bank and he is not having authority to perform those actions.
2.4 Pre Conditions
The employee must possess a account login and password.
2.5 Post Conditions
The account database is modified after transaction. Employee issues dd/cheque to user.
3. Login- Use case specifications3.1 Brief DescriptionThe online customer or a bank employee has to login to access their accounts from bank database. A vendor is provided for communication with bank’s database and this vendor provides safety and atomicity. A user may be an invalid user so the system has to prompt the person appropriately.
Flow of Events3.2 Basic flow
1. User enters username and password.
2. Bank Database validates the user.
3. On success user can precede the transaction.
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.
3.4 Pre Conditions
The user must possess a login id and password.
3.5 Post Conditions
None.
4. Logout- Use case specifications4.1 Brief DescriptionThe person who ever logged in to the system or bank database has to logout after all the work is over. The vendor provided for communication is now closed from database.
Flow of Events4.2 Basic flow
1. User clicks the logout
2. All the transactions he performed are reflected in the bank database.
4.3 Alternate Flow
If in the basic flow, if the internet connection is lost user must refresh the page again.
4.4 Pre Conditions
The user should have been logged in already.
4.5 Post Conditions
None.
5. Invalid Login- Use case specifications5.1 Brief DescriptionIf a person with a invalid user id or password details want login to the system, the system has to prompt the person about failure and should not open the vendor of communication until he furnishes valid user id & password.
Flow of Events5.2 Basic flow
1. User enters username and password.
2. Bank Database validates that the login is invalid.
3. Further he may not be allowed to proceed until enters a valid login.
5.3 Alternate Flow
1. If the user enters a valid login he must be allowed to proceed further.
5.4 Pre Conditions
None.
5.5 Post Conditions
None.
6. Card transaction – Use case specifications6.1 Brief DescriptionCard transaction includes a credit/debit card. This service is provided by a retail institution to a card holding customer. The customer may want to buy any thing form merchant, 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. A credit card will have a
credit amount you can deduct amount more than that. A debit card will be having some level of funds if the funds are over the transaction will not continue.
Flow of Events6.2 Basic flow
1. The retailer places the card in card reader.
2. Card reader checks the card validity after that retailer asks the customer
to enter pin number.
3. After entering the pin number retailer enters amount to be paid by customer.
4. Card reader proceeds transaction after that it updates bank Database
and finally gives a receipt to customer.
6.3 Alternate Flow
If in the basic flow, 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.
6.4 Pre Conditions
The User must possess a debit/credit card.
6.5 Post Conditions
The user has to sign in the receipt and put a copy of receipt with him for security reasons.
7. ATM transaction- Use case specifications7.1 Brief DescriptionIf a customer approaches an ATM, the person is requested to insert card. After inserting the card it is checked for validity if the card is valid transaction continues. And then pin validation is done; if the pin is invalid the transaction is doesn’t allowed. The customer may
have transactions like checking balance, draw amount and donation. If there are less funds the transaction is sustained.
Flow of Events7.2 Basic flow
1. User inserts card in ATM.
2. Bank Database validates the card.
3. On success employee must enter pin and select from his list of services
appeared on the screen.
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.
7.4 Pre Conditions
The User must possess an ATM card
7.5 Post Conditions
The user must take the receipt.
8. Insert card – Use case specifications8.1 Brief DescriptionThe 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 outFlow of Events8.2 Basic flow
1. Customer inserts card in ATM or Card reader
2. ATM or Card reader validates the card.
3. 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.
8.4 Pre Conditions
The User must possess an ATM card or else a debit/credit card.
8.5 Post Conditions
None.
9. Invalid card – Use case specifications9.1 Brief DescriptionThe card inserted will be checked for validation. The card may not be inserted properly or it may be out of date or it can be an invalid for specific bank. In those situations it is requested for re-insert.
Flow of Events9.2 Basic flow
1. Customer inserts card in ATM or swipes in Card reader.
2. ATM (Card reader) validates the card is invalid.
3. Customer must re-insert (swipe) the card again.
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.
9.4 Pre Conditions
The User must possess an ATM card or a credit/debit card.
9.5 Post Conditions
None.
10. Pin validation – Use case specifications10.1 Brief DescriptionAfter inserting the card and if it is checked for validation, the user is requested for pin. The pin is itself present on magnetic strip on back of card and it is checked with the entered one.Flow of Events10.2 Basic flow
1. Customer inserts card in ATM and enter his pin number.
2. ATM validates the pin.
3. On success user can precede the transaction
10.3 Alternate Flow
If the pin is invalid, ATM ejects the card and gives a receipt indicating
the error number.
10.4 Pre Conditions
The User must possess an ATM card.
10.5 Post Conditions
None.
11. Invalid Pin – Use case specifications11.1 Brief Description
The pin entered may be wrong in that case transaction is cancelled. The customer is requested for re-inserting of card and re-entry of pin. The number of wrong trials may be limited according to bank’s specifications.Flow of Events11.2 Basic flow
1. Customer inserts card in ATM and enter his pin number.
2. ATM founds that pin is invalid.
3. The customer requested to reinsert card or reenter the pin.
4. In case the number of trials exceeded, ATM blocks the card temporarily.
11.3 Alternate Flow
If customer enters a correct pin transaction proceeds further.
11.4 Pre Conditions
The User must possess an ATM card.
11.5 Post Conditions
The user should not enter the pin number more than the number of trials.
Class Diagram for Banking System:
Sequence DiagramsandCollaboration DiagramsOnline Transaction Sequence Diagram:
Online Transaction Collaboration Diagram:
Client desktop Transaction Sequence Diagram:
Client desktop Transaction Collaboration Diagram:
Login & Logout Sequence Diagram:
Login & Logout Collaboration Diagram:
ATM Transaction Sequence Diagram:
ATM Transaction Collaboration Diagram:
Card Validation Sequence Diagram:
Card Validation Collaboration Diagram:
Pin Validation Sequence Diagram:
Pin Validation Collaboration Diagram:
Web merchant Transaction Sequence Diagram:
Web merchant Transaction Collaboration Diagram:
Activity DiagramsOnline Transaction Activity Diagram:
Client Desktop Transaction Activity Diagram:
ATM Transaction Activity Diagram:
Web Merchant Transaction Activity Diagram:
Component Diagram for Banking System:
Deployment Diagram for Banking System:
