Sunteți pe pagina 1din 17

A

Software Requirement Specification

”Bank Management System”

Software Requirement Specification

Prepared By:

Md. Arshad Ayub


Vinay P
Vinay kumar MJ

Student of NIIT Malleshwaram, Bangalore.

Under the guidance of

Mr.Nishant

(Faculty, NIIT)

1
CONTENTS
 Acknowledgement

1. Introduction
1.1 Purpose
1.2 Scope of the product
1.3 Technologies used
1.4 Overview of the remainder of the document

2. General description
2.1 Product perspective

3. Requirements
3.1 Software Interface
3.2 Hardware Interface
3.3 Product Functions
3.4 User characteristics
3.5 Constraints
4. Design
5. Conclusion
6. References
 Certificate
2
1. Introduction

1.1 Purpose
This project is standalone application that can be accessed anywhere on the suitable computer system. This
application is useful to access their account and perform transactions. This is one integrated system that contains two
different types of users: an administrator (Bank Official) to manage customers and accounts, and the bank customers to
do transaction and maintain their account information.

1.2 Scope of the Product


 Create two different application users, Administrator and the customers providing them with access to the
centralized system by issuing username and password.
 Manage all the account details such as user name, customer’s account number, balance, address, phone number
etc.
 Keep track of all the account holders and their contact details.
 Confirmation of end user identity and will verify which users are authorized to receive support.
 Customers can access account information and perform operations on accounts.

1.3 Technologies Used


CORE JAVA: Application Architecture

MS - Access: Database

Swing: Advanced Java Abstract Window Toolkit

Net Beans: IDE used for (GUI) Development

1.4 Overview
SRS includes two sections:

Overall description describes the major components of the system, interconnection and external interfaces.

Specific Requirements describes the functions of the actors, their role in the system and constraints.

3
2. General Description

Describes the general factor that affects the products and its requirement.

Overview of the remainder of the document


2.1 Product Description

 This system has two types of users Application administrator and the Bank customers.

 GUI (Graphical User Interface) is provided by Swing technology.

 The programming logics are supported by java programming language which includes classes, interfaces and
certain predefined abstract methods.

 Database is accessed through the programming codes with the help of ODBC Bridge drivers. DSN (Data Source
Name) is used to specify the description of the database through MS-Access driver.

 Security measures are taken as major task by verification directly through database.

4
3. Requirements

3.1. Software Interface


Client using product: JDK, OS (any).

Development End: Java, Net beans, JAVA swing, MS-Access, OS (Windows XP),SQL(for query language).

3.2. Hardware Interface

Client side
RAM: 512 or higher

Hard Disk: 10GB or higher.

Computer processor: Pentium IV

Clock Speed: 700 MHz processor.

3.3. Product Functions


 Administrator can create customers and assign accounts to customers.

 Administrator could be able to enquire about the customer only by providing the Account number only.

5
 A person/customer should be able to login into the application through the first page of the application.

 Customer could be able to check account, perform transaction like withdrawl,deposite.

3.4. User characteristics

 Every user should be comfortable of interacting with computer installed in the bank should be having the basic
knowledge of English.

 Customer should remember there user name and password which they got during Account opening.

3.5. Constraints

 GUI is in English.

 Login and password is used for authentication and there is no guest facility.

 Application is working for a single system.

 Backup should be available.

6
4. Design
4.1 USE-CASE DIAGRAM

login
update

customer
create
Login/logout

remove
withdraw
account Customer
enquire
deposit

Administrator logout

7
Use case specification:
Authentication
Actor: Administrator

Preconditions:

The username and password are already stored on the system.

Basic Flow: 1. Enter Username and password.

2. Submit.

3. Username and password checked from database and logged on to the system.

Alternative Flow: 1. If the username and password entered is not correct a message appears. Invalid user, enter again.

Post conditions:

The administrator is logged on to the system. She/he can enquire the customer’s account, create customer account and
delete customer’s account.

Enter username and password


8
a

Username/password

incorrect

Actor: Bank Customer

Preconditions:

The username and password are already stored on the system.

Basic Flow: 1. Enter Username and password.

2. Submit.

3. Username and password checked from database and logged on to the system.

Alternative Flow: 1.If the username and password entered is not correct a message appears. Invalid user, enter again.

Post conditions:

The user is logged on to the system. She/he can do the transaction (withdraw/deposit) with their account.

Enter username and password

9
Username/password
incorrect

Compile-time Runtime
Environment

Java Source (.java) Class loader Byte code Java Class Library
verifier

Java Just in Time


Ivnterpreter
Interpreter Compiler

Java Byte code move logically or through


Java Compiler Runtime system

Java Byte code (.class) Operating system

Hardware
10
Java Environment / Life Cycle of Java Code

JDBC Driver Types

Java Application
JDBC
API
JDBC Driver Manager
JDBC Driver
API
JDBC-Net JDBC-ODBC Driver Driver
Driver Bridge Driver A B JDBC
ODBC and DB
implementation
Driver
alternatives

JDBC
Middleware Proprietary database Access Protocols
Protocol

Tables:-

Name of
Name of the Table Data_Type Description
attribute

11
Uname text User identification no (Primary Key)
Admin login
Password text password

Name of
Name of the Table Data_Type Description
attribute
Acc text Account number(Primary key)

Login Uname text User identification name

password Text password

Name of
Name of the Table Data_Type Description
attribute
Acc text Account number(Primary key)

Balance Uname text User identification name

Balance Number Balance in the customer’s account.

Name of
Name of the Table Data Type Description
attribute
Acc Text Account number (Primary Key)

Uname Text User identification name


Details
Address Text Address

Phone Text Phone number

12
Snapshots:-

Fig 1.Welcome page

13
Fig 2.Administrator login page

Fig 3.Customer’s login page

14
Fig 4.Administrator’s login page

15
Fig 5.Customer’s login page

5. Conclusion
Features for Bank management system

 This standalone application provides several inbuilt features for safe and secure banking.
 Administrator can enquire user’s profile.
 Administrator can delete user’s profile.
 Administrator can create user’s profile.
 User can use this software to automate the functioning of her/his account.
 User can also perform account checking, periodic accounting operation etc. by providing the correct
user name and password.
 The GUI is user friendly, and easy to use.

6. References
16
 Books: JAVA complete reference, Black book.
 Websites: www.google.com,www.w3schools.com.

17

S-ar putea să vă placă și