SYSTEM REQUIRMENT SPECIFICATIONS FOR

FIN CORP - CASH CONTROLLER

PURPOSE OF THE SYSTEM

This project is mainly developed for the Account Division of a Banking sector to provide
better interface of the entire banking transactions. This system is aimed to give a better
out look to the user interfaces and to implement all the banking transactions like
depositing, withdrawing, customer account information, transaction information etc.

PROBLEMS IN THE EXISTING SYSTEM:

• It is limited to a single system.

• It is less user-friendly.
• It is having lots of manual work (Manual system does not mean that you are
working with pen and paper, it also include working on spread sheets and other
simple software's).
• The present system is very less secure.
• It is unable to generate different kinds of report.
• It doesn’t have the mail and file upload feature.

SOLUTION OF THESE PROBLEMS

The development of the new system contains the following activities, which try to
automate the entire process keeping in view of the database integration approach.

• User friendliness is provided in the application with various controls.

• The system makes the overall project management much easier and flexible.

• It can be accessed over the Internet.

• Various classes have been used to provide file upload and mail features.

• There is no risk of data mismanagement at any level while the project

development is under process.

• Report generation feature is provided using Crystal Reports to generate

different kinds of reports like bar graphs, pie charts and table type charts etc.
It provides high level of security using different protocols like https etc.

STUDY OF THE SYSTEM

In the flexibility of the uses the interface has been developed a graphics concept in
mind, associated through a browses interface. The GUI’S at the top level have been
categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is

practically, part of the organizational activities and which needs proper authentication
for the data collection. The interfaces help the administrations with all the transactional
states like Data insertion, Data deletion and Date updation along with the extensive data
search capabilities.

The operational or generic user interface helps the users upon the system in
transactions through the existing data and required services. The operational user
interface also helps the ordinary users in managing their own information helps the
ordinary users in managing their own information in a customized manner as per the
assisted flexibilities.

Number of Modules
The system after careful analysis has been identified to be presented with the following
modules:

The modules involved are:

• Account Information
• New Account Creations
• Deposits
• Withdraws
• Cheque book issues
• Stop payments
• Transfer of accounts
 • Report Generations.

Account Information
The account information service will provide customers a summary of their accounts.
These accounts could be saving of current Deposit account. The customers can get
details of each account, a snapshot of the balances, a record of payment and
transfers made, whenever they require.
In addition to displaying the account balance information, the clients would get
a warning when the account Balance falls below the minimum limit. This limit is
decided by the bank.
The customers will also be provided account statements and transaction reports
based on any user-defined criteria. Moreover, this system will make tracking of
transactions easy, the User would be able to get details of the various transactions
based on the Account number, the transaction date, the period of the transaction,
and so on.

New Account Creation

Whenever a new customer comes, this system facilitates to create an account in his
name. The customer must provide information regarding the type of account he
wants to open, amount of deposit, his address and optionally his photo copy and
digital signature.

Deposits
All sort of banking deposits need to be implemented in the system. The user needs to
enter the information like account number, the mode of deposit and the amount.

Withdrawals
All sort of banking withdrawals need to be implemented in the system. The user
needs to enter the information like account number and the amount. The system
must maintain the minimum amount for each account.
 Cheque - Book Issues
Cheque books should be issued to an account holder whenever he requests and it
should be on the basis of the minimum balance. The Cheque book number generated
by the system must be unique.

Stop Payments
Withdraws on a particular Cheque must be stopped upon the request made by the
customer.

Transfer of Amount from one Account to Other

The system should transfer the amount transfers from one account to another. Here
the user need to enter both the from account number and to account number. Both
accounts should get updated during the transaction.

Report Generation
Reports are very essential for the banking organization. It needs to generate different
reports of banking information from the stored information. These reports can be
printed and also can be stored as soft copies in the system for future use.

INPUTS & OUTPUTS

The main inputs, outputs and major functions of the system are as follows.
Inputs:
• Admin enters his or her user id and password.
• Users enter his or her user id and password.
• General Users enter his or her user id and password.
• User requests the reports.
• User requests the search.
• Admin can edits the personal details and so on.
Outputs:
• Admin receives personal details.
• Users receive the personal details.
• Users can see the quota and give the quotation for that quota.
• Users receive requested reports.
• Displays search result.
SCOPE OF THE PROJECT

This Document plays a vital role in the development life cycle (SDLC) as it describes the
complete requirement of the system. It is meant for use by the developers and will be
the basic during testing phase. Any changes made to the requirements in the future will
have to go through formal change approval process.
Object Oriented Analysis and Design (OOAD) is the model, chosen to design and develop
the proposed system.

Features of OOAD:
• It users Objects as building blocks of the application rather functions
• All objects can be represented graphically including the relation between them.
• All Key Participants in the system will be represented as actors and the actions
done by them will be represented as use cases.
• A typical use case is nothing bug a systematic flow of series of events which
can be well described using sequence diagrams and each event can be
described diagrammatically by Activity as well as state chart diagrams.
• So the entire system can be well described using OOAD model, hence this
model is chosen as SDLC model.

Architecture Flow

The current application is being developed by taking the 3-tier architecture as a

prototype. The 3-tier architecture is the most common approach used for web
applications today. In the typical example of this model, the web browser acts as the
client, IIS handles the business logic, and a separate tier MS-SQL Server handles
database functions.

Although the 3-tier approach increases scalability and introduces a separation of

business logic from the display and database layers, it does not truly separate the
application into specialized, functional layers. For prototype or simple web applications,
the 3-tier architecture may be sufficient. However, with complex demands placed on
web applications, a 3-tiered approach falls short in several key areas, including flexibility
and scalability. These shortcomings occur mainly because the business logic tier is still
too broad- it has too many functions grouped into one tier that could be separated out
into a finer grained model.

The proposed system can be designed perfectly with the three tier model, as all
layers are perfectly getting set as part of the project. In the future, while expanding the
system, in order to implement integration touch points and to provide enhanced user
interfaces, the n-tier architecture can be used. The following diagram will represent the
typical n-tier architecture.
Output Design:
One of the most important factors of an information system for the user is the output the
system produces. Without the quality of the output, the entire system may appear unnecessary that
will make us avoid using it possibly causing it to fail. Designing the output should process the in an
organized well throughout the manner. The right output must be developed while ensuring that each
output element is designed so that people will find the system easy to use effectively.
The term output applying to information produced by an information system whether printed or
displayed while designing the output we should identify the specific output that is needed to
information requirements select a method to present the formation and create a document report or
other formats that contains produced by the system.

Types of output:

Whether the output is formatted report or a simple listing of the contents of a file, a computer
process will produce the output.

• A Document
• A Message
• Retrieval from a data store
 • Transmission from a process or system activity
• Directly from an output sources

Layout Design:
It is an arrangement of items on the output medium. The layouts are building a

mock up of the actual reports or document, as it will appear after the system is in operation. The
output layout has been designated to cover information. The outputs are presented in the appendix.

Input design and control:

Input specifications describe the manner in which data enter the system for processing. Input
design features will ensure the reliability of the systems and produce results from accurate data, or
thus can be
result in the production of erroneous information. The input design also determines whenever the
user can interact efficiently with this system.

Objectives of input design:

Input design consists of developing specifications and procedures for data preparation, the steps
necessary to put transaction data into a usable from for processing and data entry, the activity of
data into the computer processing. The five objectives of input design are:

• Controlling the amount of input

• Avoiding delay
• Avoiding error in data
• Avoiding extra steps
• Keeping the process simple
Controlling the amount of input:
Data preparation and data entry operation depend on people, because labour costs are high, the
cost of preparing and entering data is also high. Reducing data requirement expense. By reducing
input requirement the speed of entire process from data capturing to processing to provide results
to users.

Avoiding delay:
The processing delay resulting from data preparation or data entry operations is called
bottlenecks. Avoiding bottlenecks should be one objective of input.

Avoiding errors:
 Through input validation we control the errors in the input data.
Avoiding extra steps:
The designer should avoid the input design that cause extra steps in processing saving or adding
a single step in large number of transactions saves a lot of processing time or takes more time to
process.

Keeping process simple:

If controls are more people may feel difficult in using the systems. The best-designed system fits
the people who use it in a way that is comfortable for them.

CONTEXT DIAGRAM

Custome
r

Customer
Bank Information
Product Branch
Information Information
Customer Branch
Report

Product
Report

Branch
Report

Cheque
Book
Cheque Information
Book
Request Cheque
Book Fin Corp - Cash
Report
Controller Account Info
Information

Deposit
Report
Account Accoun
Info Report
Withdraw
t
Information Informa
Deposit Deposit
Information
tion
Withdraw
Report

Withdra
w
PERFORMANCE REQUIREMENTS:

Performance is measured in terms of the output provided by the application. Requirement

specification plays an important part in the analysis of a system. Only when the requirement
specifications are properly given, it is possible to design a system, which will fit into required
environment. It rests largely in the part of the users of the existing system to give the
requirement specifications because they are the people who finally use the system. This is
because the requirements have to be known during the initial stages so that the system can be
designed according to those requirements. It is very difficult to change the system once it has
been designed and on the other hand designing a system, which does not cater to the
requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
• The system should be able to interface with the existing system
• The system should be accurate
• The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.

FEASIBILITY REPORT

Preliminary investigation examine project feasibility, the likelihood the system will
be useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and debugging
old running system. All system is feasible if they are unlimited resources and infinite
time. There are aspects in the feasibility study portion of the preliminary investigation:
• Technical Feasibility
• Operation Feasibility
• Economical Feasibility

Technical Feasibility
The technical issue usually raised during the feasibility stage of the investigation
includes the following:
• Does the necessary technology exist to do what is suggested?
• Do the proposed equipments have the technical capacity to hold the data required
to use the new system?
 • Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
• Can the system be upgraded if developed?
• Are there technical guarantees of accuracy, reliability, ease of access and data
security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation
System’. The current system developed is technically feasible. It is a web based user
interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users.
The database’s purpose is to create, establish and maintain a workflow among various
entities in order to facilitate all concerned users in their various capacities or roles.
Permission to the users would be granted based on the roles specified. Therefore, it
provides the technical guarantee of accuracy, reliability and security. The software and
hard requirements for the development of this project are not many and are already
available in-house at NIC or are available as free as open source. The work for the
project is done with the current equipment and existing software technology. Necessary
bandwidth exists for providing a fast feedback to the users irrespective of the number of
users using the system.

Operational Feasibility
Proposed projects are beneficial only if they can be turned out into information system.
That will meet the organization’s operating requirements. Operational feasibility aspects
of the project are to be taken as an important part of the project implementation. Some
of the important issues raised are to test the operational feasibility of a project includes
the following: -
• Is there sufficient support for the management from the users?
• Will the system be used and work properly if it is being developed and
implemented?
• Will there be any resistance from the user that will undermine the possible
application benefits?
This system is targeted to be in accordance with the above-mentioned issues.
Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can undermine
the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer resources
and would help in the improvement of performance status.

Economic Feasibility
A system can be developed technically and that will be used if installed must still be a
good investment for the organization. In the economical feasibility, the development
cost in creating the system is evaluated against the ultimate benefit derived from the
new systems. Financial benefits must equal or exceed the costs. The system is
economically feasible. It does not require any addition hardware or software. Since the
interface for this system is developed using the existing resources and technologies
available at NIC, There is nominal expenditure and economical feasibility for certain.