SDD

A Project SDD

On

“ONLINE BANKING SYSTEM”

SUBMITTED TO: UNDER THE GUIDANCE OF:Harshbardhan Barik MS.Aayushi

(Mini Project Coordinator) (Faculty IIMT Engineering College)

SUBMITTED BY:SHUBHAM GUPTA

RESHUAMBUJ CHAUHAN

VINITA

IIMT ENGINEERING COLLEGE MEERUT (127)

Table of Contents

Table of Contents.......................................................................................iiTable of Figures.........................................................................................iii1.0. Introduction..........................................................................................1

1.1. Purpose..................................................................................................11.2. Scope.....................................................................................................11.3. Glossary.................................................................................................11.4. References.............................................................................................21.5. Overview of document..........................................................................2

2.0. Architecture design...........................................................................33.1. Web System Architecture......................................................................4

Home Page................................................................................................5New registration........................................................................................6fund transfer...............................................................................................7Withdraw and deposit fund.......................................................................8Feedback & query Info 9Loan details ..............................................................................................7Banking Database.....................................................................................9

4.0. Data structure design 104.1. Data field types ..................................................................................11

5.0. Use case realizations.......................................................................12Use Case: Login.........................................................................................13Use Case: New registration........................................................................14Use Case: Withdraw fund..........................................................................15Use Case: Deposit fund..............................................................................16Use Case:E -banking………………………………………………………17 Use Case: Feedback................................................................................. 18

UseCase:Loan…………… ………………………………………… .19Use Case: Emlpoyee details.......................................................................20

Use Case: Generel information…………………………..……………. 216.0. Interface design................................................................................22Figure 23 Return used instead of Submit......................................................237.0. Help system design.........................................................................248.0. Index.....................................................................................................25

Table of Figures

Figure 1 Deployment Diagram......................................................................25Figure 2 Architecture Design........................................................................26Figure 3 System Sequence Diagram.............................................................27Figure 4 Login Sequence Diagram..............................................................28Figure 5 Registration Details Sequence Diagram........................................29Figure 6 Withdraw Sequence Diagram.........................................................30Figure 7 Depsit Sequence Diagram..............................................................31Figure 8 E-banking Sequence Diagram........................................................32Figure 9 Feedback Sequence Diagram..........................................................33Figure 10 Loan Sequence Diagram...............................................................34Figure 11 Employee details Sequence Diagram...........................................35Figure 12 Home page....................................................................................36Figure 13 login page......................................................................................37Figure 14 View and update profile page.......................................................38Figure 15 Transfer fund page........................................................................39Figure 16 New registration page...................................................................40Figure 17 Withdraw fund page.....................................................................41Figure 18 Deposit fund page.........................................................................42Figure 19 Loan details page..........................................................................43Figure 20 Customer_home page...................................................................44Figure 21 Withdraw_csahier home page.......................................................45Figure 22 Deposit cashier home page...........................................................46Figure 23 Clerk home page...........................................................................47Figure 24 Admin_home page........................................................................481.0. Introduction

1.1. PurposeThis Software Design Document provides the design details of online banking system with

the help of computer software. The aim of this project is to develop a secured online banking

system with the following objectives:

• Create a banking system that is easily accessible by customers from the comfort of their

homes,

offices etc.

• Reduce the flow of human traffic and long queues at banks Reduce the time wasted in

going to banks tostay on queues.

It fastens the traditional work and activities with the implementation of computers.

1.2. ScopeThis document contains a complete description of the design of Online banking System.

The basic architecture is a web server from a client server paradigm. The basic pages will be

in HTML and JSP.

The scope of this project is limited to the activities of the operations unit ofthe banking system which include opening of Account, Deposit of funds, Withdrawal of funds and transfer as well as maintaining security .

Online banking system will replace old paper work system, to save time and reduce number of employee. It provides a relational database containing a list of account holders, fund transfer, and account details which makes the system flexible.

1.3. GlossaryTerm DefinitionAdmin Manager of bankopms Online project management systemOBS Online bankingSystemHtml Hyper text markup languageIEEE Institute of Electrical and Electronic

EngineersQA Quality assuranceSCMP Software Configuration Management PlanSDD Software Design DocumentSQAP Software Quality Assurance PlanSRS Software Requirement SpecificationWeb Site A place on the world wide webJsp Java server pagesOs Operating system

1.4. References

SOFTWARE ENGINEERING by K.K. AGGARWAL AND YOGESH SINGH, third edition, new age publication.

IEEE std 830-1998,IEEE recommended practice for software requirements specifications.

1.5. Overview of document

Section 2 is the Architectural Design that specifies the design entities that collaborate to

perform all the functions included in the system. Each of these entities has an Abstract

description concerning the services that it provides to the rest of the system. In turn, each design

entity is expanded into a set of lower-level design operations that collaborate to perform its

services.

Section 3 concerns the Data Structure Design.

Section 4 contains the Use Case Realizations. Each Use Case stated in the SRS Document

can be traced by the given design objects.

Section 5 discusses the User Interface Design, and how it can be created with maximum

user efficiency and ease of use.

2.0. Architecture design

2.1. Web System Architecture

emp_detailspostsalarydate_joinbank_id

show_empdt()update_empdt()

feedbackqueryresponsefeedbackdate

view()resp()send()

loan_detailsloan_iddateacc_noloan_amntinteresttypeduration

add_loan()delete_loan()update_loan()

transfer_detailtrans_iddatesor_accdes_accamount

show_trans()update_trans()

customer_detailsnamefath_nameagepho_nosexacc_typebranchaddressemail_idcur_amountoccupationdate_birthacc_no

show_cdetail()update_cdetail()delete_cdetail()add_cdetail()

depositdep_amnt

addAmount()

loginuser_idpassworduser_type

update()login()

bank_detailbranch_codebranch_ namelocationno_customersno_employeesmanager

show()update()

withdrawwdrw_amnt

reduceAmount()

ONLINE BANKING SYSTEM Name: Home pageType: Web pageDescription: This is the initial home page presented to the users upon connection with the Departmental Server. There are four buttons. The user is required to click his/her relevant button and provide his/her login id and password to enter if required. Customer

can see bank information , can obtain contacts of bank & employees can go to the entries page for registration, withdraw,& deposit and Admin is main actor who can handle all details but emphasizing on loan & important bank activities.

Operations: Name: login()Arguments: NoneReturns: No return valuePre-condition: Connected to sitePost-condition: On another pageExceptions: None

Flow of Events:1. User is presented with the Gram Panchayat Home Page.2. User clicks login button3. User is connected to another page if validated.

New registrationName: clerk_home PageType: Web page formDescription: When the clerk logins successful he/she will be presented with a list of available actions based on given privilege. Upon selecting suitable task a form will be displayed to be completed. Some fields will be marked as required. When the form is completedclerk can submit the form or clear the form If the form is submitted the information is saved on the Server in the corresponding Database.

Attributes: TextResources: Verified DocumentsOperations:

Name: Submit()Arguments: NonePre-condition: Connected to sitePost-condition: Form saved and Database updated.Exceptions: None

Flow of Events:1. Clerk is presented with registration forms.2. Clerk submits the form3. Sarpanch or DEO clicks submit4. Departmental server save data in a DataBase

Name: Clear()Arguments: NoneReturns: No return valuePre-condition: Connected to sitePost-condition: Form is cleared

withdrawName: withdrawType: Web pageDescription:

On the withdraw entry page the withdraw cashier is presented with a form to be completed. Once the user has completed the form the withdraw cashier can then either submit or clear the form. When the form is submitted the Departmental Server will check to ensure that the required fields are not blank. If the required fields are blank the Departmental Server will return a message stating a required field is blank. The all required fields are not blank the Departmental Server will create a new record in the Database.

Resources:amountOperations: withdrawName: Submit()

Arguments: NoneReturns: NonePre-condition: Connected to sitePost-condition: New entry in database createdExceptions: None

Flow of Events:1. Withdraw cashier fills the form

2. Withdraw cashier clicks submit.3. Departmental server add the new entry to the Database4. Withdraw cashier is returned to their Home Page

Name: Clear()Arguments: NoneReturns: NonePre-condition: Connected to sitePost-condition: Form is clearedExceptions: None

DEPOSITName: depositType: Web pageDescription:

On the deposit entry page the deposit cashier is presented with a form to be completed. Once the user has completed the form the deposit cashier can then either submit or clear the form. When the form is submitted the Departmental Server will check to ensure that the required fields are not blank. If the required fields are blank the Departmental Server will return a message stating a required field is blank. The all required fields are not blank the Departmental Server will create a new record in the Database.

Resources: amountOperations: deposit

Name: Submit()Arguments: NoneReturns: NonePre-condition: Connected to sitePost-condition: New entry in database createdExceptions: None

Flow of Events:1. Deposit cashier fills the form2. Deposit cashier clicks submit.3. Departmental server add the new entry to the Database4. Deposit cashier is returned to their Home Page

Name: Clear()Arguments: NoneReturns: NonePre-condition: Connected to sitePost-condition: Form is clearedExceptions: None

TransactionName: transferType: Web pageDescription:

On the transfer page the customer/cashier is presented with a form to be completed. Once the customer/cashier has completed the form he/she can then either submit or clear the form. When the form is submitted the Departmental Server will check to ensure that the required fields are not blank. If the required fields are blank the Departmental Server will return a message stating a required field is blank. When all required fields are not blank the Departmental Server will create a new record in the Database.Resources: Transaction slipOperations: Name: Submit()

Arguments: NoneReturns: NonePre-condition: Connected to sitePost-condition: New entry in database createdExceptions: None

Flow of Events:1. Customer/cashier is on the transfer fund Entry form2. Customer/cashier completes the empty boxes and chooses from list boxes.3. Customer/cashier clicks submit.4. Departmental server add the new entry to the Database5. Customer/cashier is returned to the Home Page

Name: Clear()

Arguments: NoneReturns: NonePre-condition: Connected to sitePost-condition: Form is clearedExceptions: None

Flow of Events:

Feedback & QueryName: Send Feedback & query Type: Web pageDescription:customer can access this webpage after going through any login procedure. A customer is required to write a feedback/query in text area and submit it.

A customer can also view his query response details by view response available as hyperlinks.Customer is provided a form to enter query id to get response.The selected category is searched by database and the information is displayed in suitable manner.

Operations:Name: Submit()Arguments: NoneReturns: TextPre-condition: Connected to sitePost-condition: Feedback/query is submittedExceptions: None

Flow of Events:1. The customer is requested to type feedback/query2. The customer clicks submit.3. The customer can also click the view response hyperlink to view query response.4. The Departmental server queries the Gram Panchayat Database for the information5. If the information is present, the Departmental server will present it to the viewer.

LOAn detailsName:loan Type: Web pageDescription:customer can access this webpage after going through any login procedure. A customer is required to write a feedback/query in text area and submit it.

A customer can view loan details by loan details available as hyperlinks.Customer is provided a webpage of related loan details.The selected category and the information is displayed in suitable manner.

Operations:Name: view()Arguments: NoneReturns: Text

Pre-condition: Connected to sitePost-condition: loan details are providedExceptions: None

Flow of Events:1. The customer is requested to select loan type2. The customer selects loan type3. The customer is provided the selected loan type details

DatabaseName: Banking DatabaseType: DatabaseDescriptions: The Database will reside on the Departmental server. The Database will be

created and maintained in Oracle10g edition.

For Detailed description of Database design see SRS (Ref. 3.3)

4.0. Data structure designThe data is stored in a relational database using Oracle. The relations are described by

the database administrator. The data types used in this web project for storing various types of

information is listed below.

4.1. Data field types and sizes.Text Type Attribute Type Attribute SizeText String (vachar) Requirement Based

Number Integer Size of int

Number Float Size of floatDate dateNumber long Size of long

admin

clerk/ cashier

customer

The above depicts the type of various attributes to be used while designing this database.

5.0. Use case realizations

Figure 1 System Sequence Diagram

Enter And Update Details Database

View and update all details

View Details ,update profile

Admin/customer Login

Use Case: LoginSee also Detail Login in Software Requirement Specifications 2.2.1.

Login Checker Login Details

2. Submit Login Details3. Get Login Details

4. Verify Login

5. Error / Success Message

1. Enter User id & Password

Figure 2 Login Sequence Diagram

clerk customer Data Controller

customer Detail customer Detail

7.database updated

8.get success message

10.get details

11.show details

9.enter customer acc.no

6.enter new registration details

Figure New registration Details Sequence Diagram

3.WITHDRAW

withdraw cashier

interface bank network

database

7.check validation


8.update database

6.enter acc.no and withdrawl amount

4.DEPOSIT

Deposit cashier

interface bank network

database

7.check validation


6.enter acc.no and deposit amount

8.update database

5.E-BANKING

customer interface bank network database

3.get details

6.database updated

11.show details

5.enter transfer details

enter account number

2.submit details

4.show details

6.FEEDBACK

user interface bank network

database

1.enter feedback orquery

2.submit details

5.get error or success message

database updated

10.get details

manager interface bank network

database

1.enter account.no

2.submit details

5.get details

get feedback details

10.get details

6.submit query response

7.submit details

8.DATABASE UPDATED

7.LOANcustomer interface bank

networkdatabase

1.apply for loan

2.submit details

5.show message

3.application submitted

8.EMPLOYEE-DETAILSmanager interface bank

networkdatabase

1.enter employee_id

2.submit details

4.show details

3.get employee details

9.GENEREL INFORMATION

clerk interface bank network

database

1.enter acc.no

2.submit details

4.show details

3.get customer details

The following user interfaces will be provided by the system.

HOME PAGE:

LOGIN PAGE:

This will be the first form,which will be displayed.it will allow users to access the different forms based on his/her role.

Various forms available on this form will be USERNAME:alphanumeric of max 20 characaters are allowed.

Special chracaters,blank spaces are not allowed.

PASSWORD: alphanumeric of max 20 characaters are allowed.blank spaces are not allowed.

USERTYPE:will be customer,bank employee.

a) CHANGE PASSWORD:this will help the users to change the password Various field in this form will be

OLDPASSWORD: alphanumeric of max 20 characaters are allowed.blank spaces are not allowed.

NEWPASSWORD: alphanumeric of max 20 characaters are allowed.blank spaces are not allowed.

CONFIRM PASSWORD: alphanumeric of max 20 characaters are allowed.blank spaces are not allowed. The content of this field must match with the content of new password field

a) TRANSFER FUNDS:this will help the users to change the password

Various field in this form will be Trans_id: numeric of max 20 characters are allowed.

blank spaces are not allowed. Source_id: alphanumeric of max 20 characters are allowed.

blank spaces are not allowed. Des_id: alphanumeric of max 20 characters are allowed.

blank spaces are not allowed Amount: numeric.

blank spaces are not allowed

b) LOAN:this will help the users to apply for loan

Various field in this form will be LOAN_id: numeric of max 10 characters are allowed.

blank spaces are not allowed. TYPE: should be in (home, education, car)

blank spaces are not allowed. Des_id: alphanumeric of max 20 characters are allowed.

blank spaces are not allowed Amount: numeric. Account_no: blank spaces are not allowed

VIEW AND UPDATE DETAILS: this will give customer details and allows to update their information

Various field in this form will be ACCOUNT_NO: not editable.

NAME: alphabetic of max 20 characaters are allowed.blank spaces are not allowed

Age: numeric. Email_id: optional Loan_amount:not editable Current amount:not editable Address:alphanumeric of max 30 characters allowed.

FEEDBACK AND QUERY: this will allow the customers to send feedback and query.

FIGURE: NEW REGISTRATION DETAILS:

CLERK_HOME PAGE:

Deposit cashier_home page:

CUSTOMER_HOME PAGE: