[attachment=14238]
ABSTRACT
The I-Connect is an application that has been developed for a well-established regional bank operating primarily in south India. The bank has several branches in key cities and towns in the north. In the world of this competitive environment and technological development, the bank has been totally computerized in the last 3 years, and to increase its customer base has started planning, for a concept called as e-banking; with this concept the bank wants to move very nearer to the customers and increase its basic operational strategies. Through I-Connectthe bank wants to introduce the core concept of IT based Enabled Services (ITES). The I-Connectservices are executed only upon the customer, and these I-Connectservices would fully integrate with the core banking solution that is already in usage. The major idea is to provide a series of services to the customer through the internet, and make the customer feel flexible in calling out simple tasks faster instead of making visit to the bank every time. The I-Connectservice is open only to savings bank. Customers and not for current account holders. The customer is privileged to use most of the system only as a viewing phase, the only online transactions the customer can do are chequebook requisition and fund transfer among his personal accounts.
The project ahs been planned to be having the view of distributed architecture, with centralized storage of the database. The application for the storage of the data has been planned. Using the constructs of MS-SQLServer2000 and all the user interfaces have been designed using the ASP.Net technologies. The database connectivity is planned using the “SQL Connection” methodology. The standards of security and data protective mechanism have been given a big choice for proper usage. The application takes care of different modules and their associated reports, which are produced as per the applicable strategies and standards that are put forwarded by the administrative staff.
INTRODUCTION
1.1 Purpose of Project
This document contains a description for “E-Banking” enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers. Section 2 is concentrated more on the
1.2 Scope of the project
The entire project has been developed keeping in view of the distributed client server computing technology, in mind. The specification have been normalized up to 3NF to eliminate all the anomalies that may arise due to the database transaction that are executed by the general users and the organizational administration. The user interfaces are browser specific to give distributed accessibility for the overall system. The internal database has been selected as MS-SQL server 200.The basic constructs of table spaces, clusters and indexes have been exploited to provide higher consistency and reliability for the data storage. The MS-SQL server 200 was a choice as it provides the constructs of high-level reliability and security. The total front end was dominated using the ASP.Net technologies. At all proper levels high care was taken to check that the system manages the data consistency with proper business rules or validations. The database connectivity was planned using the latest ”SQL Connection” technology provided by Microsoft Corporation. The authentication and authorization was crosschecked at all the relevant stages. The user level accessibility has been restricted into two zones namely. The administrative zone and the normal user zone.About the OrganizationThe National Bank (TNB) is a well-established regional bank operating primarily in south India, but with several branches in key cities and towns in the North.
PROJECT OVERVIEW
The general description gives an "executive overview" and is very client-oriented. It expounds on the functional and data requirements of the application. It also lists the limitations, assumptions and dependencies of the application. Section 3.0, the specific requirements section, includes the developers’ technical view of the client's expectation of the application. It also touches on the performance and quality requirements of the application and provides a solid definition of the interface