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

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

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 of Bachelor 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:

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

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 sports centre 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 for those 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 without contacting 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 is no 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.

SOFTWARE REQUIREMENTS:

Technologies Databases Web Server Operating System

: : : :

Servlets, JSP, JDBC Oracle Apache Tomcat 5.5 Windows 2000 Prof/XP.

HARDWARE REQUIREMENTS:

Processor Processor Speed RAM

: : :

Intel P-IV based system 250 MHz to 833MHz 256 MB to 2 GB

CERTIFICATE

This is to certify that Mr., /Miss ****************** bearing Roll No. ********************** have developed software project Titled **************** For ********************* Software Solutions as Partial fulfillment for the award of the Degree of **************

Head of the Department

Principal ******College Name******

External

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 SYSTEM 2.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

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 sports centre 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 for those 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 without contacting 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 is no 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 Databases Web Server : : : Servlets, JSP, JDBC Oracle Apache Tomcat 5.5 Windows 2000 Prof/XP.

Operating System :

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

CLASS DIAGRAM :

A class diagram gives an overview of a system by showing its classes and the relationships among them.Class diagrams are static they 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 association between 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 a diamond end pointing to the part containing the whole.

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

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.

login

Homepage

Add stadium dteails

admin Delete stadium details

Add restaurent details

Add rooms

Add staff member details

login page

Home page

Add ticket details

Staff

View stadium booking details

view room booking details

my profile

login page

Home page

Room bookings

stadium bookings

Board view room booking details

view stadium booking details

my profile

change password

login page

Home page

ticket details User

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.

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 12: back to homepage

13: logout

Staff:

Staff

login

homepage

Stadium Booking

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 10: back to homepage

11: changes Profile 12: back to homepage

13: logout

Board:

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 10: back to homepage

11: logout

1: login details 3: Relogin Admin login

4: validate homepa ge 6: Backtohomepage 13: logout Logout 11: Add Staff details 5: Add Details

2: invalidate

Stadium

8: back to homepage 7: Add restaurant details

12: back to homepage

9: Add Room details 10: back to homepage

Staff Mumber

Restaurant Details

Rooms Details

1: login details 3: Relogin Staff login

4: validate homepa ge 6: Backtohomepage 13: logout Logout 11: changes Profile 5: View stadium details

2: invalidate

Stadium Booking

8: back to homepage 7: View Room details

12: back to homepage

9: Add ticket details 10: back to homepage

My Profile

Room Booking

Ticket Details

Logout 15: logout 1: login details 3: Relogin Board login 6: Backtohomepage 12: back to homepage 5: booking stadium Stadium Booking 8: back to homepage 14: back to homepage 7: booking room 9: View booking details 10: back to homepage back to homepage 13: changes Password View Room booking 4: validate homepa ge 11: view booking details

2: invalidate

Change password

View Stadiu m booking

Logout 15: logout 1: login details 3: Relogin Board login 6: Backtohomepage 12: back to homepage 5: booking stadium Stadium Booking 8: back to homepage 14: back to homepage 7: booking room 9: View booking details 10: back to homepage back to homepage 13: changes Password View Room booking 4: validate homepa ge 11: view booking details

2: invalidate

Change password

View Stadiu m booking

COMPONENT DIAGRAM :

DEPLOYMENT DIAGRAM :

3.2 ENTITY RELATION DIAGRAM

Register

Has

Activity

Allows

Login

Checks

User Accounts Has Booking

Has

Fee

Choose

Location

DATA FLOW DIAGRAMS

1.2Verify Details

Validation Data

Login

3.3 CONTEXT LEVEL

User

1.1 Accept UserName, Password

1.2Verify Details

Validation Data

Login

data store

Process Data store

Booking

View details

Update details

Figure3.4

1ST LEVEL

Admin

1.1 Accept UserName, Password

1.2Verify Details

Validation Data

Login

Process

Data Store

Booking

User profile

Location profile

Activity profile View Details

Figure 4.5 2nd level

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

SAMPLE CODE:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>Basketball</title> <link rel="stylesheet" href="style.css" type="text/css" charset="utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> </head> <body> <div id="wrapper"> <div id="man"><h1><img src="C://Tomcat 5.5//webapps//sports//images//logo.gif" width="778" height="60" alt="Logo"></h1> <div id="nav"> <a href="user.jsp"><img src="C://Tomcat 5.5//webapps//sports//images//h1.gif" width="246" height="30" alt="M1"></a> <a href="viewticket.jsp"><img src="C://Tomcat 5.5//webapps//sports//images//tc.gif" width="246" height="25" alt="M2"></a><a href="ticketprintview.jsp"><img src="C://Tomcat 5.5//webapps//sports//images//vtd.gif" width="246" height="25" alt="M2"></a><a href="userprofile.jsp"><img src="C://Tomcat 5.5//webapps//sports//images//profile.gif" width="246" height="25" alt="M9"></a> <a href="index.html"><img src="C://Tomcat 5.5//webapps//sports//images//logout.gif" width="246" height="25" alt="M7"></a><img src="C://Tomcat 5.5//webapps//sports//images//m8.gif" width="246" height="" alt="M8"> </div>

<div id="body"> <div class="drk" id="welcome"> <div class="top"> <div class="bot"><div class="picbar"><img src="images/tt3.jpg" width="151" height="78" alt="Pic 2"><img src="images/CA6A107F.jpg" width="151" height="78" alt="Pic 2"><img src="images/r.jpg" width="155" height="78" alt="Pic 2"></div> <p> <!--<pre>--> <p> </p> <!--</pre>--> </p> <p>&nbsp;</p> <p> <body><form action="ticketbooking.jsp" method="get" name="f4"> <center><caption> Enter the person name </caption></center>

<table width="500" border="0" align="center"> <tr> <td width="121">&nbsp;Person Name</td> <td width="369"><label> <input type="text" name="pname" id="pname" /> </label></td> </tr> <tr> <td width="121">&nbsp;Account No</td> <td width="369"><label> <input type="text" name="accountno" id="accountno" /> </label></td> </tr> <tr> <td width="121">&nbsp;Bank Name</td> <td width="369"><label> <input type="text" name="bname" id="bname" /> </label></td> </tr> <tr> <td>&nbsp;</td> <td><label> <input type="submit" name="submit" id="submit" value="Submit" /> </label></td> </tr> </table> </form> </body> </p> <p>&nbsp;</p> <p>&nbsp;</p>

<div class="pad"></div> </div> </div> </div> <div class="drk" id="news"> <div class="top"> <div class="bot"> <img src="images/c.jpg" width="156" height="249" alt="Pic 3" class="right" /> <div class="pad"> <h2><img src="images/h_current_sports_news.gif" width="117" height="21" alt="Current Sports News"></h2>

<h3>20-12-06</h3> <p>Even more websites all about website templates on <a href="http://www.justwebtemplates.com">Just Web Templates</a>.</p> <h3>20-12-06</h3> <p>If you're looking for beautiful and professionally made templates you can find them at <a href="http://www.templatebeauty.com">Template Beauty</a>.</p> <h3>20-12-06</h3> <p>If you're having problems editing the template please don't hesitate to ask for help on the <a href="http://www.free-css.com/">forum</a>.</p> <p class="more"><a href="http://www.free-css.com/" class="diamond">Know more</a></p> </div> <div class="clear"></div> </div> </div> </div> <div class="lit" id="features"> <div class="top"> <div class="bot"> <div class="pad"> <h2><img src="images/h_featured_events.gif" width="97" height="17" alt="Featured Events"></h2> <div class="event"> <h3>23-12-06</h3> <p>Even more websites all about website templates on <a href="http://www.justwebtemplates.com">Just Web Templates</a>.</p> <p class="more"><a href="http://www.free-css.com/" class="diamond">more</a></p> </div> <div class="event"> <h3>23-12-06</h3> <p>If you're looking for beautiful and professionally made templates you can find them at <a href="http://www.templatebeauty.com">Template Beauty</a>.</p> <p class="more"><a href="http://www.free-css.com/" class="diamond">more</a></p> </div> </div> <div class="clear"></div> </div> </div> </div> </div> <div class="clear"></div> </div> </div> <div id="foot"> <div id="foot-left"> <div id="foot-ball"></div> &copy;Automated Sports Club All right Reservered. | designed by Honeypot IT</div></div>

</body></html>

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

(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 to uncover 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

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 fully exercise 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 to inbound 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. Each component 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.

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 are tested 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 software development 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 any errors 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

TEST CASES:

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

VERIFYING ADMIN LOGIN DETAILS

SNO

Test Case Name

Objective

Description

1 Admin_Login

To verify that admin is able to login into the system

Admin enters his user name and password and clicks on Login button

Test Steps 1)Admin enters his/her username and password 2)Clicks on the submit button

Expected Result Admin logs in into the application and his home page is displayed with filtering and user details

Actual Result Admin logs in and his home page is displayed with filtering and user details

Result

Pass

DELETING A USER :

SNO

Test Case Name

Test Steps Objective Description 1)Deletes a user with the help of delete option Admin clicks on Delete User link, enters the user name to be deleted and clicks on delete button User is deleted and a screen displaying success message along with login link is displayed Expected Result

Admin_DelUser

To verify if Admin is able to delete a User

Actual Result User is deleted and a screen displaying success message along with login link is displayed

Result

Pass

CREATING A NEW USER:

1)Creates a new user Admin clicks on 2)Enter the Create User, enters username & To verify of the new user details password of Admin is like the user able to name,password,email 3)clicks on create new address and clicks on the create Admin_CreateUser user Create button button

Admin creates new user with all his specified details and a success screen is displayed

Admin creates new user with all his specified details and success screen is displayed.

Pass

MODIFYING ADMIN PASSWORD:

Test Steps SNO Test Case Name Objective Description 1)Admin clicks on the modify password option. 2)Admin enters his new password. 3)Clicks on the okay button

Expected Result

Actual Result

Result

Admin_ChangePwd

To verify if Admin is able to change his password

Details of each filters are displayed

Password is changed

Password is changed

Pass

ADMIN FILTERING

SNO

Test Case Name

Test Steps Objective To verify if filtering details are displayed to the Admin Description 1)Admin clicks on the filter details Expected Result

Actual Result Filtering details are displayed to the Admin

Result

Admin_Filtering

Admin clicks on filetering details link

Filtering details are displayed to the Admin

Pass

ADMIN FILTER DETAILS

Test Steps SNO Test Case Name Objective To verify if details of each filtering options are displayed Description 1)Admin clicks on the filter details 2)Filter options are displayed.

Expected Result

Actual Result

Result

Admin_FilertingDetails

Admin clicks on the filtering details link

Details of each filter options are displayed

Details of each filter option are displayed

Pass

ADMIN LOGOUT

SNO

Test Case Name

Test Steps Objective To verify if Admin can logout from the application Description 1)Admin clicks on the logout button Admin clicks on Logout Expected Result

Actual Result

Result

Admin_logout

Admins logs out from the application

Admins logs out from the application

Pass

USER LOGIN

Test Case Name User_Login

Objective To verify if a user is able to login into the application

Description User enters the details of user name and password

Test Steps 1)User login using username & password. 2)Clicks on the login button

Expected Result User logs into the application and his home page is displayed

Actual Result User logs into the application and his home page is displayed

Result Pass

USER COMPOSE MAIL

Test Case SNO Name

Test Steps Objective Description User clicks on Compose link , enters the details of the email to be sent and clicks on Send button 1)User clicks on the compose button. 2)Compose the mail 3)clicks on the send button Expected Result Actual Result Result Email is sent to the addressed person and a success message is displayed Pass

User_Mail

To verify if user is able to compose a mail and send it

Email is sent to the addressed person and a success message is displayed

USER FILTERING

SNO

Test Case Name

Test Steps Objective Description User clicks on Filter Details link and a screen with the filtered data is displayed 1)User clicks on the filter details option. 2)All the filter details are displayed. Expected Result Actual Result Result

10

To verify if Report is generated with the filetered User_Filter details

Report is generated with the filtered details

Report is generated with the filtered details

Pass

USER FILTER DETAILS

Test Steps SNO Test Case Name Objective To verify if details of each filtering options are displayed Description 1)User clicks on the filtering options 2)Checks whether each and everyone is working or not. Expected Result Actual Result

11

User_FilertDetails

User clicks on Filtering Details link

Filtering details with options are displayed

Filtering details with options are displayed

USER MODIFYING HIS PASSWORD

Test Expected Actual Steps SNO Test Case Name Objective Description Result Result Result 1)User User clicks clicks on on Change the Password, modify enters password. old,new and 2)Enters To verify confirm his new if user is password password. able to details and 3)Click change clicks on on the Password Password his change submit is is 12 User_ChangePwd password button button. changed changed Pass

SNO

Test Case Name

Test Steps Objective Description User clicks on the filter details to see whether he can add filter details or not

13

User_AddFilter

To verify user is able to add filters

User clicks on Filter Details and under options , select to add a new filter

Expected Result 1)User clicks on the filter options. 2)Creates a new filter by providing a name to it

Actual Result

Result

New Filter with the desired value is ceated

New Filter with the desired value is ceated

Pass

SCREEN SHOTS

6.1 EXPLANATION OF THE OUTPUT RESULTS

WELCOME PAGE :

ADMINISTRATOR LOGIN PAGE

ADMIN LOGIN HOME PAGE

DELETE THE STADIUM NAME.

ADDING RESTAURANT LOCATION DETAILS.

INSERTING THE EMPLOYEE DETAILS.

LOGIN PAGE OF STAFF

ADDING THE TICKET DETAILS.

DETAIL OF USER

CHOOSE LOCATION WITH VIEW ROOMS

ROOM BOOKING PAGE.

SELECTED STADIUM NAME AND NO OF DAYS.

USER BOOKING ACTIVIST.

BOOKING DETAIL OF LOCATION .

USER DETAIL UPDATE.

USER DETAIL UPDATED SUCCESSFULLY.

CHANGE THE PASSWORD

Home page

LOGIN THE USER

ACCOUNT DETAILS

UPDATING THE USER DETAILS.

ABOUT MATCHES

ABOUT TICKET INFORMATION

UPDATED NEWS.

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.

8. BIBLIOGRAPHY

Web References Sun Java Homepage http://java.sun.com Sang Shins Java Passion J2EE Homepage

http://javapassion.com/j2ee Core J2EE Blueprints / Patterns: Patterns Homepage

http://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 JSP Wrox Publication Java Servlet Programming- Oreilly Developing Java Servlets- Published by: Techmedia The Complete Reference of Java2- Author: Patric Naughton, Herbert Schildt HTML 4.0-Published by: BPB Publications