Scribd
Upload
6 views

Software Engineering Notes-2

Uploaded by

riamadan7010
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views

Software Engineering Notes-2

Uploaded by

riamadan7010
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Submitted by: Ria 102299002 3EM3

EXPERIMENT:2
NAME OF EXPERIMENT: Use case diagram for ATM System.
AIM: To design and implement Use case diagram for ATM System.
SOFTWARE USED:- STAR UML
THEORY: A Use case Diagram is a diagram that shows a set of Use cases and actors
and their relationships. These diagrams are used to model the static use case view
of a system.
To model a system the most important aspect is to capture the dynamic behavior.
To clarify a bit in details, dynamic behavior means the behavior of the system when
it is running /operating. So only static behavior is not sufficient to model a system
rather dynamic behavior is more important than static behavior. In UML there are
five diagrams available to model dynamic nature and use case diagram is one of
them. Now as we have to discuss that the use case diagram is dynamic in nature
there should be some internal or external factors for making the interaction. These
internal and external agents are known as actors. So, use case diagrams are consists
of actors, use cases and their relationships. The diagram is used to model the
system/subsystem of an application. A single use case diagram captures a
particular functionality of a system. So, to model the entire system numbers of use
case diagrams are used.
Purpose:
The purpose of use case diagram is to capture the dynamic aspect of a system. But
this definition is too generic to describe the purpose. Because other four diagrams
(activity, sequence, collaboration and State chart) are also having the same
purpose. So, we will look into some specific purpose which will distinguish it from
other four diagrams. Use case diagrams are used to gather the requirements of a
system including internal and external influences. These requirements are mostly
design requirements. So, when a system is analyzed to gather its functionalities use
cases are prepared and actors are identified.

So, in brief, the purposes of use case diagrams can be as follows:


 Used to gather requirements of a system.
 Used to get an outside view of a system.
 Identify external and internal factors influencing the system.
 Show the interacting among the requirements are actors.

Withdrawal Use Case:


A withdrawal transaction asks the customer to choose a type of account to
withdraw from (e.g. checking) from a menu of possible accounts, and to choose a
dollar amount from a menu of possible amounts. The system verifies that it has
sufficient money on hand to satisfy the request before sending the transaction to
the bank. (If not, the customer is informed and asked to enter a different amount.)
If the transaction is approved by the bank, the appropriate amount of cash is
dispensed by the machine before it issues a receipt. A withdrawal transaction can
be cancelled by the customer pressing the Cancel key any time prior to choosing
the dollar amount

Deposit Use Case


A deposit transaction asks the customer to choose a type of account to deposit to
(e.g. checking) from a menu of possible accounts, and to type in a dollar amount on
the keyboard. The transaction is initially sent to the bank to verify that the ATM can
1
Submitted by: Ria 102299002 3EM3

accept a deposit from this customer to this account. If the transaction is approved,
the machine accepts an envelope from the customer containing cash and/or checks
before it issues a receipt. Once the envelope has been received, a second message is
sent to the bank, to confirm that the bank can credit the customer‘s account –
contingent on manual verification of the deposit envelope contents by an operator
later.
A deposit transaction can be cancelled by the customer pressing the Cancel key any
time prior to inserting the envelope containing the deposit. The transaction is
automatically cancelled if the customer fails to insert the envelope containing the
deposit within a reasonable period of time after being asked to do so.
Transfer Use Case
A transfer transaction asks the customer to choose a type of account to transfer
from (e.g. checking) from a menu of possible accounts, to choose a different
account to transfer to, and to type in a dollar amount on the keyboard. No further
action is required once the transaction is approved by the bank before printing the
receipt.
A transfer transaction can be cancelled by the customer pressing the Cancel key
any time prior to entering a dollar amount.
Inquiry Use Case
An inquiry transaction asks the customer to choose a type of account to inquire
about from a menu of possible accounts. No further action is required once the
transaction is approved by the bank before printing the receipt. An inquiry
transaction can be cancelled by the customer pressing the Cancel key any time
prior to choosing the account to inquire about.
Validate User use case:
This use case is for validate the user i.e. check the pin number, when the bank
reports that the customer‘s transaction is disapproved due to an invalid PIN. The
customer is required to re-enter the PIN and the original request is sent to the bank
again. If the bank now approves the transaction, or disapproves it for some other
reason, the original use case is continued; otherwise, the process of re-entering the
PIN is repeated. Once the PIN is successfully re-entered
Print Bill use case
This use case is for printing corresponding bill after transactions (withdraw or deposit
or balance enquiry or transfer) are completed.
Update Account
This use case is for updating corresponding user accounts after transactions (withdraw
or deposit or transfer) are completed.

FLOWCHART:

2
Submitted by: Ria 102299002 3EM3

RESULT
Hence we have drawn the use case for the atm system

You might also like