Online Movie Ticket Booking System: A Case Study, Exercises of Computer Vision

Download Online Movie Ticket Booking System: A Case Study and more Exercises Computer Vision in PDF only on Docsity!

CASE STUDY

ON

“ONLINE MOVIE TICKET BOOKING SYSTEM”

SUBMITTED BY:

VIKRAM YADAV(59)

RUSHIKESH PATHAK(38)

MANTHAN PATHAK(37)

GROUP NAME:

NOCTURNAL NAVIGATORS

INDEX  Project introduction.  Objective.  Problem statement.  Problem definition.  System Analysis.  Identification of Need.  System Analysis phase.  Preliminary Evaluation.  Summary of finding recommendation.  Feasibility Consideration.  Project Planning.  Project Scheduling.  SRS.  Software Process Model.  Project Module.  Data Structure.  Testing.  Bibliography.  Future scope and further enhancement of the project.

OBJECTIVE OF THE PROJECT

 The main purpose of our online ticket booking system is to provide another way for the customer to buy cinema ticket. It is an automatic system.  After inserting the data to database, staff need not todue with the order receive through the system. In fact, there is similar system on the internet, but there is no refund method found in the existing system.  This system is basically aimed to provide the customer the complete information of the movie, according to which the customer can book the tickets and the refund facility provides more flexibility to the system.  The goals of our system are:

1 To provide a anytime anyplace service for the customer 2 To minimize the number of staff at the ticket box 3 To promote the film on the internet 4 To increase the profit To obtain statistic information from the booking record

Identification of Need

 If system, which is going to be developed, is complex in nature the goals of the entire system could not be easily comprehended. Hence the need for a more rigorous system analysis phase arose.

Generate Request

Build Models

Developer Managers Problem Statement

User Interviews

Experience

User

Functional Model

Object Model

Dom Domain Knowledge

Preliminary Evolution

 The preliminary investigation starts as soon as someone either a user or a member of a particular department recognizes a problem or initiates a request, to modify the current computerized system, or to computerize the current manual system.  An important outcome of the preliminary investigation is determining whether the system is feasible or not.

Project Scheduling

GANTT CHART

 Gantt chart is also known as Time Line Charts. A Gantt chart can be developed for the entire project or a separate chart can be developed for each function.

 A tabular form is maintained where rows indicate the tasks with milestones and columns indicate duration (weeks/months).

 The horizontal bars that spans across columns indicate duration of the task. Task January Februar y

March April May

Requirement specification and Analysis Design Test Cases Coding with unit testing Testing Documentation

Non Functional Requirements :

 It consists of following parameters :-

Reliability : The system will consistently perform its intended

function. For eg. The important information must be validated.

Efficiency : Unnecessary data will not be transmitted on the network

and database server will be properly connected.

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.

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 the modules.

Used Tools AndPlateform

Software Specification:

Front-end Tool: - Microsoft ASP.NET 2.  User friendly  Low Cost Solution  GUI feature  Better designing aspects Back-end Tool: - Microsoft SQL Server 2005  Security  Portability  Quality

Platform

Windows platform like: 2000 professional, XP & Vista

Hardware Specification:

 Intel Pentium and Celeron class processor  Processor Speed – 1.2 GHz or above  RAM - 512 MB  HDD - 40 GB  Monitor-14”SVGA  Printer – Laser Printer

The Prototyping Model

Online booking System for movie is based on prototype model.

Requireme nt

Design Implementation

Evaluati on

Improve the Specification Design Implem ent Testing

Operation and Maintenance

Project Modules

Login Module

This module is for both type of users(customers and admin).In this module according to the type of user(customer or admin) the further links and operations will be provided.

Customer Module

 As soon as a visitor registers himself as a customer,the customer can now book the movie tickets and pay for them online.

Hall Module

 This module deals with the information about the hall. There are several multiplexes and each of them has 4 halls and according to the vacancy of seats in the hall the booking takes place.

Booking Module

 In this module movie ticket is booked for a customer. This module contains all the information related to booking. As soon as the customer request is complete, all the booking details are displayed to him.

Payment Module

 This is the most important module because it deals with the payment of the tickets booked in the booking module. The customer can pay for the tickets before the show by cash

= Source or destination of data

= Data flow

= Process that transforms data

Or = Data store

0-Level DFD

Admin Staff

Users

Online Movie Ticketing

View

Response

View

View Response

Response

FLOW CHART:

START Input details of all users

rating If user is

visitor

booking

customer

staff Input movie details^ Process detail

Input paymen t detail If payment mode is

cash Cash detail

Payment info

paypal

Credit card info

Credit card

Booking completed

STOP

Admin

View View

View

Physical Design

DATABASE DESIGN

 A database may be thought of as a set of related files. Related files mean that record of one file may be associated with the records in another file.  The conventional file based systems emphasized that the application and files were built around it. The database environment emphasizes the data independently of the applications that use the data.  The applications are allowed to evolve around a database design such that it can adapt to changing needs. Data becomes the central resource in the database environment.  Information systems are built around this central resource to give flexible access to data.