07-08-2012, 04:10 PM
Software Requirements Document for BANK System
[attachment=30440]
Introduction
PURPOSE
The purpose of this SRS (Software Requirements Specification) document is to provide a detailed
description of our software project, specifications, and goals. This document describes the features
included that are included in our project, its user interface, and its functionality. The document
describes hour our team sees and understands the requirements of the software.
Overall Description
The application is to be fully-functional bank software. It will consist of a few different modules.
The first module is to be a software application that can be used by bank customers as in an ATM.
This application will allow the user to deposit funds, withdraw funds, check balance, and transfer
funds.
The second module is to be a software application that is used within the bank by the bank tellers
and managers. This application will allow everything the ATM allows as well as some additional
features. These features include: account creation, account deletion, loan approval, customer
records, and reports.
Both pieces of software will be linked to a central bank server. This server will handle multiple
threads and will therefore allow for simultaneous access of multiple users. It will provide for user
authentication and will store all data.
PRODUCT PERSPECTIVE
The product is banking software similar in functionality to the software run in most banks. The
reporting feature is also similar to the reports available in Intuit QuickBooks and Quicken.
Concept of Operations
The bank software will allow for two different methods of operation. The first method of operation
will be through an ATM terminal. This operation is performed by the user. The user will be
allowed to deposit funds, withdraw funds, check balance, and transfer funds. It will all be done
through a simple, easy to use graphic user interface. It will implement the standard buttons found
on a standard ATM machine.
Main Flow
1. The user is presented with the main menu screen.
2. The user requests transfer funds from ATM system main menu screen.
3. The user selects the accounts for outgoing funds and incoming funds.
4. The user enters the dollar amount of funds to transfer.
5. The ATM system queries the bank server to validate fund transfers vs
account balances.
6. The ATM System queries the bank server to complete funds transfer.
7. The user is prompted for another transaction. If the user input is Yes then
go to main menu screen. If the user input is No then go to login screen.
Alternate Flow
1. If the user doesn’t have the necessary funds to complete a funds transfer
then the user is notified.
2. The user is prompted for another transaction. If the user input is Yes then
go to main menu screen. If the user input is No then go to login screen.
[attachment=30440]
Introduction
PURPOSE
The purpose of this SRS (Software Requirements Specification) document is to provide a detailed
description of our software project, specifications, and goals. This document describes the features
included that are included in our project, its user interface, and its functionality. The document
describes hour our team sees and understands the requirements of the software.
Overall Description
The application is to be fully-functional bank software. It will consist of a few different modules.
The first module is to be a software application that can be used by bank customers as in an ATM.
This application will allow the user to deposit funds, withdraw funds, check balance, and transfer
funds.
The second module is to be a software application that is used within the bank by the bank tellers
and managers. This application will allow everything the ATM allows as well as some additional
features. These features include: account creation, account deletion, loan approval, customer
records, and reports.
Both pieces of software will be linked to a central bank server. This server will handle multiple
threads and will therefore allow for simultaneous access of multiple users. It will provide for user
authentication and will store all data.
PRODUCT PERSPECTIVE
The product is banking software similar in functionality to the software run in most banks. The
reporting feature is also similar to the reports available in Intuit QuickBooks and Quicken.
Concept of Operations
The bank software will allow for two different methods of operation. The first method of operation
will be through an ATM terminal. This operation is performed by the user. The user will be
allowed to deposit funds, withdraw funds, check balance, and transfer funds. It will all be done
through a simple, easy to use graphic user interface. It will implement the standard buttons found
on a standard ATM machine.
Main Flow
1. The user is presented with the main menu screen.
2. The user requests transfer funds from ATM system main menu screen.
3. The user selects the accounts for outgoing funds and incoming funds.
4. The user enters the dollar amount of funds to transfer.
5. The ATM system queries the bank server to validate fund transfers vs
account balances.
6. The ATM System queries the bank server to complete funds transfer.
7. The user is prompted for another transaction. If the user input is Yes then
go to main menu screen. If the user input is No then go to login screen.
Alternate Flow
1. If the user doesn’t have the necessary funds to complete a funds transfer
then the user is notified.
2. The user is prompted for another transaction. If the user input is Yes then
go to main menu screen. If the user input is No then go to login screen.