Online Event Booking System - TutorialsDuniya

TUTORIALSDUNIYA.
COM
Online Event Booking

System
Software Engineering Project
Download FREE Software Engineering Projects for any

university student of BCA, MCA, B.Sc, M.Sc, B.Tech at
https://www.tutorialsduniya.com
If you find any error or mistake in this Software Engineering

project then report at abhishek@tutorialsduniya.com
Please Share these SE Projects with your Friends

Download FREE Software Engineering Projects from TutorialsDuniya.com
om
.c
i ya
un
O
D
N
ls
LINE EVENTS TICKET BOOKING SYSTEM

ia
t or
Tu

om
.c
By
i ya
un
Abhishek Agarwal 12345
D
Jatin Tiwari 12345

ls
ia
t or
Tu

TABLE OF CONTENTS
Certificate
Acknowledgement
1. Introduction
2. Project Management
2.1. Process Model
2.2. Risk Management and Analysis
om
2.3. Scheduling
 Schedule Table
 Timeline
.c
2.4. Functional Point Analysis
2.5. Effort Estimation
ya
3. Requirement Analysis
 Product Functions
 User Characteristics
 General Constraints
i
un
 Assumptions and Dependencies
 Functional Requirements
D
 Performance Requirements
 Data Requirements
ls
 Data Flow Diagram

 Data Dictionary
ia
 ER Diagram
4. Design
or
 Data Design
 Architecture Design
t
 Interface Design
Tu
 Coding
5. Testing
 Flow graph
 Cyclomatic Complexity
References

Certificate
This is to certify that the project report entitled "AmuseIT" done by
om
Abhishek Agarwal and Jatin Tiwari is an authentic work carried out by them.
It embodies the work done by them during semester IV of their course

under the due supervision of TutorialsDuniya.Com.
.c
ya
Date: 12th April
Signature of the Guide
i
un
Name of the guide
D
ls
ia
t or
Tu

Acknowledgment
We are indebted to TutorialsDuniya.Com for her guidance and patience. It is
her guidance that led us to envision our project “AmuseIT” to a full-fledged
om
solution for online event booking system.
We are also thankful to TutorialsDuniya and TutorialsDuniya for their guidance

throughout the project.
.c
We again thank all my teachers and all the people who helped in creation of this
ya
project.
i
un
D
ls
ia
t or
Tu

Introduction
The main aim of this project is to develop the software for the process of
booking events and movies which should lead to increased efficiency and
reduced drawbacks which were present in the previous procedure of online
om
ticket booking and makes it convenient for the customer to book a
particular ticket. The software should control redundancy so that no two
customers can access the same seat at the same time and transactions
.c
should be independent. Moreover ticket booking has been a hassle for the
customer, they are left with just an option i.e. book the tickets by visiting
ya
the venue. Technical system is fast, accurate, informative, reliable and user
friendly. The proposed system enables the customer to do things such as
search for movies that are available on a specified date for a particular
i
venue. The system displays all the movie details such as price, duration,
un
venue, time, date.
D
ls
ia
t or
Tu

Process Model
Waterfall process model is used in our project AmuseIT.

This model is generally applied to the projects where the requirements are very
clear and the customer keeps on patience.
om
Different phases of model:-
1. Software Requirements Analysis

In this, software engineer understand the nature of a program to be built,
.c
he must understand the information domain for the software as well as
required function, behavior, performance and interface. Requirements for
ya
both the system and software are documented and reviewed with the
customer.
2. Design i
un
It has four distinct attributes of a program: data structure, software
architecture, interface representations and procedural details. It is
documental and becomes part of software.
D
3. Code Generation
ls
Design must be translated into a machine readable form which is done by

code generation.
ia
4. Testing
It focuses on the logical internals of the software, ensuring that all the
or
statements have been tested, and on the functional externals, that is

conducting test to uncover errors and ensure that defined input will
t
produce actual results.

Tu
5. Support
This is a phase when software will undoubtedly undergo change after it is
delivered to the customer. Change will occur because errors have been
encountered, because the software must be adapted to accommodate
changes in its external environment, or because the customer requires
functional or performance enhancements. Software support/maintenance

reapplies each of the preceding phases to an existing program rather than a

new one.
Waterfall model is used because of the following reasons:
• It's relatively simple and easier to understand approach as compared to
om
other models.
• The requirements are well stated and understood before in hand.
• In this model we have to complete one stage before proceeding to next. So,
.c
we have clearly defined stages and well understood milestones.
ya
• The advancement in program does not need to be checked upon by the
customer during the process. So this model does not create problem.
• The requirements are fixed and work can proceed to com
i completion in a linear
un
manner.
• The Waterfall Model provides a structured approach.
D
Communication
ls
Planning
ia
Modeling
or
Construction
t
Tu
Deployement

Requirement Analysis
Overall Description:
Product Functions:
Our online ticket booking system, AmuseIT is a web-based system.
The customers can buy tickets online. Admin can use the system to
om
insert and delete data (e.g. film description, time table) which will
update the webpage (webpage are dynamic page, changing
according to the data in database). Also, admin can check the statistic
information from the system. The project is being developed keeping
.c
in mind the following objectives:
 Reduce the paperwork and storage area.
ya
 Improve the output of operators.
 Improve accuracy in result.
 Manage the man and machine resources efficiently.
i
un
 It has user friendly interface having quick authenticated access to
documents.
 More security and safety of data.
D
 Quick query processing.

 Easy access to data.
ls
 Reliable and efficient.

 Increase the processing speed.
ia
 Quick access to appropriate candidate.

 Easy retrieval of information.
or
The features of this product are as follows:

t
 Prevention against unauthorized access

Tu
 Prevention against spamming.

 Easy navigation.
 Online ticket booking of all movies and events at any time.
 A presentable, fast and easy user interface.
 Minimizes the number of staff at the ticket box.
 Online promotion of the events and movies.
 Obtains statistic information from the booking record.

User Characteristics:
 Customer uses the system to fetch information about available
events and movies, their price and majorly to book tickets.
 Admin manages the system and keeps it up-to-date. Admin also looks
over customers and organizers.
 Organizers use the system to list their events, movies and other
om
related information like availability, price, duration, date and timings.
General Constraints:
 User interface is only in English. No other language option is
.c
available.
 An internet connection is required to use the system. A broadband
ya
(DSL or cable) or faster connection is recommended.
 The files in which the information regarding account should be
i
secured against malicious deformations.
un
 Data should not become corrupted in case of system crash or power
failure.
D
Assumptions and Dependencies:

ls
 Admin is created in the system already.

 Roles and tasks are predefined.
ia
 There is no limit for booking for the website. If this were so then the
instantaneous communication between the two systems would not
or
exist.
 In general it has been assumed that the user has complete
t
knowledge of the system that means user is not a naïve user. Any
Tu
data entered by him/her will be valid.

 It depends that the one should follow the international standards for
the generating the User ID & should fill the related information in the
proper format.
 Central server of the system must be able to handle all the incoming
requests simultaneously.
 Back up of the databases in case of hardware failure, disaster, natural
calamities.

 No data loss in case of handling of the system by the administrators

or the system related personnel.
 Username are valid email addresses of respective user
 Administrator has the authority to reserve/cancel movie tickets.
User Interfaces:
 It is a login window that requires user to enter correct ID and
om
password, so that after matching values stored in the database you
are proved as a valid user to enter into the 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
.c
the database for future login purpose.
 Customer logins to book event tickets by selecting event, date, time,
ya
venue and number of tickets required.
 Organizer logins to list his/her event on the system or to update
his/her existing event. i
un
Database Interfaces:
 All databases for the software will be configured. These databases
D
include events’ details database, customers’ details database, and

ls
organizers’ details database.

 The customers’ details database includes user ID, password and
ia
previous and current booking details.

 The events’ details database includes information about all listed
or
events, their organizers, dates, timings, venue, price per ticket and
available seats.
 The organizers’ details database includes organizers’ ID, password
t
Tu
and previous and current listed events’ details.
Functional Requirements:
Booking:
 This module basically deals with the booking of events. It accepts
order details, retrieve event details, processes the order based on
customer requirements and finally processes the payment to

generate tickets. After successful transaction, customers’ details

database is updated with E-tickets and other details, events’ details
database is updated with the number of seats left after last
transaction and other details, organizers’ details database is updated
with number of tickets booked and left and other details also.
Event Hosting:
om
 This module basically deals with the hosting of events. It accepts
event details, add event details. After successful hosting, events’
details database is updated with order and customer details, events’
.c
details database is updated with the number of seats and other event
details, organizers’ details database is updated with number of
ya
tickets booked and left and other details also.
Performance Requirements:
i
un
 Each component of the system can accept and work with only one
account at a time. Internet access is required for filtering events,
D
booking tickets, adding events and making payments.

ls
Data Requirements:
ia
 The system can store the following data: text data including name,
or
address, event details, venue and numeric data including number of

tickets, price, date, time and much more.
 Assuming a user has correctly authenticated him/her via email ID,
t
Tu
system will read back any of the previous data.

 The system will also maintain a backup database.

TutorialsDuniya.com
Download FREE Software Engineering Projects PDF for any

university student of BCA, MCA, B.Sc, B.Tech, M.Sc at
 3 Level Authentication  Airline Reservation System

 Banking Management System  Bus Route Enquiry System
 Car Showroom Dealership  Cricket Management System
 Criminal Record Management  E-Boutique
 Exam & Result Management  Health Care
 Hospital Management System  Online Bookstore
 Online Complaint Portal  Online Event Booking
 Online MetroCard Recharge  Online Missing Person Info
 Online Shopping  Online Shopping System
 Our First Home  Railway Reservation System
 Reality Show Management  Tour & Travel Management
 Smart City Traveller  Weather ForeCasting
Many more FREE Software Engineering Projects are available at

Please Share these SE projects with your Friends as well

Risk Management and Analysis

Risks Category Probability Impact
Quality is not maintained PS 60% 2
Customer will change requirements PS 80% 3
Staff inexperienced ST 30% 3
Delivery Deadline will be tightened BU 50% 2
Lack Of cooperation from user CU 30% 1
om
Lack of effective project managing technology BU 40% 1
Inadequate estimation of required resources PS 50% 1
Loss of database PS 50% 1
Developing wrong user interface DE 70% 2
.c
ya
PS - Product Size
BU - Business Impact i
un
CU - Customer Characteristics
DE - Development Environment
D
ST - Staff Size
ls
Impact value
ia
1 - CATASTROPHIC
or
2 - CRITICAL
3 - MARGINAL
t
4 - NEGLIGIBLE
Tu

Scheduling
Schedule Table
Work Tasks Schedule
1. Identify Needs & benefits
Meet with concerned members Week1
om
Identify needs & project constraints Week 1
Establish Problem Statement Week 2
Milestone Week 2
.c
2. Project Management
ya
Computing F.P. & Effort Week 3
Schedule Table Week 3
Risk Table Week 4
Timeline Chart
i Week 5
un
Milestone Week 5
D
3. Requirement Analysis Week 5

Detailed discussion of the project Week 6
ls
Creating Data Flow diagram Week 7

Data dictionary Week 8
ia
Milestone Week 8
or
4. Design Engineering
Architectural Design Week 8
t
Tu
Data Design Week 9

Pseudo Code Week 9
Milestone Week10
5. Testing Week 12

Timeline
om
.c
i ya
un
D
ls
ia
t or
Tu

Function Points Analysis

ILF Complexity Matrix
S. No. Data File Complexity

1. Customers’ Details Database Low
om
2. Organizers’ Details Database Low
3. Events’ Details Database Low
.c
EIF Complexity Matrix
ya
S. No. Data File Complexity
1.
i
Current Events Database Low
un
2. Venues’ Details Database Low
D
EIs Complexity Matrix

ls
S. No. Screens Complexity

ia
1. Login Low
or
2. Register Low
t
3. Add Event Low

Tu
4. Forget Password Low

5. Edit Customers’ Details Low
6. Edit Organizers’ Details Low
7. Book Tickets Low

EOs Complexity Matrix

1. E-Ticket High
2. Order Details Low
om
3. Payment Details High
4. Event Details Low
EQs Complexity Matrix
.c
ya
1. View Events Low
2.
i
View Orders Low
un
Complexity Adjustment Values Table
D
S. No. Questions VAFs

ls
1 Does the system require reliable backup and recovery? 4

Are specialized data communications required to transfer information
2 2
to or from the application?
ia
3 Are there distributed processing functions? 2

4 Is performance critical? 3
Will the system run in an existing, heavily utilized operational
or
5 2
environment?
6 Does the system require online data entry? 4
Does the online data enquiry require the input transaction to be built
7 2
t
over multiple screens or operations?

Tu
8 Are the ILFs updated online? 4

9 Are the inputs, outputs, files or inquiries complex? 2
10 Is the internal processing complex? 4
11 Is the code designed to be reusable? 4
12 Are conversion and installation included in the design? 3
Is the system designed for multiple installations in different
13 4
organizations?
Is the application designed to facilitate change and ease of use by the
14 4
user?
∑F(i) 44

Function Point Table
Information Domain Value WEIGHING FACTOR CALCULATION RESULT
COUNT SIMPLE AVG COMPLEX
(7*3)+(0*4)+(0*
External Inputs 7 3 4 6 21
6)
om
(2*4)+(0*5)+(2*
External Outputs 4 4 5 7 22
7)
(2*3)+(0*4)+(0*
External Inquiries 2 3 4 6 6
6)
.c
(3*7)+(0*10)+
Internal Logical Files 3 7 10 15 21
ya
(0*15)
External Interface (2*5)+ (0*7)+

2 5 i 7 10 10
Files (0*10)
un
Count Total 80
D
FP = count total * [0.65 + 0.01 * fi]

ls
FP = 80 * [0.65 + 0.01 * 44]

FP = 80 * [1.09]
ia
FP = 87.2
or
Effort Estimation
In PHP it takes 15 hrs to complete 1FP by 1 person. Let us say aperson works 6-7
t
hrs per day and 24 days a month. Then in 1 month 1person will be able to
Tu
complete approximately 10.4 FP. Then in approximately 8 months 1 person will

be able to complete 87.2 FP.
Efforts = (Total FP) / (Avg. Productivity) = 8.38 PM
To complete a project in 2 months we need 4 persons.

Level 0 DFD
om
.c
i ya
un
Level 1 DFD
D
ls
ia
t or
Tu

Level 2 DFD
om
.c
i ya
un
D
ls
ia
t or
Tu

Data Dictionary
Data Maximum
Field Name Description
Type Length
Customer’s Name Text 30 Name of the customer
Mobile number of the
Customer’s Phone Integer 10
om
customer
Customer’s Address Text 50 Address of the customer
Organizer’s Name Text 30 Name of the organizer
Mobile number of the
Organizer’s Phone Integer 10
.c
organizer
Organizer’s Address Text 50 Address of the organizer
ya
Unique email address of the
Customer’s Email Text 30
customer
Customer’s Password Text 30 Password of the customer
Customer ID Integer
i
10 Unique ID of the customer
un
Organizer’s ID Integer 10 Unique ID of the customer
Unique email address of the
Organizer’s Email Text 30
organizer
D
Organizer’s Password Text 30 Password of the organizer

Purchase ID Integer 10 Unique order ID
ls
Venue Text 30 Venue of the event/movie

Timing Date 10 Timing of the event/movie
ia
Event Name Text 30 Name of the event

Available tickets of the
or
Number of Tickets Integer 10

event/movie
Price of a ticket of the
Price Float 10
event/movie
t
Tu
Event ID Integer 30 Unique event ID of the event

Total Cost Float 10 Total cost of the order

ER Diagram
om
.c
i ya
un
D
ls
ia
t or
Tu

Data Design
om
.c
i ya
un
D
ls
ia
t or
Tu

Architectural Design
om
.c
i ya
un
D
ls
ia
t or
Tu

Coding
Customer/Organizer Login
1. {Choose customer or organizer (0/1) login

2. if(chosen==customer){
3. Enter email
4. If (email syntax is incorrect) {
om
5. Show (Please enter correct email)
6. Break;}
7. Else{
8. Enter password
.c
9. Search the entered email in database
10. if(username does not exist)
ya
11. Show (Check username or Register)
12. Elseif (username exists but password does not match) {
13. Show (Check username and password)}
i
un
14. Else if (username and password match)
15. Go to event selection screen}
16. Else break;}
17. If (chosen=organizer) {
D
18. Enter email

ls
19. If (email syntax is incorrect) {

20. Show(Please enter correct email)
21. break;}
ia
22. Else{
23. Enter password
or
24. Search the entered email in database

25. If (username does not exist)
t
26. Show(Check username or Register)

Tu
27. Else if (username exists but password does not match)

28. Show(Check username and password)
29. Else if (username and password match)
30. Go to event selection screen}
31. Else break;}
32. }

Testing
Flow Graph
om
.c
i ya
un
D
ls
ia
11
t or
Tu

Cyclomatic Complexity
 Regions: 10
 V(G) = E – N + 2
V(G) = 40 – 32 + 2 = 10
 V(G) = P + 1 = 9 + 1 = 8
om
Basis Set Independent Paths
.c
Path 1: 1-2-3-4-7-8-9-10-11-32
Path 2: 1-2-3-4-7-8-9-10-12-14-16-32
Path 3: 1-2-3-4-7-8-9-10-12-13-32
i ya
un
Path 4: 1-2-3-4-7-8-9-10-12-14-15-32
Path 5: 1-2-3-4-5-6-32
D
Path 6: 1-17-18-19-22-23-24-25-26-32
ls
Path 7: 1-17-18-19-22-23-24-25-27-28-32
ia
Path 8: 1-17-18-19-22-23-24-25-27-29-30-32
or
Path 9: 1-17-18-19-22-23-24-25-27-29-31-32
t
Path 10:1-17-18-19-20-21-32
Tu

Interface Design
om
.c
i ya
un
D
ls
ia
t or
Tu

References
 https://www.tutorialsduniya.com
 Software Engineering: A Practitioner's Approachby Roger

S. Pressman 7th Edition
om
 https://www.tutorialsduniya.com
.c
i ya
un
D
ls
ia
t or
Tu

TutorialsDuniya.com
Download FREE Software Engineering Projects PDF for any

university student of BCA, MCA, B.Sc, B.Tech, M.Sc at
 3 Level Authentication  Airline Reservation System

 Banking Management System  Bus Route Enquiry System
 Car Showroom Dealership  Cricket Management System
 Criminal Record Management  E-Boutique
 Exam & Result Management  Health Care
 Hospital Management System  Online Bookstore
 Online Complaint Portal  Online Event Booking
 Online MetroCard Recharge  Online Missing Person Info
 Online Shopping  Online Shopping System
 Our First Home  Railway Reservation System
 Reality Show Management  Tour & Travel Management
 Smart City Traveller  Weather ForeCasting
Many more FREE Software Engineering Projects are available at

Please Share these SE projects with your Friends as well

Online Event Booking System - TutorialsDuniya

Uploaded by

Copyright:

Available Formats

Online Event Booking System - TutorialsDuniya

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Event Booking System - TutorialsDuniya

Uploaded by

Copyright:

Available Formats

TUTORIALSDUNIYA.

Online Event Booking

Download FREE Software Engineering Projects for any

If you find any error or mistake in this Software Engineering

Please Share these SE Projects with your Friends

LINE EVENTS TICKET BOOKING SYSTEM

Download FREE Software Engineering Projects from TutorialsDuniya.com

Jatin Tiwari 12345

Download FREE Software Engineering Projects from TutorialsDuniya.com

 Data Flow Diagram

Download FREE Software Engineering Projects from TutorialsDuniya.com

It embodies the work done by them during semester IV of their course

Download FREE Software Engineering Projects from TutorialsDuniya.com

We are also thankful to TutorialsDuniya and TutorialsDuniya for their guidance

Download FREE Software Engineering Projects from TutorialsDuniya.com

Download FREE Software Engineering Projects from TutorialsDuniya.com

Waterfall process model is used in our project AmuseIT.

1. Software Requirements Analysis

Design must be translated into a machine readable form which is done by

statements have been tested, and on the functional externals, that is

produce actual results.

Download FREE Software Engineering Projects from TutorialsDuniya.com

reapplies each of the preceding phases to an existing program rather than a

Waterfall model is used because of the following reasons:

• It's relatively simple and easier to understand approach as compared to

Download FREE Software Engineering Projects from TutorialsDuniya.com

 Quick query processing.

 Reliable and efficient.

 Quick access to appropriate candidate.

The features of this product are as follows:

 Prevention against unauthorized access

 Prevention against spamming.

Download FREE Software Engineering Projects from TutorialsDuniya.com

Assumptions and Dependencies:

 Admin is created in the system already.

data entered by him/her will be valid.

Download FREE Software Engineering Projects from TutorialsDuniya.com

 No data loss in case of handling of the system by the administrators

include events’ details database, customers’ details database, and

organizers’ details database.

previous and current booking details.

and previous and current listed events’ details.

Download FREE Software Engineering Projects from TutorialsDuniya.com

generate tickets. After successful transaction, customers’ details

booking tickets, adding events and making payments.

address, event details, venue and numeric data including number of

system will read back any of the previous data.

Download FREE Software Engineering Projects from TutorialsDuniya.com

Download FREE Software Engineering Projects PDF for any

 3 Level Authentication  Airline Reservation System

Many more FREE Software Engineering Projects are available at

Please Share these SE projects with your Friends as well

Risk Management and Analysis

Download FREE Software Engineering Projects from TutorialsDuniya.com

3. Requirement Analysis Week 5

Creating Data Flow diagram Week 7

Data Design Week 9

Download FREE Software Engineering Projects from TutorialsDuniya.com

Download FREE Software Engineering Projects from TutorialsDuniya.com

Function Points Analysis

External Interface (25)+ (07)+