SYSTEM REQUIREMENT SPECIFICATION

ON

“ONLINE BANKING SYSTEM”

SUBMITTED TO:- SUBMITTED BY:-

VIJAY MOHAN SHRIMAL SAWAN KUMAR
(Assist. Professor) MAHAWAR
(CSE Deptt) ( CS-A/2ndyear)
Index

S.NO. PARTCULAR PAGE NO.

1. Project introduction 1
1.1 Purpose of document 1-2
1.2 Scope of developments 2
1.3 Overview 2-3
1.4 Business context 3-4

2. General Description 5-7

2.1 Product function 5
2.2 User problem statement 5
2.3 User objectives 6-7

3. System Analysis 8-17

3.1 Functional requirement 8
3.1.1 System requirement 8
3.1.2 Program requirement 8
3.1.3 Stability & speed 8
3.2 Feasibility study 9
3.2.1 Operational 9-12
3.2.2 Technical 12-15
3.2.3 Economic 15-17

4. System Design 18-26

4.1 Scope 18
4.2 Database design 18-21
4.3 Data flow diagram (DFD) 21-24
4.4 Entity relationship diagram(E- 24-25
R diagram)
4.5 Module description 25-26
5. Interface requirement 27
5.1 Graphical interface 27
5.2 Command line interface 27
5.3 Hardware interface 27
5.4 Software interface 27
6. Performance requirement 28-29

7. Non functional attributes 30-32

7.1 Security 30
7.2 Reliability 30
7.3 Maintainability 30
7.4 Portability 30-31
7.5 Reusability 31
7.6 Resource utilization 31
7.7 Stable and speed efficiency 32
8. Security 33-35
8.1 Description 33
8.2 Technical issues 33
8.3 Cost and schedule 33-34
8.4 Risk 34-35

9. Reference & Appendices 36

10. Conclusion 36
 1

ONLINE BANKING SYSTEM

1. INTRODUCTION
Internet banking is a product of e-commerce in the field of banking and financial services. In
what can be described as business to customer domain for banking industry, Internet banking
offers different online services like balance enquiry, balance transfer, opening account, calculate
EMI’s etc. Mostly, these are traditional services offered through internet as a new delivery
channel. Banks are also offering payment services on the behalf of their customers who shop in
different e-shops, e-malls etc. Further, different banks have different levels of such services
offered, starting from level-1 where only information is disseminated through internet to level-3
where online transactions are put through.

1.1 PURPOSE OF THE SYSTEM

1. SECURITY: There is a lot of security of data on this content management system. One
cannot open our system without knowing the password. Immediately after opening login screen
will appear on screen. Only after entering the correct username and password user can operate
our system.

2. REFERENTIAL INTEGRITY: User cannot change the date in the transaction files.
Addition of data can be done only on the master files date in transaction files cannot be entered
until addition is done on the master files.

3. EASY RETRIEVAL OF DATA: Data is retrieved easily and quick using sql commands. On
line commands are used to retrieve huge amount of data.

4. GENERATION OF AUTOMATIC VALUES: In project in some screen some fields

generated automatically like Profile detail, Account number, etc.
 2

1.2 SCOPE OF THE PROPOSED SYSTEM

Though there are many online systems available on internet but this can compete with them with
some advancement in its functionality and can be used by any bank organization to maintain
their customer’s account and online transaction process.

The basic functionalities of the system are:

 Create Account
 Login
 Update Profile
 Password Recovery
 View Profile
 ATM and Bank finder
 Contact Form
 Amount Transaction
 EMI and Loan Calculator
 Delete account
 Logout

1.3 OVERVIEW OF PROPOSED SYSTEM

1. MENU DRIVEN:
The project uses menu throughout which we can choose required options. Menus are self-
explanatory, as they are very easy to use and user can go to any other web page using the menu.

2. USER CONFIRMATION:
 3

Whenever the user tries to delete or edit the data, the system asks for the confirmation. This is
used to avoid the accidental changes to the database. A confirmation is also provided for the exit
of the application.

3. GRAPHICAL USER INTERFACE:

User is provided with a graphical interface in which user can select from various options and can
perform desired operations with perfect understanding of the menu selected.

4. MULTIPLE DOCUMENT INTERFACE:

The package provides a multiple document interface to the user. The user can view more than
one entry form or pages at the same time.

5. SECURITY AND ACCESS: A password form has been provided at the beginning of the
package. Entering the correct password will take user to the main user page

1.4 BUSINESS CONTEXT

Existing banking system is a manual system, which leads to a number of problems in
maintaining proper records. These are:
1. PAPER WORK: All the activities that are performed by Management involve a lot of paper
work involving register consultations and entries. A separate file has to be maintained for each
kind of activity and for different periods of time.

2. TIME CONSUMPTION: A lot of time is consumed in referencing the registers involved for
particular activities and a lot of computation as well as report verification activity is also paper
based and time consuming.

3. COMPLEXITY: Complexity of information handling and the gathering and determination of

information is usually the most difficult problem faced.
 4

4. REDUNDANCY: Maintaining separate files for each department can lead to duplication of
data present in files. This can lead to:

a) Inconsistencies
b) Update anomalies
c) Decentralization problems

5. HUMAN ERRORS: Human kind of errors may be generated in typing errors and slow
arithmetic calculations, fatigue and boredom.

6. ILLEGAL ACCESS: The security of a lot of documents, which are paper, based if difficult
may be in terms of illegal access or manipulation by malicious personals either intentionally or
by accident.

7. DYNAMIC ENVIRONMENT: As the working environment is dynamic and company policies

change time and again, changing the way of working will be difficult.
 5

2. General Description
2.1 Product function:

 Track Account Level Data: In this module, check the authentication of users.

 Service Level Agreements: It contains the agreements of providing the services related to
users.

 User Contact Information: It maintains all the details (Personal, Official and Contact) of
the users.

 Product Access Right Details: It maintains the information that does which user have the
rights of using which service.

2.2 User problem statement

A problem statement is a concise description of the issues that need to be addressed by a

problem solving team and should be presented to them (or created by them) before they try to
solve the problem. When bringing together a team to achieve a particular purpose provide them
with a problem statement. A good problem statement should answer these questions:

1. What is the problem? This should explain why the team is needed.
2. Who has the problem or who is the client/customer? This should explain who needs the
solution and who will decide the problem has been solved.
3. What form can the resolution be? What is the scope and limitations (in time, money,
resources, technologies) that can be used to solve the problem? Does the client want a
white paper? A web-tool? A new feature for a product? A brainstormingon a topic?

The primary purpose of a problem statement is to focus the attention of the problem solving
team. However, if the focus of the problem is too narrow or the scope of the solution too limited
the creativity and innovation of the solution can be stifling.

In project management, the problem statement is part of the project charter. It lists what's
essential about the project and enables the project manager to identify the project scope as well
as the project stakeholders.

A research-worthy problem statement is the description of an active challenge (i.e. problem)

faced by researchers and/or practitioners that does not have adequate solutions available
 6

including the argumentation for its viability based on solid peer-reviewed sources as well as
theoretical foundation. The research-worthy problem statement should address all six
questions: what, how, where, when, why, and who. On the other hand, a statement of the
problem is one or two sentences claim that outlines the problem that the study addresses. The
statement of the problem should briefly address the question: What is the problem that the
research will address?

2.3 User objectives

2.3.1 CREATE ACCOUNT
This module is used by the user to create a new account to join services of online banking.
The user is required to fill in a few details and is automatically assigned as an user at the end
of process.
2.3.2 LOGIN
This module is used by all the users to log into the account. The user is required enter his/her
user name and password. After login user will be redirected to the user’s home page.

2.3.3 UPDATE PROFILE

Update profile module will be used to update or change any detail of user such as address,
phone number, city, state, etc.

2.3.4 PASSWORD RECOVERY

This module is used to recover the lost password by the user by entering his/her valid email
address. This email address will be matched from database and automatically generated
email will be sent to the user containing his/her user name and password.

2.3.5 VIEW PROFILE

This module is the automatically generated page when user clicks the view profile button.
This contain the user account detail such as name, account balance, email id, address, city.

2.3.6 ATM AND BANK LOCATOR

This module is used to find the address and location of ATM and banks in the selected city.

2.3.7 AMOUNT TRANSACTION

 7

This module is the user view page after login where he/she can transfer the amount to other
account by providing the amount to be transferred and the account number where to be
transferred.

2.3.8 CONTACT FORM

This module is used by both registered and non-registered user to contact bank or to give any
feedback trough message. His/her message will be saved into the database and further bank
can contact him/her.

2.3.9 EMI AND LOAD INTEREST CALCULATOR

This module is used to calculate the interest amount of EMI and load by proving the interest
rate, total amount and duration.

2.3.10 DELETE ACCOUNT

This module is used to delete the user’s account by the confirmation of user.

2.3.11 LOGOUT
This module is used to logout from the user’s session and redirected to the home page of
website.
 8

3. SYSTEM ANALYSIS
3.1 Functional requirement
3.1.1 System requirement:

To view your accounts in Online Banking you will need internet access using one of the
following supported browsers:

 Microsoft Internet Explorer 6 or higher

 Firefox 3
 Safari 3

To view your accounts in Online Cash Manager you will need internet access using one of the
following supported browsers:

 Microsoft Internet Explorer 6 or higher

 Firefox 3

3.1.2 Program requirement

The following are the most essential requirements for developing and hosting web applications:

(ii) Server-side Runtime Support - This includes support for network services and a runtime
for executing the applications.

(iii) Deployment Support – Deployment is the process of installing the application on the
server. Deployment could also include customizing the application.

3.1.3 Stability & speed

SPEED delivers unparalleled analysis into the latest developments in payments systems, real
time gross settlement, straight-through-processing, securities trading, risk management and
banking technology.

It is the essential source of information policymakers and market participants like you read to
stay informed about the policy issues shaping settlements, payments, e-money and e-trading.

Few sources of information set out to analyse changes in the financial infrastructure as a whole.
They stay in their silo. Yet increasingly what happens in one area has far reaching implications
for all others.

SPEED aims to help you track these developments not just at a national or global level, but as an
integrated whole.
 9

3.2 Feasibility study

3.2.1 Operational
Now almost all Banks branches are connected through the online banking facilities. The
transactions of a particular bank are transmitted through the Micro-Bank software from INFLEX
Solutions to the Head Office, where every data is stored in the database.
Real-time On-line any branch banking for the clients is used to facilitate the clients to deposit /
draw or remit funds to and from their accounts, from one bank to another.
Meanwhile, for the Smooth operation and efficient functioning of the system they have
completed the proper training to the related personnel

3.2.2 Technical
.NET Programming Framework
The .NET framework is a cluster of different technologies. It includes:
 The .NET languages, which include C# and Visual Basic .NET, the object-oriented and
modernized successor to Visual Basic 6.0.
 The Common Language Runtime (CLR), the .NET runtime engine that executes all
.NET programs, and provides modern services such as automatic memory management,
security, optimization, and garbage collection etc.
 The .NET class library which collects thousands of pieces of pre-built functionality that
you can snap in to your applications. These are sometimes organized into technology sets,
such as ADO.NET (the technology for creating database applications) and Windows Forms
(the technology for creating desktop user interfaces)
 ASP.NET, the platform services that allow you to program web applications and Web
Services in any .NET language, with almost any feature from the .NET class library.
 Visual Studio .NET, an optional development tool that contains a rich set of productivity
and debugging features.

2. VB .NET, C#, and the .NET Languages

In fact, all the .NET languages are compiled to the same intermediate language, which isJust IL.
The CLR only runs IL code, which is the reason why the C# and VB .NET
 10

Code in Code In C# Code in another

VB.NET .NET language

VB. NET C # compiler Appropriate

compiler compiler

IL ( Intermediate
Language ) Code

CLR just-in-time
execution

Language comilation in .NET

languages are so similar (and perform essentially the same).

Figure 2:- The .NET Framework

 11

ADO NET Web forms Windows

data access forms

XML File I/O (And so on)

Core System classes (threading , serialization, reflection, collections, and so

on)
The .NET Library

Comiler and Loader

Code verification and optimization

Memory management and garbage collection

Code access security

(Other managed code services)

The .NET Framework

 12

3. The Common Language Runtime

The Common Language Runtime (CLR) is the engine that supports all the .NET languages. Most
modern languages use runtimes, these runtimes may provide libraries used by the language, or
they may have the additional responsibility of executing the code (as with Java).
Runtimes are nothing new, but the CLR represents a radical departure from Microsoft’s previous
strategy. To start, the CLR and .NET framework are much larger and more ambitious. The CLR
also provides a whole set of related services such as code verification, optimization, and garbage
collection, and can run the code from any .NET language.
However, before it can be executed by the CLR, any source code that you develop (in C# or
some other language) needs to be compiled. Compilation occurs in two steps in .NET:

1. Compilation of source code to IL

2. Compilation of IL to platform-specific code by the CLR

This two-stage compilation process is very important, because the existence of the IL (managed
code) is the key to providing many of the benefits of .NET.

4. Features of Dot Net

Simple:
Dot Net framework supports a very user friendly IDE Visual Studio which makes dot net very
simple. Visual Studio supports a rich set of design tools, including a well known set of
debugging tools and IntelliSense, which catches errors and offers suggestions as you type.
It also supports the robust code-behind model, which separates the .NET code you write from the
web-page markup tags.

Platform independence:
First, it means that the same file containing IL code instructions can be placed on any platform;
at run-time the final stage of compilation can then be easily accomplished so that the code will
run on that particular platform. In other words, by compiling to IL you obtain platform
independence for .NET, in much the same way as compiling to Java byte code gives Java
platform independence.
 13

Performance improvement:
Instead of compiling the entire application in one go (which could lead to a slow start-up time),
the JIT compiler simply compiles each portion of code as it is called (just-in-time). When code
has been compiled once, the resultant native executable is stored until the application exits; so
that it does not need to be recompiled the next time that portion of code is run.

Common Type System:

This data type problem is solved in .NET through the use of the Common Type System (CTS).
The CTS defines the predefined data types that are available in IL, so that all languages that
target the .NET Framework will produce compiled code that is ultimately based on these types.

Common Language Specification:

The Common Language Specification (CLS) works with the CTS to ensure language
interoperability. The CLS is a set of minimum standards that all compilers targeting .NET must
support. CLS works in two ways. First, it means that individual compilers do not have to be
powerful enough to support the full features of .NET this should encourage
the development of compilers for other programming languages that target .NET. Second, it
provides a guarantee that, if you restrict your classes to exposing only CLS-compliant features,
code written in any other compliant language can use your classes.

Garbage collection:
The .NET runtime relies on the garbage collector instead. This is a program whose purpose is to
clean up memory. The idea is that all dynamically requested memory is allocated on the heap
(that is true for all languages, although in the case of .NET, the CLR maintains its own managed
heap for .NET applications to use). , when .NET detects that the managed heap for a given
process is becoming full and therefore needs tidying up, it calls the garbage collector.
 14

Security:
.NET can really excel in terms of complementing the security mechanisms provided by Windows
because it can offer code-based security, whereas Windows only really offers role-based
security.

Rich API (Application Programmer’s Interface) / Namespaces:

.Net API is very rich as compared to other languages.
Robust :
Most programs fail for one of the two reasons:
(i) Memory Management
(ii) Exceptional conditions at run time
While designing the language one of the aim was to ensure that .Net programs are as robust as
possible i.e. they should rarely fail. So due importance was given to the above two factors in the
.Net.

Better support for Dynamic Web Pages:

.Net offers an integrated support for web pages, using a new technology ASP.NET. With
ASP.Net, code in your page is compiled, and may be written in a any of the .Net languages like
C#, J# or VB.Net
Efficient Data Access:
A set of .Net components, collectively known as ADO.NET provides efficient access to
relational databases and variety of data sources. Components are also available to allow access to
the file system and to directories.

Object-Oriented:
C# is based on object-oriented paradigm. Object-oriented programs are organized around data
(i.e. objects) and a set of well-defined interfaces (public methods) to that data.

Introduction to Web Applications in Dot Net

1. Introduction
 15

Web applications run on the Web Server. Web applications are accessed through web clients i.e.
web browsers like Internet Explorer or Netscape. Whenever you access some web site by
specifying the URL (Universal Resource Locator), you are accessing some web application. The
main components of a web application written in .net are:

 ASP.Net (aspx files)

 HTML
ASP.Net (aspx file) are also .net programs, which run on the Server and then send the
result/response to the client. Aspx pages can be thought of as a combination of HTML and C# or
VB. net or any .net compatible language code.

You access the web application by specifying the URL. If the URL corresponds to an

HTML page the web server simply returns the HTML page to the client, which then displays it.
If the URL corresponds to the aspx, then it is executed on the Server and the result/response is
returned to the client, which is then displayed by the client. A web application is nothing but a
web-site.

2. Web Client:
In web client based architectures, the user interaction layer is separated from the traditional client
layer. Web browser manages the user interaction but leaves the rest to applications on the server
side, including the logic for driving the user interface, interacting with components in the
middle-tier, and accessing databases.

3. The HTTP Protocol:

The HTTP is an application – level protocol (generally implemented over TCP/IP Connection).
The HTTP is a stateless protocol based on requests & responses. In this paradigm, client
application (such as your web browser) sends request to the server (such as the web server of an
online store) to receive info (such as downloading a catalog) or to initiate specific processing on
the server (such as placing an order).

4.The Requirements for Developing & Hosting Web Applications:

The following are the most essential requirements for developing and hosting web applications:
 16

(ii) Server-side Runtime Support - This includes support for network services and a runtime
for executing the applications.

(iii) Deployment Support – Deployment is the process of installing the application on the
server. Deployment could also include customizing the application.
For building and running web applications, the .NET provides the following to meet each of the
above requirements:

(i) ASPX Pages:

These are the building blocks for developing web Applications in .NET. ASPX pages can be
developed using any dot net compatible language.
(ii) Web development Server for Hosting Web Applications:
IIS is providing .NET runtime for providing all the facilities for writing web applications in
.NET. The IIS is responsible for initializing, invoking and managing the life cycle of ASPX
files

(iii) Packaging Structure & Deployment Descriptor

The .NET specification defines a packaging structure for web applications. The
specification also defines a deployment descriptor for each web application. The
deployment descriptor is an XML file that lets you customize the web application at
deployment time

ASP.NET Applications
ASP.NET applications are divided into multiple web pages. This division means that a user can
often enter an ASP.NET application at several different points, and follow a link out of your
application to another part of your web site or another web server.

3.2.3 Economic
Personal Banking including personal finance, banking on an international arena, banking on a
priority basis.
Transaction Banking includes management of cash, facilities related to credit availability and
services related to trade.
Relationship services with the investors.
 17

Depository Services including dematerialized account openings and associated updates.

Internet Banking services comprising of account specifications, transaction details, performance
of monetary transactions, bill payment through electronic means, etc
Latest News and updates related to the market (world/national)
All the information related to the bank under the head of “About Us”
Specifications and online availability of loans, debit and credit cards, insurance and other
investment services.
 18

4. System Design
4.1 Scope:
Though there are many online systems available on internet but this can compete with them with
some advancement in its functionality and can be used by any bank organization to maintain
their customer’s account and online transaction process.

The basic functionalities of the system are:

 Create Account
 Login
 Update Profile
 Password Recovery
 View Profile
 ATM and Bank finder
 Contact Form
 Amount Transaction
 EMI and Loan Calculator
 Delete account
 Logout

4.2 Database design:

Database design is required to manage the large bodies of information. The management of data
involves both the definition of structure of the storage of information and provisions of
mechanism for the manipulation of information. in addition to the database system must provide
for the safety of information handled, despite the system crashes due to attempts art unauthorized
access. for developing an efficient data base , we will have to full fill certain condition such as:
 Control Redundancy

 Ease of use

 Accuracy and integrity

 Avoiding inordinate delays

 Recovery from failure

 19

 Privacy and security

 Performance

There are 6 major steps in design process. The first 5 steps are usually done on paper and finally
the design is implemented.
 Identify the tables and relationship

 Identify the data that is needed for each table and relationship

 Resolve the relationship

 Verify the design

 Implement the design

NORMALIZATION
Normalization is a technique that is more applicable to record based data models. Each of the
process can be carried out independently to arrive at normalized tables. Normalization refines the
data structure and data are group in simple way as possible. So later changes can be bring about
the least impact on database structure and eliminates data redundancy.

DATA INTEGRITY
Data integrity refers to the procedure that ensures correctness of the data entered in the database.
Functions have been provided in the software, which check data while being entered. Integrity
problems are occurred due to hardware or software malfunctions such as power failure and disk
crashes. Side effect from the program development may also be the reason.

DATA CONSISTENCY
Problem with data consistency occur when adding records without first checking for records with
same key or deleting records without deleting other related records. Likewise the software is
coded such that primary keys can’t be duplicated. For developing an efficient database, we have
to fulfill certain conditions such as :
• Control redundancy
 20

• Ease of use
• Data independence
• Privacy and security
• Performance
For achieving the above criteria’s we have to make use of various features that are available with
DBMS such as:
• Enforcing integrity constraints to ensure data integrity and to reduce data inconsistency.
• Recovery from failures using backup facility.

DATABASE TABLES AND STORED PROCEDURES

* DATABASE TABLES
1. bk_register
This table has been included in many modules such as Login, register, Update, View Profile,
Transaction, Password Recovery.

2.contact
This table has been used in the contact page where user can submit the feedback and queries
along with his name and email id
 21

3.loc
This table has been used in the ATM and Bank finding Module where one can find the address of
ATM or bank by providing the type and the state

* STORED PROCEDURES
A stored procedure is a subroutine available to applications accessing a relational database
system. Stored procedures (sometimes called a proc, sproc, StoPro, StoredProc, or SPS) are
actually stored in the database data dictionary.

Following are the stored procedures used in this system :

 sps_contact

 sps_forgot

 Sps_Global

 sps_loc

 sps_register

 sps_transac

4.3 Data flow diagram (DFD)

Data Flow Diagrams - Introduction

Data flow diagrams can be used to provide a clear representation of any business function. The
 22

technique starts with an overall picture of the business and continues by analyzing each of the
functional areas of interest. This analysis can be carried out to precisely the level of detail
required. The technique exploits a method called top-down expansion to conduct the analysis in
a targeted way.

External
Entity Process Data store

Data Store Process

External
Entity

Process
Data Store

There are only five symbols that are used in the drawing of business process diagrams (data flow
diagrams). These are now explained, together with the rules that apply to them.

2 Counter
Enquiries
Customer D2 Account Details
CASH Deposits &
Withdrawals
External Entity

Customer
 23

An external entity is a source or destination of a data flow which is outside the area of study.
Only those entities which originate or receive data are represented on a business process
diagram. The symbol used is an oval containing a meaningful and unique identifier.

Process

2 Counter

Enquires
Deposits and Withdrawals

A process shows a transformation or manipulation of data flows within the system. The symbol
used is a rectangular box which contains 3 descriptive elements:
Firstly an identification number appears in the upper left hand corner. This is allocated arbitrarily
at the top level and serves as a unique reference.
Secondly, a location appears to the right of the identifier and describes where in the system the
process takes place. This may, for example, be a department or a piece of hardware. Finally, a
descriptive title is placed in the centre of the box. This should be a simple imperative sentence
with a specific verb, for example 'maintain customer records' or 'find driver'.
 24

Data Flow

ACCOUNT
INFORMATION

A data flow shows the flow of information from its source to its destination. A data flow is
represented by a line, with arrowheads showing the direction of flow. Information always flows
to or from a process and may be written, verbal or electronic. Each data flow may be referenced
by the processes or data stores at its head and tail, or by a description of its contents.

Data Store

D2 Account Details

A data store is a holding place for information within the system:

It is represented by an open ended narrow rectangle.
Data stores may be long-term files such as sales ledgers, or may be short-term accumulations: for
example batches of documents that are waiting to be processed. Each data store should be given
a reference followed by an arbitrary number.

Resource Flow

Cash

A resource flow shows the flow of any physical material from its source to its destination. For
this reason they are sometimes referred to as physical flows.
The physical material in question should be given a meaningful name. Resource flows are
usually restricted to early, high-level diagrams and are used when a description of the physical
flow of materials is considered to be important to help the analysis.
 25

4.4 Entity relationship diagram(E- R diagram)

Customer
Trust boundary

Withdrawal Request

Auth User Auth Z

Transaction

Identity

Withdrawal Account Balance

Request Policies

New Balance Perform

Transaction
Account

Account Balance

Audit log

4.5 Module description

4.5.1 CREATE ACCOUNT
This module is used by the user to create a new account to join services of online banking.
The user is required to fill in a few details and is automatically assigned as an user at the end
of process.
 26

4.5.2 LOGIN
This module is used by all the users to log into the account. The user is required enter his/her
user name and password. After login user will be redirected to the user’s home page.
4.5.3 UPDATE PROFILE
Update profile module will be used to update or change any detail of user such as address,
phone number, city, state, etc.
4.5.4 PASSWORD RECOVERY
This module is used to recover the lost password by the user by entering his/her valid email
address. This email address will be matched from database and automatically generated
email will be sent to the user containing his/her user name and password.
4.5.5 VIEW PROFILE
This module is the automatically generated page when user clicks the view profile button.
This contain the user account detail such as name, account balance, email id, address, city.
4.5.6 ATM AND BANK LOCATOR
This module is used to find the address and location of ATM and banks in the selected city.
4.5.7 AMOUNT TRANSACTION
This module is the user view page after login where he/she can transfer the amount to other
account by providing the amount to be transferred and the account number where to be
transferred.
4.5.8 CONTACT FORM
This module is used by both registered and non-registered user to contact bank or to give any
feedback trough message. His/her message will be saved into the database and further bank
can contact him/her.
4.5.9 EMI AND LOAD INTEREST CALCULATOR
This module is used to calculate the interest amount of EMI and load by proving the interest
rate, total amount and duration.
4.5.10 DELETE ACCOUNT
This module is used to delete the user’s account by the confirmation of user.
4.5.11 LOGOUT
This module is used to logout from the user’s session and redirected to the home page of
website
 27

5. Interface requirement

5.1 Graphical interface

 Internet Explorer

 Google Chrome

 Mozilla Firefox

 Opera

5.2 Command line interface

 Notepad ++

 Dreamweaver

 Visual Studio

5.3 Hardware interface

 Intel Pentium-IV processor

 256 MB RAM or higher

 40 GB HDD or higher

 Printer

 UPS

 LAN Connectivity (Assets Management should be accessible through Intranet)

5.4 Software interface

 Microsoft Windows XP / 2000 or Above.

 Dot Net framework 2.0 OR ABOVE

 IIS

 RDBMS (Back end): Sql Server

 Web Browser: Internet Explorer6 or higher, Mozilla Firefox, Opera.

 Front End: HTML and Asp.net, C#.

 28

6. Performance requirement
The completion of a system is achieved only after it has been thoroughly tested. Though this

gives a feel the project is completed, there cannot be any project without going through this

stage. Hence in this stage it is decided whether the project can undergo the real time environment

execution without any break downs, therefore a package can be rejected even at this stage.

6.1 SYSTEM TESTING

Testing is a set of activities that can be planned in advance and conducted systematically. The

proposed system is tested in parallel with the software that consists of its own phases of analysis,

implementation, testing and maintenance. Following are the tests conducted on the system.

6.2 UNIT TESTING

During the implementation of the system each module of the system was tested separately to

uncover errors with in its boundaries. User interface was used as a guide in the process.

6.3 MODULE TESTING

A module is composed of various programs related to that module. Module testing is done to

check the module functionality and interaction between units within a module.

It checks the functionality of each program with relation to other programs within the same

module. It then tests the overall functionality of each module.

 29

6.4 INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure while

conducting tests to uncover errors associated with interfacing. The objective is to take unit-tested

module and build a program structure that has been dictated by design.

6.5 ACCEPTANCE TESTING

The software has been tested with the realistic data given by the client and produced fruitful

results. The client satisfying all the requirements specified by them has also developed the

software within the time limitation specified. A demonstration has been given to the client and

the end-user giving all the operational features.

 30

7. Non functional attributes

7.1 Security
Event management is the application of project management to the creation and development
of festivals, events ,extra vagenga and conferences.

Event management involves studying the intricacies of the brand, identifying the target audience,
devising the event concept, planning the logistics and coordinating the technical aspects before
actually executing the modalities of the proposed event. Post-event analysis and ensuring a return
on investment have become significant drivers for the event industry.

The recent growth of festivals and events as an industry around the world means that the
management can no longer be ad hoc. Events and festivals, such as the Asian Games, have a
large impact on their communities and, in some cases, the whole country.

The industry now includes events of all sizes from the Olympics down to a breakfast meeting for
ten business people. Many industries, charitable organization and interest groups will hold events
of some size in order to market themselves, build business relationships, raise money or
celebrate.

7.2 Reliability
Internet banking renders location and time irrelevant, and empowers customers with greater
control of their accounts. Banks achieve cost and efficiency gains in a large number of
operational areas. This paper addresses the aspects of reliability and accessibility from a banking
enterprise point of view and puts forth present day solutions to problems involving these issues.
An Indian perspective of Internet banking is also looked at in order to gaining a better
perspective regarding the situation.

7.3 Maintainability
 The aptitude of a system to undergo repair and evolution.
 (1) The ease with which a software system or component can be modified to correct
faults, improve performance or other attributes, or adapt to a changed environment.
 (2) The ease with which a hardware system or component can be retained in, or restored
to, a state in which it can perform its required functions. [IEEE Std. 610.12]

7.4 Portability
Portability in high-level computer programming is the usability of the same software in
different environments. The prerequirement for portability is the generalized abstraction between
the application logic and system interfaces. When software with the same functionality is
 31

produced for several computing platforms, portability is the key issue for development cost
reduction.

7.5 Reusability
In computer science and software engineering, reusability is the likelihood a segment of source
code that can be used again to add new functionalities with slight or no modification. Reusable
modules and classes reduce implementation time, increase the likelihood that prior testing and
use has eliminated bugs and localizes code modifications when a change in implementation is
required.
Subroutines or functions are the simplest form of reuse. A chunk of code is regularly organized
using modules or namespaces into layers. Proponents claim that objects and offer a more
advanced form of reusability, although it has been tough to objectively measure and define levels
or scores of reusability.
The ability to reuse relies in an essential way on the ability to build larger things from smaller
parts, and being able to identify commonalities among those parts. Reusability is often a required
characteristic of platform software. Reusability brings several aspects to software
development that do not need to be considered when reusability is not required.
Reusability implies some explicit management
of build, packaging, distribution, installation, configuration, deployment, maintenance and upgra
de issues. If these issues are not considered, software may appear to be reusable
from design point of view, but will not be reused in practice.
Software reusability more specifically refers to design features of a software element (or
collection of software elements) that enhance its suitability for reuse.

7.6 Resource utilization

A supply chain network uses resources of various kinds: manufacturing resources (machines,
material handlers, tools, etc.); storage resources (warehouses, automated storage and retrieval
systems); logistics resources (trucks, rail transport, air-cargo carriers, etc.); human resources
(labor, scientific and technical personnel); and financial (working capital, stocks, etc.). The
objective is to utilize these assets or resources efficiently so as to maximize customer service
levels, minimize lead times, and optimize inventory levels.

7.7 Stable and speed efficiency

The implementation is the final and important phase. It involves User training, system testing
and successful running of the developed system. The users test the developed system when
changes are made according to the needs. The testing phase involves the testing of the developed
system using various kinds of data. An elaborate testing of data is prepared and system is tested
using the tests data.
 32

Implementation is the stage where theoretical design turned into a working system.
Implementation is planned carefully to propose system to avoid unanticipated problems. Many
preparations involved before and during the implementation of proposed system. The system
needed to be plugged in to the organization’s network then it could be accessed from anywhere,
after a user logins into the portal. The tasks that had to be done to implement the system were to
create the database tables in the organization database domain. Then the administrator was
granted his role so that the system could be accessed.

The next phase in the implementation was to educate the system. A demonstration of all the
functions that can be carried out by the system was given to examination department person, who
will make extensive use of the system.
 33

8.Security

8.1 Description
Event management is the application of project management to the creation and development
of festivals, events ,extra vagenga and conferences.

Event management involves studying the intricacies of the brand, identifying the target audience,
devising the event concept, planning the logistics and coordinating the technical aspects before
actually executing the modalities of the proposed event. Post-event analysis and ensuring a return
on investment have become significant drivers for the event industry.

The recent growth of festivals and events as an industry around the world means that the
management can no longer be ad hoc. Events and festivals, such as the Asian Games, have a
large impact on their communities and, in some cases, the whole country.

The industry now includes events of all sizes from the Olympics down to a breakfast meeting for
ten business people. Many industries, charitable organization and interest groups will hold events
of some size in order to market themselves, build business relationships, raise money or
celebrate.

8.2 Technical issues

 Software companies service event planners with a complete Tool, Hotel Booking Tool,
Travel Booking Tool, Budgeting Tool etc.
 As far as the technical issues related to this project from security point of view, there is
no chance of steal the data until either we want or if there is any problem in the coding
section.

8.3 Cost and schedule

Merely we think of the cost estimation on the basis of the following points:

Static IP for WEB ---- null

Paper work & reports ---- Rs.400
 34

Labour costs ---- null

Other expenses ---- Rs. 50

Now looking at the time limit of 15 days and working for 2 hours and work to do we can
divide our work in following parts and complete it.

8.4 Risk
Risk is the term applied to a logical and semantic method of establishing the context,
identifying, analyzing, evaluating, treating, monitoring and communicating risks associated with
any activity, function or process in a way that will enable organizations to maximize
losses and minimize opportunities.

The complete RISK ANALYSIS is given below in the table :-

S.NO. RISK ITEMS. RISK MANAGEMENT TECHNIQUES.
1. Personnel Team comprises of the persons who are ignorant or novice in the
Shortfalls security issues and also in the technology that we are going to use
for the implementation of the same.
2. Unrealistic The term/ time span allotted is very short, quite insufficient and the
Schedule and things are really next to impossible to be in such a short span of
Budget time, with the same working hours per day.
3. Developing the Mission Analysis is strong but what if a person or more gets
wrong s/w diverted from.
functions
4. User interface For the user interface developed , even after getting it sanctioned
from the opposite side if it denies to accept the existing user
interface.
5. Continuation What if the user side even after signing the contract are
stream of continuously asking for the changes and modification an undue
requirement problem would be there in the development of the software and
changes. undue time would be utilized for the same which can ultimately
result in a delay in the project.
 35

Risk may occur with the WEB is

 Internet speed
 Proper security and communication for password and premium
submission.

We have to take certain important measures to not face these risks to occur.
 36

9. Reference & Appendices

 www.google.com

10. Conclusion

This project was successfully completed within the time span allotted. The project Online
Banking has been developed in asp.net. All the modules are tested separately and put together to
form the main system. Finally the system is tested with real data and everything worked
successfully. Thus the system has fulfilled the entire objective identified.

The system had been developed in an attractive dialogs fashion. So user with minimum
knowledge about computers can also operate the system easily. It will make easy interactions
between users and store. The speed and accuracy are maintained in proper way.