Assignment 1: Write problem statement to define the project title with bounded scope of the project.

Ans. :

AIM : To prepare PROBLEM STATEMENT for any project.

Theory :

The problem statement is the initial starting point for a project. It is basically one to three page
statement that everyone on the project agrees with that describe what will be done at a high level. The
problem statement is intended for a broad audience and should be written in non-technical terms. It
helps the non-technical and technical terms. It helps the non-technical and technical personnel.
Communicate by providing a description of a problem. It doesn’t describe the solution to the problem.

The project entitled ATM system has drastic change to that of the older version of banking system,
customer feel inconvenient with the transaction method as it was in the hands of the bank employees.
In the hands of the bank employees.

In our ATM system, the above problem is overcome here, the transaction are done in person by the
customer thus makes the customers feel safe and secure.

Thus application of our system helps the customer in checking the balance and transaction of the
amount by validating the pin number therefore ATM system is more users friendly.

Assignment 2: Select relevant process model to define activates and related tasks set for assigned
project.

Ans. :

Waterfall Model

 Waterfall model is the first approach used in software development process.

 It is also called as classical life cycle model or linear sequential model.
 In waterfall model any phase of development process begins only if previous phase is
completed.
1. Requirement Analysis
 In this phase all business requirements of system are gathered and analyzed by
communication between stakeholders and customer or user.
 At the end of this phase requirement specification documents is created.
2. Design
 Based on requirement specification document design of system is created called
software architecture.
 It is blue print of system representing system’s internal structure and behavior.
 It is responsibility of developer.
 3. Verification/Testing
 Here coding or job done by developer is verified against requirement
of user in order to ensure that software will satisfy all business
requirements of user.
 After the successful verification software is deployed at user’s site for
their use.
4. Maintenance
 While using software if user faces some problems, then those problems must be
solved time by development team. This task comes under maintenance of
software.
 Maintenance also includes adding new functionalities in software as per user
requirements.

Assignment 3: Gather application specific requirements for assimilate into RE (Requirements

Engineering) model.

Ans. :

Functional Requirements

The functional requirement are organized in two sections; Requirements of the ATM and
Requirements of the bank computer.

1. Requirements of the ATM

 Authorization process
 Transaction (withdrawal process)
2. Requirements of the bank computer
 Authorization process(bank code password)
 Transaction
Non-functional Requirements
The non-function requirement is bellowed.
 The ATM network has to be available 24 hours a day.
 Each bank may be processing transactions from several ATMs at the same time.
 The ATM must be able to use several date formats according to the data
formats according to the data format that are provided by the database of
different banks

Assignment 4 :: prepare broad SRS (Software Requirement specification) for the above selected project.

Ans.:

SRS for ATM

 1) Introduction
The software ATMExcl3.0TM version 1.0 is to be developed for automated Teller Machine
(ATM).
As Automated Teller Machine (ATM) Is computerized Automated Teller Machine (ATM) is
computerized telecommunications device that provides a financial institution’s customers a
secure method of performing financial transactions, in a public space Without the need for a
human bank teller. Through ATMExcl 3.0M , customers interact with a user-friendly interface
that enable them to access their bank accounts and perform various transactions.

Purpose
This SRS defines External Interface, performance and software system attributes requirements
of ATMExcl3.0TM This document is intended for the following group of people:
 Developers for the purpose of maintenance and few release of the software.
 Management of the bank.
 Documentation writers.
 Testers.

Scope


This document applies to Automated Teller Machine Software ATM 3.0M. This
software facilitates the user to perform various transaction in his account without
going to bank this software offers benefits such cash withdrawals, balance transfers,
deposits, inquiries, credit card advances and other banking related operations for
customers.
 It also allows the administrator to fix the tariffs and rules as and when required.
 The software takes as input the login Id and bank account number of the user login
purposes.
 The output then comprise of an interactive display that lets the user select the
desirable function that he wants to perform.
2) The Overall Description

Product Perspective

 The ATM is a single functional unit consisting of various sub components.

 This software allows the user to access their bank accounts remotely through ATM
without any aid of human bank teller.
 This software also allows performing various other functions apart from just accessing
his bank account such as mobile bill clearings etc.
 Some of its hardware components are cassettes, memory, drives , dispensers I.e. for
receipts and cash, a card port, a network port and disks .
 The ATM communication with the bank’s central server through a dial-up
communication link.
  The memory of the system shall be 20MB.
 The Cassette capacity shall be a least 200 notes.

Product function

The major functions that ATMExcl3.0 performs are described as follows:

 Language Selection : After the user has logged in, the display provided him with a list of
languages from which he can select any one in order to interact with the machine
throughout that session.
 After the language selection the user is prompted with an option that whether he wants
the selected language to be fixed for future use so that he is not offered with the language
selection menu in future thus making the transaction a bit faster.
 User al so has the freedom to switch to a different language mentioned in the list in
between that session.
 Account Maintenance: The various functions that a user can perform with his account are
as follow:

 Account Type: The user has the freedom to select his account type to which all the
transactions are made, I.e. he can select whether the account is current account or
savings account etc.
 Withdrawal/Deposit : The software allows the user to select the kind of operation
to be performed i.e. whether he wants to withdraw or deposit the money.
 Amount : The amount to be withdrawal or deposited is then mentioned by the
user.
 Denomination: The user is also provided with the facility to mention the required
denominations. Once he enters his requirements the machine goes through its
calculations on the basis of current resources of check whether it is possible or
not. IF other possible alternatives are displayed.
 Money Deposition: Money deposition shall be done with an envelope. After
typing the amount to be deposited and verification of the same, the customer
must insert the envelope in the depositary.
 Balance Transfer :Balance transfer shall be facilitated between any two accounts
linked to the card for example saving and checking account.
 Balance Enquiry : Balance enquiry for any account linked to the card shall be
facilitated.

 Billing :
Any transaction shall be recorded in the form of a receipt and the same would be
dispensed to the customer. The billing procedures are handled by the billing module that
enable user to choose whether he wants the printed statement of the transaction or just
the updating his account.
  Cancelling
The customer shall abort a transaction with the press of a Cancel key. For example on
entering a wrong deposition amount. In addition the user can also cancel start fresh session
all over again.

Constraints

The major constraints that the project has are as follows:

 The ATM must service at most one person at a time .

 The number of invalid pin entries attempted must not exceed three. After three
unsuccessful login attempts, the card is seized/blocked and need to be unlocked by the
bank.
 The simultaneous access to an account through both, the ATM and the bank is not
supported.
 The minimum amount of money a user can withdraw is Rs 100 / and the maximum amount
of money a user can withdraw in a session is Rs.!0,000/ and the maximum amount of
Rs.1000/is left in the user’s account after the withdrawal failing which withdrawal is
denied.
 The minimum amount a user can deposit is Rs. 100 / and the maximum amount of he can
deposit is Rs.1000/.
 A user can select only that cellular operator for mobile bill clearings that is supported by
the bank.
 The software requires a minimum memory of 20 GB
 There shall be a printer installed with the machine to provide the user with the printed
statement of the transaction . For voice interactions, speakers should also be there to
accompany the machine

3. External Interface Requirements

 The interface provided to the user should be a very user friendly one and it should provide
an option an op0tional interactive help for each of the service listed . The interface
provided is a menu driven one and the following screens will be provided:

1) A login screen is provided in the beginning for entering the required username/pin
no. and account number.
2) An unsuccessful login leads to reattempt (maximum three) screen for again
entering the same information. The successful login leads to a screen displaying a
list of supported language form which user can selected any one.
3) In the case of administrator, a screen will be shown having options to reboot
system, shut down system, block system, and disable any service.
 4) In case of reboot/shut down, a screen is displayed to confirm the user’s will to
reboot and also allow the user to take any backup if needed.
5) In case of blocking system, a screen is provided asking for the card no. By entering
the card no of a particular user, system access can be blocked for him.
6) Administrator is also provided with a screen that enables him to block any service
provided to the user by enter in the name of the service or by selecting it from the
list displayed.
7) After the login, a screen with a number of options is then shown to the user. It
contains all the options along with their brief description to enable the user to
understand their functioning and select the proper option.
8) A screen will be provided for user to check his account balance.
9) A screen will be provided that displays the location of all other ATMs of same bank
elsewhere in the city.
10) A screen will be provided for the user to perform various transaction in his account.

4. System features

1) Validity Checks
2) In order to gain access to the system, the user is required to enter his/her
correct user id/pin no and account no failing which his card may be blocked.
3) The user can access only one account at a time and can enter only one
account no.
4) Also if the user is an administrator, he is required to enter his login id in order
to access and change the facilities provided by the system.

5. Sequencing information

1) The information about the users and their account should be entered into
the database prior to any of the transactions and the backup be maintained
for all account information .

6. Error Handling/Response t Abnormal situations

1) If any of the above validation/sequencing flow does not hold true,

appropriate error message will be prompted to the user for doing the
needful.
7. Receipt Generation

1) After each transaction user has performed , a receipt is generated that

contains all the information about the transaction.
Assignment 5: Prepare Use-cases
cases and draw use-case
use case diagram using software modeling tool.

Ans. :

Use case diagram for ATM

1) First click on the actor icon on the tool palette, then click on the diagram an
done actor symbol should appear. Repeat this to create the second actor.

2) Enter the name of the actor.

3) To add use cases essentially follow the same procedure as we did for the
actors, click on the use case icon on the palette within click within the
diagram. Give name.

4) Repeat this to create other use cases.

5) To connect the actors to the use cases, select association. Then click on the
actor, hold down the mouse button and the mouse arrow to the
appropriate use case.
6) Complete the diagram by using a package to represent the system
boundary. We can resize any object by clicking on it and there dragging on
one of the corners with the mouse. We can delete any object by selecting it
and pressing the delete key.