1

Project Report

On

BookMyShow (Online Movie Ticket

Booking Application)

Submitted in partial fulfillment for the award of

Post Graduate Diploma in Advanced Computing

(PG-DAC) from C-DAC, ACTS (Pune)

Guided by:

Mr. Arun

Presented by:

Mr. Gholkar Mangesh Vinayak Prn: 150240120070

Mr. Lathiya Sanket Rameshbhai Prn: 150240120096

Mr. Mohit Rajendra Mehta Prn: 150240120107

Mr. Patel Santoshkumar Babubhai Prn: 150240120128

Centre for Development of Advanced Computing (C-DAC), Pune

2

CERTIFICATE

TO WHOMSOEVER IT MAY CONCERN

This is to certify that

Mr. Gholkar Mangesh Vinayak

Mr. Lathiya Sanket Rameshbhai

Mr. Mohit Rajendra Mehta

Mr. Patel Santoshkumar Babubhai

have successfully completed their project on

BookMyShow (Online Movie Ticket Booking

Application)

under the guidance of Mr. Arun

Project Guide Project Supervisor

HOD ACTS Ms. Mita Karajagi

3

Project Report

On

BookMyShow (Online Movie Ticket Booking

Application)

Submitted in partial fulfillment for the award of

Post Graduate Diploma in Advanced Computing

(PG-DAC) from C-DAC ACTS (Pune)

Guided by:

Mr. Arun

Presented by:

Mr. Gholkar Mangesh Vinayak Prn: 150240120070

Mr. Lathiya Sanket Rameshbhai Prn: 150240120096

Mr. Mohit Rajendra Mehta Prn: 150240120107

Mr. Patel Santoshkumar Babubhai Prn: 150240120128

Centre of Development of Advanced Computing (C-DAC), Pune

4

ACKNOWLEDGEMENT

A project usually falls short of its expectations unless aided and guided by the right

person at the right time. We avail this opportunity to express our deep sense of gratitude.

We are deeply indebted and grateful to them for their guidance, encouragement and

deep concern for our project. Without critical evaluation and suggestions at every stage

of the project, this project could never have reached its present form.

We would especially like to thank our guide Mr. Arun who constantly guided us in

developing; pushing us to search for more answers to his numerous questions. And

thanks to the staff members of CDAC, Pune for their support.

Mr. Gholkar Mangesh Vinayak Prn: 150240120070

Mr. Lathiya Sanket Rameshbhai Prn: 150240120096

Mr. Mohit Rajendra Mehta Prn: 150240120107

Mr. Patel Santoshkumar Babubhai Prn: 150240120128

5

Table of Contents

1. Introduction ....................................................................................................... 8

1.1 Purpose ......................................................................................................... 8

1.2 Scope of the Project ...................................................................................... 8

1.3 Glossary ........................................................................................................ 8

1.3.1 JSPs ......................................................................................................... 8

1.3.2 Hibernate ................................................................................................ 9

1.3.3 Java EE .................................................................................................... 9

1.3.4 Html and Xml: ......................................................................................... 9

1.3.5 JavaScript: ............................................................................................. 10

1.3.6 JQuery ................................................................................................... 10

1.3.7 Css ......................................................................................................... 10

1.3.8 Ajax ....................................................................................................... 10

1.3.9 HQL ....................................................................................................... 10

1.4 Main Modules of the project ...................................................................... 11

1.4.1 SUPER ADMIN module .......................................................................... 11

1.4.2 THEATRE ADMIN module ...................................................................... 11

1.4.3 USER module ........................................................................................ 11

1.5 Features and Advantages Of the system ..................................................... 11

2. Overall Description ........................................................................................ 12

2.1 Functional Requirements: ........................................................................... 12

2.2 Hardware Requirements ............................................................................. 13

2.3 Software Requirements ............................................................................... 13

3. Diagrams .......................................................................................................... 15

6

3.1 Use Case Diagram ...................................................................................... 15

3.2 Data Flow Diagram (DFD) ........................................................................... 16

3.3 Activity diagrams: ....................................................................................... 18

3.3.1 Activity diagram for Main Admin: ............................................................ 19

3.3.2 Activity diagram for Theatre Admin ........................................................ 20

3.3.3 Activity diagram for User Module ........................................................... 21

3.4 E-R diagrams: .............................................................................................. 22

4. Software Life Cycle Model ................................................................................ 22

1. System Engineering and Analysis:- ................................................................ 22

2. Software requirement Analysis: - .................................................................. 22

3. Design: .......................................................................................................... 23

4. Coding: .......................................................................................................... 23

5. Testing: ......................................................................................................... 23

6. Maintenance: ................................................................................................ 24

7. Documentation:- ........................................................................................... 24

5. FEASIBILITY STUDY ........................................................................................... 24

1. Technical Feasibility ...................................................................................... 24

2. Operational Feasibility .................................................................................. 24

3. Economical Feasibility ................................................................................... 24

4. Time Feasibility ............................................................................................. 25

6. Database Tables ............................................................................................... 25

7. Screenshots ...................................................................................................... 26

8. Testing ............................................................................................................. 33

8.1 Testing phase: ............................................................................................. 33

8.2 Unit testing: ................................................................................................ 33

7

8.3 Integration testing: ..................................................................................... 33

8.4 System Testing ............................................................................................ 34

8.5 Functionality testing: .................................................................................. 34

8.6 Performance Strategy: ................................................................................ 34

8.7 Testing strategy .......................................................................................... 34

Appendix A: References ...................................................................................... 34

8

1. Introduction

1.1 Purpose

The main purpose of Book Your Show application is to provide customers anytime and anywhere service for booking cinema tickets and providing information about the movies and their schedule online.

Users can easily search for the movies and available seats of their choice by using seat layout UI and book it in advance.

This project basically manages the ticket booking process of all registered multiplexes, providing a user interface to the user to book movie tickets in a easy way.

This software updates of new shows and upcoming movies.

This ticket booking software provides with various attractive offers like taking premium membership and reward points for getting discount.

1.2 Scope of the project: It may help collecting perfect management in details. In a very short time, the collection will be obvious, simple and sensible. It will help a person to know the management of passed year perfectly and vividly. It also helps in current all works relative to College. It will be also reduced the cost of collecting the management & collection procedure will go on smoothly. The present project has been developed to meet the aspirations indicated in the modern age. An attempt has been made through this project to do all work ease & fast. It provide current add, Update, Move Next, Move Previous, Move Last, Find & Delete all facilities to accomplish the desired objectives. The facility Include in this project and the suggested activities have been organized to impart knowledge & develop skill & attitude in the College official works.

1.3 Glossary 1.3.1 JSPs Java Server Pages (JSP) is a technology that helps software developers create

dynamically generated web pages based on HTML, XML, or other document types. Released in 1999 by Sun Microsystems, [1] JSP is similar to PHP, but it uses the Java programming language.

1.3.2 Hibernate

9

Hibernate ORM (Hibernate in short) is an object-relational mapping framework

for the Java language, providing a framework for mapping an object-oriented domain model to a traditional relational database. Hibernate solves object-relational impedance mismatch problems by replacing direct persistence-related database accesses with high-level object handling functions.

1.3.3 Java EE

Java Platform, Enterprise Edition (Java EE) is the standard in community-driven enterprise software. Java EE is developed using the Java Community Process, with contributions from industry experts, commercial and open source organizations, Java User Groups, and countless individuals. Each release integrates new features that align with industry needs, improves application portability, and increases developer productivity.

1.3.4 HTML and XML

HyperText Markup Language, commonly referred to as HTML, is the standard markup language used to create web pages. Web browsers can read HTML files and render them into visible or audible web pages. HTML describes the structure of a website semantically along with cues for presentation, making it a markup language, rather than a programming language.

Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format which is both human-readable and machine-readable. It is defined by the W3C's XML 1.0 Specification and by several other related specifications, all of which are free open standards.

1.3.5 JavaScript

JavaScript , also known as ECMAScript (the untrademarked name used for the

standard), is a dynamic programming language. It is most commonly used as part of web browsers, whose implementations allow client-side scripts to interact with the user, control the browser, communicate asynchronously, and alter the document content that is displayed. JavaScript (at least the strict subset asm.js) is also considered an "assembly language of the web" – a compile target of source-to-source compilers – for making client side web applications, using other programming languages, supported by all the major browsers without plug-ins. It is also used in server-side network programming with runtime environments such as Node.js, game development and the creation of desktop and mobile applications.

10

1.3.6 JQuery jQuery is a fast, small, and feature-rich JavaScript library. It makes things like

HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript.

1.3.7 CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing the

look and formatting of a document written in a markup language. Although most often used to change the style of web pages and user interfaces written in HTML and XHTML, the language can be applied to any kind of XML document, including plain XML, SVG and XUL. Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobile applications.

1.3.8 Ajax Ajax short for (asynchronous JavaScript and XML) is a group of interrelated Web

development techniques used on the client-side to create asynchronous Web applications. With Ajax, web applications can send data to and retrieve from a server asynchronously (in the background) without interfering with the display and behavior of the existing page. Data can be retrieved using the XMLHttpRequest object. Despite the name, the use of XML is not required (JSON is often used in the AJAJ variant), and the requests do not need to be asynchronous.

1.3.9 HQL

Hibernate Query Language (HQL) is an object-oriented query language, similar to SQL, but instead of operating on tables and columns, HQL works with persistent objects and their properties. HQL queries are translated by Hibernate into conventional SQL queries which in turns perform action on database.

11

1.4 Main Modules of project

1.4.1 SUPER ADMIN Module :

Super Admin Module handles the entire work structure , maintainance, updation and supervision of all the modules and sub-modules. Admin can add multiplexes. Admin can also add upcoming movies and can update or delete previous movies. Admin can also view transaction report and can analyze revenue based on report.

1.4.2 THEATRE ADMIN Module :

This Module allows the registered theatre owners to access the various services like updating movies and show times as per their convenience.

1.4.3 USER Module :

User Module allows the registered users to access the various services. Users can easily search for the movies and available seats of their choice by using seat layout UI and book it in advance and pay the required amount using various payment modes .Users also can edit their profile here. These changes will be reflected

directly to database.

1.5 Features and Advantages of the system

Support concurrency in transactions.

Independent of client browser and OS

Admin can inform registered users about new releases and discounts and can get their feedback.

User can also book bulk tickets and get Premium Customers get featured discounts on their booking.

Users can search even without login. They need to login only for booking the tickets.

Server load balancing and transparent server failure.

Customers will get booking details via e-mail.

Customers will get rewards points on booking the tickets and in future they can use this points for discounts while booking.

12

2 Overall Description

2.1 Functional Requirements: The schedule of the movies will be generated via a query according to the data

selected by the user. A way in which users(both customer & admin) can login to the system to perform

different operation. A way in which the customer can commit order by “Point and Click” method. The system can verify the data before transaction. Support concurrency in transactions. Independent of client browser and OS Admin can inform registered users about new releases and discounts and can get

their feedback. User can also book bulk tickets and get Premium Customers get featured

discounts on their booking. Users can search even without login. They need to login only for booking the

tickets. Server load balancing and transparent server failure. Customers will get booking details via e-mail. Customers will get rewards points on booking the tickets and in future they can

use this points for discounts while booking. 2.2 Product Functions • User Registration User Register with Name, a username (for logging in later),Password,

Phone Number, E-mail address. • User Login User Can Book the Ticket After Log in. User Login with User Name and Password. Forgot Password use for Retrieve Password.

• Check Availability After Login, User, Can Search Movie From Movie List. User Can Check Ticket Availability. User can also check the Movie Running Hours. If Ticket is Available User Can Book Ticket.

• Book Ticket. User can book ticket by specifying username and Phone Number.

13

Then Select Number Of Seats to Book. A conformation Message will be sent to the Given Number.

The content of the message is as shown below:- Admin Control: • Admin User Login. Admin User Login with Admin User Name and Password.

• Show Manage. Admin Can Change Show Name and Show Time.

• Movie Mange. Admin Can Add New Movie. Admin Can Edit Old Movie Details. Admin Can Delete Movie.

• Schedule Manage. Admin Can Add New Movie Schedule. Admin Can Edit Movie Schedule. Admin Can Delete Movie Schedule.

• User Manage Admin Can control the signed up users Admin can delete the account of users who didn't show up for the movie

after booking tickets. • Counter Control Counter Employee Login with Counter User Name and Password.. Counter Employee type the message shown by the Customer in the field

given and confirm the user. Tickets are issued from the Counter.

2.3 Hardware requirements: Operating System : 32/64 bit Processor : pentium4/Dual core/x-86 Processor RAM : 2GB Hard Disk : 40GB

14

2.4 Software requirements: • Operating System: WINDOWS 8.1/8/7/NT/2000/XP/Linux • Languages: J2EE, JSP, HTML, JAVA SCRIPT, JQuery • Development Tools: ECLIPSE Luna. • Framework : Spring 4.X, Hibernate 4. • Database: ORACLE 11g • Web Server: Apache Tomcat. -

15

3 Diagrams

3.1 Use Case Diagram

16

3.2. Data Flow Diagram 3.2.1 Level 0

17

3.2.2 Level-1

18

3.3 Activity Diagram

3.3.1 Main Admin

19

3.3.2 Theatre Admin

20

3.3.3 User Module

21

3.4 E-R Diagram

22

4 Software life Cycle Models

4.1 System Engineering and Analysis

At this step the developers decide a roadmap of their plan and try to bring up the best software model suitable for the project. System analysis includes Understanding of software product limitations, learning system related problems or changes to be done in existing systems beforehand, identifying and addressing the impact of project on organization and personnel etc. The project team analyzes the scope of the project and plans the schedule and resources accordingly.

4.2 Software requirement Analysis If the feasibility report is positive towards undertaking the project, next phase starts with gathering requirements from the user. Analysts and engineers communicate with the client and end-users to know their ideas on what the software should provide and which features they want the software to include.

4.3 Design Next step is to bring down whole knowledge of requirements and analysis on the desk and design the software product. The inputs from users and information gathered in requirement gathering phase are the inputs of this step. The output of this step comes in the form of two designs; logical design and physical design. Engineers produce meta-data and data dictionaries, logical diagrams, data-flow diagrams and in some cases pseudo codes. 4.4 Coding This step is also known as programming phase. The implementation of software design starts in terms of writing program code in the suitable programming language and developing error-free executable programs efficiently. 4.5 Testing An estimate says that 50% of whole software development process should be tested. Errors may ruin the software from critical level to its own removal. Software testing is done while coding by the developers and thorough testing is conducted by testing experts at various levels of code such as module testing, program testing, product testing, in-house testing and testing the product at user’s end. Early discovery of errors and their remedy is the key to reliable software.

23

4.6 Maintenance This phase confirms the software operation in terms of more efficiency and less errors. If required, the users are trained on, or aided with the documentation on how to operate the software and how to keep the software operational. The software is maintained timely by updating the code according to the changes taking place in user end environment or technology. This phase may face challenges from hidden bugs and real-world unidentified problems. 4.7 Documentation

Software Requirement Specification SRS is a document created by system analyst after the requirements are collected from various stakeholders. SRS defines how the intended software will interact with hardware, external interfaces, speed of operation, response time of system, portability of software across various platforms, maintainability, speed of recovery after crashing, Security, Quality, Limitations etc. The requirements received from client are written in natural language. It is the responsibility of system analyst to document the requirements in technical language so that they can be comprehended and useful by the software development team.

5. Feasibility Study

5.1 Technical Feasibility

The technical feasibility assessment is focused on gaining an understanding of the present technical resources of the organization and their applicability to the expected needs of the proposed system. It is an evaluation of the hardware and software and how it meets the need of the proposed system.

5.2 Operational Feasibility

Operational feasibility is a measure of how well a proposed system solves the problems, and takes advantage of the opportunities identified during scope definition and how it satisfies the requirements identified in the requirements analysis phase of system development. 5.3 Economic Feasibility

24

The purpose of the economic feasibility assessment is to determine the positive

economic benefits to the organization that the proposed system will provide. It includes quantification and identification of all the benefits expected. This assessment typically involves a cost/ benefits analysis.

5.4 Time Feasibility

A project will fail if it takes too long to be completed before it is useful. Typically this means estimating how long the system will take to develop, and if it can be completed in a given time period using some methods like payback period. Schedule feasibility is a measure of how reasonable the project timetable is. Given our technical expertise, are the project deadlines reasonable? Some projects are initiated with specific deadlines. It is necessary to determine whether the deadlines are mandatory or desirable.

25

6. Database Tables :

26

7. Screenshots 1 ) User Module Home Page select city, movie and date

Select showtime

27

Select Class and no. of tickets and click on checkout

If You have not login at home page then login here

28

Now it will show summary after login. Here, You can enter reward points to get discount.

Proceed for payment - select payment method.

29

After successful payment, You will receive a mail about your booking details.

User can view Booking their booking history

30

2) Main Admin Module Home Page

Here, he can add movies and theatres.

31

He can also generate transaction report

3) Theatre Admin Module Home page- show movies

32

He can add, update and delete show data. Also, he can generate report about his theatre revenue.

Our team page

33

Contact Us

8. Testing

8.1 Testing Phase Software Testing is evaluation of the software against requirements gathered from users and system specifications. Testing is conducted at the phase level in software development life cycle or at module level in program code. Software testing comprises of Validation and Verification. 8.2 Unit Testing While coding, the programmer performs some tests on that unit of program to know if it is error free. Testing is performed under white-box testing approach. Unit testing helps developers decide that individual units of the program are working as per requirement and are error free. 8.3 Integration Testing

34

Even if the units of software are working fine individually, there is a need to find out if the units if integrated together would also work without errors. For example, argument passing and data updation etc. 8.4 System Testing :-

The software is compiled as product and then it is tested as a whole. This can be accomplished using one or more of the following tests: 8.5 Functionality testing –

Tests all functionalities of the software against the requirement. 8.6 Performance testing –

This test proves how efficient the software is. It tests the effectiveness and average time taken by the software to do desired task. Performance testing is done by means of load testing and stress testing where the software is put under high user and data load under various environment conditions. Security & Portability - These tests are done when the software is meant to work on various platforms and accessed by number of persons. 8.7 Testing strategy

both verification and validation test constructive test testing accomplished by independent test group testing conducted independent of debugging test scope: unit testing and block testing (due to the limitation of time)

Appendix A: References

www.javatpoint.com

www.stackoverflow.com

www.tutorialspoint.com

www.bookmyshow.com

http://www.mkyong.com –- Spring and Hibernate