Scribd
Upload
5 views

Lab No-2

The document describes the functional requirements and classes for an ATM system. It specifies that the ATM is associated with one bank and allows customers to perform various transaction types through a card verification process, interface, and connections to the bank. Key requirements include card verification, performing transactions, printing receipts, canceling transactions, retaining cards after failed attempts, and transferring transaction information to the bank each night. The classes identified are Card, ATM, Customer, Bank, Employee, Transaction, Receipt, and Session, with attributes specified for each.

Uploaded by

رحمت خان
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

Lab No-2

The document describes the functional requirements and classes for an ATM system. It specifies that the ATM is associated with one bank and allows customers to perform various transaction types through a card verification process, interface, and connections to the bank. Key requirements include card verification, performing transactions, printing receipts, canceling transactions, retaining cards after failed attempts, and transferring transaction information to the bank each night. The classes identified are Card, ATM, Customer, Bank, Employee, Transaction, Receipt, and Session, with attributes specified for each.

Uploaded by

رحمت خان
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Lab No.

2 8/11/2023
Class Diagrams
• The ATM is associated with only one bank
o It gives access to all the accounts the customer owns in the bank
• Several types of transactions can be chained in a single session
o Withdrawal, deposit, transfer between the customer's own accounts, consulting an
account
o The customer may obtain a printed receipt for each transaction
• The card contains
o an ID number
o an expiration date
o a secret code
• The card must be verified by the ATM
o The customer cannot make more than 3 attempts to enter the correct code, otherwise the
card is swallowed
• Interface
o Keyboard and screen, with menus
o The customer may cancel the current transaction at meaningful points
• The connections with the bank are kept to a minimum
o When a session is opened, a connection makes it possible to known all the accounts the
customer owns
o Every night, the information about the current day transactions are transferred to the bank
• From time to time an employee manually
o empties the machine and/or fills it with bank notes
o Supplies consumables and does any maintenance that may be needed.

Extract the functional requirements from the above case study.

Functional requirements
Card Verification:
The system must verify the customer's card by checking the ID number, expiration date, and
secret code.
Perform Transactions:
The system must allow customers to perform various transactions such as withdrawal, deposit,
transfer between accounts, and account inquiry.
Print Receipt:
The system must provide an option for the customer to obtain a printed receipt for each
transaction.
Cancel Transaction:
The system must allow customers to cancel the current transaction at meaningful points without
any adverse effects.
Card Retention:
If the customer enters an incorrect PIN more than three times, the system must retain the card.
A connection to the bank must be established when a session is opened to retrieve information
about the customer's accounts.
Session Initialization:
The system must transfer information about daily transactions to the bank every night.
Manual Maintenance:
The system must support manual maintenance activities performed by an employee, including
emptying the machine, filling it with banknotes, supplying consumables, and performing any
needed maintenance.
Transfer Transactions to the bank:
The system must transfer information about daily transactions to the bank every night.

Write down the classes and their attributes separately.


Card:
• ID number
• Expiration date
• Secret code
ATM:
• Connection status
• Transaction history
• Maintenance status
Customer:
• Account information
• Transaction history
Bank:
• Account database
• Daily transaction records
Employee:
• Maintenance tools
• Maintenance schedule
Transaction:
• Type (withdrawal, deposit, transfer, inquiry)
• Amount
• Timestamp
Receipt:
• Transaction details
• Timestamp
Session:
• Start time
• End time
• Connection details
Draw the class diagram of the above case study and show the
relationship between classes.

You might also like