GLOBSYN SUMMER SCHOOL-2011 ORACLE-SONARPUR(12:30pm to 3:30pm)

Software Requirement Specification- Banking Management System

MEMBERS
ABHISHEK GUPTA Birbhum Institute Of Engineering and Technology Form No. -5047 ANIRBAN DAS Durgapur Institute of Advanced Technology and Management, Form No.-5081 ANKEET GHOSH Techno India College of Technology, Form No.-4970 BIKRAMJIT BANERJEE Camellia School Of Engineering And Technology, Form No.-4014 SHERYASHI MAZUMDER Calcutta Institute Of Technology, Form No.-4804 SOMRITA MITRA Camellia School Of Engineering And Technology, Form No.-4050

PROJECT FACULTY
CHAYAN DEBNATH
1|Page

Index & Tables 1) Introduction.......................................................................................................................3

1.1) Purpose...............................................................................................................................3 1.2) Scope:.................................................................................................................................3 1.3) programmer interface used:................................................................................................4 1.4) References: ........................................................................................................................4 1.5) Technologies:...............................................................................................................5 1.6) Overview:...5 2) Overall Description: ...........................................................................................................6 2.01) Product Perspective:.................................................................................................6 2.02) Software Interface:...........................................................................................................7 2.03) Hardware Interface:..........................................................................................................7 2.04) Communication Interface: ...............................................................................................7 2.05) User Characteristics: ........................................................................................................7 2.06) Constraints: ................................................................................................................7

user of the system......8

2.07) Use-Case Model Survey: ..............................................................................................8-11 2.07.01)user details....12 2.07.02) class diagram........13 2.08) Assumptions and Dependencies: ......................................................................................14 3) Specific Requirements: .....................................................................................................................14

3.1) Supplementary Requirements: .....................................................................................14

4) Valiadation: .......................................................................................................................................15

2|Page

1. Introduction:
1.1. Purpose:
ALLTIME Bank has branches in different location in India. They want to develop one automated system for the branches which will maintain the customer accounts along with different type of transactions. The users of the application are the employee of different branches. Customers are coming to different counters of branch for different type of operations as given below after filling the form for the specific operations with the required data.

1.2. Scope:
Creating new account (Savings, Credit) Savings account minimum balance should be 1000. No balance restriction for Credit account. Account no should generate automatically by the system. Modifying the account details ( address , phone no) Withdrawing Amount Depositing Amount Transferring Amount from one account to another account. Bill Payment: BSNL Bill payment CESC Bill Payment

Vodafone Bill Payment Display all transaction details between the given dates for a specific account no.

3|Page

1.3 . Programmer interface used:

HTML: Hypertext Markup Language is a markup language used to design static web pages. ORACLE: Oracle database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications. ORACLE FORMS DEVELOPER: Oracle forms developer is an application server that runs business applications and supports the oracle and web services standard. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between Web browser & a Web Server. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer) TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP.

1.4 . References:

IEEE Standard SRS Format An Integrated Approach to Software Engineering, Third Edition by Pankaj Jalote, Narosa Publishing House SQL,PL/SQL by Ivan Bayross

4|Page

1.5 . Technologies:
o Oracle Forms Developer: Application architecture o Oracle 10g: Database o i-Sql plus: Architecture designing

1.6 . Overview:
Overall description of the major components, interconnection between the users, external interface of the project Detailed requirements of the actors i.e. the users of the system and their roles in the system and constraints

5|Page

2. OVERALL DESCRIPTION:
Description of the general factors that affect the product and its requirements.

2.01. Product perspective:

HTTP and HTTPS

Users terminal of the system (HTML client)

Oracle Forms

(application server) TCP/IP System User (Client Software)

ORACLE

The web pages (XHTML/UML) are present to provide the user interface on customer client side. Communication between customer and server is provided through HTTP/HTTPS protocols. The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used. On the server side web server is for EJB and database server is for storing the information.

6|Page

2.02. Software Interface:

Client on Internet: Web Browser, Operating System (linux,windows) Client on Intranet: Client Software, Web Browser, Operating System (linux,windows) Web Server: Oracle Forms, Operating System (linux,windows) Data Base Server: DB2, Operating System (linux,windows) Development End: Oracle Forms Developer Oracle 10g, OS (Windows), Web Server.

2.03. Hardware Interface:

Browser CLIENT SIDE Processor RAM Disk Space

Internet exploer(6.0 onwards),Mozzilla Firefox,safari SERVER SIDE Oracle Forms Builder application server Oracle

Pentium series, AMD processors

256 MB (onwards)

1.5 GB

Pentium series, AMD processors Pentium series, AMD processors

1GB (onwards)

2.5 GB

1GB (onwards)

1.5 GB(without data)

2.04. Communication Interface:

Client on Internet will be using HTTP/HTTPS protocol. Client on Intranet will be using TCP/IP protocol.

2.05. User Characteristics:

Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.

2.06. Constraints:
GUI is only in English.
7|Page

 Unique Login and password is used for unique identification of the employees(least rank is bank_employee),the senior and junior managers and the DBA This system is working for single server. There is maintainability of back up so availability will not get affected. Limited to HTTP/HTTPS.

Users Of The System: A. Employees: a. Senior Managers b. Junior Managers c. Normal Bank Employees
B. System Architect (system developer) C. System administrator (super user of the system)

8|Page

9|Page

2.07. USE CASE MODEL SERVEY:

**SYSTEM USER PYRAMID STRUCTURE**

10 | P a g e

11 | P a g e

2.07.01. USER DETAILS: Customers: This is the primary user of the system having no access to the main database. This class mainly interacts with the basic employee of the system. i.e. the normal bank employee. Normal bank employee: This is the primary user of the system having restricted access to the system. People in this group have unique user id and password to access the system in specified domain. This class has the direct access to the end user of the system i.e the customers. Junior Manager: These people have access to the system information with restrictions. The main work of these people is to store the data for the customers and the employees with relevant branches. These people can directly interact with the senior managers. Senior Manager: These people have access to the system information with restrictions. The main work of these people is to manipulate and modify the data and store all relevant employee information. They can directly access to the DBA with some restrictions. System Architect: These people have access to the system information with full permissions to design the database and end user environments.

System administrator:
This person is the super user i.e. the controller of the total system implemented having his/her own unique id password. This user can change, control, and modify each system module.

12 | P a g e

2.07.02. Class Diagram:

13 | P a g e

2.08. Assumptions and Dependencies:

The details related to the customer should be reported manually within the specified time by the customer. Administrator is created in the system already. Roles and tasks are predefined.

3. Specific Requirements: 3.01. Supplementary Requirements:

Have hours of operation that are 24 x 7 Because system can be an automated process, so it can stay open for 24 hours a day. If the base is now the entire world, staying open 24 hours a day becomes critical. System is required to be available 24X7 so UPS support must be on server site for at least 8 hours in case of power failure. System will remain inaccessible to users at 2:00 to 4:00 am for backup and maintenance purpose. Make the existing Web site more dynamic in nature Many early Web implementations consisted of static HTML pages. This becomes very difficult to manage if the number of pages gets too large. An effective system should be largely dynamic taking advantage of technology that automates this process rather than relying on manual processes. Application should serve dynamic user based customized web pages to its clients from server. Tie the existing Web site into existing enterprise systems Any existing Web site that relies on the manual duplication of data from another system is one that can be improved. Most of the business data in the world today exists in enterprise servers that can be connected to the Web servers to make this process far more effective.

14 | P a g e

Provide good performance and the ability to scale the server The Web Application Server should provide good performance and the ability to manage performance with techniques, such as support for caching, clustering, and load balancing.

Providing session management capability Web application developers should not spend valuable time worrying about how to maintain sessions within the application. The web Application Server should provide these services.

4. Validation:
Every table has a primary key, so no chance of duplicate value. There is some restriction for every transaction action, so if some action or transaction violates that restriction it cannot be successful. People can get their required data about the products very easily and very fast.

*********************************************************************

15 | P a g e