A

Project Report On

Online Ticket Reservation for Cinema Hall

SUBMITTED IN PARTIAL FULFILLMENT

FOR THE AWARD OF

DIPLOMA IN ADVANCED COMPUTING

From C-DAC, ACTS (Pune)

Guided by:-

Mrs. Ranjana Ghuge

Presented by

Nachiket Paluskar PRN 0811004010206

Nikhil Singh Rajput PRN 0811004010199

Prasad Patankar PRN 0811004010155

Pankaj Pimpalkar PRN 0811004010219

Rohit Pareek PRN 08110040101217

CENTER FOR DEVELOPMENT OF ADVANCE COMPUTING

ACTS-PUNE

CERTIFICATE

This is to certify that

The project

On

Online Ticket Reservation for Cinema Hall

Presented by

Nachiket Paluskar Nikhil Singh Rajput

Prasad Patankar Pankaj Pimpalkar Rohit Pareek

For the award of Diploma in Advance Computing

embodies the bona fide work done by them under my supervision.

Project Guide Project Supervisor Mrs. Ranjana Ghuge Ms. Namrata Ailawar

Principal Technical Officer

Shri. Aditya Kumar Sinha

ACKNOWLEDGEMENT

The success of this project the outcome of the enormous contribution of

various people involved directly or indirectly with project work. It is a pleasure to

express our sincere thanks to them all.

First and foremost, we are deeply indebted to our guide Mrs. Ranjana

Ghuge for their inspiring guidance, encouragement and supervision to complete

the project entitled “Online Reservation of Tickets for Cinema Hall” this project

would never have been possible without their guidance and supervision.

We are thankful to Mr. Hemant Darbari (Director: DAC ACTS PUNE)

our Ms. Namrata Ailawar (Course Coordinator) for her support, encouragement

and valuable guidance throughout our work.

Finally we are thankful to the staff members and colleagues who

contributed to complete the project tangibly or intangibly.

Pankaj Pimpalkar PRN 0811004010219

Nachiket Paluskar PRN 0811004010206

Prasad Patankar PRN 0811004010155

Rohit Pareek PRN 0811004010217

Nikhil Rajput PRN 0811004010199

INDEX

1. Introduction2. Project overview and summary

2.1 Purpose of Project2.2 Scope of Project2.3 Overview of Project

3. System Specification3.1 Hardware Requirements3.2 Software Requirements.

4. Preliminary Investigation4.1 SDLC & Methodology.4.2 Project Management.

5. System Analysis5.1 Existing System5.2 Proposed System

6. Design Approach6.1 UML – Use Case Diagram6.2 UML- Class Diagram6.3 ER Diagram6.4 Data Flow Diagram

7. Project Modules7.1 Organization Module7.2 Creator7.3 Approver7.4 User

8. Data Tables9. Testing Strategies

10. Output Screens 10.1 Admin Window 10.2 Creator Window 10.3 User Window

11. Future Scope 12. Conclusion

1 . 1 . INTRODUCTIONINTRODUCTION

This project is aimed at developing an online ticket reservation system for Cinema

Halls. The Ticket Reservation System is an Internet based application that can be

accesses throughout the Net and can be accessed by anyone who has a net connection.

This application will automate the reservation of tickets and Enquiries about availability

of the tickets. This application includes email confirmation for the tickets.

This is one of the important feature of our system. By examining the existing system on

the internet, we found that there is no such function available at this moment, so we try

to include it in our system. To protect the benefit of the cinema, we will not give the

money back to the customer, instead the customer has to visit cinema hall for further

process. So, the customer can get the money from the cinema hall. Hence both the

customer and the cinema can sort out further matter

.

Functional components of the project:

Following is a list of functionalities of the system. More functionality that you find appropriate

can be added to this list. And, in places where the description of functionality is not adequate,

you can make appropriate assumptions and proceed.

The Cinema hall has a web site and any user of internet can access this. The cinema hall is a

multiplex which has 4 or more screens. Each screen has 3 different types of seats/classes viz

Platinum, Gold & Silver depending on the rate of the class/seat. Only 100% of the seats are

available for online reservation.

1. A person should be able to

Choose city where he/she want to see the Movie.

Choose the film which he/she wish to book tickets.

Query the films on show for one weeks (Only one weeks advance reservation is available) should be there.

Able to choose the seats which are available for a certain class.

Can select seats from different classes as well for same show and screen also.

Give details about the credit card or debit card through which he is doing payment.

Able collect tickets at the counter presenting the unique id send to him/her through email.

2. A mail should be send to the concerned person about the confirmation of the ticket to the specified email address.

3. The system should automatically show the fare for the corresponding shows and amount of money needs to be pay for selected seats.

2. Project Overview and SummaryProject Overview and Summary

2.1 Purpose of Project :2.1 Purpose of Project :

The main purpose of our online ticket booking system is to provide another way

for the customer to buy cinema ticket. It is an automatic system. After inserting the data

to database, staff needs not to do with the order receive through the system. In fact, there

is similar system on the internet, but there is no refund method found in the existing

system

The goals of our system are:

1. To provide a anytime anyplace service for the customer

2. To promote the film on the internet

3. To increase the profit

4. To obtain statistic information from the booking record

2.2 Scope of Project :2.2 Scope of Project :

2.2.1 General Requirements (functional):

1. The web page (e.g. the time table page) will be generated automatically according

to the data in database.

2. A way in which the cinema hall admin (staff) can login to the system to perform

different operation.

3. A way in which the customer can modify its own data(booked seats before payment).

4. A way in which the customer can commit order by just clicking the seat (which is

shown on the screen) and insert some card data.

5. A way in which the customer can check the ticket record (seat numbers)selected

by him/her at the time of payment.

6. A way in which the staff can use the system to add data(e.g. film description) to

the database.

7. The system can verify the data before transaction.

8. The system can generate the time table automatically as the time table is set by

the staff.(operating mode for the staff to insert data).

11. The system can generate some statistic information according booking and

ticket selling record for the cinema hall per Movie based.

2.2.2 Interface Enhancements:

Our web-based system needs about more than 30 interfaces to handle all the functions.

Staff:

One of the main purpose of our system is to reduce the number of staff in the ticket

box. So, most of the job is done by the system automatically. Staff only need to insert

new film data and due with the refund part.

Customer:

To make the system more user-friendly, customer need not to enter lots of data. An order

will be commit step by step with guideline (request about 7 steps for an order).

2.3 Overview of Project :2.3 Overview of Project :

Our Online Ticket Reservation for Cinema Halls is a web-based system. The customers can

buy ticket online and cancel the seat at a suitable time (2 days before the show to 1hour before

the show)by visiting the cinema hall. To enhance the refund function, all the customers have

to present the unique id provided at the time of booking seats online.

Staff can use the system to insert and delete data (e.g. film description, time table) which will

update the webpage (webpage are dynamic page, changing according to the data in database).

Also, staff can check the statistic information from the system.

2.3.1 Features :

Lists all Times and Theaters

The website lists all of the major theaters, the movies that are showing and the movie times,

along with the information of available seats.

Movie Synopsis

The online movie ticket site provides a short summary of each movie plot to help you decide if

you want to see that movie.

Trailers

The online movie ticket site has short movie clips that you can view to get an idea of the plot and

genre of the movie.

Consumer Review

The movie ticket service offers consumer movie reviews posted and generated by different

critics and media.

Limit Search by Area

You can limit the movie search by theater location.

Limit Search by Theater

You can limit your search by a specific theater.

Limit Search by Movie

You can search for a certain movie on the online movie ticket website.

Limit Search by Date

You can search for movies according to the date they are showing.

Message Board/Forum

The website provides an area for clients to post comments or questions for other consumers to view.

Upcoming Movie

The service posts a list of movies that will be in the theaters soon.

3.3. SYSTEM SPECIFICATIONSSYSTEM SPECIFICATIONS

3.1 3.1 Hardware RequirementsHardware Requirements :-:-

Pentium-IV (Processor).

256 MB Ram

512 KB Cache Memory

Hard disk 10 GB

Microsoft Compatible 101 or more Key Board.

3.2 Software Requirements: -3.2 Software Requirements: -

Operating System : Windows XP

Programming language: JAVA-1.6

Web-Technology: Hibernate , Struts

Scripting: JAVASCRIPTING

Front-End: JSP,HTML

Back-End: Oracle (10g)

Web Server: Apache Tomcat.

4. PRELIMINARY INVESTIGATION

4.1 SDLC & METHODOLOGY

The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in

systems engineering and software engineering, is the process of creating or altering systems, and

the models and methodologies that people use to develop these systems. The concept generally

refers to computer or information systems.

In software engineering the SDLC concept underpins many kinds of software

development methodologies. These methodologies form the framework for planning and

controlling the creation of an information system: the software development process.

Systems Development Life Cycle (SDLC) is a logical process used by a systems analyst to

develop an information system, including requirements, validation, training, and user

(stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds

customer expectations, reaches completion within time and cost estimates, works effectively and

efficiently in the current and planned Information Technology infrastructure, and is inexpensive

to maintain and cost-effective to enhance.

Computer systems are complex and often (especially with the recent rise of Service-

Oriented Architecture) link multiple traditional systems potentially supplied by different

software vendors. To manage this level of complexity, a number of SDLC models have been

created: "waterfall"; "fountain"; "spiral"; "build and fix"; "rapid prototyping"; "incremental"; and

"synchronize and stabilize"

There are seven step of SDLC:

1. Planning

2. Design

3. Implementation

4. Testing

5. Acceptance

6. Maintenance

7. Disposal

4.1.1 Planning

Everything starts with a concept. It could be a concept of some-one, or everyone.

However, there are those that do not start out with a concept but with a question, ―What do you

want? they ask thousands of people in a certain community or age group to know what they want

and decide to create an answer. But it all goes back to planning and conceptualization.

It is also essential for developers to know that this stage deals a lot with upper management so if

you are not the owner of the software development company; you have to deal with them a lot in

this stage.

4.1.2. Design

Once planning and arguing with the manager or the owner about the plan and somehow

convincing them, it is time to design or create a rough plan regarding the software. Developers

will work together and decide the initial specifics of the software to be created.

They will decide what platform or programming language to use, which will take care

the coding of a certain part of the software and even the time frame. This could be conducted by

a project manager along with the developers. The workflow about the project is also laid out.

Some will also treat this stage as planning for the back-end operations in developing the

software. It is not only important that developers should have a solid plan; they should at least

know that something will help them achieve to finish the program faster.

4.1.3. Implementation

The first two stages are quite common in all SDLC models. However, things change

starting on this stage. When the design and all the things that you need have been laid out, it is

time to work on the plan. Some developers, especially those that follow the standard plan of

developing soft-ware will work on the plan and present them for approval. Implementation in

some SDLC models is a combination of implementation and testing to a focus group.

4.1.4. Testing

This could mean two things depending on an SDLC model. The first type of testing is

the actual testing by users. This is usually done in models wherein implementation does not go

with pre-testing with users. On the other hand, there are also testing that uses professionals in the

field. This testing is aimed in cleaning the software of all the bugs altogether.

For software that are set for public release, the software is first tested by other

developers who were not in charge in creating the software. They will weed out the bugs and

suggest fixes if every they find one. Once this stage is completed, it is time to test the software

not just to the developers but to actual users.

4.1.5. Acceptance

When the software is released to be used by a certain company, acceptance means the

software is implemented as an added tool or could be replacing another software that has been

found too wanting after years of use. On the other hand, when the software is implemented to the

public a new software could be an added software for use. It is difficult to change public

software but they are not closing their ears to new software. So developers will always have a

fighting chance in the market as long as they implement good software for public use.

4.1.6. Maintenance

When the software is implemented, it does not mean that the software is good as it is. All

SDLC models include maintenance since there are absolutely no way that a software will be

working perfectly. Someone has to stay in the present software to take a look and ensure the

program works perfectly.

When the software is implemented in public. Software companies either set up a call

center or an e-mail service to address the concerns of the consumer. As we have indicated in

previous chapters, Maintenance is quiet an easy task as long as the right food and product is

serve in an expected time frame. However, it is always a challenge when something goes wrong.

The whole team might not be there to help the developer so addressing a major concern could

never be answered.

4.1.7. Disposal

Last but not the least, when a software is being outmoded, it is not just all deletion of

files. Project managers should take a look at all the affected files of the software and determine

which file to protect and dispose. Disposal will also require an efficient purging of documents so

that no traces of information could be retrieved from memory devices inside the computer.

If the company is planning to re-use the company computers that is ok but it is an entirely

different story when the computer and other related equipments is sold.

4.2 PROJECT MANAGEMENT

4.2.1 Project Planning and Scheduling

As this product is pure business application the solution, is known. So mapping a

customer’s desires and a firm’s development must not be a bigger issue. We keep these factors in

mind and the model of the software development process was derived from other engineering

processes and it is undergoing.

The project has to develop from many stages before reaching its final development. It

offers meanings of the developments process more visible. Because from one phase to another.

This model is known as the “Iterative Waterfall Model”.

The waterfall model derives its name due to the cascading effect from one phase to the

other as is illustrated in Figure. In this model each phase is well defined with a starting and an

ending point, with identifiable deliveries to the next phase. This model is sometimes referred to

as the linear sequential model or the software life cycle.

It includes following activities:

Proposal writing.

Project planning and scheduling.

Project costing.

Project monitoring and reviews.

Personnel selection and evaluation.

Report writing and presentations.

Iterative Waterfall Model

The model consists of six distinct stages, namely:

1. Requirements analysis phase

(a)    The problem is specified along with the desired service objectives (goals),

(b)   The constraints are identified.

2.    In the specification phase, the system specification is produced from the detailed definitions

of (a) and (b) above. This document should clearly define the product function.

3.  In the system and software design phase, the system specifications are translated into a

software representation. The software engineer at this stage is concerned with:

Software architecture,

Algorithmic detail and

Interface representations.

The hardware requirements are also determined at this stage along with a picture of the

overall system architecture. By the end of this stage the software engineer should be able to

identify the relationship between the hardware, software and the associated interfaces. Any

faults in the specification should ideally not be passed ’downstream’.

4. In the implementation and testing phase stage, the designs are translated into the software

domain.

Detailed documentation from the design phase can significantly reduce the coding efforts.

Testing at this stage focuses on making sure that any errors are identified and that the

software meets its required specification.

5.   In the integration and system testing phase, all the program units are integrated and tested

to ensure that the complete system meets the software requirements. After this stage the

software is delivered to the customer.

6.   The maintenance phase is the usually the longest stage of the software. In this phase the

software is updated to: 

Meet the changing customer needs,

Adapted to accommodate changes in the external environment,

Correct errors and oversights previously undetected in the testing phases,

Enhancing the efficiency of the software.

Observe that feed back loops allow for corrections to be incorporated into the model. For

example a problem/update in the design phase requires a ‘revisit’ to the specifications phase.

When changes are made at any phase, the relevant documentation should be updated to reflect

that change.

ADVANTAGES:

Testing is inherent to every phase of the waterfall model,

It is an enforced disciplined approach,

It is documentation driven, that is, documentation is produced at every stage.

4.2.2. Risk Management

There are four stages to risk management planning:

1. Risk Identification; 2. Risk Quantification; 3. Risk Response;

4. Risk Monitoring and Control Assessment.

1. Risk Identification

Risk Identification is the first stage of risk management. It is concern with discovering

possible risks to the project. In principal, these should not be assessed or prioritized at this stage,

although in practice risks with very minor consequences or very low probability risks are not

usually considered. During the project development we faced following risk and try to solve

them by best efforts.

Business Impact Risk,

Staff Risk,

Process Risk,

Technology Risk.

2. Risk Analysis

Identifying risk and drawing up plans to minimize their effect on the project work is

called Risk Analysis. Risk may threaten the project, the software that is being developed.

Risk analysis and management are a series of steps that help a software team to

understand and manage uncertainty. Many problems can plague a software project. A risk is a

potential problem – it might happen, it might not. But, regardless of the outcomes, it is really

good idea to identify it, assess its probability of occurrence, estimate its impact, and establish a

contingency plan should the problem occur.

3. Business Impact Risk

This is the risk where concern is that of not being able to create the product that has

impact on clients business. If this project fails then all the future plans depending on this project

would also fail.

4. Staff Risk

This risk is dependent on the ability, experience and willingness of the software team

members to create the working product. All team members should put maximum effort to finish

the product on time. Employee risk is one of the major risks to be considered while designing

the software.

5. Process Risk

Process risk involves risks involving product quality. If the product developed does not

meet the standards set by the customer or the development team then it will be a failure. The

process must be clearly defined and responsibility should be divided among the members. True

business need should be described to avoid risk.

6. Technology Risk

Technology risk involves using technology that already is or soon to become obsolete in

the development of the software. Since technology changes rapidly nowadays so a matured

technology should be used in the development of the software. Technology should be selected in

such a way that it is long sustaining and is functional for longer period of time.

4.2.3. Risk Planning

Risk planning process considers each of the key risks which have been identified and identified

strategies to manage the risk. Again there is no simple process, which can be followed to establish risk

management plans. It relies on the judgment and experience of the project manager.

Risk Strategy

Change to the requirements which require

major design rework are proposed.

Derive traceability information to assess

requirement change impact.

The requirements are not understood

properly.

Analyze the requirements thoroughly.

The time required to develop the software

is under-estimated.

Allocate one more week than deadline.

Lack of training on tools that are used. Allocate more time for training on the tools.

The resources are insufficient. Analyze tools required and allocate them.

Technology will not meet Expectations Developed Proof of Concept

5. SYSTEM ANALYSIS5. SYSTEM ANALYSIS

5.1 Existing System5.1 Existing System

In the existing system, the Customer has to visit cinema hall for booking seats.

further they do not even have the information about the Movie which is in the cinema

hall, it's show time and different rates of the ticket.

Even the customer may not be able to get information about different cinema hall

available in the city. So, if he wish to see a Movie on a particular day he has to first roam

around the city to find out where it is being shown at the specific time.

Further cinema hall owner has to hire large number of staff at the counter for selling

tickets. enquiries about movie, etc.

Hence this system is much tedious and not much user friendly as per the need of current

scenario.

5.2 Proposed System5.2 Proposed System

In order to overcome the existing problem we are making this system as online where

every information about any cinema hall, movie, theater and rates can get online which helps the

customer to get better facilities at his own computer or laptop.

FUNCTIONALITIES OF THIS SYSTEM

A person should be able to

Choose city where he/she want to see the Movie.

Choose the film which he/she wish to book tickets.

Query the films on show for one weeks (Only one weeks advance reservation is available) should be there.

Able to choose the seats which are available for a certain class.

Can select seats from different classes as well for same show and screen also.

Give details about the credit card or debit card through which he is doing payment.

Able collect tickets at the counter presenting the unique id send to him/her through email.

6. 6. DESIGN DESIGN

Design is the first step in the development phase for any techniques and principles for the

purpose of defining a device, a process or system in sufficient detail to permit its physical

realization.

6.1 USECASE Diagrams6.1 USECASE Diagrams

Use case diagrams model behavior within a system and helps the developers understand

of what the user require. The stick man represents what’s called an actor.

6.1.1 User Profiles

1. Full Control(IT Support)

2. Read/Write/Modify Own(User/Administrative Staff)

3. Read Only(General Public)

6.1.2 USECASE

The Read/Write/Modify own group are the main and important user of this software.

Full Control Group (IT Support) :

IT Support is a team which manipulates and maintains the system. Since further improvement

and testing of the system is needed, the team will be inside the full control group.

Besides it is also responsible to add more functionality as per requirement of time . Further

information about movie reviews, upcoming movies, discounts, etc. has to be updated time to

time. Payment support through different bank gateways has to be ensured and added time to

time.

Read/Write/Modify Own Group :

User1. Search for movies show time.

2. Check for available seats.

3. Book his/her seats.

4. Make payment through credit or debit card.

5. Providing feedback or may contact us(regarding any problem while booking

tickets).

Administrative Staff

1. Able to login in website.

2. Add information to database(movie name, description)

3. Delete information from database

4. Modify information in the database.(adding new movie section, changing movie

description)

5. Obtain statistic information

Use –case diagram for admin(cinema hall)

Login

View

Add

UpdateSearchLogout

Admin

Use case diagram for user

Search Movie

Select Date

Search City

user

6.2 Sequence Diagram6.2 Sequence Diagram

Customer Sequence Diagram

Search City Name

Search Result Match Sent

Search Movie Name

Select Theatre

View Show

Book Tickets

Payment

Pre-booking

Email confirmation

Feedback

Client Application Database

Search Result Match Sent

Select Date send request

Date Result send response

Select Theater send request

Theater Result send response

Select Show Request

Show Screen Response

Select Price & number of seat Request

Show Seats Response

Select Seats

Proceed to Payment

Enter Payment Details Validate Payment

Send Email Generate unique id

Feedback Response

Admin Sequence Diagram

login

login successful {login verify}

View Movie send Request

Detailed Screened Send Result

Admin Application Database

Add Movie request

Update Message Movie added

Add City, Theater send request

Update Message send response

Add Show

Select Date

Select City Request

Select Theatre

Select Price

Select Class

Update Message Show Added

Update Button Update Database

Update Message Result Update

Delete Show RequestUpdate Message Show Deleted

Delete MovieRequest Update

Message Movie DeletedDelete Theatre Request

Update MessageTheatre Deleted

Logout Close Session

Logout SuccessfulLogout Successful

5.3 Activity Diagram5.3 Activity Diagram

Activity Diagram for User

A ctivity Diagram for Admin

Main Page

Search Movie Select Class Payment Select Seats Cancel

Exit

Login

no

yes

6.4 E-R Diagram6.4 E-R Diagram

Main Page

Add Update

City Movie

ShowTheater

Refresh StatusDeleteView

Show Movie

Price Screen

MovieTheater

Show

Exit

Gold

Silver Rate ID

Platinum

Rate

Name

NO. of screens

Location

Theatre ID

Theatre

Time

Rate ID

TheatreID

ShowMovie ID

Show date

Show ID

Password Theatre ID

Login

ActressRated ActorMovie ID

MovieDirector Name Booking ID Bookinfo

n 1

n 11m1 n11

n 1

n

1

n

1

1

1

6.5 Data Flow Diagram6.5 Data Flow Diagram

The DFD takes an input-process-output view of a system i.e. data objects flow into the

software, are transformed by processing elements, and resultant data objects flow out of the

software.

BOOKING MOVIE TICKET

USER

THEATER

MOVIE

PRICE

BOOKING

BOOKED SEATS

PaymentDATE

Remaining Seats

Screen ID

User name

Logo path

Booked Seat

Show ID

7.PROJECT MODULE7.PROJECT MODULE

Since the Administrative Staff and the user are the main target group of our software, we will

only concern about some important functions for the Administrative Staff and the user. The user

can start the buy ticket process after checking the movie detail.

7.1. Buying ticket

The buying ticket process is the most important function in our system. We will describe this

process in detail.

1. Choose the movie ,time and venue

2. Check the status of select venue at certain time.(by system)

3. Choosing the seat position.

4. Enter data like ticket type and payment method if the user pay by credit card, credit card

number need to be insert too.

5. Validation the data entered by the user.(e.g. credit card number) (by system)

6. Ask the user to confirm the transaction. (by system)

7. Show the transaction number to the user. (by system)

7.2 Administrative Staff

The system for the Administrative Staff part is not shown in the main page. Before the Administrative

Staff to perform any operation, he/she must login to the system first. Once the Administrative Staff login

to the system, the statistic information will be shown. And the Administrative Staff can choose function

by clicking the button on left hand side. The functions are:

1. Insert movie data.

2. Delete movie data.

3. Modify movie data.

4. Add new show to current showing movie.

8. DATABASE TABLES

8.1 Movie

  Movie      S.no Colname Datatype Size Constraints1 MovieID Number 10 Pk_movie_id

2 Name Varchar2 20 not null

3 Actor Varchar2 20 not null4 Actress Varchar2 15 not null5 Director Varchar2 11 not null6 Rated Number 10 not null7 Logopath Varchar2 15 not null8 Status Varchar2 10 not null

8.2 Show

  State      S.no Colname Datatype Size Constraints1 Show Id varchar2 10 pk_show_id2 Date Date not null3 MovieID varchar2 10 not null4 Time Number 10 not null5 RateID Number 10 not null6 TheareID Number 10 Fk_theatre_id7 ScreenID Number 10 not null8 RemainingSeat varchar2 10 not null

8.3 Book Info

  BookInfo      S.no Colname Datatype Size Constraints1 BookingID Varchar2 10 pk_booking_id2 BookSeat Varchar2 20 not null3 ShowID Varchar2 10 Fk_show_id

8.4 Bank Info

  Theatre      S.no Colname Datatype Size Constraints1 BankName Varchar2 10 not null2 Discount Varchar2 20 not null

8.5 Theatre

  Movie      S.no Colname Datatype Size Constraints1 TheatreID Number 10 pk_theatre_id2 Name Varchar2 20 not null3 No_of_Screens Number 10 not null4 Location Varchar2   not null

8.6 Rate

  Movie      S.no Colname Datatype Size Constraints1 Type Varchar2 20 not null2 Platinum Number 10 not null3 Gold Number 10 not null4 Silver Number 10 not null

9.TESTING STRATEGIES

Testing

The first step in planning testing is to develop a test strategy based on risk analysis. The purpose

of a test strategy is to clarify the major activities involved, key decision made, and challenges

faced in the testing effort. This includes identifying testing scopes, testing techniques, coverage

metrics, test environment and test staff skills requirements. The test strategy must account for the

fact that time and budget constraints prohibit testing every component of software a system and

should balance test effectiveness with test efficiency based on risks to the system. The level of

effectiveness necessary depends on the use of software and its consequence of failure. The

higher the cost of failure for software, the more sophisticated and rigorous a testing approach

must be ensure to effectiveness. Risk analysis provides the right context and information to

derive a test strategy.

Test strategy is essentially a management activity. A test manager (or similar role) is responsible

for developing and managing a test strategy.

Black Box Testing

Black Box Testing performs a comprehensive analysis, exposing security holes in your product

after development. Be to represents a new approach to security auditing. This new approach is

sometimes called “fizzing”, “fuzz testing” or “fuzzier” and can be used for securing in-house

developed applications and devices, as well as applications and devices of external document.

Most of the security holes found today in products and applications can be discovered

automatically. By using an automated attack tool that tries virtually all different attack

combinations, with the ability to detect certain applications anomalies and indicate a successful

attack, those security holes can be found almost without user intervention.

White Box Testing

The purpose of any security testing method is to ensure the robustness of a system in the face of

malicious attacks or regular software failures. White Box testing is performed based on the

knowledge of how the system is implemented. White Box testing includes analyzing dataflow,

control flow, information flow, coding practices, and exception and error handling within the

system, to test the intended and unintended software behavior. White Box Testing can be

performed can be performed to validate whether code implementation follows intended design,

to validate implemented security functionality and to uncover exploitable vulnerabilities.

10. OUTPUT SCREENS 10. OUTPUT SCREENS

Home Page(index.jsp)Home Page(index.jsp)

Theater Page

Seat Selection Page

Admin Login Page

Update Page

11. CONCLUSION11. CONCLUSION

The project was designed in such a way that future modifications can be done easily. The

following conclusions can be deduced from the development of the project.

Automation of the entire system improves the efficiency

We can provides the communication between Customer and Cinema Hall.

Can also create Registration for Customer so that Cinema Hall can contact them

about exiting offers.

Can also make Customer to Post their View on Website.

The System has adequate scope for modification in future if it is necessary.

It is the best way to improve selling Tickets with less efforts.

This is the best way for customer as well as Cinema Halls to Interact with each

other without much efforts.

12 . FUTURE ENHANCEMENTS12 . FUTURE ENHANCEMENTS

The project Online Ticket Reservation for Cinema Hall is flexible enough to meet the

requirements of the Customers. This project also has the scope of enhancements like:

12.1- Home delivery of tickets may be provided.

12.2 -Online Booking of Purchases of eatables(cold drinks, popcorn etc) can be provided.

12.3-Corporate booking

Multimedia support for corporate presentation can be provided. Conference facility can be

provided for corporate meetings in the hall. This will increase the profit of cinema halls as well

as the company organizing event.

12.4 Group booking

Any institute/company can book the tickets for students/clients and special discount will be

provided to them.

13. BIBILOGRAPHY

1. Oracle 11g Complete Reference

2. Software Engineering by Roger Pressman

3. Complete Reference for java by Simon Robinson

4. Headfirst JSP & Servlet

5. Struts2 in Action

REFRENCES:-

www.oracle.org www.w3schools.com www.coderanch.com www.wikipedia.com www.apache.org www.javasoft.com www.vaanilla.com