Beruflich Dokumente
Kultur Dokumente
Draw the following diagrams using Argo UML Case tool for an ATM Case Study;
Use Case Diagram
Class Diagram
DESCRIPTION
ATM Case Study has following classes:
Money, Message, Balances, Log, Status, Receipt, Cash Dispenser, Envelope Acceptor, Network
to bank, Customer Console, ATM, Card Reader, Operator Panel, Receipt Printer, Session, Card,
Transaction, Withdrawal, Deposit, Transfer, Inquiry, Account Information.
The classes Withdrawal, Deposit, Transfer, Inquiry are generalized into transaction.
The classes Cash Dispenser, Envelope Acceptor, Network to Bank are generalized into
Log.
The classes Card Reader, Customer Console, Cash Dispenser, Operator Panel, Network to
bank, Envelope Acceptor are aggregated into ATM class.
Withdrawal, Deposit, Transfer, Inquiry are dependent on Account Information.
Customer Console uses Receipt, Money, Balances, Receipt Printer.
Card Reader, Transaction, Session is dependent on card.
Transaction is aggregated into session and associated with ATM class.
Network to Bank uses status, Message, Balances.
Log class uses status, Message, Balnaces.
LABORATORY-2
Draw the following diagrams using Argo UML Case tool for an ATM Case Study;
Sequence Diagrams
Collaboration/Communication Diagram Activity diagram
Swim Lane Diagram
SEQUENCE DIAGRAM FOR STARTUP
Here first call is message which is equal to get specifies from customer method when
deposit is made.
There is another method of receipt as well associated with the first object
When the first method is invoked and done then the create message method is invoked
The envelope acceptor method is associated with the object envelope acceptor and it is
the third method in the sequence
Then the create receipt method is invoked and it is related to network to bank object and
receipt object
Later send method with message and balances as parameters is invoked which is the fifth
method and associated with message object
At last the receipt call is done with complete transaction method which is linked to
customer console object
When the money is deposited in a bank the following tasks are carried out
A message is generated by firstly taking the specifics from the customer, Envelope is
accepted from the envelope acceptor and a receipt is created by using network from the bank and
details like balances are obtained which are later sent in the message to the customer.
ACTIVITY DIAGRAM FOR A TRANSACTION
If the password is correct the transaction type will be asked else, a password not accepted
message will be shown and the password is asked again
Once the transaction type is taken then, the transaction is performed
If there are no more transactions the card is taken back by the customer
DESCRIPTION
The Swim Lane Diagram for withdrawal includes the participation of 3 objects: Customer,
ATM Machine and Bank.
This diagram shows the actions performed by each object and the flow of these actions.
The object Customer performs the following actions or makes use of the following Use cases:
Inserting/Taking the card
Enter PIN,
Enter Amount
Take Money.
The object ATM Machine makes use of the following Use cases:
Validate ATM Card, Show Balance, Eject Card.
The object Bank makes use of the following Use cases:
Authorize PIN, Check Balance, Debit Account.
The ATM Card is first inserted by the Customer, which the ATM validates. If invalid, the card is
ejected. If valid, the customer enters the PIN, which is authorised by the Bank. If the PIN is
valid, the Customer enters the Amount. The Bank checks the Balance in the Account and debits
the money accordingly. Transaction is completed and the card is ejected. Decision boxes after
each check-point continues the transaction or cancels it.
LABORATORY-3
STATE CHART DIAGRAMS
Demonstrate modelling the behaviour of the ATM system and sub systems by constructing state
chart diagram and construct the model using Argo UML case tool
STATE CHART DIAGRAM OF ATM
Demonstrate modelling the behaviour of an object (life cycle) using a state chart diagram and
construct the model using Argo UML case tool
STATE CHART DIAGRAM FOR MAINTENANCE OF ATM
LABORATORY-4
COMPONENT AND DEPLOYMENT DIAGRAMS
Draw the following diagrams using Argo UML Case tool for an ATM Case Study:
Component Diagram
Deployment Diagram
COMPONENT DIAGRAM-ATM
LABORATORY-5
TEST DESIGN
Design test cases for the use cases shown in Figure 12. by creating a test case sheet. Design at
least two test cases, one for normal flow of control and one for any exception that may occur.
Use Case
Test Case
Precondition
Input Conditions
Expected Output
System is OFF
Activate ON
switch
System shut
down
Session
System is OFF
System is ON
Activate OFF
switch
Insert ATM card
System is ON
Session
Session
System displays
transaction types
Perform a
transaction
Session
System is asking
whether customer
wants another
transaction
NO
Customer chooses
withdraw
Customer chooses
withdraw
Customer enters an
amount to withdraw
Customer enters an
amount to withdraw
Customer chooses
deposit
Customer chooses
deposit
Customer enters an
amount to deposit
Customer enters an
amount to deposit
Transfer
Customer chooses
transfer.
Transfer
Customer chooses
transfer
Inquiry
Session
Transaction
Transaction
Withdraw
Withdraw
Deposit
Deposit
System is in
working
Condition
System is off
Card is accepted.
Enter the PIN
Card is
unaccepted.
Reject the card
System displays
menu of
transaction types
System asks
whether need
another type of
transaction
System ejects a
card and can start
a new session
Cash Dispenser
dispenses cash
Error
No sufficient
Balance
Amount is
deposited
Amount selected
is below the
deposit limit
Successful
transaction
Account Number
is Incorrect
Statement is
displayed