Professional Documents
Culture Documents
<<include>>
<<extend>>
invalid card insert card retail institution
user invalid pin
<<include>>
<<extend>>
invalid login
online transaction
bank employee <<extend>>
web merchant <<include>> Bank Database
<<include>>
login logout
<<include>> <<include>>
Flow of Events
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.
Client 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 Events
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.
Flow of Events
If in the basic flow, the details specified by user are invalid the he is informed
that his login is failed.
None.
4. Logout- Use case specifications
The 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 Events
If in the basic flow, if the internet connection is lost user must refresh the page
again.
None.
5. Invalid Login- Use case specifications
Flow of Events
None.
None.
Flow of Events
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.
The user has to sign in the receipt and put a copy of receipt with him for security
reasons.
Flow of Events
If in the basic flow, the card or pin is invalid a receipt ejects out from ATM in
response to the error.
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
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.
None.
9. Invalid card - Use case specifications
The 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 Events
Even after reinserting the card, if the card is invalid ATM (Card reader) gives a
receipt indicating that the card is invalid.
None.
10. Pin validation - Use case specifications
After 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 Events
If the pin is invalid, ATM ejects the card and gives a receipt indicating
the error number.
None.
11. Invalid Pin - Use case specifications
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 Events
The user should not enter the pin number more than the number of trials.
+transfercash()
Sequence Diagrams
and
Collaboration Diagrams
transaction
1 : loginRequest()
2 : validity()
3 : profileRequest()
4 : display()
5 : transferRequest()
6 : transfer()
7 : succed()
8 : acknowledgement()
9 : transferRequest()
1 : login request()
4 : display()
7 : succeed()
9 : transfer request()
2 : validity()
3 : profile request()
5 : transfer request() 8 : acknowledgement()
transaction 6 : transfer()
transaction
1 : login request()
2 : validity()
3 : menuChoice()
4 : proceedTransaction()
5 : accountInfo()
6 : succed()
7 : menuChoice()
8 : proceedTransaction()
8 : transaction proceed()
4 : proceed transaction()
5 : account info()
3 : choice menu()
2 : validity() 6 : succeed()
7 : choice menu()
transaction
1 : enterId&Pswrd()
2 : verify()
3 : validity()
4 : logout()
5 : reqLogout()
7 : loggedout() 6 : succeded()
2 : verify()
1 : enter id pwd() network to bank
desktop front end
3 : validity()
1 : insert card()
2 : validation()
3 : verified()
4 : ChoiceMenu()
5 : selectservice()
6 : accountInfo()
7 : feasibility()
8 : give receipt()
9 : another transaction()
3 : verified() 7 : feasibility()
9 : another trans()
8 : give receipt()
6 : account info()
2 : validation()
5 : select service()
transaction
Card Validation Sequence Diagram:
card validation
sequence diagram
1 : insert card()
2 : validation()
3 : card valid()
4 : eject card()
1 : enterpin()
2 : pin validation()
3 : validity()
4 : choiceMenu()
1 : gives card()
2 : insert card()
3 : validation()
4 : verified()
5 : enter amount()
7 : give receipt()
7 : give receipt()
3 : validation()
4 : verified()
6 : update bank DB()
bank network
Activity Diagrams
Online Transaction Activity Diagram:
no
valid login
furnish details
yes
choice menu
no
valid details
yes
finished
Client Desktop Transaction Activity Diagram:
employee login
no
valid login
yes
choice menu
proceed transaction
ATM Transaction Activity Diagram:
employee login
no
valid login
yes
choice menu
proceed transaction
Web Merchant Transaction Activity Diagram:
insert card
no
card valid
yes
enter amount
no
sufficient bal
yes
proceed transaction
take receipt
finish
Component Diagram for Banking System:
ATM transaction
Account info
Employee console
Card reader Bank Database
webmerchant transactrion
Customer may be
ATM card holder,
ATM Machine
credit/debit card holder or
providing services of
an online user of
ATM transaction
a Bank
ATM Machine
Customer Console Bank Database
keeping the details of
each and every account
Client Desktop
providing services of
banking at desks