Report

On Online Movie Ticket Booking

SUBMITTED BY Gurpreet Singh (90490306149) Roll No. 4327

Computer science and engineering Department LUDHIANA COLLEGE OF ENGINEERING. & TECHNOLOGY KATANIKALAN, INDIA.

Table of Contents

1. General introduction about the project.. .. 3 2. Feasibility study 4 3. Requirements analysis & specification.... 5 3.1. Requirements gathering 3.2. Requirement specification 3.2.1. SRS 4. Design 4.1. Database Design 4.2. Designing of modules 4.3. Designing of user interface 5. Coding and testing.. 5.1 Software testing 5.2 Testing levels 5.3 Objectives of testing 13

32

6. Maintenance 39

1. General introduction about the project

To solve actual problems in an industry setting, a software engineer or a team of engineers must incorporate a development strategy that encompass the process, methods, and tools layers. Our software is based on Waterfall Model. The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall). The waterfall development model has its origin in the manufacturing and construction industries; highly structured physical environments in which after-the-fact-changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adopted for software development. Project title is Online Movie Ticket Booking

2. Feasibility Study
Technical Feasibility: The minimum requirement to implement the system is Pentium-IV processor with 512 MB RAM, Any Operating System, Java Run Time Environment and must have an internet connection. Economical Feasibility: It is more commonly a cost-benefit analysis of the system. The ratio of one time cost or recurring cost should not exceed the benefits from the system. Cost of acquiring Machine, Software, Operational Setup, training cost. No Extra cost for set up of operating environment needed as the computer is already in use for other purposes. And the staff is well conversant and familiar with the computer technology. The system is User friendly and need minimum data entry from the end users, thus is easy to use. Operational Feasibility: This system software will reduce the work load and loss of information, saves time and would help to the system generalized rather than person dependent. It is convenient for the staff of cinema as well as for users.

3. Requirement analysis and specification

It includes the gathering of the requirements and their specifications to be generated. After the requirement gathering state, the SRS document is prepared in the next stage that is requirement specification. SRS document is a software requirement specification; its a kind of conclusion of the gathered requirements.

3.1 Requirement Gathering

Every cinema has many movies running in one week, whose timing may differ day by day. Costumers found it difficult to go to cinema to check the timing and check if the tickets are available. It is also easy and safe to maintain record of tickets online for the owners. Here one can watch the trailers, one can book tickets and get information about upcoming movies. Here are some requirements: Book tickets online Maintain the record of tickets. List of different movies, which are currently running. List of different movies, which are next changes. Trailers of all movies currently running. Location of cinema in city. .

3.2 Requirement Specification

In this phase, the requirements of the customer are organized into an specification or SRS i.e. Software Requirement Specification. SRS document of the above gathered requirements is as follow in section 3.2.1.

3.2.1 Software Requirement Specification

A. INTRODUCTION:
Online movie ticket booking is the one of very advanced features of the modern science or technology. It saves the time of people of modern world. 5

In the old times when the families or friends go to cinema to watch movies for entertainment, they wait for a long time to buy the tickets. With change in generation it was needed to be change with the change in generation. This project of online movie ticket booking is concerned with not only with online ticket booking but here is also information about the cinema, the details of currently running movies. Here one can also watch the trailers of current movies as well as upcoming movies. Here one can book tickets with credit card and how it works with sms.

PURPOSE OF THE PROJECT

The purpose of this project is to save the time of costumers as well as of management. It makes easy to enjoy your free time or makes a good entertainment with your family and friends. While using this way internet gives you the option to select the movie you want to watch, to buy tickets, to watch the trailers of current and upcoming movies. It provides the information about the remaining seats of a particular show, releasing date of new movies, location of cinema. The management has less work to do. The less the work lesser the employs needed to do that work. It makes the job done with lesser number of employs, which is economically beneficial for the cinema owner.

It keeps the record of tickets at online database, which keeps the record safe even if there any system crash happens. Administrator can access the ticket record anytime from anywhere.

SCOPE OF THE PROJECT

Scope of this project is very broad. Customers will have full enjoyment of their free time without wasting it in standing in long rows and then return home without watching a movie. One of the main features in online movie ticket booking is time saving for costumers and economic benefit to owner. Few of the scopes are listed as. This can be used in any cinema to manage their ticket record. Can be used any type of cinema i.e. may be by small or large cinemas, it does not matters. Both can use this software.

 This project is extended to an Intranet based application. Organizations that are spread across geographical locations with their offices are most benefitted by such a system. You can track and manage any cinema with such system.

Definitions / Acronyms
Acronym 1.JDK 2.OOA 3.OOD 4.GUI Definition Java Development Kit Object Oriented Analysis Object Oriented Design Graphical User Interface

REFERENCES
Software Requirements Engineering Process, Prem Lanman, FL,2002. Software Engineering, Rajib mall, 2003.

OVERVIEW OF DOCUMENT
This project is implemented in the java programming language. This srs document covers all the software requirements for this project.

B. OVERALL DESCRIPTION:
As years progressed, the approach of the management changed towards the human capital. Now Hierarchical Organization is part of every organization, and has its own identity and importance. In this scenario, the bigger organizations need to put lot of effort in the management of human Resources, as they are underlying capital asset to the organization. In doing so, along with times, the Organization Information changed from its basic operations to more strategic approach. Some of the features are: Finding ground level employee performance by the topmast manager. Maintenance of profile details of the employees, and retrievals as and when required. Overall & detailed view of the organization hierarchy, which is very much essential in making effective decisions. Judging the potentiality of the employees.

Maintenance of the data when the organization has many branches spread over wide geographical area. Accessing one branch information from another branch. Future planning issues based on the current HR information. Employees success planning. Vacancy situations and their priority /effect on the organizations performance. Employee motivational & conflict resolving issues.

SYSTEM ENVIRONMENT
This firstly I am going to discuss all the hardware and software requirements that are required to make this application possible. Hardware: RAM minimum 256 MB HARD DISK- 300 MB free hard disk space.

Software: Front End : Java Back End : MY-SQL JDK 1.6 Version(Java Development Kit tool) Operating System- Windows. FUNCTIONAL REQUIREMENTS 1. The web page (e.g. The time table page, the main page) will be generated automatically according to the data in database. A way in which the customer can create its own account(member registration). A way in which the users (both customer and staff) can login to the system to perform different operation. A way in which the customer can modify its own data. A way in which the customer can commit order by just clicking the seat (which is shown on the screen) and insert some card data.(some simple operation) A way in which the customer can cancel the order and get the refund. 8

2. 3.

4. 5.

6.

7.

A way in which the customer can check the ticket record according to the transaction number. A way in which the staff can use the system to add data(e.g. film description) to the database. The system can verify the data before transaction.

8.

9.

10. The system can generate the time table automatically(by just input the length of the film) or the time table is set by the staff.(2 operating mode for the staff to insert data). 11. The system can generate some statistic information according booking and ticket selling record. 12. Users can check film data by clicking on a certain film on main page(e.g. The cinema which will show this films). 13. Users can check a cinema data by clicking on a certain cinema on main page(e.g. which film is now showing)

NON-FUNCTIONAL REQUIREMENTS
The non functional requirements deal with the characteristics of a system that cannot be expressed as functions. Non functional requirements address aspects concerning maintainability, portability, usability, maximum number of the concurrent users, timing and throughput. Non functional requirements under this project are listed as below: Graphical User Interface (GUI) Standards - The interface should be very friendly. The system should operate in a GUI environment. The following should be provided but not at all conclusive: 1. Standard tabs 2. Full mouse capability 3. Vertical and horizontal scrolling 4. Drop-down selection windows (where possible). 5. Response messages 6. Informative prompts 7. Warning messages 8. Help button.. Platform- Both Windows and Linux versions need to be developed.

C. BEHAVIOURAL DESCRIPTION:
SECURITY: All the users of the system shall not be able to perform the addition of new departments or the new sections. But user can do the employee addition.

10

4. Design:
This phase is a move from user requirement to defining how system will work thus it is quite technical it specifies

Exactly each input/output, data audit and control requirement will be handled. Acceptance test plan/ scheduled. Facilities, equipments and personal required. Manual procedures required to operate system.

We choose the object oriented approach to make this software. Other important concepts under this phase are listed as. o Design database. o Design of the user interface / input screen.

11

USE CASE DIAGRAMS :

1. Overview For the following Diagram, we will show overall view of our system. We just show the basic function of our system without any detail.

12

2. Use case diagram for buying ticket In the following diagram, a sequence of buying ticket will be shown. Some alternative choice are also shown in the diagram.

13

3. Class diagram for buying ticket In the following diagram, we will show relation between classes when buying ticket. The attributes and the functions are also shown.

14

4. Sequence diagram for buying ticket In the following diagram, a sequence of buying ticket are demonstrated . There is some more things I need to state, this is just one of the sequences of buying ticket. There are some more alternative sequence for buying ticket. For example, we can choice cinema before choice movie. But the overall structures of all buying ticket sequence are similar, so, others sequence will not be shown.

15

16

 Database Design:
The most popular relational database model is used for permanent storage of data. It is two dimensional and easy to handle. Thus logical and physical changes are easy to handle.

Designing of modules :

Hierarchical Organization Information software tool has been designed keeping in view of all the technical aspects, to suit the proposed requirements using the current technology.

Combining these powerful, state of art, burning technologies with tightly integrated database, the Hierarchical Organization Information software will meet the proposed solution of providing controlled and effective Management of the employees. The Hierarchical Organization Information software has been modularized into following modules.

A. Employee Creation B. Employee hierarchy C. Department entry/Department interdependency D. Live status E. Employee list enumeration F. Process details G. Job rotation H. Position Weight-age based on Department wise, section wise I. Vacancies maintenance & process details

Module Description:

A) Employee Creation In the Hierarchical Organization Information System each employee is created with their corresponding department, designation and section details.

17

B) Employee hierarchy In this system Administration department is the Root Department under which different departments exist. So the Employment hierarchy will start with root department head like chairman and subsequently the department employees with dept head and section employees with their section employees and for sub departments in the departments can be identified.

C) Department entry/department hierarchy In this module, Master Data for the departments can be created employees refer this data .Sub departments Can be identified .Some of The departments will have Different Sections. Each Department having Department heads ,so department employees should reported to the department head he may be subordinate to his superior Department he shall report to him. Some of departments having sections so section employees shall be reported to the section in charge he shall report to the department head. From this Departments, sub-departments the Department hierarchy shall be created.

D) Live status Live status gives accurate information about which Employee Will work in which section his superior employees or his subordinates can be identified along with their corresponding departments so that the employee info can be managed easily. Their performance can be monitored and if need they can be deputed to other department as and when required this can be effectively managed.

E) Employee list enumeration The employee details already in the database so the details can be retrieved as and when required by taking the selective criteria from the HR manager.

F) Process details This following process will be done to get the desired results. Employee hierarchy can be created using Employers and their superiors information. Department Hierarchy can be created using the departmental interdependencies. 18

Vacancy list in various departments can be identified and prioritized by calculating the position weight ages. Employees can be transferred from one department to another based on different criteria provided by the HR manager. Employee retention can be processed depending their performance.

G) Job Rotation Job rotation process will be invoked when the employee experiences monotony in his work / duty. These will result in poor performance, some times leads to major errors in the field of operation. This can be overcome by job rotation process. In this the employee will be moved to other department of interest, so that the employee will work with renovated vigor and vitality.

In some cases, to fill up the emergency vacancies, job rotation process will be executed to avoid unforeseen delays. In any case along with the candidate / employee his credentials and other associates will be passed to the destination department.

H ) Position Weight-age Position weight-age will be calculated based on Departments weight-age, section weight-age and even the designation weight-age. Each position in the organization will have certain importance in the functionality of the overall organization. The weight-age of the each position will be calculated by using the actual position in the organization and as well as the position in the authority flow.

I) Vacancies details and process details Vacancies raised in various departments can maintained by filling the new employees or by shifting/additional charges to existing employees.

19

Data Flow diagrams

Basic context diagram.

Administrator Add Employee View Employee Edit employee Report building Trace Employee

Employee Information Manager Access own profile

Report builder View employee Access own profile

Line Manager

Simple Employee

20

Level 1 diagram.

Successfully login Domain login Checks domain name Result masters Establishment Table

Administrator

result

Domain Login masters result Master table operation Employee list Master tables

result Employee list result Employee Informaiton Manager Employee details

Employee list Line Manager Result

21

Level 2 (Adding employee)

Add employee Result Verify employee Administrator Result

Add employee Result Establishment details Employment details Result

Employee Information Manager Insert employee details Result Employee

Employment details Employee details Result Employee details

22

Level 2 diagram (For tracing employee and reporting utility):

Trace Employee Result Establishment Table Report Trace Employee Result Result Administrator Report Report Result Employment Details Utilities Result Employee Details

23

Flow chart:

Start

Contact to administrator

No

Checks domain name of user

yes Select module

yes

Admin

EIM

Change module

No

END

24

 Design of User Interface Screen:

Input screen are user friendly and care is taken that minimum amount of data entry is done.

The master information once entered and stored is displayed in a combo box or as a list for further input thus there are no chances of error in data entry as the use only has to select the information from the provided list.

Key data is displayed from the master tables where ever needed if any redundancy exists then the data is not reentered it is fetch form appropriate tables. e.g. while entering master information it is verified that data already exist for that entity only then further data is accepted. Thus duplication and redundancy is properly handled. Link for saving is enabled only after proper verification and validation of data is done.

And basic information is first validated and then further data entry is allowed thus it saves unnecessary data typing. Proper messages are provided where ever needed. Thus care is taken for control of data and correctness of data with minimum typing efforts.

Proper conversions of data type and formats are done.

25

26