Scribd
Upload
26 views11 pages

A1222573634 31139 6 2024 SRSTemplate

For software engineering subject

Uploaded by

nitaspirant81
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
26 views11 pages

A1222573634 31139 6 2024 SRSTemplate

For software engineering subject

Uploaded by

nitaspirant81
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 11
Software Requirements Specification for Version 1.0 approved Prepared by Copyright © 2024 Software Requirements Specification for Page 1 1. Introduction 1.1 Purpose This document describes the software requirements and specification for an automated teller machine (ATM) network. 1.2 Document Conventions Page 2 to process accounts, but we are only concerned with the one that interacts with the network. = Cash Card ‘Acard assigned to a bank customer that authorizes access to accounts using an ATM. Machine. Each card contains a bank code and a card number, coded in accordance with national standards on credit cards and cash cards. The bank code uniquely identifies the bank within the consortium. The card number determines the accounts that the card can access. A card does not necessarily access all of a customer's accounts. Each cash card is owned by a single customer, but multiple copies of it may exist, so the possibility of simultaneous use of the same card from different machines must be considered. * Customer The holder of one or more accounts in a bank. A customer can consist of one or more Persons or corporations, the correspondence is not relevant to this problem. The same person holding an account at a different bank is considered a different customer. “Transaction 2 single integral request for operations on the accounts of a single customer. We only specified that ATMs must dispense cash, but we should not preclude the possibility of printing checks or accepting cash or checks. We may also want to provide the flexibility to operate on accounts of different customers, although it is not required yet. The different operations must balance properiy. 1.4.2 Abbreviations Throughout this document the following abbreviations are used: k: is the maximum withdrawal per day and account. m: Is the maximum withdrawal per transaction. 1: Is the minimum cash in the ATM to permit a transaction. t + is the total fund in the ATM at start of day. 1.5 Project Scope The software supports a computerized banking network. The network enables customers to ‘complete simple bank account services via automated teller machines (ATMs) that may be located off premise and that need not be owned and operated by the ‘customer's bank. The ATM identifies a customer by a cash card and password. It collects information about a simple account transaction (e.g., deposit, withdrawal, transfer, bill payment), communicates the transaction information to the customer's bank, and dispenses cash to the customer. The banks provide their own software for their own computers. The bank software requires appropriate record keeping and security provisions. The software must handle concurrent accesses to the same account correctly. Software Requiremems Specification for Page 3 1.6 References «List any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access @ copy of each reference, including title, author, version number, date, and source or location.> 2. Overall Description 2.1 Product Perspective ‘The ATM network does not work independently. It works together with the banks’ computers and the software run by the network's banks. ‘Communication interface The ATMs communicate with the banking systems via a ‘communication network. Software interface ‘The messages sent via the communication network are specific to the target banking software systems. At present, two known banking systems will participate in the ATM network. Hardware interface The software will run on an ATM computer yet to be chosen. User interfaces Customer 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. Bank Security Personnel Bank security personnel are responsible for removing deposits and adding cash to ATMs. There should be a simple interface (€.g., a switch or button) that they can use to initialize the ATM Whenever they restock. Maintainer The maintainer is responsible for adding new ATMs to the network and servicing existing ATMs. A maintainer should be possible to add a new ATM to the network within 1 hour. Diagrammmmmmmm????????? Software Requiremems Specification for Page 4 2.2 Product Features The ATM should work 24 hrs. The ATM identifies a customer by a cash card and password. It collects information about a simple account transaction (€.g., deposit, withdrawal, transfer, bill payment), communicates the transaction information to the customer's bank, and dispenses cash to the customer. The banks provide their own software for their own ‘computers. The bank software requires appropriate record keeping and security provisions. The software must handle concurrent accesses to the same account correctly. Diagrammmmmmm DFD 2.3 User Classes and Characteristics Characteristics There are several users of the ATM network: Customers are simply members of the general public with no special training. Bank security personnel need have no special education or experience. Maintainers must be experienced network administrators, to be able to connect new ATMS to the network. 2.4 Operating Environment ‘The hardware, software and technology used should have following specifi + 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 Requiremems Specification for Page 2.5 Design and Implementation Constraints + 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 + IFPIN 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 2.6 User Documentation Software Requiremems Specification for Page 6 2.7 Assumptions and Dependencies + 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) 3. Specific Requirements 3.1 Functional Requirements ‘The functional requirements are organized in two sections First requirements of the ATM and second requirements of the bank. 3.1.1 Requirements of the automated teller machine The requirements for the automated teller machine are organized in the following way Gen_ eral requirements, requirements for authorization, requirements for a transaction General Functional requirement 1 * Description Initialize parameters t, k, m,n * Input ATM is initi * Processing Storing the parameters. * Output Parameters are set. fed with t dollars, k, m,n are entered Functional requirement 2 * Description If no cash cards in the ATM, the system should display initial display. Functional requirement 3 * Description If the ATM is running out of money, no card should be accepted. An error message is. Displayed Software Requiremems Specification for Page 7 Input Acard is entered. * Processing ‘The amount of cash is less than t. * Output Display an error message. Return cash card. Authorization The authorization starts after a customer has entered his card in the ATM Functional requirement 4 * Description ‘The ATM has to check if the entered card is a valid cash-card, Input Customer enters the cash card. + Processing Check if it isa valid cash card.tt will be valid if 1L the information on the card can be read. 2. itis not expired. * Output Display error message and return cash card if itis invalid 4. External Interface Requirements 4.1 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 4.2 Hardware Interfaces ‘The hardware should have following specifications’ + Ability to read the ATM card + Ability to count the currency notes + Keypad (in ease touchpad fails) Software Requiremems Specification for Page 8 + Continuous power supply + Ability to connect to bank’ network + Ability to take input from user + Ability to validate user 4.3 Software Interfaces ‘The software interfaces are specific to the target banking software systems. 5. Other Nonfunctional Requirements 5.1 Performance Requirements + It must be able to perform in adverse conditions like high/low temperature etc. + Uninterrupted interrupted connections + High data transfer rate 5.2 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 5.3 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 three 5.4 Software Quality Attributes Page 9 usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.> 5.4.1 Availability The ATM network has to be available 24 hours a day. 5.4.2 Security The ATM network should provide maximal security .In order to make that much more ‘Transparent there are the following requirements 1 It must be impossible to plug into the network 5.4.3 Maintainability Only maintainers are allowed to connect new ATMs to the network. 6. Other Requirements Data Base ‘The ATM must be able to use several data formats according to the data formats that are provided by the data bases of different banks. A transaction should have all the properties of a data base transaction (Atomicity, Consistency, Isolation, Durability). Appendix A: Glossary «Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.> Appendix B: Analysis Models Appendix C: Issues List < This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy