Movie Ticket Booking System

Introduction of the project Online Movie Ticket Booking System: This project is aimed at developing a ticket reservation system for Cinema Halls. The Ticket Reservation System is an Internet based application that can be accesses throughout the Net and can be accessed by anyone who has a net connection. This application will automate the reservation of tickets and Enquiries about availability of the tickets. This application includes email confirmation for the tickets. This is one of the important features of our system. By examining the existing system on the internet, we found that there is no such function available at this moment, so we try to include it in our system. To protect the benefit of the cinema, we will not give the money back to the customer, instead the customer has to visit cinema hall for further process. So, the customer can get the money from the cinema hall. Hence both the customer and the cinema can sort out further matter

Functional components of the project: Following is a list of functionalities of the system. More functionality that you find appropriate can be added to this list. And, in places where the description of functionality is not adequate, you can make appropriate assumptions and proceed. The Cinema hall has a web site and any user of internet can access this. The cinema hall is a multiplex which has 2 or more screens. Each screen has 3 different types of seats/classes viz Platinum, Gold & Silver depending on the rate of the class/seat. Only 100% of the seats are available for online reservation. 1. A person should be able to  Choose city where he/she want to see the Movie.  Choose the film which he/she wish to book tickets.  Query the films on show for one weeks (Only one weeks advance reservation is available) should be there. 

Able to choose the seats which are available for a certain class.



Can select seats from different classes as well for same show and



screen also. Give details about the credit card or debit card through which he is



doing payment. Able collect tickets at the counter presenting the unique id send to

him/her through email. 2. A mail should be send to the concerned person about the confirmation of the ticket to the specified email address. 3. The system should automatically show the fare for the corresponding shows and amount of money needs to be pay for selected seats. 2. Project Overview and Summary 2.1 Purpose of Project: The main purpose of our 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 needs not to do 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 The goals of our system are: 1. To provide a anytime anyplace service for the customer 2. To promote the film on the internet 3. To increase the profit 4. To obtain statistic information from the booking record

2.2 Scope of Project : 2.2.1

General Requirements (functional):

1. The web page (e.g. the time table page) will be generated automatically according to the data in database. 2. A way in which the cinema hall admin (staff) can login to the system to perform different operation. 3. A way in which the customer can modify its own data(booked seats before payment). 4. 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. 5. A way in which the customer can check the ticket record (seat numbers)selected by him/her at the time of payment. 6. A way in which the staff can use the system to add data(e.g. film description) to the database. 7. The system can verify the data before transaction. 8. The system can generate the time table automatically as the time table is set by the staff.(operating mode for the staff to insert data). 9. The system can generate some statistic information according booking and ticket selling record for the cinema hall per Movie based. 2.2.2 Interface Enhancements:

Our web-based system needs about more than 30 interfaces to handle all the functions. 

Staff: One of the main purpose of our system is to reduce the number of staff in the ticket box. So, most of the job is done by the system automatically. Staff only need to insert new film data and due with the refund



part. Customer: To make the system more user-friendly, customer need not to enter lots of data. An order will be commit step by step with guideline (request about 7 steps for an order).

2.3 Overview of Project :

Our Ticket Reservation for Cinema Halls is a web-based system. The customers can buy ticket online and cancel the seat at a suitable time (2 days before the show to 1hour before the show)by visiting the cinema hall. To enhance the refund function, all the customers have to present the unique id provided at the time of booking seats online. Staff can use the system to 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, staff can check the statistic information from the system.

SYSTEM ANALYSIS INTRODUCTION TO SYSTEM ANALYSIS System analysis is a process of gathering and interpreting facts, diagnosing problems and the information to recommend improvements on the system. It is a problem solving activity that requires intensive communication between the system users and system developers. System analysis or study is an important phase of any system development process. The system is studied to the minutest detail and analyzed. The system analyst plays the role of the interrogator and dwells deep into the working of the present system. The system is viewed as a whole and the input to the system are identified. The outputs from the organizations are traced to the various processes. System analysis is concerned with becoming aware of the problem,

identifying

the

relevant

and

decisional

variables,

analyzing

and

synthesizing the various factors and determining an optimal or at least a satisfactory solution or program of action. A detailed study of the process must be made by various techniques like interviews, questionnaires etc. The data collected by these sources must be scrutinized to arrive to a conclusion. The conclusion is an understanding of how the system functions. This system is called the existing system. Now the existing system is subjected to close study and problem areas are identified. The designer now functions as a problem solver and tries to sort out the difficulties that the enterprise faces. The solutions are given as proposals. The proposal is then weighed with the existing system analytically and the best one is selected. The proposal is presented to the user for an endorsement by the user. The proposal is reviewed on user request and suitable changes are made. This is loop that ends as soon as the user is satisfied with proposal. Preliminary study is the process of gathering and interpreting facts, using the information for further studies on the system. Preliminary study is problem solving activity that requires intensive communication between the system users and system developers. It does various feasibility studies. In these studies a rough figure of the system activities can be obtained, from which the decision about the strategies to be followed for effective system study and analysis can be taken.

Existing System In the existing system the exams are done only manually but in proposed system we have to computerize the exams using this application.

     

Lack of security of data. More man power. Time consuming. Consumes large volume of pare work. Needs manual calculations. No direct role for the higher officials

Proposed System The aim of proposed system is to develop a system of improved facilities. The proposed system can overcome all the limitations of the existing system. The system provides proper security and reduces the manual work.

        

Security of data. Ensure data accuracy’s. Proper control of the higher officials. Minimize manual data entry. Minimum time needed for the various processing. Greater efficiency. Better service. User friendliness and interactive. Minimum time required.

FEASIBILITY STUDY Feasibility study is made to see if the project on completion will serve the purpose of the organization for the amount of work, effort and the time that spend on it. Feasibility study lets the developer foresee the future of the project and the usefulness. A feasibility study of a system proposal is according to its workability, which is the impact on the organization, ability to meet their user needs and effective use of resources. Thus when a new application is proposed it normally goes through a feasibility study .The document provide the feasibility of the project that is being designed and lists various areas that were considered very carefully during the feasibility study of this project such as Technical, Economic and Operational feasibilities. The following are its features: TECHNICAL FEASIBILITY

The system must be evaluated from the technical point of view first. The assessment of this feasibility must be based on an outline design of the system requirement in the terms of input, output, programs and procedures. Having identified an outline system, the investigation must go on to suggest the type of equipment, required method developing the system, of running the system once it has been designed. Technical raised during the investigation are:

  The

Does the existing technology sufficient for the suggested one? Can the system expand if developed? project

should

be

developed

such

that

the

necessary

functions

and

performance are achieved within the constraints. The project is developed within latest technology. Through the technology may become obsolete after some period of time, due to the fact that never version of same software supports older versions, the system may still be used. So there are minimal constraints involved with this project. The system has been developed using JAVA the project is technically feasible for development.

ECONOMIC FEASIBILITY The developing system must be justified by cost and benefit. Criteria to ensure that effort is concentrated on project, which will give best, return at the earliest. One of the factors, which affect the development of a new system, is the cost it would require. The following are some of the important financial questions asked during preliminary investigation:

  

The costs conduct a full system investigation. The cost of the hardware and software. The benefits in the form of reduced costs or fewer costly errors.

Since the system is developed as part of project work, there is no manual cost to spend for the proposed system. Also all the resources are already available, it give an indication of the system is economically possible for development.

2.1 PRODUCT PERSPECTIVE Web traffic can be analyzed by viewing the traffic statistics found in the web server log file, an automatically-generated list of all the pages served. A hit is generated when any file is served. The page itself is considered a file, but images are also files, thus a page with 5 images could generate 6 hits (the 5 images and the page itself). A page view is generated when a visitor requests any page within the web site – a visitor will always generate at least one page view (the main page) but could generate many more.. Web Traffic Analyzer is aimed towards the vendors who want to reach out to the maximum cross-section of customer and common people who can be potential customer. This project envisages bridging the gap between the seller, the retailer and the customer. Web Traffic Analyzer should be user-friendly, ‘quick to learn’ and reliable software for the above purpose. OSM is intended to be a stand-alone product and should not depend on the availability of other software. It should run on both UNIX and Windows based platform.

2.2 PRODUCT FUNCTIONS Web traffic is the amount of data sent and received by visitors to a web site. It is a large portion of Internet traffic. This is determined by the number of visitors and the number of pages they visit. Sites monitor the incoming and outgoing traffic to see which parts or pages of their site are popular and if there are any apparent trends, such as one specific page being viewed mostly by people in a particular country. There are many ways to monitor this traffic and the gathered data is used to help structure sites, highlight security problems or indicate a potential lack of bandwidth — not all web traffic is welcome. Some companies offer advertising schemes that, in return for increased web traffic (visitors), pay for screen space on the site.

Sites also often aim to increase their web traffic through inclusion on

search engines and through Search engine optimization.

2.3 USER CHARACTERISTICS

We have 2 levels of users 

User module: This is a normal level of user who will be very few number of



functionality for website Administration module: This user is an admin type who has full rights on the system.

2.4 GENERAL CONSTRAINTS The amount of traffic seen by a web site is a measure of its popularity. By analysing the statistics of visitors it is possible to see shortcomings of the site and look to improve those areas. It is also possible to increase (or, in some cases decrease) the popularity of a site and the number of people that visit it. 2.5 ASSUMPTIONS AND DEPENDENCIES All the data entered will be correct and up to date. This software package is developed using HTML as front end which is supported by Aapache Server system. MySQL as the back end which is supported by Window 7.

3.1.1 User Interface

 

HTML has been used for developing the User Layout for the system JAVAScript has been used for creating all the validations and client side scripting functionality



CSS has been used for designing the web pages of the system

3.1.2 HARDWARE INTERFACE:

   

Processor

:

Intel Pentium IV or more

Ram

:

512 MB or more

Cache

:

1 MB

Hard Disk

:

10 GB recommended

3.1.3 Software Interface:

   

Client on Internet: Web Browser, Operating System (any) Web Server: Operating System (any), Apache 2 Database: MySQL Scripting Language: HTML, JAVAScript, JQuery

3.1.4 Communication Protocol Following protocols are required to be permitted on the server side



HTTP incoming request

3.2 Functional Requirements



The system runs of apache server so it is needed that server must have apache server version 2.0 available



We have used HTML for server side scripting so the current version of HTML must be available on the server

   

MySQL database has been used for storing the data of the website HTML has been used for creating the layout of the web application CSS has been used for creating the designing of the webpages JAVAScript scripting language has been implemented on the system for performing all of the Client Side Server Validation.

3.4. Classes and Objects of the Project

     

Login Class: Used for performing all the operations of the login functionality. Page Class: Class for managing all the operations of the page. Traffic Class: Class for managing the traffic of the website IP Class: It has been used for storing all the IPs which hits the website Users Class: Class for managing all the user operations Permission Class: This class has been used for managing all the permissions level opeations.

3.5. Non-Functional Requirements



Performance: System should be able handle multiple users at a time using any of the web browsers.



Reliability: Database updating should follow transaction processing to avoid data inconsistency.



Availability: The project will be deployed on a public shared server so it will be available all the time and will be accessible anywhere of the world using internet.



Security: We have implemented a lot of security mechanism to avoid to hack the system by outer world.



Maintainability: It is very easy to maintain the system. The system has been developed on HTML so anyone who has the knowledge of HTML, can easily maintain the system



Portability: Yes this system is portable and we can switch the servers very easily.



Browser Compatibility: The project being web based required compatibility with at least the popular web browsers. Microsoft Windows XP and above, Linux and Macintosh being the current popular operating system and Microsoft Internet Explorer, Mozilla Firefox, Opera, Safari and Google Chrome being

the

currently

popular

web

browser.

Software Requirement Specifications (SRS): The software, Site Explorer is designed for management of web sites from a remote location.

INTRODUCTION Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system. Scope: This Document plays a vital role in the development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.

DEVELOPERS RESPONSIBILITIES OVERVIEW: The developer is responsible for: 

Developing the system, which meets the SRS and solving all the requirements of the system?



Demonstrating the system and installing the system at client's location after the acceptance testing is successful.



Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.



Conducting any user training that might be needed for using the system.



Maintaining the system for a period of one year after installation.

5.1. FUNCTIONAL REQUIREMENTS

5.1.1.

OUTPUT DESIGN

Outputs

from

computer

systems

are

required

primarily

to

communicate the results of processing to users. They are also used to provides a permanent copy of the results for later consultation. The various types of outputs in general are: 

External Outputs, whose destination is outside the organization.



Internal Outputs whose destination is within organization and they are the



User’s main interface with the computer.



Operational outputs whose use is purely within the computer department.



Interface outputs, which involve the user in communicating directly.

5.1.2.

Output Definition

The outputs should be defined in terms of the following points: 

Type of the output



Content of the output



Format of the output



Location of the output



Frequency of the output



Volume of the output



Sequence of the output It is not always desirable to print or display data as it is held on a

computer. It should be decided as which form of the output is the most suitable. For Example 

Will decimal points need to be inserted



5.1.3.

Should leading zeros be suppress

Output Media: In the next stage it is to be decided that which medium is the most

appropriate for the output. The main considerations when deciding about the output media are: 

The suitability for the device to the particular application.



The need for a hard copy.



The response time required.



The location of the users



The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are: The outputs were needed to be generated as a hot copy and as well as queries to be viewed on the screen.

Keeping in view these outputs, the

format for the output is taken from the outputs, which are currently being obtained after manual processing.

The standard printer is to be used as

output media for hard copies.

5.1.4.

Input Design

Input design is a part of overall system design.

The main objective

during the input design is as given below: 

To produce a cost-effective method of input.



To achieve the highest possible level of accuracy.



To ensure that the input is acceptable and understood by the user.

5.1.5.

Input Stages:

The main input stages can be listed as below:



Data recording



Data transcription.



Data conversion



Data verification



Data control



Data transmission



Data validation



Data correction

5.1.6.

Input Types:

It is necessary to determine the various types of inputs.

Inputs can be

categorized as follows: 

External inputs, which are prime inputs for the system.



Internal inputs, which are user communications with the system.



Operational, which are computer department’s communications to the system?



Interactive, which are inputs entered during a dialogue.

5.1.7.

Input Media:

At this stage choice has to be made about the input media. conclude about the input media consideration has to be given to; 

Type of input



Flexibility of format



Speed



Accuracy



Verification methods



Rejection rates



Ease of correction

To



Storage and handling requirements



Security



Easy to use



Portability Keeping in view the above description of the input types and input

media, it can be said that most of the inputs are of the form of internal and interactive. As Input data is to be the directly keyed in by the user, the keyboard can be considered to be the most suitable input device

5.1.8.

Error Avoidance

At this stage care is to be taken to ensure that input data remains accurate form the stage at which it is recorded up to the stage in which the data is accepted by the system.

This can be achieved only by means of

careful control each time the data is handled.

5.1.9.

Error Detection

Even though every effort is make to avoid the occurrence of errors, still a small proportion of errors is always likely to occur, these types of errors can be discovered by using validations to check the input data.

5.1.10.

Data Validation Procedures are designed to detect errors in data at a lower level of

detail. Data validations have been included in the system in almost every area where there is a possibility for the user to commit errors. The system will not accept invalid data.

Whenever an invalid data is keyed in, the

system immediately prompts the user and the user has to again key in the

data and the system will accept the data only if the data is correct. Validations have been included where necessary. The system is designed to be a user friendly one. In other words the system has been designed to communicate effectively with the user.

The

system has been designed with popup menus.

5.1.11.

User Interface Design

It is essential to consult the system users and discuss their needs while designing the user interface:

5.1.12. 1.

User Interface Systems Can Be Broadly Classified As: User initiated interface the user is in charge, controlling the progress of the user/computer dialogue.

In the computer-initiated

interface, the computer selects the next stage in the interaction. 2.

Computer initiated interfaces In the computer initiated interfaces the computer guides the progress

of the user/computer dialogue.

Information is displayed and the user

response of the computer takes action or displays further information.

5.1.13.

User Initiated Interfaces

User initiated interfaces fall into tow approximate classes: 1. Command driven interfaces: In this type of interface the user inputs commands or queries which are interpreted by the computer. 2. Forms oriented interface: The user calls up an image of the form to his/her screen and fills in the form.

The forms oriented interface is

chosen because it is the best choice.

5.1.14.

Computer-Initiated Interfaces

The following computer – initiated interfaces were used: 1. The menu system for the user is presented with a list of alternatives and the user chooses one; of alternatives. 2. Questions – answer type dialog system where the computer asks question and takes action based on the basis of the users reply. Right from the start the system is going to be menu driven, the opening menu displays the available options.

Choosing one option gives

another popup menu with more options. In this way every option leads the users to data entry form where the user can key in the data.

5.1.15.

Error Message Design: The design of error messages is an important part of the user interface

design. As user is bound to commit some errors or other while designing a system the system should be designed to be helpful by providing the user with information regarding the error he/she has committed. This application must be able to produce output at different modules for different inputs.

5.2. PERFORMANCE REQUIREMENTS Performance is measured in terms of the output provided by the application. Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment.

It

rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system.

This is because the requirements have to be known during the

initial stages so that the system can be designed according to those requirements.

It is very difficult to change the system once it has been

designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use. The requirement specification for any system can be broadly stated as given below: 

The system should be able to interface with the existing system



The system should be accurate



The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.

Security Testing of the Project Testing is vital for the success of any software. no system design is ever perfect. Testing is also carried in two phases. first phase is during the software engineering that is during the module creation. second phase is after the completion of software. this is system testing which verifies that the whole set of programs hanged together. White Box Testing: In this technique, the close examination of the logical parts through the software are tested by cases that exercise species sets of conditions or loops. all logical parts of the software checked once. errors that can be corrected using this technique are typographical errors, logical expressions which should be executed once may be getting executed more than once and error resulting by using wrong controls and loops. When the box testing tests all the independent part within a module a logical decisions on their true and the false side are exercised , all loops and bounds within their operational bounds were exercised and internal data structure to ensure their validity were exercised once. Black Box Testing: This method enables the software engineer to device sets of input techniques that fully exercise all functional requirements for a program. black box testing tests the input, the output and the external data. it checks whether the input data is correct and whether we are getting the desired output. Alpha Testing: Acceptance testing is also sometimes called alpha testing. Be spoke systems are developed for a single customer. The alpha testing proceeds until the system developer and the customer agree that the provided system is an acceptable implementation of the system requirements.

Beta Testing: On the other hand, when a system isto be marked as a software product, another process called beta testing is often conducted. During beta testing, a system is delivered among a number of potential users who agree to use it. The customers then report problems to the developers. This provides the product for real use and detects errors which may not have been anticipated by the system developers. Unit Testing: Each module is considered independently. it focuses on each unit of software as implemented in the source code. it is white box testing. Integration Testing: Integration testing aims at constructing the program structure while at the same constructing tests to uncover errors associated with interfacing the modules. modules are integrated by using the top down approach. Validation Testing: Validation testing was performed to ensure that all the functional and performance requirements are met. System Testing: It is executing programs to check logical changes made in it with intention of finding errors. a system is tested for online response, volume of transaction, recovery from failure etc. System testing is done to ensure that the system satisfies all the user requirements.

Implementation and Software Specification Testings Detailed Design of Implementation This phase of the systems development life cycle refines hardware and software specifications, establishes programming plans, trains users and implements extensive testing procedures, to evaluate design and operating specifications and/or provide the basis for further modification. Technical Design This activity builds upon specifications produced during new system design, adding detailed technical specifications and documentation. Test Specifications and Planning This activity prepares detailed test specifications for individual modules and programs, job streams, subsystems, and for the system as a whole. Programming and Testing This activity encompasses actual development, writing, and testing of program units or modules. User Training This activity encompasses writing user procedure manuals, preparation of user training materials, conducting training programs, and testing procedures. Acceptance Test A final procedural review to demonstrate a system and secure user approval before a system becomes operational.

Installation Phase In this phase the new Computerized system is installed, the conversion to new procedures is fully implemented, and the potential of the new system is explored. System Installation The process of starting the actual use of a system and training user personnel in its operation. Review Phase This phase evaluates the successes and failures during a systems development project, and to measure the results of a new Computerized Transystem in terms of benefits and savings projected at the start of the project. Development Recap A review of a project immediately after completion to find successes and potential problems in future work. Post-Implementation Review A review, conducted after a new system has been in operation for some time, to evaluate actual system performance against original expectations and projections for cost-benefit improvements. Also identifies maintenance projects to enhance or improve the system. THE STEPS IN THE SOFTWARE TESTING The steps involved during Unit testing are as follows: a.

Preparation of the test cases.

b.

Preparation of the possible test data with all the validation checks.

c.

Complete code review of the module.

d.

Actual testing done manually.

e.

Modifications done for the errors found during testing.

f.

Prepared the test result scripts.

The unit testing done included the testing of the following items: 1.

Functionality of the entire module/forms.

2.

Validations for user input.

3.

Checking of the Coding standards to be maintained during coding.

4.

Testing the module with all the possible test data.

5.

Testing of the functionality involving all type of calculations etc.

6.

Commenting standard in the source files.

After completing the Unit testing of all the modules, the whole system is integrated with all its dependencies in that module. While System Integration, We integrated the modules one by one and tested the system at each step. This helped in reduction of errors at the time of the system testing. The steps involved during System testing are as follows: 

Integration of all the modules/forms in the system.



Preparation of the test cases.



Preparation of the possible test data with all the validation checks.



Actual testing done manually.



Recording of all the reproduced errors.



Modifications done for the errors found during testing.



Prepared the test result scripts after rectification of the errors.

The System Testing done included the testing of the following items: 1.

Functionality of the entire system as a whole.

2.

User Interface of the system.

3.

Testing the dependent modules together with all the possible test data scripts.

4.

Verification and Validation testing.

5.

Testing the reports with all its functionality.

After the completion of system testing, the next following phase was the Acceptance Testing. Clients at their end did this and accepted the system with appreciation. Thus, we reached the final phase of the project delivery. There are other six tests, which fall under special category. They are described below: 

Peak Load Test: It determines whether the system will handle the volume of activities that occur when the system is at the peak of its processing demand. For example, test the system by activating all terminals at the same time.



Storage

Testing: It

determines

the

capacity

of

the

system

to

store

transaction data on a disk or in other files. 

Performance Time Testing: it determines the length of time system used by the system to process transaction data. This test is conducted prior to

implementation to determine how long it takes to get a response to an inquiry, make a backup copy of a file, or send a transmission and get a response. 

Recovery Testing: This testing determines the ability of user to recover data or re-start system after failure. For example, load backup copy of data and resume processing without data or integrity loss.



Procedure Testing: It determines the clarity of documentation on operation and uses of system by having users do exactly what manuals request. For example, powering down system at the end of week or responding to paper-out light on printer.



Human Factors Testing: It determines how users will use the system when processing data or preparing reports.

Software Requirements:

Name of component

Specification

Operating System Language Database Browser Web Server Software Development Kit Scripting Language Enable Database JDBC Driver

Windows 98, Windows XP, Windows7, Linux Java 2 Runtime Environment MySQL Server Any of Mozilla, Opera, Chrome etc Tomcat 7 Java JDK 1.7 or Above JSP (Java Server Pages) MySQL Jconnector

Hardware Requirements: Name of component Processor RAM Hard disk Monitor Keyboard

Specification Pentium III 630MHz 128 MB 20 GB 15” color monitor 122 keys

Software Engineering Paradigm applied: The waterfall model is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception, initiation, analysis,

design,

construction,

testing,

production/implementation

and

maintenance. The waterfall development model originates in the manufacturing and construction industries: highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Because no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development.

Project Category Relational Database Management System (RDBMS) : This is an RDBMS based project which is currently using MySQL for all the transaction statements. MySQL is an opensource RDBMS System. Brief Introduction about RDBSM : A relational database management system (RDBMS) is a database management system (DBMS) that is based on the relational model as invented by E. F. Codd, of IBM's San Jose Research Laboratory. Many popular databases currently in use are based on the relational database model. RDBMSs have become a predominant choice for the storage of information in new databases used for financial records, manufacturing and logistical information, personnel data, and much more since the 1980s. Relational databases have often replaced legacy hierarchical databases and network databases because they are easier to understand and use. However, relational databases have been challenged by object databases, which were introduced in an attempt to address the objectrelational impedance mismatch in relational database, and XML databases.

Implementation Methodology: Model View Controller or MVC as it is popularly called, is a software design pattern for developing web applications. A Model View Controller pattern is made up of the following three parts:   

Model - The lowest level of the pattern which is responsible for maintaining data. View - This is responsible for displaying all or a portion of the data to the user. Controller - Software Code that controls the interactions between the Model and View.

MVC is popular as it isolates the application logic from the user interface layer and supports separation of concerns. Here the Controller receives all requests for the application and then works with the Model to prepare any data needed by the View. The View then uses the data prepared by the Controller to generate a final presentable response. The MVC abstraction can be graphically represented as follows. MVC (Model View Controller Flow) Diagram

PROJECT

SCHEDULING

An

elementary

Gantt chart

or Timeline

chart for the

development

plan is

given

below.

The

plan explains the tasks versus the time (in weeks) they will take to complete. January

February

March

Requirement Gathering Analysis Design Coding Testing Implement W

W

W

W

W

W

W

W

W

W

W

1

2

3

4

1

2

3

4

1

2

3

Wi‘s are weeks of the months, for i =1, 2, 3, 4

W4

Identification of Need The old manual system was suffering from a series of drawbacks. Since whole of the system was to be maintained with hands the process of keeping, maintaining and retrieving the information was very tedious and lengthy. The records were never used to be in a systematic order. there used to be lots of difficulties in associating any particular transaction with a particular context. If any information was to be found it was required to go through the different registers, documents there would never exist anything like report generation. There would always be unnecessary consumption of time while entering records and retrieving records. One more problem was that it was very difficult to find errors while entering the records. Once the records were entered it was very difficult to update these records. In present, work done in the electricity board is performed manually which is a great headache for the department .The reason behind it is that there is lot of information to be maintained and have to be kept in mind while running the business .For this reason we have provided features Present system is partially automated (computerized), actually existing system is quite laborious as one has to enter same information at three different places. Following points should be well considered: 

Documents and reports that must be provided by the new system: there can also be few reports, which can help management in decision-making and cost controlling, but since these reports do not get required attention, such kind of reports and information were also identified and given required attention.



Details of the information needed for each document and report.



The required frequency and distribution for each document.



Probable sources of information for each document and report.



With the implementation of computerized system, the task of keeping records in an organized manner will be solved. The greatest of all is the retrieval

of information, which will be at the click of the mouse. So the proposed system helps in saving the time in different operations and making information flow easy giving valuable reports. DATA DICTIONARY: This is normally represented as the data about data. It is also termed as metadata some times which gives the data about the data stored in the database. It defines each data term encountered during the analysis and design of a new system. Data elements can describe files or the processes. Following are some major symbols used in the data dictionary 

= equivalent to



+ and



[] either/ or



() Optional entry

Following are some rules, which defines the construction of data dictionary entries: 1. Words should be defined to understand for what they need and not the variable need by which they may be described in the program . 2.

Each word must be unique. We cannot have two definition of the same client.

3.

Aliases or synonyms are allowed when two or more enters shows the same meaning. For example a vendor number may also be called as customer number.

4. A self-defining word should not be decomposed. It means that the reduction of any information in to subpart should be done only if it is really required that is it is not easy to understand directly. Data dictionary includes information such as the number of records in file, the frequency a process will run, security factor like pass word which user must enter to get excess to the information.

CONCLUSION The project was designed in such a way that future modifications can be done easily. The following conclusions can be deduced from the development of the project.   

Automation of the entire system improves the efficiency We can provides the communication between Customer and Cinema Hall. Can also create Registration for Customer so that Cinema Hall can contact

   

them about exiting offers. Can also make Customer to Post their View on Website. The System has adequate scope for modification in future if it is necessary. It is the best way to improve selling Tickets with less efforts. This is the best way for customer as well as Cinema Halls to Interact with each other without much efforts.

References and Bibliography: 

http://www.wampserver.com/en/



http://www.HTML.net/



http://www.tutorialspoint.com/mysql/



httpd.apache.org/docs/2.0/misc/tutorials.html



Complete Reference for java by Simon Robinson



Headfirst JSP & Servlet



Struts2 in Action



Learn programming in java by Lakhanpal Publishers