Documente Academic
Documente Profesional
Documente Cultură
Project Report On
Presented by
Nachiket Paluskar PRN 0811004010206
Nikhil Singh Rajput PRN 0811004010199
Prasad
Patankar
PRN 0811004010155
PRN 08110040101217
CERTIFICATE
This is to certify that
The project
On
Nachiket Paluskar
Nikhil Singh Rajput
Prasad Patankar
Pankaj Pimpalkar
Rohit Pareek
Project Guide
Project
Supervisor
ACKNOWLEDGEMENT
Ms.
Namrata
Ailawar
(Course
Coordinator)
for
her
support,
Pankaj Pimpalkar
PRN 0811004010219
PRN 0811004010155
Rohit Pareek
PRN 0811004010217
Nikhil Rajput
PRN 0811004010199
INDEX
1. Introduction
2. Project overview and summary
2.1
Purpose of Project
2.2
Scope of Project
2.3
Overview of Project
3. System Specification
3.1
Hardware Requirements
3.2
Software Requirements.
4. Preliminary Investigation
4.1
4.2
Project Management.
5. System Analysis
5.1
Existing System
5.2
Proposed System
6. Design Approach
6.1
6.2
6.3
ER Diagram
6.4
7. Project Modules
7.1
Organization Module
7.2
Creator
7.3
Approver
7.4
User
8. Data Tables
9. Testing Strategies
10. Output Screens
10.1 Admin Window
10.2 Creator Window
10.3 User Window
11. Future Scope
12. Conclusion
1 . INTRODUCTION
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
.
Platinum, Gold & Silver depending on the rate of the class/seat. Only 100% of the seats are
available for online reservation.
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.
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
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.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.
You can search for a certain movie on the online movie ticket website.
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. SYSTEM SPECIFICATIONS
Pentium-IV (Processor).
256 MB Ram
Hard disk 10 GB
Operating System :
Web-Technology:
Hibernate , Struts
Scripting:
JAVASCRIPTING
Front-End:
JSP,HTML
Back-End:
Oracle (10g)
Web Server:
Apache Tomcat.
Windows XP
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.
Computer systems are complex and often (especially with the recent rise of ServiceOriented 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"
4.1.1 Planning
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
The problem is specified along with the desired service objectives (goals),
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,
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:
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:
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.
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.
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.
Strategy
Derive traceability
information
to
assess
properly.
The time required to develop the software
is under-estimated.
Lack of training on tools that are used.
5. SYSTEM ANALYSIS
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.
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. 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 Diagrams
Use case diagrams model behavior within a system and helps the developers understand
of what the user require. The stick man represents whats called an actor.
6.1.1 User Profiles
1.
2.
3.
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 :
User
1. Search for movies show time.
2.
3.
4.
5.
Administrative Staff
1.
2.
3.
4.
5.
Login
View
Add
Update
Search
Logout
Admin
Search
Movie
Select Date
Select
Theatre
View Show
Book
Tickets
user
Payment
Pre-booking
Email
confirmatio
n
Feedback
Applicati
Search on
Search Result
Database
City Name
Match Sent
Search
Movie Name
Search Result
Match Sent
Select Date
send request
Date Result
send response
Select Theater
send request
Theater Result
Select Show
send response
Request
Show Screen
Response
Request
Response
Select Seats
Proceed to Payment
Enter Payment Details
Validate Payment
Send Email
Generate unique id
Feedback
Response
Applicati
login on
login successful
View Movie
Detailed Screened
Add Movie
Update Message
Add City, Theater
Update Message
Database
{login verify}
send Request
Send Result
request
Movie added
send request
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
Delete Show
Deleted
Request
Message
Logout
Result Update
Request
Update Message
Show
Delete Movie
Update
Movie Deleted
Delete Theatre
Request
Update Message
Theatre Deleted
Close Session
Logout Successful
Main Page
Search
Movie
Select
Class
Payment
Select
Seats
Canc
el
Exit
Login
yes
Main Page
no
Add
City
Update
Movie
Show
View
Movi
e
Price
Delete
Theat
er
Scree
n
Platinu
m
Refresh
Status
Movi
e
Show
Theatre
ID
Name
Rate
Theatre
Silver
Rate ID
Exit
Locatio
n
NO. of
screens
n
1
1
n
Time
Theatre
ID
Screen
ID
Login
Show
1
1
m
1
Movie ID
Show
date
Rate ID
Actress
Rated
Directo
Movie
User
name
n
1
1
n
1
Theatre
ID
1
Passwor
d
n
Show ID
Remaini
ng
Seats
Show
ID
n
Movie
ID
Name
Actor
1 Booking
Bookinfo
Logo
path
Booked
Seat
USER
BOOKING
THEATER
BOOKING
MOVIE
TICKET
MOVIE
BOOKED
SEATS
PRICE
Payment
DATE
7.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.
8. DATABASE TABLES
8.1 Movie
Movie
S.n
o
1
2
3
4
5
6
7
8
Colname
MovieID
Name
Actor
Actress
Director
Rated
Logopath
Status
Datatype
Number
Varchar2
Varchar2
Varchar2
Varchar2
Number
Varchar2
Varchar2
Size
10
20
20
15
11
10
15
10
Constraints
Pk_movie_id
not null
not null
not null
not null
not null
not null
not null
8.2 Show
State
S.n
o
1
Colname
Show Id
Datatype
Size
Constraints
varchar2
10
pk_show_id
2
3
4
5
6
7
8
Date
MovieID
Time
RateID
TheareID
ScreenID
RemainingSeat
Date
varchar2
Number
Number
Number
Number
varchar2
10
10
10
10
10
10
not null
not null
not null
not null
Fk_theatre_id
not null
not null
Colname
BookingID
BookSeat
ShowID
Datatype Size
Varchar2
Varchar2
Varchar2
10
20
10
Constraints
pk_booking_id
not null
Fk_show_id
Colname
BankName
Discount
Datatype Size
Varchar2
Varchar2
10
20
Constraints
not null
not null
8.5 Theatre
Movie
S.n
o
1
2
3
4
Colname
TheatreID
Name
No_of_Screens
Location
Datatype Size
Number
Varchar2
Number
Varchar2
10
20
10
Constraints
pk_theatre_id
not null
not null
not null
8.6 Rate
Movie
S.n
o
1
2
3
4
Colname
Type
Platinum
Gold
Silver
Datatype Size
Varchar2
Number
Number
Number
20
10
10
10
Constraints
not null
not null
not null
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.
Theater Page
Update Page
11. 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 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
by Roger Pressman
by Simon Robinson
REFRENCES:
www.oracle.org
www.w3schools.com
www.coderanch.com
www.wikipedia.com
www.apache.org
www.javasoft.com
www.vaanilla.com