I011 SPM Lab 2 Naman Chaware

Lab: 2
Software Project Management
Aim: Preparing Software Requirements Specification document on the following points as
mentioned below.
i. Identify the product whose software requirements are specified
I have chosen Banking system (ATM) software.

ii. Describe any standards or typographical conventions to be followed

 Users should abide to government norms to be followed in banking capacity.
 All users must be 18+ or should have adult guardian.
 Watch out for additional charges and penelties.
 All the information will depend on what it is provided by Government and the RBI.

iii. Describe the different types of reader that the document is intended for\, such as
developers, project managers, marketing staff, users, testers, and documentation
writers
The intended audience of this SRS consists of:
 Software designers
 Systems engineers
 Software developers
 Software testers
 Customers

iv. Discuss briefly the software being specified and its purpose, including relevant
benefits, objectives, and goals.
Product Perspective: -
An automated teller machine (ATM) is a computerized telecommunications device that
provides the customers of a financial institution with access to financial transactions in a
public space without the need for a human clerk or bank teller. On most modern ATMs,
the customer is identified by inserting a plastic ATM card with a magnetic stripe or a
plastic smartcard with a chip, that contains a unique card number and some security
information, such as an expiration date or CVC (CVV). Security is provided by the
customer entering a personal identification number (PIN).

Product Functions: -
Using an ATM, customers can access their bank accounts in order to make cash
withdrawals (or credit card cash advances) and check their account balances.
The functions of the system are:
1. Login
2. Get Balance Information
3. Withdraw Cash
4. Transfer Funds

1
I011 SPM Lab 2 Naman Chaware

v. Identify the positives and limitations available to the developers

Login:
Validate Bank Card
• Validate for Card Expiration Date
• Validate that the card's expiration date is later than today's date
• If card is expired, prompt error message "Card is expired"
Validate for Stolen or Lost Card
• Validate that the card is not reported lost or stolen
• If card is lost, prompt error message, "Card has been reported lost"
• If card is stolen, prompt error message, "Card has been reported stolen"
Validate for Disabled Card
• Validate that the card is not disabled
• If card is disabled, prompt error message, "Card has been disabled as of
<expiration date>"
Validate for Locked Account
• Validate that the account is not locked
• If account is locked, prompt error message "Account is locked"
Validate PIN
• Validate that the password is not blank
• If PIN is blank, prompt error message "Please provide PIN"
• Validate that the password entered matches the password on file
• If password does not match, prompt error message "Password is Incorrect
Lock Account
• If number of consecutive unsuccessful logins exceeds three attempts, lock
account
• Maintain Consecutive Unsuccessful Login Counter
• Increment Login Counter
• For every consecutive Login attempt, increment logic counter by 1.
• Reset login counter to 0 after login is successful.
• Get Balance Information
• Withdraw Cash
• Transfer Funds

vi. List the user documentation components to be delivered with the software
User manual, Safety manual and the terms and conditions.

vii. Highlight the assumed factors that could affect the requirements stated in the SRS
• Hardware never fails
• ATM casing is impenetrable
• Limited number of transactions per day (sufficient paper for receipts)
• Limited amount of money withdrawn per day (sufficient money)
viii. Describe the logical and physical characteristics of each interface used in the
project
User interfaces:
The customer user interface should be intuitive, such that 99.9% of all new ATM
users are able to complete their banking transactions without any assistance.
Hardware interfaces:

2
I011 SPM Lab 2 Naman Chaware

The hardware should have following specifications:

• Ability to read the ATM card
• Ability to count the currency notes
• Touch screen for convenience
• Keypad (in case touchpad fails)
• Continuous power supply
• Ability to connect to bank„s network
• Ability to take input from user
• Ability to validate user
Software interfaces:
The software interfaces are specific to the target banking software systems. At present,
two
known banking systems will participate in the ATM network.
• State Bank
• Indian Overseas Bank

ix. Illustrates the functional requirements for the product by system features, the
major services provided by the product.
The hardware, software and technology used should have following specifications:
• Ability to read the ATM card.
• Ability to count the currency notes.
• Touch screen for convenience.
• Keypad (in case touchpad fails)
• Continuous power supply.
• Ability to connect to bank’s network.
• Ability to validate user.

x. Enlist the non-functional requirements like performance, safety, security, software

quality attributes, business rules
Safety Requirements: -
• Must be safe kept in physical aspects, say in a cabin
• Must be bolted to floor to prevent any kind of theft
• Must have an emergency phone outside the cabin
• There must be an emergency phone just outside the cabin
• The cabin door must have an ATM card swipe slot
• The cabin door will always be locked, which will open only when user swipes his/her
ATM
• card in the slot & is validated as genuine
Security Requirements: -
• Users accessibility is censured in all the ways
• Users are advised to change their PIN on first use
• Users are advised not to tell their PIN to anyone
• The maximum number of attempts to enter PIN will be threeUser interfaces:

3
I011 SPM Lab 2 Naman Chaware

xi. Cite relevant literature and use proper appendix