MyShowA

Project ReportSubmitted in partial fulfillment of the requirement for the award of degree of

Bachelor of EngineeringIn

Computer Science & Engineering

Submitted toRAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA,

BHOPAL (M.P.)

Guided by Submitted By Prof. Nandkishore Sharma Shubham Deshmukh

0875CS131149

Head

Prof.Prashant Lakkhadwala

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING ACROPOLIS TECHNICAL CAMPUS,

INDORE (M.P.) 4520012015-2016

DeclarationI hereby declared that the work, which is being presented in the project entitled “MyShow” partial fulfillment of the requirement for the award of the degree of Bachelor of Engineering in Computer Science & Engineering, submitted in the department of Computer Science & Engineering at Acropolis Technical Campus, Indore is an authentic record of my own work carried under the supervision of “Prof.Nandkishore Sharma”. I have not submitted the matter embodied in this report for award of any other degree.

Shubham Deshmukh0875CS131149

Prof. Nandkishore Sharma

Supervisor

ii

Acropolis Technical Campus

Department of Computer Science & Engineering

CertificateThe project work entitled “MyShow” submitted by Shubham Deshmukh

(0875CS131149) is approved as partial fulfillment for the award of the degree of Bachelor of Engineering in Computer Science & Engineering by Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal

(M.P.).

Internal Examiner External Examiner

Name: Name:

Date: Date:

iii

Acknowledgement

I wish to express my sincere gratitude to Prof. Nandkishore Sharma, who has the attitude and substance of genius which has always been sincere and helpful in making me understanding the different system of legal project and convincingly conveyed a spirit of adventure in regards to make my minor project more adorable.

I would like to express my deepest thank to Project Co-ordinator Dr. Abhishek Singh Rathore, Prof. Sumit Jain, Prof Brajesh Chaturvedi who encouraged me to cope with the problems that I faced during this course of this project and I would also like to thank other faculties who supported and helped me during this project.

I sincerely thank to Head of DeparmentProf.Prashant Lakkadwala, for his continuous supportin completing the minor project.

This project cannot be completed without the effort and co-operation from Group members :Sheetal Ojha, Yash Vaid, Yashi Garhwal.

Last but not the least, I would like to thank my friends and family for the support and encouragement they have given me directly or indirectly during the course of this work.

Shubham Deshmukh0875CS131149

iv

Abstract

My Show is aimed to provide information of the movie in more usable way, according to which they can book the tickets in registered theatre by user. It proceeds through a sequence of well designed forms provided with validations to ensure consistency, reliability and most importantly correctness of information. Here, User is responsible for the registration of the User Account, The user can Change password, can view number of seats available and can book tickets. Whereas, Administrator is responsible for maintaining right information about the movies, seat availability, employee details and many more things.

The salient feature of MyShow is that website recommended best suitable theatre to the user, which is helpful for tourist or any outside people who don’t know about the current city. Another feature of the project is that is user can book ticket only by less clicks of options.

v

Table of ContentChapter 1: Introduction........................................................................................................1

1.1 Rationale....................................................................................................................11.2 Goal............................................................................................................................11.3 Objective....................................................................................................................21.4 Methodology..............................................................................................................21.5 Role............................................................................................................................21.6 Contribution of Project..............................................................................................2

1.6.1 Market Potential..................................................................................................21.6.2 Innovativeness....................................................................................................21.6.3 Usefulness...........................................................................................................2

1.7 Report Organization...................................................................................................2Chapter 2: Requirement Engineering..................................................................................3

2.1 Requirement Collection.............................................................................................32.1.1 <Collection Type 1>...........................................................................................32.1.2 <Collection Type N>..........................................................................................3

2.2 Requirements.............................................................................................................3Chapter 3: Analsis & Design...............................................................................................4

3.1 Use-case Diagrams....................................................................................................43.2 Activity Diagrams......................................................................................................53.3 Sequence Diagrams...................................................................................................63.4 Class Diagrams..........................................................................................................63.5 Data Design...............................................................................................................6

3.5.1 Schema Definitions.............................................................................................63.5.2 Integrity Constraints...........................................................................................6

3.6 System Architecture...................................................................................................6Chapter 4: Construction.......................................................................................................7

4.1 Implementation..........................................................................................................74.1.1 Implementation Details.......................................................................................7

4.2 Testing.......................................................................................................................74.2.1 White Box Testing..............................................................................................74.2.2 Black Box Testing..............................................................................................7

Conclusion & Future Works…………

Appendix A

vi

1IntroductionThis project is aimed to provide the customers facility to book tickets for cinema halls online, through which they can book tickets anytime, anywhere.MyShow is basically made for providing the 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 choice.Through this project we present a comprehensive solution for ticket booking in multiplexes. Theatre 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.Admin can use MyShow Project to insert and delete data such as movie description, movie schedule which will update the related webpage(webpage are dynamic page, changing according to the data in database) and admin can check the statistic information from the system.

1.1 Rationale To provide complete information of the movie and schedule to the customer,

according to which he can book the tickets. To provide an easy option for the customer who is willing to book tickets online

for a movie. To provide recommendation and suggestion for best theatre available in city. To provide better user interface as displaying movie in transition way, through

which user will see current movies detail very quickly which helps to reduce dicision of user.

1.2 GoalThe goal of the project is to put in place new solutions as per the end user expectations; so that the accuracy, speedup, digitalization of the system will be enhanced. To do this:

Provide anytime anyplace service for the customer. Provide effective solutions for easily availability of movie tickets. Provide simpler way to choose our seat and area for movie show To minimize the number of staff at the ticket box. To promote movies the movies on the web. Try to increase profit as much as possible

1

1.3 ObjectiveThrough this project we present a comprehensive solution for ticket booking inmultiplexes.This powerful web application is specifically designed for theater owners,to sell tickets online. Therefore, Themain objective of MyShow is develop an enhanced, automated, accurate, user-friendly and less maintained way of web application.

1.4 MethodologyThis project contains Three Modules :

1 Admin:

Admin can mange movies such as Add, Edit, Delete. Admin can manage movie schedule such as Add, Edit, Delete. Admin can mange show such as change in Show Name and Show Time.

2. Booking tickets:

After login, user can book ticket directly by following ways :o User can book ticket by selecting Movie.o User can book ticket by selecting Theatre.o User can book ticket by selecting Time

.3. Users:

User can Register. User can Login. User can Check Availability. User can Book Ticket User can follow MyShow on Social Networking.

1.5 Role :In this project, my group has been go through six phases :Information Gathering, Designing, Coding or Developing, Database Management, Testing and Documentation. where, I try to compelete Phases: Coding & Database Management.

________________________________________________________________________

1.6 Contribution of Project

1.6.1 Market PotentialThis project is aimed to provide the customers facility to book tickets for cinema halls online, through which they can book tickets anytime, anywhere. And provides a good facility for the user and for better development of town/city.

2

1.6.2 InnovativenessThrough this project we present a comprehensive solution for ticket booking in multiplexes. Theatre 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

1.6.3 UsefulnessMyShow is basically made for providing the 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 choice.

1.7 Report OrganizationThe subsequent chapters of the reports are:

Chapter Two : Requirements Engineering It is concerned with the requirement of the software product.It convey the expectations of users from the softwareproduct. It consists of the detail description of the problem definition, requirement gathering.The requirements can be obvious or hidden, known or unknown,expected or unexpected from client’s point of view.The goal of requirement engineering is to develop and maintain sophisticated anddescriptive ‘System Requirements Specification (SRS)’ document.

Chapter Three : Analysis and DesignIt is concerned with the Analysis and Design. It having all the respective diagrams and their architecture. It tries tospecify how to fulfill the requirements mentioned in SRS, whichmoves the concentration from problem domain to solution domain.Software design is a process to transform user requirements into some suitable form, which helps the programmer in software coding and implementation. Theserequirement specifications come in the shape of human readable andunderstandable documents, to which a computer has nothing to do.

Chapter Four: Construction This chapter includes implementation approaches, testing objectives and testing principles followed and we will study about programming methods and challenges in software implementation and try to build up our product using programing languages which will concurrently tested by some common approaches like white box testing or black box testing and try to build up more accurately as much as possible accordingly.

3

ConclusionThis chapter specifies the concluding thoughts along with project’s limitations and future enhancements possible in the project.

Appendix:This chapter specifies the results generated: Snapshots of the screen.

4

Chapter 2

Requirement EngineeringRequirement engineering is a process to gather the software requirement from client, analyse and document them is known as requirement engineering. The goal of requirement engineering is to develop and maintain sophisticated and descriptive ‘System Requirement Specification’ documents.

In real scenario, Requirement engineering process contain four steps :Feasibilty Study, Requirement Gathering, Software Requirement Specification, Software Requirement Validation.

Activities involved in requirement engineering depending on the type of system being developing and the specific practices of the organization involved.

1.8 Requirement Collection

1.8.1 Data reqirementsThe Data-requirements are given as follows:-

o USER MODULE

o ADMIN CONTROL

1.8.2 System Requirement Funtional Requirement covers the functionality of the product in detail.

• 1. The schedule of the movies will be generated via a query according to the data selected by the user.

• 2. A way in which users (both customer & admin) can login to the system to perform different operation.

• 3. A way in which the customer can commit order by “Point and Click” method.

• 4. The system can verify the data before transaction.

1.9 RequirementsBR 1:

BR N:

TR 1:

TR N:_______________________isme shayad kuch galti ho smjh nh aarha___________

5

Chapter 3Analysis and design3.1 Use-case Diagrams

Figure 3.1: Use-case Diagram of <<Myshow>>

6

3.2 Activity Diagrams

Figure 3.2: Activity Diagram of <<Myshow>>

7

3.3 Sequence DiagramsSequence diagram for Myshow

8

Sequence diagram for admin

9

Sequence diagram for user

10

3.4 Class Diagrams

LOGIN INFO

Username :textPassword :text+insert()+edit()-delete()

Payment_transiction

Ticket no.:textMovie date:dateAcc_no.: numBank_name:text+insert()-delete()

11

movie infoCurr_movie :textUpcom_movie:textScreen_no.:numShow time:numType_seat:text+insert()+edit()-delete()

Cancel booking

Movie_name:textShow time:numTicket no.:textMovie date:date

-delete()

booking transaction

Movie_name:textShow time:numScreen_no.:NumbTicket no.:textMovie date:date

+insert()+edit()-delete()

booking master

Movie_name:textScreen_no.:numShow time:numType_seat:textNo. of seat+insert()+edit()-delete()

3.5 Data Design

12

3.5.1 Schema DefinitionsTable 3.1: Schema for <<>>

3.5.2 Integrity Constraints________________________________________________________________________

3.6 System Architecture

13

Chapter 4

Construction4.1 ImplementationThe various system tools that have been used in developing both the front end, back end and other tools of the project are being discussed in this chapter.

4.1.1Implementation Details

Here Phased approach is followed for the implementation of the system. The phases include planning, requirement gathering, design, coding and testing phases. The objective is to completely finish each logical step in the development process before moving onto the next. We can go back to make modifications if necessary, progress should flow from one stage to the next.

4.1.1.1Software DetailsOperating System : Windows XP or Higher IDE : VisualStudio.NET 2005/2008 Front End : RubyOnRailsDatabase : PostgresDeployment server : Heruko(free)

4.1.1.2Hardware Details Minimum 1 GB RAM 256GB or above Hard Drive Intel Dual Core Processor or higher

4.2TestingTesting begins at the module level and works outward towards the integration of the entire computer based system. Different testing techniques are appropriate at different level of time. Testing & debugging are different activities, but debugging must be accommodated in any testing strategy. There are different model of testing. On the basis of testing methods. There are two types of testing.

Black-box testing.

White-box testing

4.2.1White Box Testing

Test Case: 1Table 4.2: Test Case for <<>>

14

Test Case: N

4.2.2Black Box TestingTest Case: N+1

Test Case: M

15

Conclusion & Future WorksConclusion:

In our project: with this cinema ticketing system; cinema companies can satisfy comfortable facilities to their customers. The relationship between cinema manager, employee, and customer satisfy a good communication to complete ticketing process. With this platform we developed, we are hoping to reduce time wasting, avoid misunderstandings, provide easy data flow, customer pleasure, and less hard work. We believe that we have accomplished our goals and satisfied with the code we developed.

Future Work:

We think that not a single project is ever considered as complete forever because our mind is always thinking something new and our necessities also are growing day by day. We always want something more than what we have. Our application also, if you see at the first glance than you find it to be complete but we want to make it still mature and fully automatic. Some of the expansions which we have thought of are:

We want to improve our home page , as it is the main things which attracts all users.

Payment facility for bank to user.

16

Appendix A

Home Page

List of theatres

17

Ticket booking

Ticket confirmation

18

Checking movie timings

Movie timings

19

Listing movies

20