Contents

1.SRS 2.Use Case Diagram 3.Data Flow Diagrams 4.ER Diagram 5.Class Diagram 6.Simulation

Software Requirements Specification

for

Bank Management System

Prepared by Saurav Chandra

Ambedkar Institute of Advanced Communication and Technologies

Table of Contents
1. Introduction..............................................................................................................................................4 1.1 Purpose ..............................................................................................................................................4 1.2 Document Conventions......................................................................................................................4 1.3 Intended Audience and Reading Suggestions....................................................................................4 1.4 Project Scope.....................................................................................................................................5 1.5 References..........................................................................................................................................5 1.6 Overview............................................................................................................................................5 2. Overall Description..................................................................................................................................6 2.1 Product Perspective............................................................................................................................6 2.1.1 System Interfaces........................................................................................................................6 2.1.2 User Interfaces............................................................................................................................7 2.1.3 Hardware Interfaces....................................................................................................................8 2.1.4 Software Interfaces.....................................................................................................................8 2.1.5 Communication Interfaces..........................................................................................................8 2.1.6 Memory Constraints....................................................................................................................8 2.2 Product Functions..............................................................................................................................9 2.3 User Classes and Characteristics.......................................................................................................9 2.4 Design and Implementation Constraints..........................................................................................11 2.5 Assumptions and Dependencies......................................................................................................11 2.6 Apportioning of Requirements........................................................................................................11 3. Specific Requirements...........................................................................................................................12 3.1 External Interface Requirements......................................................................................................12 3.1.1 User Interface............................................................................................................................12 3.2 Performance Requirements..............................................................................................................13 3.3 Design Constraints...........................................................................................................................14 3.4 Software system attributes...............................................................................................................14 3.4.1 Security.....................................................................................................................................14 3.4.2 Maintainability..........................................................................................................................14 3.4.3 Portability..................................................................................................................................14 3.5 Other Requirements.........................................................................................................................14

1.

Introduction

1.1

Purpose

This document aims at defining the overall software requirements for Bank Management System version 1.0. Efforts have been made to define the requirements exhaustively and accurately. The final product will be having only features/functionalities mentioned in the document and assumptions for any additional functionality/features should not be made by any parties involved in developing/testing/implementing/using this product. In case it is required to have some additional features, a formal change request will need to be raised and subsequently a new release of this document and/or product will be produced. It also states the various required constraints by which the system will abide.

1.2

Document Conventions

The following abbreviations have been used in rest of the document: SRS : Software Requirement Specification. BMS : Bank Management System. Engg : Engineering. Admin : Administrator. Dept : Department.

1.3

Intended Audience and Reading Suggestions

The document is intended for developers, project managers, banking staff, users, testers, and documentation writers. The audience should be at least graduate and comfortable with English language and should be well informed with various banking processes. Also one should have basic knowledge of computer and should understand its general terminology.

1.4

Project Scope

The software product BMS will be used for managing various processes involved in banking like debit, credit, loan, foreign exchange. The customers can debit money from the bank by providing their account no. The customers can deposit money the take interest from the bank. Bank also provides the facility of loan which its customers can take after providing some security to the bank. Also bank operates in foreign currency as per the customer needs following the legal procedure laid down by the government. This system will generate report at the end of each day. The application will greatly and simply speed up the various processes involved in banking system. It will provide easily manageable interface to the end-users to make it user friendly. Security will also be implemented in the software to avoid cheating and any misuse of information. For this different powers will be assigned to different users, eg.admin will have the highest power, manager a bit lower and so on.

1.5
(i) (ii) (iii) (iv)

References
Rules laid down by the RBI and government for the banks. IEEE Recommended Practice for Software Requirement Specifications IEEE Std 830-1993 Software Engg by K.K. Aggarwal, 2006 edition Software Engg by Roger S. Pressman, 2006 edition

1.6

Overview
The rest of this SRS document describes the various system requirements, interfaces, features and functionalities in detail.

2.

Overall Description

Bank Management involves various processes. It consists of cashiers who handle the debit/credit of the customers. Customers have to provide his account no. and some personal information for this purpose. Customers can use the facility of foreign exchange after completing legal formalities and then the currency is converted according to present day rates. Loan facility is also available so that customers in need can apply after providing some security and paying some rate of interest. Loan department is under Admin who has the authority to approve and provide loan. Admin can view the staff and information and customers can inquire about the new facilities through customer care. At the end of the day report are generated by the clerks giving the details about the transaction taking place in the day.

2.1

Product Perspective

The application will be a windows based, self contained and independent software project. This is the first version(v1.0) of BMS.

Front End Client Application (with loggingin / Update / View and Reporting facility.)

Back End Database

2.1.1 None

System Interfaces

2.1.2

User Interfaces

The application will have a user-friendly and menu based interface. Following screens will be provided : (i) (ii) (iii) (iv) (v) (vi) (vii) (viii) (ix) A login screen for entering the username, password, id no. Different Id no. will be provided to customers, administrator, clerk, cashier, customer care. There will be a screen for capturing and displaying information regarding what the customers want debit, credit, loan, inquiry or foreign exchange. There will be a screen in debit showing the balance amount of money left. There will be a screen in credit showing the balance amount of money left. There will be a screen in loan showing the limit of money that can be applied by the customer according to his previous records. There will be screen showing his pass-book details. Balance Sheet : The customers will be able to view the balance sheet of their account. There will be a screen which will show the message wrong id or password when that combination of id and password is not found in database. There will be a screen which will only be available to admin at which admin can assign powers / access to different users. The following reports will be generated each day : (i) (ii) (iii) (iv) (v) Debit report : It shows amount of money withdrawn from the bank by its customers. Credit report : It shows amount of money deposited to the bank by its customers. Loan report : It shows amount of loan money transaction taken place in the bank. Staff report : The staff members present today and addition of new staff members. Foreign Exchange Report : It shows the foreign exchange transactions of the bank.

2.1.3 (i) (ii) (iii) (iv) (v) (vi) 2.1.4 (i) (ii) (iii)

Hardware Interfaces Screen resolution of at least 800 x 600 required for proper and complete viewing of screens. Higher resolution would not be a problem. A touch screen panel is needed to take input from users accordingly they touch the screen for input. Support for printer with appropriate drivers installed and which is required for printing reports. Network systems are required to run the application so that all information is available to all actors of the system. Free space of 5GB on every system. At least 256 MB RAM in every system. Software Interfaces Any Windows based operating system (Microsoft Windows 95/98/2000/xp) C++ programming software should be installed. Microsoft Office installed on the computers.

2.1.5 None. 2.1.6

Communication Interfaces

Memory Constraints

At least 256 MB RAM and 5 GB of free space on hard disk will be required for running the applications.

2.2

Product Functions

The system will allow access only to authorized users with specific roles (Administrator, Clerk, Cashier, Customer Care, Customers). Depending upon the users role, he/she will be able to access only specific modules of the system. (i) (ii) (iii) (iv) (v) (vi) (vii) (viii) A Login facility for enabling only authorized access to the system. Customer will be able to debit/credit and apply for loans and could see his/her passbook details. Also customer can see balance sheet of his/her account anytime. Cashier will be able handle the cash and issues debit/credit but doesnt have the authority to handle loans. Admin can update staff information and issues loans to its customer and its recovery. Admin will allow foreign currency transaction after checking the documents as according to legal procedure. Clerk can only generate reports. It has no direct contact with the customer. Customer Care can only handles inquiries of the customer but it has no authority to access the database.

2.3

User Classes and Characteristics

Various user classes that will use this product are : (i) Admin : He/She should have following characteristics : Educational level : He/She should at least be a graduate and should be comfortable with English language. He/She should good management skills as well so as to manage all the things. Experience : He/She should be well informed with the various banking processes. He/She should know very well the criterion of how to distribute powers among other users. Technical Expertise : He/She should be comfortable using general purpose applications on a computer.

(ii)

Cashier : He/She should have following characteristics : Educational level : He/She should at least be a graduate and should be comfortable with English language. Experience : He/She should be well informed with the banking processes that involve credit and debit of cash. Technical Expertise : He/She should be comfortable using general purpose applications on a computer.

(iii)

Customer Care : He/She should have following characteristics : Educational level : He/She should at least be a graduate and should be comfortable with English language. Experience : He/She should be well informed with the various banking processes. He/She should be able to process queries so as to satisfy different customers as per their needs. Technical Expertise : He/She should be comfortable using general purpose applications on a computer.

(iv)

Clerk : He/She should have following characteristics : Educational level : He/She should at least be a graduate and should be comfortable with English language. He/She should have good knowledge of accounts. Experience : He/She should be well informed with the various banking processes especially accounting. Technical Expertise : He/She should be comfortable using general purpose applications on a computer.

(v)

Customer : He/She should have following characteristics : Educational level : He/She should at least be a graduate and should be comfortable with English language. Experience : He/She should be informed with the some banking processes like credit, debit, etc.

10

Technical Expertise : He/She should be comfortable using general purpose applications on a computer.

2.4
(i) (ii) (iii)

Design and Implementation Constraints

Since the DBMS being used is Microsoft office which is not a very powerful DBMS it will not be able to store a very large no. of records. Due to limited features of DBMS the system may become slow with the increase in number of records being stored. Due to limited features of DBMS being used, database auditing will not be provided.

2.5
(i) (ii) (iii) (iv)

Assumptions and Dependencies

The rate of interest is fixed for deposits as well as for loans. The minimum balance of Rs. 1000/- is fixed. The maximum withdrawal of money in a single transaction is fixed at Rs. 1,00,000/The bank should get registered copy of the softwares to be used: a) Microsoft Windows(any version stated above in section 2.4.1) b) Microsoft Office(for MS Access)

2.6

Apportioning of Requirements

Not required.

11

3.

Specific Requirements

This section contains the software requirements to a level of detail sufficient to enable designers to design the system, and testers to test that system.

3.1
3.1.1

External Interface Requirements

User Interface

The following screens will appear: a) Login screen:

This screen will be displayed first. It will allow user to access different screens based upon the users role. Various fields available on this screen will be (i) (ii) (iii) b) (i) (ii) (iii) (iv) (v) (vi) (vii) (viii) c) (i) (ii) Name: in alphabetical letters Id no: numeric no upto 10 digits Password: Alphanumeric upto 8 characters Inquiry/update screen: Inquiry about new policies then enter 1 want to debit enter 2 want to credit enter 3 want to apply for loan enter 4 want to apply for foreign currency enter 5 want to see reports enter 6 want to see pass-book details enter 7 want to exit enter 0 Debit screen: i) Shows the balance amount of money. ii) Enter the amount of money to be withdrawn.

12

d) (i) (ii) e) (i) (ii) (iii)

Credit screen: Shows the balance amount of money. Enter the amount of money to be deposited. Loan screen: The security that have to be submitted. The max. amount of money that can be borrowed. The rate of interest and time period.

f) Foreign currency screen: (i) (ii) (iii) g) (iv) (v) (vi) (vii) (viii) h) (i) (ii) (iii) Enter the currency wanted. Enter the currency to be converted. Present rate of the currencies. Reports screen: Shows total debit in the day. Shows total credit in the day. Shows total loan given in the day. Shows total no. of customers visited. Shows total no. of staff present. Passbook details screen: Shows the date of transaction. Shows the type of transaction. Shows the amount of transaction.

i) Exit screen Thanks giving screen.

3.2
None

Performance Requirements

13

3.3
None

Design Constraints

3.4
3.4.1

Software system attributes

Security

This application will be password protected. Users will have to enter correct passwords and username to access the application. 3.4.2 Maintainability

The application will be designed in a maintainable manner. It will be easy to incorporate new requirements in the individual modules. 3.4.3 Portability

The application will be easily portable on any windows-based system that has windows based OS.

3.5
None.

Other Requirements

14

Use Case Diagram

for

Bank Management System

15

Use Case Diagram

Administrator Login

Inquiry Cashier Debit Customer

Customer Care Credit

Loan Clerk

Foreign Currency

Staff Info

Recovery

Report Generation

16

Data Flow Diagrams

for

Bank Management System

17

Level0 DFD
Customer Administrator Debit, Credit or Foreign exchange the money Maintains passbook .handles credit, debit of customers Cashier

Maintenance of account info. Handles inquires of Customer customers care

Bank Managemen t

Generate Reports Clerk

Report generation

Staff info.

Report on transaction

18

ER Diagram
for

Bank Management System

19

Class Diagram
for

Bank Management System

Version 1.0 approved

20

Class Diagram

Login details NAME Id no. Password Addstaff() Addcustomer() delstaff() delcustomer()

Debit account no. showbalance() minbalance() modify()

Credit account no showbalance() minbalance() modify()

Loan account no showtimeduration() showbalance() showinterest() pass-book account no showbalance() showinterest() showdetails()

Report date type show() delete() modify()

foreign currency account no showpresentrates() exchange()

21

Simulation
for

Bank Management System

22

Simulation
#include<iostream.h> #include<conio.h> #include<graphics.h> #include<dos.h> #include<process.h> #include<math.h> main() { int gd=DETECT,gm,i,j; initgraph(&gd,&gm,"c:\\tc\\bgi"); setcolor(CYAN); settextstyle(1,0,4); outtextxy(90,20,"SOFTWARE RELIABILITY MODEL"); settextstyle(1,0,3); setcolor(WHITE); outtextxy(130,100,"BASIC EXECUTION TIME MODEL "); settextstyle(3,0,1); delay(2000); sound(4500); setcolor(RED); outtextxy(420,320,"MADE BY : ---"); delay(1000); outtextxy(450,340,"RAHUL CHUGH"); delay(1000); outtextxy(450,360,"ATUL KHANNA"); outtextxy(450,400,"CSE- VII SEM."); nosound(); setcolor(CYAN); outtextxy(80,420,"Press enter to continue "); int ch=getch(); if(ch==13) { cleardevice(); setcolor(CYAN);

23

outtextxy(80,20,"The basic parameters of this software are : "); cout<<"\n\n\n\n 1. ^ ----- Failure intensity " <<"\n\n 2. ^o ----- Initial failure intensity " <<"\n\n 3. Vo ----- Number of failures experienced " <<"\n\n 4. u ----- Average or expected number of failures experienced at a given point in time" <<"\n\n 5. t ----- Execution time "<<endl; outtextxy(80,420," press enter to continue "); int c=getch(); if(c==13) { while(1) { cleardevice(); setbkcolor(BLACK); settextstyle(2,0,8); setcolor(CYAN); outtextxy(80,20,"RELATIONSHIP BETWEEN PARAMETERS"); cout<<"1. Between Failure intensity(^) and mean failure experienced(u)"<<endl <<"\n\n2. Between mean failure experienced(u) and execution time(t)"<<endl <<"\n\n3. Between Failure intensity(^) and execution time(t) "<<endl <<"\n\n4. EXIT "<<endl; cout<<"\n\nENTER YOUR CHOICE(1,2 OR 3) TO SEE THE RELATIONSHIP OR 4 TO EXIT"<<endl; cin>>j;

switch(j) { case 1: cleardevice(); setbkcolor(BLUE); outtextxy(80,20,"Relationship between Failure intensity "); outtextxy(100,40,"AND Mean failures experienced "); settextstyle(1,0,1); outtextxy(130,110,"^o"); outtextxy(330,302,"Vo"); line(150,100,150,300); line(150,300,350,300); int x,y;

24

for( x=150, y=120;x<330,y<300;x++,y++) { if(kbhit()) break; putpixel(x,y,YELLOW); delay(200); } getch(); break; case 2: cleardevice(); setbkcolor(BLUE); outtextxy(80,20,"Relationship between execution time(t) "); outtextxy(100,40,"AND Mean failures experienced(u) "); settextstyle(1,0,1); outtextxy(135,180,"Vo"); line(150,100,150,300); line(150,300,350,300); arc(250,300,95,180,100); setlinestyle(DASHED_LINE,1,1); line(150,190,320,190); getch(); break; case 3: cleardevice(); setbkcolor(BLUE); outtextxy(80,20,"Relationship between execution time(t) "); outtextxy(100,40,"AND failure intensity(^) "); settextstyle(1,0,1); outtextxy(135,180,"^o"); line(150,100,150,300); line(150,300,350,300); arc(250,170,180,265,100); line(235,270,340,275); getch(); break; case 4: exit(0); } }

25

} } getch(); return 0; }

26