Report1 Odt

A
PROJECT ON
“ONLINE MOVIE TICKET BOOKING SYSTEM”
SUBMITTED IN
PARTIAL FULFILLMENT OF THE REQUIREMENT
FOR THE COURSE OF
DIPLOMA IN MOBILE COMPUTING FROM CDAC
SUNBEAM INSTITUTE OF INFORMATION TECHNOLOGY

Phase 2, Hinjewadi Rajiv
Gandhi Infotech Park,
Hinjawadi, Pune, Maharashtra
411057
MH-INDIA
SUBMITTED BY:
SAMADHAN NIVRUTTI IVARE
UNDER THE GUIDENCE OF:

Mr. ----------
Sunbeam Institute of Information Technology, PUNE.
- 32-
1-
CERTIFICATE
This is to certify that the project work under the title “Online Movie Ticket Booking System” is
done by Samadhan Nivrutti Ivare in partial fulfillment of the requirement for award of Diploma
in Mobile Computing Course.
Mr. ------------- Mr. Rohan Paramane

Project Guide Course Co-Coordinator
Date:
ACKNOWLEDGEMENT
The satisfaction that accompanies that the successful completion of any task would be incomplete
without the mention of people whose ceaseless cooperation made it possible, whose constant guidance
and encouragement crown all efforts with success.
We are grateful to our project guide Mr. Rohan Paramane (Course Coordinator, Sunbeam, Pune) for
the guidance, inspiration and constructive suggestions that helpful us in the preparation of this
project.
Last but not the least we thank the entire faculty and the staff members of Sunbeam Institute of
Information Technology, Pune for their support.
SAMADHAN NIVRUTTI IVARE,

DMC Aug 2019 Batch,
SIIT Pune.
ABSTRACT
1. Objective:
The main aim of this Movie World is online booking tickets for varies movies by users.
2. Problem Definition:
Here details about now playing movies and no of tickets available in a particular theater for particular
movie, movie details, ticket cost for registered users.
3. Proposed System:
mean support code behind technology.

It supports different controls like html controls, server controls.
This project contains three modules.
1.Admin
2. Booking tickets
3.Users
1. Admin
In this admin can register movies and users.
2.Booking system
In this details about booked ticket and ticket booking admin can update, add, delete, details.
3. Users
In this users can see showing movies and details ticket booking and registering as members.
INDEX
1 INTRODUCTION 1
1.1 Project Description 1
2 PRODUCT OVERVIEW AND SUMMARY 2
2.1 Purpose 2
2.2 Scope 3
2.3 User Classes and Characteristics 3
2.4 Design and Implementation Constraints 3
3 REQUIREMENTS 4
3.1 Functional Requirements
3.1.1 Use case for Admin.
3.1.2 Use case for User.
3.2 Non - Functional Requirements
3.2.1 Usability Requirement
3.2.2 Performance Requirement
3.2.3 Reliability Requirement
3.2.4 Portability Requirement
3.2.5 Security Techniques
4 PROJECT DESIGN
4.1 Data Model
4.1.1 Database Design
4.2 Process Model
4.2.1 Functional Decomposition Diagram
4.2.2 Data Flow Diagram (DFD)
PROJECT RELATED STATISTICS
CONCLUSION
Online Movie Ticket Booking System
1. INTRODUCTION
1.1. Project Description:
Cinema-going is one of the most popular out-of-home cultural activities, affecting a serious of social,
economic and cultural phenomena in modern societies. Cinemas are considered to be an integral part
of cities and they contribute to the definition of a local geography and identity. They also contribute to
the preservation of the collective memory, since they constitute a significant social and cultural
practice linked to a specific place, which acts as a common reference or landmark for many
individuals. Through this project we present a comprehensive solution for ticket booking in
multiplexes.
Theater management system, an online ticket selling software that is easy to understand, easy to use
and offers the simplicity of fast point-and-click service to the customers. This powerful software
program is specifically designed for theater owners, to sell tickets online. This intuitive visual
interface makes day-to-day aspects of selling, exchanging, refunding, and reporting fast and easy for
both the user and administrators.
Theater management controls all back-end functionalities like, movie details, ticket rate and show
time, customer information and sales history saved in a database, etc. Theater admin manages the
report details like counter wise report, daily, weekly, monthly report and movie report etc.
1
2. PROJECT OVERVIEW AND SUMMARY

2.1 Purpose:
Users --→ Select movie --→ Book Tickets --→
Display Ticket.
Why the new system?
1. With the new system the following activities get more momentum.
The actual process of the organization can be modularized into two
different independent views.
 User view
 System administrators view
2.The user at any time can view the required information whether seats available for
particular movie in a particular theater. He can collect all information like as movie
details.
3. The information while it is collected can referentially be segregated into the

irrespective databases from single window, saving the time of multiple data entries.
4. If planned in an organized manner the users can be provided an online terminal

where they can access the information at their own hands with out the basic
intervention manually.
5. The user can first registration in enter the personal details, and user login and If you
want to update personal Details and you and update.
6. The user can book tickets and after insert movie and theater details and display
payment details.
7. The user collect all information like as theater details and movie.
8. Administrator is maintain the movie details ,Theater details, and Check the user
details.
9. The Administrator check the user account details, admin got the check. offer clear
the payment in bank. Administrator is Active the user for tickets.
2.2 Scope:
1. The proposed system is online ticket booming.
2. User can book ticket easily.
3. Current system allows the user to create account and book ticket.
4. admin can manage movie show etc.
5. This system provide facility like watch trailer, movie info,etc.
2.3 User Classes and Characteristics:
2.4 Design and Implementation constraints:

3. REQUIREMENTS
Methodology and Software Reference Model
The project is web based. Basically, it contains two main modules as per the requirement.
Software Reference Model : Waterfall Model
In a waterfall model, each phase must be completed before the next phase can begin and there
is no Overlap-ping in the phases. The outcome of one phase acts as the input for the next
phase sequentially. According to this system requirement need to develop the software with
the waterfall approach. After Finalized the project, with the help of blood donation websites
visited, requirements are collected. In next phase design of two modules done. And after
design varication, one by one modules are implemented. Test cases of two modules are
completed at the end and will deploy to web server.
4
Hardware Interfaces
l PIV 2.8 GHz Processor and Above

l RAM 512MB and Above
l HDD 20 GB Hard Disk Space and Above
Software Interfaces
l IDE: Visual Studio

l Browser: Chrome
l Database: MySQL
3.1 Functional Requirement

Use case Model:
Use case Diagrams represent the functionality of the system from a user’s point of view.
Use cases are used during requirements elicitation and analysis to represent the
functionality of the system. Use cases focus on the behavior of the system from external
point of view. Actors are external entities that interact with the system. Examples of actors
include users like administrator, bank customer …etc., or another system like central
database.
3.1.1 Admin
l Login with username and password.
l Add, Update, Delete Movie Record and view.
l Add, Update, Delete Movie Schedule Record and view.
l Delete User and view
l View all Movie and Movie schedule details.
3.1.2 User
l Login with username and password.
l User Registration.
l Select Movie.
l Book Movie.
3.2 Non-functional Requirement
 It consists of following parameters :-
3.2.1 Reliability
The system will consistently perform its intended function.
For eg. The important information must be validated.
3.2.2 Reusability
The system can be reused in any organization or site of the same group, by defining the
organization master definition under software license agreement
3.2.3 Efficiency
Website is easy to operate. Unnecessary data will not be transmitted on the network and
database server will be properly connected to web server
3.2.4 Integrity
Only system Administrator has rights to access the database, not every user can access all the
information. Each user will be having rights to access information related to its activities.
4. PROJECT DESIGN
4.1 DATA MODEL:
4.1.1 Database Design

4.2 Process model

ER Model
This diagram shows the entities in database and its related attributes. Also it describes what
Relationships between entities.
DETAILED DESIGN
Web Module
Home page
Admin Login
Admin Registration
Movie List
Movie Details
Add Movie
Edit Movie Details

Admin can see User List

User Login
User Registration
User Movie List
User Movie Details

Book Movie Ticket

2. TESTING
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding. In fact, testing is the one step in the software
engineering process that could be viewed as destructive rather than constructive.
A strategy for software testing integrates software test case design methods into a well-
planned series of steps that result in the successful construction of software. Testing is the set
of activities that can be planned in advance and conducted systematically. The underlying
motivation of program testing is to affirm software quality with methods that can
economically and effectively apply to both strategic to both large and small-scale systems.
2.1. STRATEGIC APPROACH TO SOFTWARE TESTING
The software engineering process can be viewed as a spiral. Initially system engineering
defines the role of software and leads to software requirement analysis where the information
domain, functions, behavior, performance, constraints and validation criteria for software are
established. Moving inward along the spiral, we come to design and finally to coding. To
develop computer software we spiral in along streamlines that decrease the level of
abstraction on each turn.
2.2. UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software design, the module.
The unit testing we have is white box oriented and some modules the steps are conducted in
parallel.
2.2.1. WHITE BOX TESTING

This type of testing ensures that
 All independent paths have been exercised at least once
 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational bounds
 All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have created
independently to verify that Data flow is correct, All conditions are exercised to check their
validity, All loops are executed on their boundaries.
2.2.2. CONDITIONAL TESTING

In this part of the testing each of the conditions were tested to both true and false aspects.
And all the resulting paths were tested. So that each path that may be generate on particular
condition is traced to uncover any possible errors.
2.2.3. DATA FLOW TESTING

This type of testing selects the path of the program according to the location of definition and
use of variables. This kind of testing was used only when some local variable were declared.
The definition-use chain method was used in this type of testing. These were particularly
useful in nested statements.
3. REFERENCES
https://in.bookmyshow.com/
https://www.ticketnew.com/
https://getbootstrap.com/
https://www.w3schools.com/bootstrap/
https://www.geeksforgeeks.org/

Report1 Odt

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Report1 Odt

Încărcat de

Drepturi de autor:

Formate disponibile

A

SUNBEAM INSTITUTE OF INFORMATION TECHNOLOGY

SAMADHAN NIVRUTTI IVARE

UNDER THE GUIDENCE OF:

Mr. ------------- Mr. Rohan Paramane

SAMADHAN NIVRUTTI IVARE,

mean support code behind technology.

This project contains three modules.

1.1. Project Description:

2. PROJECT OVERVIEW AND SUMMARY

3. The information while it is collected can referentially be segregated into the

4. If planned in an organized manner the users can be provided an online terminal

2.3 User Classes and Characteristics:

2.4 Design and Implementation constraints:

Methodology and Software Reference Model

Software Reference Model : Waterfall Model

l PIV 2.8 GHz Processor and Above

l IDE: Visual Studio

3.1 Functional Requirement

3.2 Non-functional Requirement

 It consists of following parameters :-

For eg. The important information must be validated.

4.1.1 Database Design

4.2 Process model

Edit Movie Details

Admin can see User List

User Movie List

User Movie Details

Book Movie Ticket

2.1. STRATEGIC APPROACH TO SOFTWARE TESTING

2.2. UNIT TESTING

2.2.1. WHITE BOX TESTING

2.2.2. CONDITIONAL TESTING

2.2.3. DATA FLOW TESTING

S-ar putea să vă placă și