This document presents an online movie ticket booking system created by five students. It describes the hardware and software requirements, procedural design including data flow diagrams and entity relationship diagram, database design with table descriptions, interface design screenshots, cost benefit analysis using function point analysis and COCOMO models, testing approach using test cases and control flow graphs, future enhancements, and conclusions. The system allows users to book movie tickets online and administrators to manage movie, theater, and screening information.

1. ONLINE MOVIE TICKET BOOKING SYSTEM
PRESENTED BY:-
 SUBHODEEP GHOSH (30201017005)
 SUBHASISH CHAKRABORTY (30201017006)
 SIDDHARTA BOSE (30201017007)
 DEBDULAL MAITY (30201017018)
 AVINANDAN GANGULY (30201017019)
BENGAL INSTITUTE OF TECHNOLOGY(MCA)
2ND YEAR, 4TH SEMESTER
SOFTWARE ENGINEERING & TQM(MCA- 401)

2. CONTENTS
 PROJECT OVERVIEW
 SOFTWARE & HARDWARE CONFIGURATION
• PROCEDURAL DESIGN
 DATABASE DESIGN
 ARCHITECTURAL DESIGN
 INTERFACE DESIGN
 COST BENEFIT ANALYSIS USING COCOMO & FPA
 TESTING
 FUTURE SCOPE
 CONCLUSION

3. PROJECT OVERVIEW
• The purpose of the online movie ticket booking system is to automate
the manual system of buying tickets from physical counters. The
required software and hardware specifications are readily available
and very efficient to work with.
The objectives are –
• Manipulate the data about movies, shows, screenings and the cities
and theatres where they are being released and screened.
• Manage data of users and buyers who bought tickets to facilitate
bookings in the future.
• The online movie booking system has two external entities interacting
with the system – user and administrator.
• The system collects details about the users who are interacting with
the system to make the process of booking a movie ticket faster.
• The administrator can keep track of the screenings of movies taking
place and also the movies themselves. The user can look for tickets
for a movie and purchase them, after logging in.

4. SOFTWARE & HARDWARE REQUIREMENTS
Hardware Specification:
• RAM – 4GB
• Hard Disk – 1TB
• Processor – Intel core i5
Software Specification:
• Operating System – Windows 10
• Code editor – Atom
• Languages used HTML,CSS(front-
end),php,MySQL(backend)
• Server – Apache, MySQL Server
• Software used – xampp, Atom
Hardware Requirements:
• RAM – 1GB
• Hard Disk – 256MB
Software Requirements:
• Operating System - Any
• Browser - Any

5. PROCEDURAL DESIGN
CONTEXT DIAGRAM

6. PROCEDURAL DESIGN (CONTD.)
1-LEVEL DATA FLOW DIAGRAM

7. DATABASE DESIGN
TABLE DESCRIPTION
USER TABLE
THEATRE TABLE
SCREENING
TABLE

8. DATABASE DESIGN(CONTD.)
TABLE DESCRIPTION
RESERVED
TABLE
MOVIE TABLE

9. DATABASE DESIGN(CONTD.)
TABLE DESCRIPTION
CITIES
TABLE
AUDITORIUM
TABLE
ADMIN TABLE

10. DATABASE DESIGN(CONTD.)

11. ENTITY
RELATIONSHIP
DIAGRAM

12. ARCHITECTURAL DESIGN
USE-CASE
DIAGRAM

13. INTERFACE DESIGN
Index page

14. INTERFACE DESIGN
Login page

15. INTERFACE DESIGN
Signup page

16. INTERFACE DESIGN
Profile page

17. INTERFACE DESIGN
Booking page

18. INTERFACE DESIGN
Purchase page

19. INTERFACE DESIGN
Confirmation page

20. INTERFACE DESIGN
Admin signup and
login pages

21. INTERFACE DESIGN
Admin area page

22. INTERFACE DESIGN
Movie add and
delete pages

23. INTERFACE DESIGN
Add location and
add theatre pages

24. INTERFACE DESIGN
Add auditorium and
add screening pages

25. COST BENEFIT ANALYSIS
FUNCTION POINT ANALYSIS
According to the formula,
FP = UFP*TCF
From the Data Flow Diagram,
no. of inputs=7
no. of outputs=6
no. of inquiries=2
no. of files=2
no. of interfaces=1
 UFP=7*4 + 6*5 + 2*4 + 2*10 + 1*10
= 96
 TCF= (0.65 + 0.01*42) = 1.07
FP = 96*1.07 = 102.72

26. COST BENEFIT ANALYSIS(CONTD.)
COCOMO (CONSTRUCTIVE COST ESTIMATION MODEL)
The multiplier values based on the factors are below:-

27. The EAF value for the project based on these factors is, 1.05.
The project size is 2.4KLOC which is < 50KLOC, hence
project falls under organic type.
So, Effort, E = 3.2 × (2.4)1.05 × 1.05 PM = 8.42 PM.
 Development time, D = 2.5 × (8.42)0.38 Months = 5.6 Months.
 Average staff size = E/D persons = 1.5 persons.

28. TESTING
TESTING USING TEST-CASES
Test Template –
Module Name: Login Page
Test Date: 05-05-2019
Case-Study:-
Sr.
no
Input
Parameters
Datatype Expected
output
Actual
output
Remarks
1. Username Varchar user name user name Passed
2. Password Varchar password password Passed

29. VALIDATION USING CONTROL FLOW GRAPH
The code after numbering the executable line:
<?php
1. if(isset($_POST['login-submit'])){
2. require 'config.php';
3. $mailuid = $_POST['mailuid'];
4. $pass = $_POST['pw'];
5. if(empty($mailuid) || empty($pass)){
6. header('location:login.php?error=emptyfields');
exit();
}
7. else{
8. $sql = "SELECT * FROM users WHERE uname=?";
9. $stmt = mysqli_stmt_init($conn);
10. if(!mysqli_stmt_prepare($stmt,$sql)){
11. header('location:login.php?error=sqlerror');
exit();
}

30. 12. else{
13. mysqli_stmt_bind_param($stmt,"s",$mailuid);
14. mysqli_stmt_execute($stmt);
15. $res = mysqli_stmt_get_result($stmt);
16. if($row = mysqli_fetch_assoc($res)){
17. $pwdCompare = password_verify($pass,$row['pwduser']);
18. if($pwdCompare==false){
19. header('location:login.php?error=wrong_password');
exit();
}
20. else if($pwdCompare==true){
21. session_start();
$_SESSION['lastActivity'] = time();
$_SESSION['userid'] = $row['uid'];
$_SESSION['username'] = $row['uname'];
22. if(isset($_POST['uri'])){
23. header('location:'.$_POST['uri']);
}
exit();
}
24. else{
25. header('location:login.php?error=wrong_password');
exit();

31. }
}
26. else{
27. header('location:login.php?error=nousers');
exit();
}
}
}
}
28. else{
29. header('location:login.php');
30. exit();
}
?>

32. CONTROL
FLOW
GRAPH

33. The cyclomatic complexity,
V(G) = E – N + 2 = 35 – 30 + 2 = 7.
V(G) = P + 1 = 6 + 1 = 7.
V(G) = R + 1 = 6 + 1 = 7.

34. FUTURE SCOPE
• This project we have carried out was a learning
curve for us in development of such systems. In the
future we shall add more features and functionalities
maintaining software engineering principles
• Add searching function to allow users to search
movies, or theatres, or locations
• Allow users to rate movies after watching them in
the theatre
• Allow users to add comments and subsequent
replies to comments to facilitate word of mouth
• Different dynamic interfaces for different mobile
devices of different sizes

35. CONCLUSION
• This project has been developed successfully and the performance
of the system has been found satisfactory. Use of this interface
helps customer in having immediate information about running
movies and reserve their seat without wasting their precious time.
User friendly Interface also for the admin to add and delete movie
information.
Thus, we may conclude that:-
• This project is basically made for providing the customer anytime
and anywhere service for booking cinema tickets and providing
information about the movies and their schedule online.
• Admins can use this project to insert and delete data such as
movie description, movie schedule which will update the related
webpage and will be accessible by the customers.
• This system is basically aimed to provide complete information of
the movie and schedule to the customer, according to which he can
book the tickets.