SRS FOR SOFTWARE DEVELOPMENT AND PROJECT

MANAGEMENT

1. Introduction: -
This document gives detailed functional and non-functional requirements for the bank
management system. This product will support online banking transaction. The purpose of this
document is that the requirements mentioned in it should be utilized by software developer to
implement the system.

1.1 Objective :-
An online banking system will be applicable everywhere, where banking exists. It will be
more efficient and easier way to have a record on systems through which everyone can
easily access it according to his rights as compared to the traditional banking system. Every
bank will prefer the online banking system instead of the traditional banking system as it
contains many useful features and fastest methods for the transactions.

1.2 Identification of Need :-

Online banking system provides is specifically developed for internet banking for Balance
Enquiry, Funds Transfer to another account in the same bank, Request for cheque
book/change of address/stop payment of cheques, Mini statements (Viewing Monthly and
annual statements). The Traditional way of maintaining details of a user in a bank was to
enter the details and record them. Every time the user needs to perform some transactions
he has to go to bank and perform the necessary actions, which may not be so feasible all
the time. It may be a hardhitting task for the users and the bankers too. The project gives
real life understanding of Internet banking and activities performed by various roles in the
supply chain. Here, we provide an automation for banking system through Internet. Internet
banking system project captures activities performed by different roles in real life banking
which provides enhanced techniques for maintaining the required in- formation up-to-date,
which results in efficiency. The project gives real life understanding of Internet banking
and activities performed by various roles in the supply chain.
This Product will automate of banking transaction process. This Project investigates the
entry threshold for providing a new transaction service channel via the real options
approach, where the entry there should is established by using an Internet banking system
designed for the use of normal users(individuals), Industrialists, Entrepreneurs, Educational

1
 Institutions(Financial sections), Organizations and Academicians under transaction rate
uncertainty.

1.3 Preliminary Investigation :-

The system provides easy solution to banks. Overview: The SRS will include two sections,
namely: Overall Description: This section will describe major components of the system,
interconnections, and external interfaces.
Specific Requirements:
This section will describe the functions of actors, their roles in the system and the
constraints faced by system.
Product Perspective:
The client will have client interface in which he can interact with the banking sys- tem. It
is a web-based interface which will be the web page of the banking application. Starting a
page is displayed asking the type of customer he is whether ordinary or a corporate
customer. Then the page is redirected to login page where the user can enter the login
details. If the login particulars are valid then the user is taken to a home page where he has
the entire transaction list that he can perform with the bank. All the above activities come
under the client interface. The administrator will have an administrative in- terface which
is a GUI so that he can view the entire system. He will also have a login page where he can
enter the login particulars so that he can perform all his actions. This administrative
interface provides different environment such that he can maintain data- base & provide
backups for the information in the database. He can register the users by providing them
with username, password & by creating account in the database. He can view the cheque
book request & perform action to issue the cheque books to the clients.
1.4 Problem Domain :-
The Bank Management System is an application for maintaining a person’s account in a
bank. The system provides the access to the costumer to create an account, deposit or
withdrawal the cash from his account , also to convert currency. The following
documentation provides the specification of the system.
We are mainly concerned with developing a banking system where a customer can submit
his/her deposit amount to bank id he/she has an account or can create a new account in this
bank. Customer can also view the status and change currency od his/her bank account, can

2
 view account balance . One can easily maintain the above things id he/she has as account
by login through his unique account number.
1.5 Solution Domain :-
The application will be extremely beneficial for the customer intending to use and operate
their bank account and will get various benefits in the field of management of accounts on
a clean and user-friendly platform.
“Bank Management System” , is a simple application which is especially generated and
designed for the bank in order to enter the applicant information about his or her bank
account and can perform other function like currency change. It is user name and ID
protected as well.

Major objectives of the proposed system :-

1. It creates a user-friendly environment, where a normal user can access through all the
benefits of the system.
2. It provides security from unauthorised access , only admin or authorized users are
access granted to the system.
3. It increases efficiency and saves the time.
4. No any danger and obstacles from external entities.
5. Easy access of saved data inside the system.
6. Complex banking operations and transactions operations are efficiently handled by the
application.
7. It has case of use along with complete reference.
8. It is highly secured and less time consuming ; hence time wastage can be avoided.
9. Up to date records of the customers are maintained by the authority.

Benefits of proposed system :-

1. User friendly GUI.

2. Fully efficient.
3. Easy to handle customer account.
4. Improved services.
5. Provides better account management facilities.

3
1.6 Platform Specification :-
1.6.1 Hardware :-
For developing application software followings are the hardware requirements :-
Processor :- INTEL CORE i3, i5, i7

For running application following are the hardware requirements:-

Device :- window 7/8/1
Storage :- Minimum 4 Gb RAM
At least have 5Gb ROM.
1.6.2 Software :-

For developing application following are the software requirements :-

Operating system :- windows 7/8/10
Languages :- JAVA , HTML , SQL , CSS .
Software :- MYSQL Database , Apache Tomcat server , NetBeans IDE.
Technologies Used :- MYSQL Database , JAVA SERVLET.

2. System Requirement Analysis :-

2.1 Information Gathering:-

2.1.1 Functional Requirements :-

This section provides the functional overview of the product. The project will require the
HTML CSS as a front end and at the back-end JAVA with the database MYSQL will be
running. Various functional modules that can be implemented by the product will be :-

1. Login :-
Customer logins by entering customer ID & a login pin
2. Validation :-
After validating the credentials, the validity of PIN must be ensured . The counter for
number of logins must be maintained Get balance information: This system must be
networked to the bank’s computer. The updated database of every customer is
maintained with bank. Hence the balance information of every account is available in
the database and can be displayed to the customer.

4
 3. Get balance information :-
The customer can bale to check the amount of money currently present in his/her
account.
4. Withdrawal of money :-
A customer is allowed to enter the amount which he/she wishes to withdraw. If the
entered amount is less than the available balance and if after withdrawing the minimum
required balance is maintained, then allow the transaction so that the user can use it
properly.
5. Transfer and Deposit Money :-
The customer can deposit or transfer the desired amount of money.

2.1.2 Non-Functional Requirements :-

Those requirements which are not the functionalities of a system but are the characteristics of
a system are called the non-functionalities. Every software system has some non-
functionalities. Just fulfilling the requirements of the user is not a good task, keeping the system
accurate, easy to maintain, reliable and secure is also a basic part of software engineering.
Online Banking System must have the following non-functional requirements so that I could
be said as a complete system

GUI (Graphical User Interface) :-

This is interface must be highly intuitive or interactive because there will not be an assistance
for the user who is operating the System. At most of the places help desk should be provided
for user’s convenience. The screens appearing should be designed in such a manner that it can
draw User attraction towards the new plans for the customers. Also, the pin and password
confidentiality should be maintained, this can be done by using asterisks at the password panel.
Proper security messages should be displayed at most of the places.

Performance :-

The system should be compatible enough to hold the general traffic . It should not get hang or
show some other problems arising out due to large no of concurrent users . The system should
be fast enough to meet the customer The high and low temperature should not affect the
performance of the device. An uninterrupted transaction must be performed.

5
Hardware Limitations :-

It should be designed in such a way that cheap hardware must be installed to access and use it
effectively. It should be platform independent. There should be no hardware limitations. In
should be designed to work with the low specification hardware so that it could easily work
with the high specification hardware.

Maintainable :-

Each of the modules should be designed in such a way that a new module can easily be
integrated with it.

Security Requirements :-

1. Account ID and Password Protection

2. Auto Timeout Screen Banking
3. Sign off Button
4. Failed log-on Attempts
5. Encryption.

2.2 System Feasibility

Feasibility study means the analysis of problem to determine if it can be solved effectively. In
other words, it is the study of the possibilities of the proposed system it studies the work ability,
impact on the organization ability to meet user’s need and efficient use of resources.

Three aspects in which the system has to be feasible are:-

2.2.1 Operational Feasibility

Operational Feasibility deals with the runtime performance of the banking S/W the proposed
system must score higher than the present in the current operational study. The Banking S/W
should have end user in mind so that when the system is designed while designing S/W the
programmer should be aware of the operations i.e., performing from the user’s side like
creating an account, depositing or withdrawal or transfer of money and many other operations
etc. The s/w contains only a minimum no. of bugs so that the user can’t face any issues in the
nearer future. Maintenance and Care should be taken of the S/W to avoid non-working means
and errors.

6
2.2.2 Technical Feasibility

This aspect concentrates on the concept of using Computer Meaning, “Mechanization” of

human works. Thus, the automated solution leads to the need for a technical feasibility study.
The focus on the platform used database management & users for the banking S/W. The
proposed system doesn’t require an in-depth technical knowledge as the banking system
development is simple and easy to understand for any kind of user.

2.2.3 Economical Feasibility

The economical analysis checks for the high investment incurred on the system. It evaluates
development & implementing charges for the proposed “Banking Project”. The S/W used for
the development is easily available at minimal cost & the database applied is freely available
hence it results in low-cost implementation. The online banking system is economically
feasible as it builds on an already existing system and the cost of hardware resources needed is
relatively low, software applications needed are readily available making the project budget to
be manageable.

3 System Design

3.1 Use Case Diagram :-

Fig 3.1 Use-Case Diagram

7
3.2 Class diagram :-

Fig 3.2 Class Diagram

8
3.3 Sequence diagram :-

Fig 3.3 Sequence Diagram

9
3.4 Activity Diagram :-

Fig 3.4 Activity Diagram

10
4. Design
4.1 Data Design
The main role of data design is to illustrate what type of data are used and stored in the system.
Data designing illustrates the types of data that are stored in the system, the relationships
between them and the ways that data can be grouped or organised.

4.1.1 ER Diagram
The relation upon the system is structure through a conceptual ER-Diagram, which not only
specifics the existential entities but also the standard relations through which the system exists
and the cardinalities that are necessary for the system state to continue.

• The entity Relationship Diagram (ERD) depicts the relationship between the data objects.
The ERD is the notation that is used to conduct the date modelling activity the attributes of
each data object noted is the ERD can be described resign a data object descriptions.

• The set of primary components that are identified by the ERD are

o Data object
o Relationships
o Attributes
o Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.

Fig 4.1.1 E-R Diagram

11
5. Implementation

5.1 Implementation of modules :-

Login Module:-
Login Page is a page that allows users to type a username and password to log in. In this
project we used the user’s account no and mpin as login details so that they can login easily.
In some case, if user forgot it’s mpin they can change their mpin as we given a kind of
facility to the users to change their mpin.

Home Module:-
A home page is the main web page of a website. The term refers to the start page of any
particular website in a web browser when we start any application or a website. Usually,
the home page is located at the root of the website’s domain or subdomain. Like, in the
banking website when users will be going to start our application, they can see firstly the
home page of our website where they can perform specific banking operation like create
account, login account, amount deposit / withdraw / transfer and many more.

Open Account Module:-

The open account definition is an account which remains to be paid. Open account is also
known as an account payable by the bearer. Their terms exist in a multitude of situations:
trade credit which is not fully paid, a deferred payment schedule for an item, a past due
account, and more. An open account credit can even exist where an account is open because
there is a positive balance which has yet to be spent. In the banking website, there is an
open account page is present through which new users can create their account by providing
their respective and especially the deposit amount in the beginning to start their account.

Deposit Module:-

Fundamentally, a deposit is money held by a bank. Same on the website there is a deposit
page is there which is used to deposit money in our account. The money that you put for
savings in your bank account for any reason. It could be to safeguard your money, increase
your savings, or money received via cheques and other forms of fund transfers – all come
under the umbrella of deposits. Every time a transaction involves a fund transfer into your
bank account, it is referred to as a deposit payment.

12
Withdrawal Module:-

A withdrawal occurs when funds are removed from an account. Withdrawals can be
triggered for many types of accounts, including bank accounts and pension accounts. A
withdrawal may not be allowed unless certain conditions are met, such as the passage of
time. There is a withdrawal page exist on the website where user can withdrawal the
specific amount from their account anytime according to their convenience.

View Balance Module:-

An account balance is the amount of money present in a financial repository, such as a

savings or checking account, at any given moment. The account balance is always the net
amount after factoring in all debits and credits. An account balance that falls below zero
represents a net debt—for example, when there is an overdraft on a checking account. For
financial accounts that have recurring bills, such as an electric bill or a mortgage, an account
balance may also reflect an amount owed. Same thing is present in the banking website
where users can see their respective amount balance by entering their account number.
After that, it will be going to display the current balance.

13
5.2 Result :-
LOGIN PAGE :-

Fig 5.2.1 Login Page

14
HOME PAGE :-

Fig 5.2.2 Home Page

15
NEW ACCOUNT PAGE :-

Fig 5.2.3 New Account Page

16
DEPOSIT PAGE :-

Fig 5.2.4 Deposit Page

17
WITHDRAWAL PAGE :-

Fig 5.2.5 Withdrawal Page

18
VIEW BALANCE PAGE :-

Fig 5.2.6 View Balance Page

19
CURRENT BALANCE PAGE:-

Fig 5.2.7 Current Balance Page

20
TRANSFER PAGE :-

Fig 5.2.8.1 Transfer Page

21
Fig 5.2.8.2 Transfer Page

22
Fig 5.2.8.3 Transfer Page

23
6 Testing
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding. In fact, testing is the one step in the software
engineering process that could be viewed as destructive rather than constructive. A strategy for
software testing integrates software test case design methods into a well-planned series of steps
that result in the successful construction of software.

Testing is the set of activities that can be planned in advance and conducted systematically.
The underlying motivation of program testing is to affirm software quality with methods that
can economically and effectively apply to both strategic to both large and small-scale systems.

6.1 Testing Objectives

Software Testing for banking system has different goals and objectives. The major objectives
of Software testing are as follows:

• Finding defects which may get created by the programmer while developing the
banking software during the development phase.

• Gaining confidence in and providing information about the bank software so that the
users do not face any issues while understanding and using the software.

• To prevent defects of the banking software.

• To make sure that the end result meets the business and user requirements of the
banking software.

• To ensure that it satisfies the BRS that is Business Requirement Specification and SRS
that is System Requirement Specification for the banking system that is demanded and
requested by the organization .

• To gain the confidence of the customers by providing them a quality banking software
so that they can perform their respective operations like creating an account in the bank,
depositing / withdrawing / transferring the amount in the bank to any other customer or
user.

24
6.2 Testing Scope

Technically, Software Testing is an investigation conducted to provide stakeholders with

information about the quality of a particular product or service under test. In other words,
software testing is a process of verification and validation of a software.

Testing scope is always good for development. A software or a product is good when we do
the testing of the product or software just like our banking system.

It contains the software components hardware, software, middleware to be tested, and also
those that will not be tested of the banking software system.

It gives the details of the objectives of the banking project. Also, it details user scenarios to be
used in tests. If necessary, the scope can specify what scenarios or issues the banking project
will not cover and what types of issues it can cover easily.

A testing plan in software testing is the backbone on which the entire project is built. Without
a sufficiently extensive and well-crafted plan, Q & A’s are bound to get confused with vague,
undefined goals and deadlines. This hinders fast and accurate testing unnecessarily, slowing
down results, and delaying release cycles.

According to researchers, made by Gartner, the costs of developing the IT sector will increase
to 3.76 trillion dollars towards the end of 2019 and by 2020 it would have increased to 3.87,
this study implies that the testing of a software plays an important role in IT sector.

6.3 Testing Principles

There are seven principles in software testing:

1. Testing shows the presence of defects

2. Exhaustive testing is not possible
3. Early testing
4. Defect clustering
5. Pesticide paradox
6. Testing is context-dependent
7. Absence of errors fallacy

25
 1. Testing shows the presence of defects:

Suppose the user is testing the banking software to identify problems so that the developer can
fix them before they deploy the software to production environments. However, this process
doesn't mean that there aren't any bugs in the product. It just means that there may be bugs, but
you didn't find them because in the banking software while performing a specific operation
there can be some minor bugs present in the software which can identify through the deeply
testing of the banking software.

There could be any number of reasons that you didn't uncover every bug, including the fact
that the test cases didn't cover every scenario.

2. Exhaustive testing is not possible:

The truth is that you can't test everything, i.e., every combination of preconditions and inputs
which is incorporated and used in the banking system software. And if you try to do so you'll
waste time and money, but it won't affect the overall quality of the banking software.

What you need to do is assess risk and plan your tests around these risks while using the
banking system so you can be sure you're testing the key functions and necessary operations.
Careful planning and assessment ensure your test coverage is good so you can have confidence
in your final product before the deployment of the banking software — and you don't even
have to test every individual line of code of the software.

3. Early Testing:

When it comes to the SDLC, early testing of the software is the key to identifying any defects
in the requirements or design phase as soon as possible which is present in your software
because it will be going to be much easier and less expensive to fix bugs in the early stages of
testing of the software than at the end of the software lifecycle as then you might have to rewrite
entire areas of functionality. And that likely means missed deadlines and cost overruns.

4. Defect clustering:

In a project, a small number of modules can contain most of the defects. Pareto Principle to
software testing state that 80% of software defect comes from 20% of modules. For Example,
the modules which are used in our banking software the majority of the defects are came out

26
of modules because it is separating it into functions that each only deal with one aspect of the
overall functionality.

5. Pesticide paradox:

Repeating the same test cases, again and again, will not find new bugs. So, it is necessary to
review the test cases and add or update test cases to find new bugs. Likewise, if the banking
software got continuously run under the same tests or operations, eventually it would fail into
finding of the new defects, even though they'll probably confirm the banking software is
working properly.

6. Testing is context-dependent:

Software testing is all about the context, which means that no one strategy will fit every
scenario. The types of testing and the methods you use totally depend on the context of the
systems or the software, e.g., the testing of an iOS application is different from the testing of
an e-commerce website. Put simply, what you're testing will always affect the approach you
use. Likewise, the banking software testing is also going to be different than the software
application because both of them have their own respective approaches and techniques of
testing.

7. Absence of errors fallacy:

If the banking software is 99% bug-free but it does not follow the user’s requirement, then it is
unusable. It is not only necessary that software is 99% bug-free but it is also mandatory to fulfil
all the customer requirements.

As such, you should also test that software with the users. You can test against early prototypes
at the usability testing phase so you can get feedback from the users that you can use to ensure
the banking software is usable and they are getting less or absolute zero issues in using the
banking system. Even though the banking software might get few issues, doesn't mean it is
ready to ship / deploy; it also has to meet the customer's requirements and expectations.

27
6.4 Testing Methods Used

1. Unit Testing

The unit testing was done after the coding phase was done of the banking system. The purpose
of the unit testing was to locate errors on the module of the software, independent of the other
modules. Some changes in the coding were done during the testing of the banking software.
Finally, all the modules were individually tested from bottom up starting with smallest and
lowest modules and proceeding one at a time.

2. Black Box Testing

This method of software testing tests the functionality of the banking software system as
opposed to its internal structures or working (i.e., white-box testing). Specific knowledge of
the internal structure and programming knowledge in general is not required. It uses external
descriptions of the banking software like specifications, requirements, and designs to derive
test cases for the banking system. The test designer selects valid and invalid inputs and
determines the appropriate outputs and checks that whether the banking system is working
efficiently or not.

3. White Box Testing

This method of software testing tests internal structures or workings of the banking system, as
opposed to its functionality (i.e., black-box testing). In white box testing an internal perspective
of the system, as well as programming skills, are required and used to design test cases for the
banking software system. The tester chooses inputs to exercise paths through the code and
determine the appropriate outputs and checks that whether the banking system is working
efficiently or not.

4. Integration Testing

Once the unit was over, all the banking software system modules were integrated for the
integration testing. External and internal interfaces are implemented and work as per design of
the software, the performance of the banking module is not degraded.

5. Validation Testing

At the culmination of integration testing, the banking software is said to be completely

assembled as a single complete package; interfacing errors have been uncovered and corrected.

28
Then as a final series of software test, validation tests were carried out throughout the
deployment of the banking software.

6. Acceptance Testing

This is the final stage in the testing process of the banking system before the system is accepted
for operational use. Any requirement problem or requirement definition problem revealed from
acceptance testing are considered and made error free the system so that the users do not face
any issues and errors.

6.5 Test Cases

Sample test cases

For New Users

o Create a new user with valid and invalid data

o Create a new user without data
o Create a new user with existing branch data
o Verify cancel and reset option
o Update user with valid and invalid data
o Update user with existing data
o Verify cancel option
o Verify deletion of the user

For Existing Users

o Verify User’s login with Valid and Invalid data

o Verify User’s login without data
o Verify all users home links
o Verify the user change password with valid and invalid data
o Verify the user change password without data
o Verify the user change password with existing data
o Verify the change mpin of the user with existing data
o Verify the change mpin of the user without existing data
o Verify the user logout

29
Use case use Input Desired Actual Output Result
Output
Admin Login No entry filled Error Invalid Entry Pass
No email id error Invalid entry pass
Incorrect
password
Incorrect email error Invalid entry pass
password
Correct email error Invalid entry pass
id incorrect
password
Correct email error Invalid entry pass
id no password
No email id error Invalid entry pass
correct
password
Incorrect email error Invalid entry pass
id correct
password
Correct email No error valid pass
id correct
password

Table 6.5.1 Test Cases for Admin

30
Use case use Input Desired Actual Output Result
Output
User Login No entry filled Error Invalid Entry Pass
No account Error Invalid entry pass
number
Incorrect mpin
Incorrect Error Invalid entry pass
account
number and
mpin
Correct account Error Invalid entry pass
number and
mpin
Correct account Error Invalid entry pass
number but no
mpin
No account Error Invalid entry pass
number but
correct mpin
Incorrect Error Invalid entry pass
account
number but
correct mpin
Correct account No error valid Pass
number and
correct mpin

Table 6.5.2 Test Cases for User

31
6.6 Sample Test Data and Results
1. Creating an Account

Fig 6.6.1.1 Creating an Account

Fig 6.6.1.2 Creating an Account

32
2. Depositing Amount

Fig 6.6.2.1 Deposit Page

Fig 6.6.2.2 Deposit Page

33
 Fig 6.6.2.3 Deposit Page

3. Withdrawal Amount

Fig 6.6.3.1 Withdrawal Amount

34
 Fig 6.6.3.2 Withdrawal Amount

4. View Balance

Fig 6.6.4.1 View Balance

35
 Fig 6.6.4.2 View Balance

5. Transfer Page

Fig 6.6.5.1 Transfer Amount

36
Fig 6.6.5.2 Transfer Amount

Fig 6.6.5.3 Transfer Amount

37
7. Limitations

• Problems of security:

Security and privacy aspects are major issue in case of online transaction through the banking
system. Various sites are not properly locked at to ensure weather customer’s money is safe in
cyber world or not.

• High cost:

The infrastructural cost of providing a good and effective online banking facility is very high.
The banks not only have to automated front-end services but also back-office services, which
involve high cost.

• Lack of awareness:

Another great hindrance is lack of awareness because effective and wide media efforts in
publishing Internet banking need to be emphasized.

• Lack of computerization:

Lack of computerization and low density of telephone lines is also a bottleneck for online
banking. In India, out of 65000 bank branches, only 5000 branches are computerized.

• Wrong assumption by people:

Many people are away from net banking or online banking on the assumption that it is more
expensive than the traditional method of dealing with banking transactions. They still prefer
going to bank in offline mode to perform transactions.

8. Future Scope
o Increased Operational Efficiency, Portability and Productivity.
o Superior Customer Service.
o Improved Management and Accountability.
o Minimal Transaction Costs.
o Improved Financial Costs.
o We can go further for Online Banking.
o We can establish and start various Branches and available help centers for Account
Holder’s Queries.
o We can also deal through internet by creating web pages and a banking website for

38
 internet dealing.
o To attract Account Holder’s, we can offer various offers during festivals months.
o We can also deal in various types of Banking Transactions.
o To have more and more customer satisfaction we will emphasize more and more on
our dealings.

9. Conclusion

This project developed, incorporated all the activities involved in the browsing centre. It
provides all necessary information to the management as well as the customer with the use of
this system; the user can simply sit in front of the system and monitor all the activities without
any physical movement of the file.

Management can service the customer’s request best in time. The system provides quickly and
valuable information. These modules have been integrated for effective use of the management
for future forecasting and for the current need.

Bank Management System is a virtualization of transactions in banking system. The banking

system are used manual working but when we used online banking system it is totally
virtualization process which avoid manual process and converts it in automatic process . If user
can make a transaction in bank management system it is available in anywhere also user can
link Aadhar with account, change branch location easily. Bank management system is saving
the time with accuracy than bank manual system.

10. Bibliography and References

For Java installation

https://www.oracle.com/in/java/technologies/downloads/

For MYSQL Database installation

https://dev.mysql.com/downloads/installer/

Reference websites

o www.javatpoint.com
o www.w3schools.com
o http://www.tutorialspoint.com/java/index.html

39
Reference Books

o Thinking in java
o OCJP Certified Programmer for Java
o Learn Java in Easy Steps
o Complete reference Java

References:

o www.w3schools.com
o www.roseindia.net
o www.dbforums.com
o www.ibm.com
o http://tomcat.apache.org

40