Electronic club

7/31/2019 Electronic club

1/73

ELECTRONIC SPORTS CLUB

A Mini Project Report

Submitted in partial fulfillment of the requirements for the award of

BACHELOR OF TECHNOLOGY

IN

INFORMATION TECHNOLOGY

Submitted By:

TOOTHIKA CHAITANYA

09671A1213

Under the esteemed guidance of

Mr.Ch.Srinivasulu

ASSOC.PROFESSOR & H.O.D

DEPARTMENT OF INFORMATION TECHNOLOGY

J.B INSTITUTE OF ENGINEERING AND TECHNOLOGY

MOINABAD, HYDERABAD

2012-13


2/73

CERTIFICATE

This is to certify that the project entitled ELECTRONIC SPORTS CLUB submitted to the

Department of information Technology, J.B Institute of Engineering and Technology, in

accordance with JNTU regulations as partial fulfillment required for successful completion of

Bachelor of Technology in IT is a Bonafide work carried out by, TOOTHIKA CHAITANYA

HT.NO: 09671A1213 at JBIET, Hyderabad under the guidance of Mr.Ch.Srinivasulu

Signature of Project Guide Signature of Head of the Department


3/73

Department of Information Technology

J.B. Institute of Engineering and Technology

Moinabad, R.R.Dist

DECLARATION

I, TOOTHIKA CHAITANYA bearing Roll No 09671A1213, hereby certify that the project

report entitled ELECTRONIC SPORTS CLUB, carried out under the guidance of

Sri.Ch.Srinivasulu, Assoc.Professor submitted in partial fulfillment of the requirements for the

award of the degree ofBachelor of Technology in Information Technology. This is a record of

bonafide work carried out by me and the results embodied in this project report have not been

reproduced / copied from any source. The results embodied in this project report have not been

submitted to any other university or institute for the award of any other degree or diploma.

TOOTHIKA CHAITANYA

Roll No: 09671A1213

Dept. of Information Technology

JBIET

Date:


4/73

ACKNOWLEDGEMENTS

I take this opportunity to thank sri Ch. Srinivasulu,., Head of Department, IT , J .B Institute of

Engineering and Technology, for his stimulating suggestions and encouragement.

I am deeply indebted to our guide Mr.Ch.Srinivasulu, Assoc.Professor, Department of

Information Technology,for their constant encouragement and valuable guidance during the

period of the project work.

I would like to express our gratitude to the staff members of the IT department. I want to thank

them for all their help, interest and valuable suggestions..

ELECTRONIC SPORTS CLUB


5/73

ABSTRACT

Aim

The Ellesmere Sports and Leisure Club (the club) provides cricket, tennis, squash,bowls, and croquet facilities to its members. In addition, there is a function room which is

available to hire by anyone, and a bar / restaurant .Main forms of analysis were performed in

order to determine problems with current systems the first being interviews with members of

staff. A transcript of the interviews is included in appendix C. The Object Oriented Analysis

and Design module provided useful guidance when performing the analysis.

PROPOSED SYSTEM

Booking process

At present, facilities must be booked in person during term time. Sports centre staff use a

printed timetable to locate available timeslots for bookings. If payment is necessary, this is made

with the booking and the sports centre user receives a numbered ticket as a receipt. This ticket is

then shown when arriving to use the facilities and the booking is ticked off on the timetable sheet.

Issues

Staff currently spends a considerable amount of time administrating the booking of sportscentre facilities. Their time could be spent more productively on other tasks or staffing

could be reduced.

Users of the sports centre must book facilities in person. This can be a great inconvenience forthose who do not live in the immediate vicinity of the sports centre.

There is currently no way for users to check what bookings they have outstanding withoutcontacting sports centre staff. This can lead to more unnecessary use of staff time or users

missing bookings.

Weekly booking records are kept on sheets of paper. If the sheets are lost or damaged there isno other method for staff to check what bookings have been made. Archived booking record

sheets are also at risk of loss or damage to the only available copy.


6/73

SOFTWARE REQUIREMENTS:

Technologies : Servlets, JSP, JDBC

Databases : Oracle

Web Server : Apache Tomcat 5.5

Operating System : Windows 2000 Prof/XP.

HARDWARE REQUIREMENTS:

Processor : Intel P-IV based system

Processor Speed : 250 MHz to 833MHz

RAM : 256 MB to 2 GB


7/73


8/73

CONTENTS

1. INTRODUCTION

1.1 OVERVIEW OF THE PROJECT

2. LITERATURE OF SERVEY

2.1 SYSTEM ANALYSIS

2.1.1 EXISTING SYSTEM

2.1.2 PROPOSED SYSTEM

2.1.3 SOFTWARE REQUIREMENTS

2.2. DESIGN OF THE SYSTEM2.2.1 SYSTEM REQUIRMENT OF THE SPECIFICATION

2.2.2 DIAGRAMS

3. IMPLEMENATATION

3.1 MODULE

3.2 MODULE DESCRIPTION

3.3 SAMPLE CODE

4. SOFTWARE TESTING

4.1 TESTING OBJECTIVES

4.2 TESTING STATEGIES

4.3 TESTING CASE DESIGN

4.4 SCREEN SHOTS

5. RESULT

5.1 EXPLANATION OF THE OUTPUT RESULTS

6. CONCLUSION

7 FUTURE SCOPE OF THE WORK

8. BIBLIOGRAPHY


9/73

2. LITERATURE SURVEY

2.1 LITERATURE SURVEY:

The literature survey is a very significant step in the research process. The basic stages in a

typical research project are:

Identify the topic of interest perform a literature review, generate related questions state your unsolved problem or hypothesis find or develop a solution, and document your results

2.2 SYSTEM ANALYSIS

2.2.1 EXISTING SYSTEM:

This is manual maintenance system. Here some spread sheet is maintained for listing all the members and facilities. Bookings are also maintained in the spread sheet. Annual bills are provided by linking word processor using mail merge.

2.2.2 THE CURRENT SYSTEM:

Booking process:

At present, facilities must be booked in person during term time. Sports centre staff use a

printed timetable to locate available timeslots for bookings. If payment is necessary, this is made

with the booking and the sports centre user receives a numbered ticket as a receipt. This ticket is

then shown when arriving to use the facilities and the booking is ticked off on the timetable sheet.

Issues:

Staff currently spends a considerable amount of time administrating the booking of sportscentre facilities. Their time could be spent more productively on other tasks or staffing

could be reduced.

Users of the sports centre must book facilities in person. This can be a great inconvenience forthose who do not live in the immediate vicinity of the sports centre.


10/73

There is currently no way for users to check what bookings they have outstanding withoutcontacting sports centre staff. This can lead to more unnecessary use of staff time or users

missing bookings.

Weekly booking records are kept on sheets of paper. If the sheets are lost or damaged there isno other method for staff to check what bookings have been made. Archived booking record

sheets are also at risk of loss or damage to the only available copy.

2.2.3 SOFTWARE REQUIREMENTS SPECIFICATION

SOFTWARE REQUIREMENTS:

Technologies : Servlets, JSP, JDBC

Databases : Oracle

Web Server : Apache Tomcat 5.5

Operating System : Windows 2000 Prof/XP.


11/73

5. SYSTEM DESIGN

5.1. INTRODUCTION TO UML:

The UML is a graphical language for visualizing, specifying, constructing and

documenting the architect of a software intensive system.The UML gives us a standard way to

write a system blueprint.,covering conceptual things such as a business process and system

functions,as well as concrete things such as classes written in a specific programming

language,data bases schemas and reusable software components.

The UML combining the best of the best form

Data modeling concept(e-r diagrams) Business modeling(work flow) Object modeling Component modeling

There are nine kinds of diagrams

Use case diagrams Sequence diagrams Collaboration diagrams Class diagrams Object diagrams State chart diagrams Activity diagrams Component diagrams


12/73

CLASS DIAGRAM :

A class diagram gives an overview of a system by showing its classes and the

relationships among them.Class diagrams are staticthey display what interacts but not what

happens when they do interact .

UML class is a rectangle divided into : class name, attributes, and operations.

Our class diagrams has three kinds of relationships

Associationa relationship between instances of the two classes.There is an associationbetween two classes if instance of one class must know about the other in order to perform its

work.

Aggregation an association in which one class belongs to a collection.An aggregation has adiamond end pointing to the part containing the whole.

Generalizationan inheritance link indicating one class is a super class of the other.


13/73

CLASS DIAGRAM:

USE CASE DIAGRAMS:

Use case diagrams describe what a system does form the standpoint of an external

observer.The emphasis is on what a system does rather than how.A use case is a summary of

scenarios for a single task or a goal.An actor is who or what initiates the events involved in that

task.Actors are simply roles that people or objects play.


14/73

login

Add restaurent details

admin

Add stadium dteails

Add rooms

Add staff member details

Homepage

Delete stadium details


15/73

Staff

login page

Home page

Add ticket details

View stadium booking details

view room booking details

my profile


16/73

Board

login page

Home page

Room bookings

stadium bookings

view room booking details

view stadium booking details

my profile

change password


17/73

User

login page

Home page

ticket details

view ticket details

My profile

SEQUENCE DIAGRAMS :

A sequence diagram is an interaction diagram that details how operations are carried out

what messages are sent and when. Sequence diagrams are organized according to time. The time

progresses as you go down the page. The objects involved in the operation are listed form left to

right according to when they take part in the message sequence.


18/73

Admin:

Admin login homepage Stadium Restaurant

Details

Rooms Details Staff Mumber Logout

1: login details

2: invalidate

3: Relogin 4: validate 5: Add Details

6: Backtohomepage

7: Add restaurant details

8: back to homepage

9: Add Room details

10: back to homepage

11: Add Staff details


13: logout


19/73

Staff:

Staff login homepage StadiumBooking

Room Booking Ticket Details MyProfile Logout

1: login details

2: invalidate

3: Relogin 4: validate 5: View stadium details

6: Backtohomepage

7: View Room details

8: back to homepage

9: Add ticket details


11: changes Profile


13: logout


20/73

Board:


21/73

User:

User Login Homepage Ticket booking View Details Myprofile Logout

1: login details

2: invalidate

3: relogin 4: validate login 5: booking ticket

6: back to homepage

7: View booked details

8: back to homepage

9: profile details


11: logout


22/73

Admin loginhomepa

ge

Stadium

RestaurantDetails

Rooms

Details

Staff

Mumber

Logout

1: login details

2: invalidate

3: Relogin 4: validate

5: Add Details

6: Back tohomepage

7: Add restaurant details

8: back to homepage

9: Add Room details


11: Add Staff details


13: logout


23/73

Staff loginhomepa

ge

StadiumBooking

Room

Booking

Ticket

Details

My

Profile

Logout

1: login details

2: invalidate


5: View stadium details

6: Backtohomepage

7: View Room details

8: back to homepage

9: Add ticket details


11: changes Profile


13: logout


24/73

Board loginhomepa

ge

Stadium

Booking

back to

homepage

View Stadium booking

Change

password

Logout

1: login details

2: invalidate


5: booking stadium

6: Backtohomepage

7: booking room

8: back to homepage

9: View booking details10: back to homepage

13: changes Password


15: logout

View Room

booking

11: view booking details



25/73

Board loginhomepa

ge

Stadium

Booking

back to

homepage

View Stadiu

m booking

Change

password

Logout

1: login details

2: invalidate


5: booking stadium

6: Backtohomepage

7: booking room

8: back to homepage

9: View booking details10: back to homepage

13: changes Password


15: logout

View Room

booking

11: view booking details



26/73

COMPONENT DIAGRAM :


27/73

DEPLOYMENT DIAGRAM :


28/73

3.2 ENTITY RELATION DIAGRAM

Register Has

LoginAllowsActivity Checks

User Accounts

Booking

Fee

Location

Has

Has

Choose


29/73


30/73

data store

Figure3.4 1ST LEVEL

Login

Validation Data

ProcessData store

Booking View details Update details

1.1 AcceptUserName, Password

Admin

1.2Verify Details


31/73

Figure 4.5 2nd

level

Login

Validation Data

Process

ooking User profile Location profile Activity profileView Details


32/73

IMPLEMENTATION

MODULES:

Admin Module Booking Schedule Club Promoters Maintenance Module

MODULE DESCRIPTION:

Admin Module :

This module is for Administrator who organizes, schedules tasks and maintains the

system.

Booking Schedule :

In this module users can access and can book sports club tasks. Board member can access

and can book stadium

Club Promoters :In this module different club promoters can see various tasks and organize them.

Maintenance Module :

In this module different maintenance tasks can be scheduled and maintained.

Categories of user :

1) Non-member

2) Member

3) Club staff

4) Administrative staff


33/73

SAMPLE CODE:

Basketball

Enter the person name


34/73

Person Name

Account No

Bank Name


35/73

20-12-06

Even more websites all about website templates on Just Web Templates.
20-12-06
If you're looking for beautiful and professionally made templates you can find them

at Template Beauty.

20-12-06

If you're having problems editing the template please don't hesitate to ask for help on

the forum.

Knowmore

23-12-06

Even more websites all about website templates on Just Web Templates.

more

23-12-06

If you're looking for beautiful and professionally made templates you can find themat Template Beauty.

more

Automated Sports Club All right Reservered. | designed by Honeypot IT


36/73

5. SOFTWARE TESTING

Software Testing is a critical element of software quality assurance and represents the

ultimate review of specification, design and coding, Testing presents an interesting anomaly for

the software engineer.

Testing Objectives include:

Testing is a process of executing a program with the intent of finding an error

A good test case is one that has a probability of finding an as yet undiscovered error

A successful test is one that uncovers an undiscovered error

Testing Principles:

All tests should be traceable to end user requirements Tests should be planned long before testing begins Testing should begin on a small scale and progress towards testing in large Exhaustive testing is not possible To be most effective testing should be conducted by a independent third party

Testing Strategies:

A Strategy for software testing integrates software test cases into a series of well planned

steps that result in the successful construction of software. Software testing is a broader topic for

what is referred to as Verification and Validation. Verification refers to the set of activities that

ensure that the software correctly implements a specific function. Validation refers he set of

activities that ensure that the software that has been built is traceable to customers requirements


37/73

(a) Unit Testing:

Unit testing focuses verification effort on the smallest unit of software design that is the

module. Using procedural design description as a guide, important control paths are tested touncover errors within the boundaries of the module. The unit test is normally white box

testing oriented and the step can be conducted in parallel for multiple modules.

(b) Integration Testing:

Integration testing is a systematic technique for constructing the program structure, while

conducting test to uncover errors associated with the interface. The objective is to take unit

tested methods and build a program structure that has been dictated by design.

Top-down Integration

Top down integrations is an incremental approach for construction of program structure.

Modules are integrated by moving downward through the control hierarchy, beginning with

the main control program. Modules subordinate to the main program are incorporated in the

structure either in the breath-first or depth-first manner.

Bottom-up Integration

This method as the name suggests, begins construction and testing with atomic modules

i.e., modules at the lowest level. Because the modules are integrated in the bottom up manner

the processing required for the modules subordinate to a given level is always available and

the need for stubs is eliminated.

(c) Validation Testing:

At the end of integration testing software is completely assembled as a package.

Validation testing is the next stage, which can be defined as successful when the software

functions in the manner reasonably expected by the customer. Reasonable expectations are


38/73

those defined in the software requirements specifications. Information contained in those

sections form a basis for validation testing approach.

(d)System Testing:

System testing is actually a series of different tests whose primary purpose is to fullyexercise the computer-based system. Although each test has a different purpose, all work to

verify that all system elements have been properly integrated to perform allocated functions.

(e) Security Testing:

Attempts to verify the protection mechanisms built into the system.

(f) Performance Testing:

This method is designed to test runtime performance of software within the

context of an integrated system.

TESTING:

Previous phase also meaningfully helps us in testing of modules. We also gave special attention toinbound testing i.e. alpha testing. A complete cycle till the satisfaction level is processed. Around

4 complete weeks were devoted to testing and its resolution.

The testing strategies that we used are given below:

Other person writes test Plans according to SRS. Then Test cases were prepared. Test suspension and resumption criteria are decided. Test stop criteria are decided.

UNIT TESTING

Here, individual components are tested to ensure that they operate correctly. Eachcomponent is tested independently, without other system components. We used entry and

exit method for the trace of control flow. In every module we place messages on its entry

and on its exit.


39/73

SUB SYSTEM TESTING :

We used this testing technique to check the interface mismatch between the collections of

components involved in each of our subsystem.

BLACK BOX TESTING

Each input interface is tested on different set of data to ensure the consistency of the

system. Data type of every field with their possible maximum and minimum values aretested strongly.

DEPLOYMENT TESTING

Set up programs and testing on different OS platforms was done.

Testing Cycle

A testing cycle includes:

1. Requirements Analysis: Testing should begin in the requirements phase of the softwaredevelopment life cycle.

During the design phase, testers work with developers in determining what aspects of a

design are testable and under what parameter those tests work.

2. Test Planning: Test Strategy, Test Plan(s), Test Bed creation.3. Test Development: Test Procedures, Test Scenarios, Test Cases, Test Scripts to use in

testing software.

4. Test Execution: Testers execute the software based on the plans and tests and report anyerrors found to the development team.

5. any errors found to the development team.6. Test Reporting: Once testing is completed, testers generate metrics and make final reports

on their test effort and whether or not the software tested is ready for release.

7. Retesting the Defects


40/73

TEST CASES:

A test case is a software testing document, which consists of event, action, input, output, expectedresult and actual result. Clinically defined (IEEE 829-1998) a test case is an input and an expectedresult.

VERIFYING ADMIN LOGIN DETAILS :

O

Test Case

Name Objective Description Test Steps Expected Result Actual Result

1 Admin_Login

To verify thatadmin is able

to login intothe system

Admin enters his

user name andpassword and

clicks on Loginbutton

1)Admin enters

his/her username

and password2)Clicks on the

submit button

Admin logs in

into theapplication and

his home page isdisplayed with

filtering and userdetails

Admin logs

in and hishome page is

displayedwith filtering

and userdetails P


41/73

DELETING A USER :

CREATING A NEW USER:

OTest Case

Name Objective DescriptionTest Steps

Expected ResultActualResult R

Admin_DelUser

To verify ifAdmin is

able to delete

a User

Admin clicks on

Delete User link,

enters the username to be

deleted and clicks

on delete button

1)Deletes a user

with the help ofdelete option

User is deleted

and a screen

displayingsuccess message

along with login

link is displayed

User is

deleted and ascreen

displaying

success

messagealong with

login link is

displayed

3 Admin_CreateUser

To verify ofAdmin is

able to

create new

user

Admin clicks on

Create User, enters

the new user detailslike

name,password,email

address and clicks on

Create button

1)Creates anew user

2)Enter the

username &

password ofthe user

3)clicks on

the create

button

Admin

creates new

user with all

his specifieddetails and a

success

screen is

displayed

Admincreates new

user with all

his

specifieddetails and

success

screen is

displayed. P


42/73

MODIFYING ADMIN PASSWORD:

ADMIN FILTERING

O Test Case Name Objective Description

Test StepsExpected

Result

Actual

Result R

Admin_ChangePwd

To verify if

Admin is

able tochange his

password

Details of eachfilters are

displayed

1)Admin clicks

on the modify

password

option.2)Admin enters

his new

password.3)Clicks on the

okay button

Password is

changed

Password is

changed

O

Test Case

Name Objective Description

Test Steps

Expected Result

Actual

Result R

Admin_Filtering

To verify if

filtering

details aredisplayed to

the Admin

Admin clicks onfiletering details

link

1)Admin clicks

on the filter

details Filtering detailsare displayed to

the Admin

Filtering

details aredisplayed to

the Admin


43/73

ADMIN FILTER DETAILS

ADMIN LOGOUT

NO Test Case Name Objective Description

Test Steps Expected

Result

Actual

Result R

6 Admin_FilertingDetails

To verify if

details of

each

filtering

options aredisplayed

Admin clicks

on the filteringdetails link

1)Admin

clicks on the

filter details

2)Filter

options aredisplayed.

Details of

each filter


Details of

each filter

option aredisplayed P

O

Test Case


Test Steps

Expected Result

Actual

Result R

Admin_logout

To verify if

Admin canlogout from

theapplication

Admin clicks onLogout

1)Admin clicks

on the logoutbutton Admins logs out

from theapplication

Admins logs

out from theapplication


44/73

USER LOGIN

USER COMPOSE MAIL

Test Case

Name

Objective Description Test Steps Expected

Result

Actual

Result

Result

8

User_Login To verify

if a user is

able to

login into

the

application

User enters the

details of user

name and

password

1)User login

using

username &

password.

2)Clicks on

the login

button

User logs into

the application

and his home

page is

displayed

User logs

into the

application

and his

home page

is

displayed

Pass

O

Test Case


Test Steps

Expected Result Actual Result

User_Mail

To verify ifuser is able to

compose a

mail and send

it

User clicks on

Compose link ,enters the details ofthe email to be sent

and clicks on Send

button

1)User clicks onthe compose

button.2)Compose themail

3)clicks on the

send button

Email is sent to theaddressed person

and a success

message is

displayed

Email is sentto the

addressedperson and a

success

message is

displayed


45/73

USER FILTERING

USER FILTER DETAILS

O

Test Case


Test Steps

Expected Result Actual Result

User_Filter

To verify if

Report is

generated withthe filetered

details

User clicks on

Filter Details link

and a screen withthe filtered data is

displayed

1)User clicks on

the filter details

option.

2)All the filterdetails are

displayed.

Report isgenerated with the

filtered details

Report is

generatedwith the

filtered details

O Test Case Name Objective Description

Test Steps

Expected Result Actual R

User_FilertDetails

To verify if

details of each

filtering


User clicks on

Filtering Detailslink

1)User clicks onthe filtering

options

2)Checks whether

each and everyoneis working or not.

Filtering details

with options aredisplayed

Filter

details

optiondispla


46/73

USER MODIFYING HIS PASSWORD

SNO Test Case Name Objective Description

Test

StepsExpected

Result

Actual

Result Result

12 User_ChangePwd

To verify

if user is

able tochange

his

password

User clickson Change

Password,

enters

old,new andconfirm

password

details andclicks on

change

button

1)User

clicks onthe

modify

password.

2)Entershis new

password.

3)Clickon the

submit

button.

Password

is

changed

Password

is

changed Pass

SNO

Test Case


Test Steps Expected

Result

Actual

Result Result

13 User_AddFilter

To verify

user is able

to addfilters

User clicks on

the filter detailsto see whether

he can add filter

details or not

User clickson Filter

Details and

underoptions ,

select to

add a newfilter

1)User

clicks onthe filter

options.

2)Creates anew filter

by

providing aname to it

New

Filterwith the

desired

value isceated

New

Filterwith the

desired

value isceated Pa


47/73

SCREEN SHOTS

6.1 EXPLANATION OF THE OUTPUT RESULTS

WELCOME PAGE :


48/73

ADMINISTRATOR LOGIN PAGE


49/73

ADMIN LOGIN HOME PAGE


50/73


51/73

DELETE THE STADIUM NAME.


52/73

ADDING RESTAURANT LOCATION DETAILS.


53/73

INSERTING THE EMPLOYEE DETAILS.


54/73

LOGIN PAGE OF STAFF


55/73

ADDING THE TICKET DETAILS.


56/73

DETAIL OF USER


57/73

CHOOSE LOCATION WITH VIEW ROOMS


58/73

ROOM BOOKING PAGE.


59/73

SELECTED STADIUM NAME AND NO OF DAYS.


60/73

USER BOOKING ACTIVIST.


61/73

BOOKING DETAIL OF LOCATION .


62/73

USER DETAIL UPDATE.


63/73

USER DETAIL UPDATED SUCCESSFULLY.


64/73

CHANGE THE PASSWORD


65/73

Home page


66/73

LOGIN THE USER


67/73

ACCOUNT DETAILS


68/73

UPDATING THE USER DETAILS.


69/73

ABOUT MATCHES


70/73

ABOUT TICKET INFORMATION


71/73

UPDATED NEWS.


72/73

7.CONCLUSION & FUTURE SCOPE OF WORK

There have been many attempts to classify reusable components using various

techniques. The proposed classification system takes advantage of the positive sides of

each classification scheme, whilst hopefully rendering the negative sides redundant. The

well classification scheme is performed the more effective the retrieval system would be.

This classification scheme uses the attribute value for different parts of a component. The

attribute value scheme is initially used within the classification for specifying the Domain,

Version, platform, operating system and development language relating to the component.

This allows the search space to be restricted to specific libraries according to the selected

attribute values. And we can expect the more relevant components by this classification

mechanism.

Future work involved with this classification scheme will be to refine the scheme,

and formalize it for implementation. Though some classification scheme is developed it

was not done with extensive study of all existing components. In order to be effective the

scheme should be enhanced to meet the interests of people.


73/73

8.BIBLIOGRAPHY

Web References

Sun Java Homepage

http://java.sun.com

Sang Shins Java Passion J2EE Homepagehttp://javapassion.com/j2ee

Core J2EE Blueprints / Patterns: Patterns Homepagehttp://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html

The Server Side Homepage

http://www.theserverside.com

Core Servlets and Java Server pages By Marty Hall

Java JSPWrox Publication

Java Servlet Programming- Oreilly

Developing Java Servlets- Published by: TechmediaThe Complete Reference of Java2- Author: Patric Naughton, Herbert Schildt

HTML 4.0-Published by: BPB Publications

Electronic club

Documents

Transcript of Electronic club