1.
0 INTRODUCTION
1.1 Purpose:
The main objective is to provide a convenient way to the users to book the tickets
for cinema hall online, through which they can book tickets anytime and anywhere. Our app will
also give the facility to let the user select any timing slot and they have the authority to choose
any seat according to their convenience . This app is basically made for providing customers an
anytime and anywhere service for booking the seat in the cinema hall and to gather information
about the movies online.
1.2 Project proposal:
Our app will also give the facility to let the user select any timing slot and they
have the authority to choose any seat according to their convenience . This app is basically made
for providing customers an anytime and anywhere service for booking the seat in the cinema hall
and to gather information about the movies online. The user can easily be able to know about the
movies released and then make the choices.
The goals of our system are:
● To provide an anytime anyplace service for the user.
● To minimize the number of staff at the ticket box.
● To promote the film on the internet.
● To increase the profit to obtain statistical information from the booking record.
1.3 Scope of this Document:
The main purpose of our online ticket booking system is to provide another way
for the user to buy cinema tickets. It is an automatic system. After inserting the data to the
database, staff need not to due with the order received through the system. In fact, there is a
similar system on the internet, but there is no refund method found in the existing system. This
system is basically aimed to provide the user the complete information of the movie, according
to which the user can book the tickets and along with can order snacks and the refund facility
provides more flexibility to the system.
2.0 Overall Description:
2.1 System Environment:
This app adopts a comprehensive approach to minimize the manual work and
schedule resources, time in a cogent manner. The software controls redundancy so that no
two users can access the same seat at the same time and transactions should be
independent.
2.1.1 Functional Requirements:
1.Register
Input – Name , email-id , contact No. , Password
Processing – User will be registered
Output – User’s account has been created successfully
2.Login
Input – Id Name ,Password
Processing – credentials will be checked to verify the user or admin 17
Output – Go to Home page
3.Book Ticket
Input – Movie name , date , time , seat type , No. of tickets
Processing – credentials of the movie will be checked to see if the desired seat is available or not
.
Output – movie will be booked
4.Order Snacks
Input – Food item ,No. of Item
Processing – snack will be check that it is available or not
Output – snack will be ordered
5.Payment
Input – Card No. , CVV No.
Processing – details are verified
Output – payment done successfully
6.Send Notification
Input – none
Processing – sends conformational message
7.Cancel Ticket
Input – user Id , Password , Ticket Id
Processing – cancellation process is started by checking that it fulfills cancellation constraint
Output – Ticket will be canceled with/without refund .
2.1.2 USE CASE DIAGRAM:
2.1.3 ENTITY RELATIONSHIP DIAGRAM :
2.1.4. WORK DATA FLOW DIAGRAM :
2.2 NON - FUNCTIONAL REQUIREMENTS:
Non-functional requirements for a movie ticket booking system involve aspects
that are not directly related to the app's core functionality but are crucial for its overall
performance, usability, and maintenance. Here are some non-functional requirements you
might consider:
2.2.1 SECURITY:
The Online Movie Ticket System is fully accessible to only authentic users. It requires a
username and password to become a member of the app.
2.2.2. RELIABILITY:
The application is highly reliable and it generates all the updated information in correct order.
2.2.3. AVAILABILITY:
Any information should be quickly available from any computer to the authorized user.
2.2.4. MAINTAINABILITY:
The application is maintainable in such a manner that if any new requirements occur then it
should be easily incorporated in an individual module.
2.2.5. PORTABILITY:
The application is not machine specific.
2.3 DESIGN CONSTRAINTS:
Software Language Used
The languages that can be used for coding Online Movie Ticket System are JavaScript and
HTML.
Database Design
In our database design, we give names to data flows, processes and data stores. Although
the names are descriptive of data, they do not give details. Our interest is to build some details of
the contents of data flow, processes and data store. A data dictionary is a structured repository of
data about data. It is a set of rigorous definitions of all DFD data elements and structures.
2.3.1 STANDARD COMPLIANCE
Report format:
All the reports produced for this project are in compliance with the standard templates provided
in the class by the advisor.
Naming Conventions:
All the documents will be named using the standard naming conventions.
3.0 SYSTEM DESIGN
3.1 Description of Procedures and Functions
3.1.1.Register
Purpose: It allows users to get registered i.e. to create a new account in the system.
Actors involved: User
Precondition: none
Post condition: User successfully gets registered and the account has been created.
Basic Flow:
1. System requests the user to login or register.
2. User clicks on the register.
3. User enters his/her name, password, email id & phone number.
4. The system validates all the details entered by the user, if correct then it creates a new account
of the user.
Alternate Flow:
If in the basic flow, the user does not enter any mandatory details or enters any invalid
information, the system displays an error message asking the user to re-enter the information.
Users can either return to the Home page or cancel the registering process altogether.
Includes: None
Extends: None
3.1.2.Login
Purpose: It allows the user to use the online movie ticket booking system –“Movie Basket “,
with the help of an already existing unique id.
Actors involved: Admin, User
Precondition: Users must have an already existing account in the system. In case of no prior
account, users must first register themselves and then log into the system.
Post condition:
1. On successful login, the actor gets logged into the system.
2. If the actor has a role of an admin then he/she would have access to accept user’s request and
make required updation in the database register, login, change password, payment and cancel
ticket.
3. If the actor has a role as a user then he/she would have access to register, login, change
password, book movie ticket, order snack, payment and cancel ticket.
Basic Flow:
1. User or admin enters his/her id and password.
2. Then their id and password will be checked for authentication.
Alternate Flow:
If the user enters an invalid id and password then the error message will be displayed asking the
user to re-enter the details or cancel the login process. If the user selects the latter option, the use
case ends.
Extends: None
Includes: None
3.1.3 Book Movie Ticket
Purpose: It allows users to book movie tickets online.
Actors involved: User
Precondition: User has to be successfully logged into the system.
Post condition: Movie is booked for the user and all the booking details are displayed to
him/her.
Basic Flow:
User selects the movie name, date, time, language, type of seat and number of tickets.
Alternate Flow:
If the user selects the date or time or type of seat that is already booked then an error message is
displayed to the user and then the user can check for that movie on the upcoming dates.
Extends: None
Includes: None
3.1.4 Order Snack
Purpose:
It allows the user to order snacks at the time of movie booking.
Actors involved: User
Precondition: User has to first book a movie ticket.
Post condition: Snacks have been ordered and users can get it at the time of movie screening in
the cinema hall.
Basic Flow: User selects the type of snacks. If there are any coupons/offers, the user can apply it
on the total amount and then can make the payment.
Alternate Flow: If the ordered snack is out of stock then an error message is displayed to the
user and the user can select other items.
Excludes: None
Includes: None
3.1.5.Payment
Purpose:Allows the user to pay the movie ticket bill and snacks bill.
Actors involved: Admin, User
Precondition: User has booked a movie ticket and ordered some snacks.
Post condition: After the bill is paid online then the user gets movie ticket and snacks payment
confirmation on his/her registered mobile number as well as mail is sent on his/her registered
email id.
Basic Flow: User pays the total bill generated through credit card or debit card.
Alternate Flow: If the user enters incorrect CVV no. or credit/debit card no. then error message
is displayed to the user to re-enter all the details.
Includes: None
Excludes: None
3.1.6.Cancel Ticket
Purpose: Allows users to cancel movie tickets.
Precondition: Ticket should be booked and payment has been made.
Post condition: If the user cancels the movie ticket before 3 hours of the movie time then only
50% refund is being transacted into the user's account and the ticket is canceled otherwise only
the ticket is canceled without any refund.
Basic Flow:
User raises the request for the movie ticket cancellation by providing details such as date, time
and ticket id. Admin checks the details and confirms the request.
Alternate Flow:
If the user does not cancel his/her ticket before 3 hours of the movie time then the ticket will not
get canceled.
Excludes: None
Includes: None
4.0 IMPLEMENTATION AND TESTING
4.1 IMPLEMENTATION:
4.1.1. EXTERNAL INTERFACES.- Payment Gateway is the external interface.
4.1.2. USER INTERFACE
● It is a login window that requires the user to enter the correct ID and password, so that
after authentication, data stored in the user database is approved as a valid user so that
user can enter into our application.
● If the user does not exist, then the user must register in order to access the system
functionalities. ID and password will be stored in the database for future login purposes.
● User login to book movie tickets by selecting movie name, date, time, venue and
number of tickets required.
4.1.3. HARDWARE INTERFACE
Various interfaces for the product could be
1. Touch screen/Monitor
2. Keypad
3. Continuous battery backup
4.1.4. SOFTWARE INTERFACE
1. Any operating system.
2. JavaScript is required for a highly interactive environment.
4.1.5. DATABASE INTERFACE
● All databases for the software will be configured. These databases include movie’s details
database, users’ details database and admin database.
● The users’ details database includes user ID, password and previous and current booking
details. The events’ details database includes information about all listed events, their
organizers, dates, timings, venue, price per ticket and available seats.
● The organizers’ details database includes organizers’ ID, password and previous and
current listed events’ details.
4.2 TESTING
Pseudo code:
String foodItem ,choice;
Int Tickets , num , movie;
While(Login_Is_Success)
{ cout<<” Enter movie details “;
cin>> movie _name;
cin>>date;
cin>>Time;
cin>>Seat_Type;
cin>>No_Of_Ticket;
movie = Is_Movie(movie _name , date , Time , Seat_Type , No_Of_Ticket);
If( ! HouseFull(movie) )
{ Book_Ticket( Seat_Type , No_Of_Ticket );
updateTickets(_name , date , Time , Seat_Type , No_Of_Ticket);
Cout<<”Along with you want to order snack (Y|N) “;
Cin>>choice;
While(choice ==”yes”)
{ Cout<<” Enter food item”;
Cin>>fooditem;
Cout<<”Enter quantity”;
Cin>>num; 1 2 3 4 5 6 7 45
If(check(foodItem) && quantity(num) )
{ Order_Snack(fooditem , num);
Update_foodstock(fooditem , num);
Check =”No” ; }
Else
cout<<”Enter another food item “; }// end of inner while loop
Go for payment
}
Else Cout<<” Select any other movie”; }
// end of the outer while loop
//end of program
4.3 LAYOUTS:
5.REFERENCES:
1. SOFTWARE
ENGINEERING:https://www.tutorialspoint.com/software_engineering/index.htm
2. https://www.guru99.com (Incremental Model)
3. IEEE Software Engineering Standards committee, (IEEE recommended practice for
software requirement specification ", 2011).
