12-02-2016, 03:15 PM
1.1 Scope
The customer should be able to withdraw the money, inquire balance and procure information about the transactions. The PIN number will be used to validate the user once the ATM card has been swiped.
1.2 Not in scope
The process of depositing cash into the ATM machine by admin/maintenance and other related functionalities will not be in scope of this application.
1.3 Business context
The proposed system will help the bank customers to withdraw money at a faster rate and also prevents the need to go to the banks thus reducing the workload on bank tellers.
It also allows withdrawal of money 24*7.
1.4 Proposed system
The system should help customer withdraw the money, inquire balance and procure information about his/her transactions along with appropriate on-screen help.
2 Interfaces Requirements
The list of Functional and non functional requirements which are applicable to the ATM System is as follows
• User Interfaces-
Describes how this product interfaces with the user.
Description- The user interface must be customizable by the administrator
Criticality-This issue is essential to the overall system. All the modules provided with the software must fit into this graphical user interface and accomplish to the standard defined.
Technical Issues-In order to satisfy this requirement the design should be simple and all the different interfaces should follow a standard template. There will be the possibility of changing colors and images, plus switching between interfaces with the minimum impact for the users.
Risks-To reduce the circumstances under which this requirement might not able to be satisfied, all the designers must have been developed ATM applications previously and they must be aware of restriction and issues before starting the designing. In order to reduce the probability of this occurrence the entire design team will be trained in basic Architecture and working of ATM system.
Dependencies with other requirements-All user interfaces should be able to interact with the user management module and a part of the interface must be dedicated to the login/logout module
• Hardware Interfaces
Server Side:
Operating System: Windows 9x/xp ,Windows ME
Processor: Pentium 3.0 GHz or higher
RAM: 256 Mb or more
Hard Drive: 10 GB or more
Client side:
Operating System: Windows 9x or above, MAC or UNIX.
Processor: Pentium III or 2.0 GHz or higher.
RAM: 256 Mb or more
• Software Interfaces
Database: SQL Server.
Application: ASP (Active Server Pages)
Web Server: IIS (Internet Information Services (IIS) is a powerful Web server that provides a highly reliable, manageable, and scalable Web application infrastructure)
• Communication interfaces
The Customer must visit the ATM kiosks to operate the application:
3 Functional Requirements/Use Case Scenarios
Functional Requirements:
There is one user who will be using this product:
Customer
The features that are available to the Customer are:
• Withdraw money
• Balance Inquiry
• Transaction History/ Details
Exception Scenarios:
Maximum amount that can be withdrawn.
Handling invalid PIN attempts(beyond the allowed limit)
Insufficient balance
The customer should be able to withdraw the money, inquire balance and procure information about the transactions. The PIN number will be used to validate the user once the ATM card has been swiped.
1.2 Not in scope
The process of depositing cash into the ATM machine by admin/maintenance and other related functionalities will not be in scope of this application.
1.3 Business context
The proposed system will help the bank customers to withdraw money at a faster rate and also prevents the need to go to the banks thus reducing the workload on bank tellers.
It also allows withdrawal of money 24*7.
1.4 Proposed system
The system should help customer withdraw the money, inquire balance and procure information about his/her transactions along with appropriate on-screen help.
2 Interfaces Requirements
The list of Functional and non functional requirements which are applicable to the ATM System is as follows
• User Interfaces-
Describes how this product interfaces with the user.
Description- The user interface must be customizable by the administrator
Criticality-This issue is essential to the overall system. All the modules provided with the software must fit into this graphical user interface and accomplish to the standard defined.
Technical Issues-In order to satisfy this requirement the design should be simple and all the different interfaces should follow a standard template. There will be the possibility of changing colors and images, plus switching between interfaces with the minimum impact for the users.
Risks-To reduce the circumstances under which this requirement might not able to be satisfied, all the designers must have been developed ATM applications previously and they must be aware of restriction and issues before starting the designing. In order to reduce the probability of this occurrence the entire design team will be trained in basic Architecture and working of ATM system.
Dependencies with other requirements-All user interfaces should be able to interact with the user management module and a part of the interface must be dedicated to the login/logout module
• Hardware Interfaces
Server Side:
Operating System: Windows 9x/xp ,Windows ME
Processor: Pentium 3.0 GHz or higher
RAM: 256 Mb or more
Hard Drive: 10 GB or more
Client side:
Operating System: Windows 9x or above, MAC or UNIX.
Processor: Pentium III or 2.0 GHz or higher.
RAM: 256 Mb or more
• Software Interfaces
Database: SQL Server.
Application: ASP (Active Server Pages)
Web Server: IIS (Internet Information Services (IIS) is a powerful Web server that provides a highly reliable, manageable, and scalable Web application infrastructure)
• Communication interfaces
The Customer must visit the ATM kiosks to operate the application:
3 Functional Requirements/Use Case Scenarios
Functional Requirements:
There is one user who will be using this product:
Customer
The features that are available to the Customer are:
• Withdraw money
• Balance Inquiry
• Transaction History/ Details
Exception Scenarios:
Maximum amount that can be withdrawn.
Handling invalid PIN attempts(beyond the allowed limit)
Insufficient balance