SRS ONLINE BANKING
Content
MEGHNAD SAHA INSTITUTE OF TECHNOLOGY
SOFTWARE REQUIREMENTS SPECIFICATION
TEAM NAME:
ECLECTIC
STATE NAME:
KOLKATA (W.B.)
PROJECT NAME:
INTERNET BANKING SYSTEM
TEAM MEMBERS:
ANWESHA DUTTA GUPTA
DEBIKA NAG
MAITRAYEE GHOSH
RITUPARNA CHOWDHURY
PROJECT GUIDE: MOM BANERJEE
Index & Tables
1) Introduction:……………………………………………………03
1.1) Purpose:……………………………………………………….. 03
1.2) Scope……………………………………………………………… 03
1.3) Abbreviations…………………………………………………. 04
1.4) Reference………………………………………………………. 04
1.5) Technologies:………………………………………………….. 04
2) Overall Description: ………………………………………05
2.1) Product Perspective: …………………………………… 05
2.2) Software Interface: ……………………………………… 05
2.3) Hardware interface: ……………………………………. 06
2.4) Communication Interface: …………………………… 06
2.5) User Characteristics: …………………………………… 06
2.6) Constraints: ………………………………………………… 06
2.7) ER Diagram: ……………………………………………….. 07
2.8) EER Diagram: …………………………………………........ 10
2.9) Data Flow Diagram: ……………………………………. .. 11
2.10) Use-Case Model Survey: …………………………… .. 13
2.11) Database Design:………………………………………..... 16
3)Specific Requirements:……………………………………18
4)Project conclusion and drawbacks:.............................19
1) Introduction:
1.1)Purpose:
Looking for an online comprehensive solution to manage Internet banking. This
will be accessible to all customers who have a valid User Id and Password. This
system provides the following facilities:
Balance Enquiry
Funds Transfer to another account in the same bank
Request for cheque book/change of address/stop payment of cheques
Viewing Monthly and annual statements.
1.2) Scope:
•
Customer must have a valid User Id and password to login to the system
•
If a wrong password is given thrice in succession, that account will be locked and
the customer will not be able to use it. When an invalid password is entered a
warning is given to the user that his account is going to get locked.
•
After the valid user logs in he is shown the list of accounts he has with the bank.
•
On selecting the desired account he is taken to a page which shows the present
balance in that particular account number
•
User can request details of the last ‘n’ number of transactions he has performed.
•
User can make a funds transfer to another account in the same bank. User is
provided with a transaction password which is different from the login password.
•
User can transfer funds from his account to any other account with this bank. If
the transaction is successful a notification should appear to the customer, in case
it is unsuccessful, a proper message should be given to the customer as to why it
failed.
•
User can request for cheque book/change of address/stop payment of cheques.
•
User can view his monthly as well as annual statements.
3
1.3) Abbreviations:
•
Personal details: Details of customer such as username, company, phone number,
address,website, e-mail address etc.
•
Contact details: Details of contact persons associated with the company (customer).
•
HTML: Hypertext Markup Language is a markup language used to design static webpages.
•
EJB: Enterprise Java Beans.
•
J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java Platform—for
developing and running distributed multitier architecture Java applications,based largely on
modular software components running on an application server.
•
DB2: DB2 Database is the database management system that delivers a flexible and costeffective database platform to build robust on demand business applications.
•
WAS: Web sphere application server is an application server that runs business applications and
supports the J2EE and web services standards.
•
WSAD: Web sphere studio application developer is a toolkit which is designed for the creation of
more complex projects, providing fully dynamic web application utilizing EJB’s . This consist of
EJB tools, CMP, data mapping tools & a universal test client that is designed to aid testing of EJB’s.
•
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 SRS Format
Problem Definition (Provided by IBM)
CT Arrington. Enterprise Java with UML. OMG Press.
1.5)Technologies:
•
•
•
•
•
J2EE: Application Architecture
DB2: Database
WSAD: Development Tool
WAS: Web Server
Rational: Design Tool
4
2)Overall Description:
2.1)Product Perspective
THE THREE-TIER ARCHITECTURE
First tier : Web clients
Client browsers
Third tier (DBMS) : database
clusters
Internet
dB2 database
SQL database
Database cluster
Second tier : Server side application
other database
Web browsers
Application server
2.2)Software Interface:
Client on Internet: Web Browser, Operating System (any)
Client on Intranet: Client Software, Web Browser, Operating System (any)
Web Server: WAS, Operating System (any)
Data Base Server: DB2, Operating System (any)
Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML),DB2, OS (Windows), Web Server.
5
2.3)Hardware Interface:
Client Side
Processor
RAM
Disk Space
Pentium II at 500
MHz
64 MB
1 GB
Web sphere
application
server
V5.0
Pentium III at 1
GHz
512 MB
2 GB
DB2 V8.1
Pentium III at 1
GHz
512 MB
1GB (Excluding
data size)
Internet
Explorer 6.0
Server Side
2.4)Communication Interface:
Client on Internet will be using HTTP/HTTPS protocol.
Client on Intranet will be using TCP/IP protocol.
2.5)User Characteristics:
Every user should be comfortable of working with computer and net
browsing. He must have basic knowledge of English too.
2.6)Constraints:
GUI is only in English.
Login and password is used for identification of customer and there is no facility for guest.
This system is working for single server.
There is no maintainability of back up so availability will get effected.
Limited to HTTP/HTTPS.
6
2.7)ENTITY RELATIONSHIP DIAGRAM(ER)
ENTITIES & THEIR ATTRIBUTES
ADMINISTRATOR
user-id
User category
User name
DOB
country
ADMINISTRATOR
City
address
phno
State
Pin code
Bank brunch
Amount
emailid
Debitcard id
USER
user-id
User category
User name
DOB
country
USER
City
address
phno
State
Bank brunch
Amount
Pin code
emailid
Debitcard id
7
LOAN
amount
loan-id
category
LOAN
Interest amount
Interest rate
TRANSACTION
transaction-id
Date of
transaction
TRANSACTION
user-id
Account no.
amount
8
RELATIONSHIP DIAGRAM
Administrator
1
1
M
Sanction
1
Supervise
1
Maintain record
Borrow
M
Transaction
Loan
M
M
Perform
1
1
User
93
2.8)EXTENDED ENTITY RELATIONSHIP DIAGRAM(EER)
USER
Is A
Administrator
Normal user
Loan
Supervise
Is A
Customer
sanction
Is A
Home
Car
Academician
Study
Industrialist
Enterpreneur
Borrow
Perform
Transaction
Supervise
10
2.9)DATA FLOW DIAGRAM(DFD)
CONTEXT LEVEL (LEVEL 0)
login
login
Provide user account
Balance enquiry
Admin
Fund transfer
Provide chequebook
Change of address
Stop payment of cheque
View
Normal
User
Balance enquiry
Fund transfer
Internet
Banking
System
Request for cheque book
Request for uptate
Stop cheque payment
View
0
Request for loan
Loan sanction
DETAILED DFD
Add 0.1.1
User
account
0.1
Update
0.1.3
User database
Re
q
ue
st
Admin
Delete
0.1.2
View 0.1.4
Normal user
11
Add 0.2.1
Loan
sanction
0.2
Loan database
View 0.2.3
Re
qu
es
t
Admin
Delete
0.2.2
Normal user
Add 0.3.1
User database
Admin
Transaction
processing
0.3
View 0.3.2
Normal user
Delete
0.3.3
Temporary deleted
database
12
2.10)USE CASE DIAGRAM
ADMINISTRATOR
Login
Provide username &
passward
Balance enquiry
Fund transfer
Update user account
Stop payment of
cheque
View statement
View transaction
13
NORMAL USER
Login
Balance enquiry
Fund transfer
Request for address
Request for cheque
book
View statement
View transaction
14
-: USE CASE ANALYSIS :ADMINISTRATOR :1)LOGIN: The administrator can log in to the system by giving correct user
name and password.
2)PROVIDE UNAME & PASSWD:The administrator can provide user name
and password to the normal users.
3) BALANCE ENQUIRY: The administrator can enquire about users' balance.
4) FUND TRANSFER: The administrator can transfer fund from one account
to another in the same bank.
5) ADDRESS CHANGE: The administrator can update stored information of
normal users.
6) STOP PAYMENT OF CHEQUES:The administrator can stop payment of
cheques.
7) VIEW STATEMENTS:The administrator can view the monthly and annual
statements.
8) VIEW TRANSACTIONS: The administrator can view the last transactions.
NORMAL USER
1)LOGSIN: The normal users can log in to the system by giving correct user
name and password provided by the administrator.
2)BALANCE ENQUIRY: The normal users can enquire about his balance.
3) FUND TRANSFER: The normal user can transfer fund from one account to
another account in same bank.
4) REQUEST FOR ADDRESS CHANGE: The normal user can request for
updating his information in case of any change.
15
5) STOP PAYMENT OF CHEQUES:The normal users can stop payment of
cheques.
6) VIEW STATEMENTS:The normal users can view the monthly and annual
statements.
7)VIEW TRANSACTIONS: The normal users can view the last transactions.
2.11)DATABASE DESIGN
ADMINLOGIN
ATTRIBUTES
DATATYPE
CONSTRAINTS
USERID
VARCHAR2(20)
NOT NULL,PRIMARY KEY
PASSWORD
VARCHAR2(40)
NOT NULL
CITYID
VARCHAR2(20)
NOT NULL
MEMBERLOGIN
ATTRIBUTES
DATATYPE
CONSTRAINTS
USERID
VARCHAR2(20)
NOT NULL,PRIMARY KEY
PASSWORD
VARCHAR2(40)
NOT NULL
16
USER
ATTRIBUTES
USERID
USERCATEGORY
USERNAME
ADDRESS
CITY
STATE
COUNTRY
PIN
PHNO
EMAILID
DOB
BANKBRUNCH
AMOUNT
DEBITCARDID
DATATYPE
VARCHAR2(20)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
NUMBER(10)
NUMBER(20)
VARCHAR2(40)
DATE
VARCHAR2(40)
NUMBER(20,2)
VARCHAR2(20)
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
DATATYPE
VARCHAR2(20)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
NUMBER(10)
NUMBER(20)
VARCHAR2(40)
DATE
VARCHAR2(40)
NUMBER(20,2)
VARCHAR2(20)
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
MAY BE NULL
NOT NULL
NOT NULL
NOT NULL
TEMPORARYDELETED
ATTRIBUTES
USERID
USERCATEGORY
PASSWORD
ADDRESS
CITY
STATE
COUNTRY
PIN
PHNO
EMAILID
DOB
BANKBRUNCH
AMOUNT
DEBITCARDID
17
LOAN
ATTRIBUTES
LOANID
AMOUNT
CATEGORY
INTAMOUNT
INTRATE
DATATYPE
VARCHAR2(20)
NUMBER(20)
VARCHAR2(40)
NUMBER(10,2)
NUMBER(10,2)
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
DATATYPE
VARCHAR2(20)
DATE
VARCHAR2(20)
VARCHAR2(20)
NUMBER(10,2)
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
MAY BE NULL
DATATYPE
VARCHAR2(20)
VARCHAR2(40)
VARCHAR2(40)
NUMBER(30,2)
VARCHAR2(40)
DATE
DATE
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
TRANSACTION
ATTRIBUTES
TRANSID
DOT
USERID
A/CNO
AMOUNT
LOANHOLDER
ATTRIBUTES
USERID
A/CNO
LCATEGORY
AMOUNT
ISSUINGBRANCH
ISSUEDATE
DUEDATE
3)SPECIFIC REQUIREMENTS
JSP,HTML : Front End
JSP,AJAX
: Server Side Scripting
XHTML
: Client Side(JAVA Script)
DB2
: Back End
Servlet
: Program Method
18
4)CONCLUSION & DRAWBACKS:
Our project can perform balance enquiry, fund transfer, view annual statements etc.
but it has certain drawbacks:
i)Searching is done by city-wise only, not country-wise or state-wise.
ii)There is no employee, all the official work is done by administrator.
19
SOFTWARE REQUIREMENTS SPECIFICATION
TEAM NAME:
ECLECTIC
STATE NAME:
KOLKATA (W.B.)
PROJECT NAME:
INTERNET BANKING SYSTEM
TEAM MEMBERS:
ANWESHA DUTTA GUPTA
DEBIKA NAG
MAITRAYEE GHOSH
RITUPARNA CHOWDHURY
PROJECT GUIDE: MOM BANERJEE
Index & Tables
1) Introduction:……………………………………………………03
1.1) Purpose:……………………………………………………….. 03
1.2) Scope……………………………………………………………… 03
1.3) Abbreviations…………………………………………………. 04
1.4) Reference………………………………………………………. 04
1.5) Technologies:………………………………………………….. 04
2) Overall Description: ………………………………………05
2.1) Product Perspective: …………………………………… 05
2.2) Software Interface: ……………………………………… 05
2.3) Hardware interface: ……………………………………. 06
2.4) Communication Interface: …………………………… 06
2.5) User Characteristics: …………………………………… 06
2.6) Constraints: ………………………………………………… 06
2.7) ER Diagram: ……………………………………………….. 07
2.8) EER Diagram: …………………………………………........ 10
2.9) Data Flow Diagram: ……………………………………. .. 11
2.10) Use-Case Model Survey: …………………………… .. 13
2.11) Database Design:………………………………………..... 16
3)Specific Requirements:……………………………………18
4)Project conclusion and drawbacks:.............................19
1) Introduction:
1.1)Purpose:
Looking for an online comprehensive solution to manage Internet banking. This
will be accessible to all customers who have a valid User Id and Password. This
system provides the following facilities:
Balance Enquiry
Funds Transfer to another account in the same bank
Request for cheque book/change of address/stop payment of cheques
Viewing Monthly and annual statements.
1.2) Scope:
•
Customer must have a valid User Id and password to login to the system
•
If a wrong password is given thrice in succession, that account will be locked and
the customer will not be able to use it. When an invalid password is entered a
warning is given to the user that his account is going to get locked.
•
After the valid user logs in he is shown the list of accounts he has with the bank.
•
On selecting the desired account he is taken to a page which shows the present
balance in that particular account number
•
User can request details of the last ‘n’ number of transactions he has performed.
•
User can make a funds transfer to another account in the same bank. User is
provided with a transaction password which is different from the login password.
•
User can transfer funds from his account to any other account with this bank. If
the transaction is successful a notification should appear to the customer, in case
it is unsuccessful, a proper message should be given to the customer as to why it
failed.
•
User can request for cheque book/change of address/stop payment of cheques.
•
User can view his monthly as well as annual statements.
3
1.3) Abbreviations:
•
Personal details: Details of customer such as username, company, phone number,
address,website, e-mail address etc.
•
Contact details: Details of contact persons associated with the company (customer).
•
HTML: Hypertext Markup Language is a markup language used to design static webpages.
•
EJB: Enterprise Java Beans.
•
J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java Platform—for
developing and running distributed multitier architecture Java applications,based largely on
modular software components running on an application server.
•
DB2: DB2 Database is the database management system that delivers a flexible and costeffective database platform to build robust on demand business applications.
•
WAS: Web sphere application server is an application server that runs business applications and
supports the J2EE and web services standards.
•
WSAD: Web sphere studio application developer is a toolkit which is designed for the creation of
more complex projects, providing fully dynamic web application utilizing EJB’s . This consist of
EJB tools, CMP, data mapping tools & a universal test client that is designed to aid testing of EJB’s.
•
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 SRS Format
Problem Definition (Provided by IBM)
CT Arrington. Enterprise Java with UML. OMG Press.
1.5)Technologies:
•
•
•
•
•
J2EE: Application Architecture
DB2: Database
WSAD: Development Tool
WAS: Web Server
Rational: Design Tool
4
2)Overall Description:
2.1)Product Perspective
THE THREE-TIER ARCHITECTURE
First tier : Web clients
Client browsers
Third tier (DBMS) : database
clusters
Internet
dB2 database
SQL database
Database cluster
Second tier : Server side application
other database
Web browsers
Application server
2.2)Software Interface:
Client on Internet: Web Browser, Operating System (any)
Client on Intranet: Client Software, Web Browser, Operating System (any)
Web Server: WAS, Operating System (any)
Data Base Server: DB2, Operating System (any)
Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML),DB2, OS (Windows), Web Server.
5
2.3)Hardware Interface:
Client Side
Processor
RAM
Disk Space
Pentium II at 500
MHz
64 MB
1 GB
Web sphere
application
server
V5.0
Pentium III at 1
GHz
512 MB
2 GB
DB2 V8.1
Pentium III at 1
GHz
512 MB
1GB (Excluding
data size)
Internet
Explorer 6.0
Server Side
2.4)Communication Interface:
Client on Internet will be using HTTP/HTTPS protocol.
Client on Intranet will be using TCP/IP protocol.
2.5)User Characteristics:
Every user should be comfortable of working with computer and net
browsing. He must have basic knowledge of English too.
2.6)Constraints:
GUI is only in English.
Login and password is used for identification of customer and there is no facility for guest.
This system is working for single server.
There is no maintainability of back up so availability will get effected.
Limited to HTTP/HTTPS.
6
2.7)ENTITY RELATIONSHIP DIAGRAM(ER)
ENTITIES & THEIR ATTRIBUTES
ADMINISTRATOR
user-id
User category
User name
DOB
country
ADMINISTRATOR
City
address
phno
State
Pin code
Bank brunch
Amount
emailid
Debitcard id
USER
user-id
User category
User name
DOB
country
USER
City
address
phno
State
Bank brunch
Amount
Pin code
emailid
Debitcard id
7
LOAN
amount
loan-id
category
LOAN
Interest amount
Interest rate
TRANSACTION
transaction-id
Date of
transaction
TRANSACTION
user-id
Account no.
amount
8
RELATIONSHIP DIAGRAM
Administrator
1
1
M
Sanction
1
Supervise
1
Maintain record
Borrow
M
Transaction
Loan
M
M
Perform
1
1
User
93
2.8)EXTENDED ENTITY RELATIONSHIP DIAGRAM(EER)
USER
Is A
Administrator
Normal user
Loan
Supervise
Is A
Customer
sanction
Is A
Home
Car
Academician
Study
Industrialist
Enterpreneur
Borrow
Perform
Transaction
Supervise
10
2.9)DATA FLOW DIAGRAM(DFD)
CONTEXT LEVEL (LEVEL 0)
login
login
Provide user account
Balance enquiry
Admin
Fund transfer
Provide chequebook
Change of address
Stop payment of cheque
View
Normal
User
Balance enquiry
Fund transfer
Internet
Banking
System
Request for cheque book
Request for uptate
Stop cheque payment
View
0
Request for loan
Loan sanction
DETAILED DFD
Add 0.1.1
User
account
0.1
Update
0.1.3
User database
Re
q
ue
st
Admin
Delete
0.1.2
View 0.1.4
Normal user
11
Add 0.2.1
Loan
sanction
0.2
Loan database
View 0.2.3
Re
qu
es
t
Admin
Delete
0.2.2
Normal user
Add 0.3.1
User database
Admin
Transaction
processing
0.3
View 0.3.2
Normal user
Delete
0.3.3
Temporary deleted
database
12
2.10)USE CASE DIAGRAM
ADMINISTRATOR
Login
Provide username &
passward
Balance enquiry
Fund transfer
Update user account
Stop payment of
cheque
View statement
View transaction
13
NORMAL USER
Login
Balance enquiry
Fund transfer
Request for address
Request for cheque
book
View statement
View transaction
14
-: USE CASE ANALYSIS :ADMINISTRATOR :1)LOGIN: The administrator can log in to the system by giving correct user
name and password.
2)PROVIDE UNAME & PASSWD:The administrator can provide user name
and password to the normal users.
3) BALANCE ENQUIRY: The administrator can enquire about users' balance.
4) FUND TRANSFER: The administrator can transfer fund from one account
to another in the same bank.
5) ADDRESS CHANGE: The administrator can update stored information of
normal users.
6) STOP PAYMENT OF CHEQUES:The administrator can stop payment of
cheques.
7) VIEW STATEMENTS:The administrator can view the monthly and annual
statements.
8) VIEW TRANSACTIONS: The administrator can view the last transactions.
NORMAL USER
1)LOGSIN: The normal users can log in to the system by giving correct user
name and password provided by the administrator.
2)BALANCE ENQUIRY: The normal users can enquire about his balance.
3) FUND TRANSFER: The normal user can transfer fund from one account to
another account in same bank.
4) REQUEST FOR ADDRESS CHANGE: The normal user can request for
updating his information in case of any change.
15
5) STOP PAYMENT OF CHEQUES:The normal users can stop payment of
cheques.
6) VIEW STATEMENTS:The normal users can view the monthly and annual
statements.
7)VIEW TRANSACTIONS: The normal users can view the last transactions.
2.11)DATABASE DESIGN
ADMINLOGIN
ATTRIBUTES
DATATYPE
CONSTRAINTS
USERID
VARCHAR2(20)
NOT NULL,PRIMARY KEY
PASSWORD
VARCHAR2(40)
NOT NULL
CITYID
VARCHAR2(20)
NOT NULL
MEMBERLOGIN
ATTRIBUTES
DATATYPE
CONSTRAINTS
USERID
VARCHAR2(20)
NOT NULL,PRIMARY KEY
PASSWORD
VARCHAR2(40)
NOT NULL
16
USER
ATTRIBUTES
USERID
USERCATEGORY
USERNAME
ADDRESS
CITY
STATE
COUNTRY
PIN
PHNO
EMAILID
DOB
BANKBRUNCH
AMOUNT
DEBITCARDID
DATATYPE
VARCHAR2(20)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
NUMBER(10)
NUMBER(20)
VARCHAR2(40)
DATE
VARCHAR2(40)
NUMBER(20,2)
VARCHAR2(20)
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
DATATYPE
VARCHAR2(20)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
VARCHAR2(40)
NUMBER(10)
NUMBER(20)
VARCHAR2(40)
DATE
VARCHAR2(40)
NUMBER(20,2)
VARCHAR2(20)
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
MAY BE NULL
NOT NULL
NOT NULL
NOT NULL
TEMPORARYDELETED
ATTRIBUTES
USERID
USERCATEGORY
PASSWORD
ADDRESS
CITY
STATE
COUNTRY
PIN
PHNO
EMAILID
DOB
BANKBRUNCH
AMOUNT
DEBITCARDID
17
LOAN
ATTRIBUTES
LOANID
AMOUNT
CATEGORY
INTAMOUNT
INTRATE
DATATYPE
VARCHAR2(20)
NUMBER(20)
VARCHAR2(40)
NUMBER(10,2)
NUMBER(10,2)
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
DATATYPE
VARCHAR2(20)
DATE
VARCHAR2(20)
VARCHAR2(20)
NUMBER(10,2)
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
MAY BE NULL
DATATYPE
VARCHAR2(20)
VARCHAR2(40)
VARCHAR2(40)
NUMBER(30,2)
VARCHAR2(40)
DATE
DATE
CONSTRAINTS
NOT NULL,PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
TRANSACTION
ATTRIBUTES
TRANSID
DOT
USERID
A/CNO
AMOUNT
LOANHOLDER
ATTRIBUTES
USERID
A/CNO
LCATEGORY
AMOUNT
ISSUINGBRANCH
ISSUEDATE
DUEDATE
3)SPECIFIC REQUIREMENTS
JSP,HTML : Front End
JSP,AJAX
: Server Side Scripting
XHTML
: Client Side(JAVA Script)
DB2
: Back End
Servlet
: Program Method
18
4)CONCLUSION & DRAWBACKS:
Our project can perform balance enquiry, fund transfer, view annual statements etc.
but it has certain drawbacks:
i)Searching is done by city-wise only, not country-wise or state-wise.
ii)There is no employee, all the official work is done by administrator.
19
