Title of the project Development of a feature rich, practical online Tickets reservation system for Cinema halls.

Abstract of the project This project is aimed at developing an online 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 any one 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. Keywords Generic Technology keywords Databases, Network and middleware, Programming Specific Technology keywords MS-SQL server, HTML, Active Server Pages UNIX, Shell, C, Oracle Project type keywords Analysis, Design, Implementation, Testing, User Interface 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 5 screens. Each screen has 3 different types of seats/classes. Only 50% of the seats are available for online reservation. 1. A person should be able to login to the system through the first page of the application change the password after logging into the system

Copyright 2004-2005 Infosys Technologies Limited

Should be able to create a new login for the accessing the reservation facility. Query the films on show for two weeks (Only two weeks advance reservation is available) should be there. No reservation before two days can be done. See his current reservations on different movies along with the details. Able to choose the seats which can are available for a certain class. Can select seats from different classes as well for same show and screen also. Give details about the details about the credit card details. Able to select the mode of transfer of tickets whether through the courier or collection at the counter (as per that fare will be charged).

2. A mail should be send to the concerned person about the confirmation of the ticket to the specified email address. 3. The login Id and password should be sent to the mentioned email address if a new account is created. 4. A calendar should be there which helps the person to select dates. It should also show the public and nation holidays. 5. The system should automatically show the fare for the corresponding shows and amount of money needs to be pay for selected seats. Steps to start-off the project There are couples of alternatives to implement such a system. A. Microsoft platform: The system is developed using Active Server Pages as the Front end and SQL Server as the back end. B. Unix-based platform: HTML or even Shell scripting, C programming, any Relational database (e.g. Postgress or Oracle or even flat files), and tools in UNIX The following steps will be helpful to start off the project. 1. Study and be comfortable with technologies such as Copyright 2004-2005 Infosys Technologies Limited

a. Active Server Pages/HTML and SQL server. b. UNIX commands, Shell programming, C Programming, Tools like AWK etc. Some links to these technologies are given in the Guidelines and References Section of this document 2. Decide on a reservation policy and other related aspects like how many screens that multiplex has and what is the fare structure of different types of tickets. Then the number of daily show and timings. 3. Make a database of people whosoever login. Decide on the various details of the people that would be stored in the database (like name, age group, address, location, system-login, password in cryptic form, etc). 4. Since the real-time project needs to be tested in real-time, you can take hours as days for testing the system. However, the display will still be in days only. 5. Create the front-page of the reservation system giving a brief description about the system and a login box. 6. Create the help-pages of the system in the form of Q&A. This will help you also when implementing the system. 7. Create other sub-systems like automatic notification, screens for various functions (like login,calendar,reservation etc) 8. The datas Encryption should be done as it deals with the credit cards and related things. Requirements Hardware requirements Number Description Alternatives (If available) 1 PC with 2 GB hard-disk Not-Applicable and 256 MB RAM 2 Software requirements Number Description 1 Windows 95/98/XP with MS-office 2 MS-SQL server 3 Linux 4 Oracle database system Alternatives (If available) Not Applicable MS-Access Not Applicable POSTgres

Copyright 2004-2005 Infosys Technologies Limited

Manpower requirements 2 to 3 students can complete this in 4 6 months if they work fulltime on it. Milestones and Timelines Number Milestone Name Milestone Description Timeline Remarks

Week no. from the start of the project Requirements Complete 2-3 Attempt should be made to Specification specification of the add some more relevant system (with functionality other than those appropriate that are listed in this assumptions) document. including the framing of reservation policy etc constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Technology Understanding of the 4-5 The presentation should be familiarization technology needed to from the point of view of implement the project. being able to apply it to the project, rather than from a theoretical perspective. Database A database should be 5-7 It is important to finalize on creation created. As per the the database at this stage rules taken for the itself so that development purpose of and testing can proceed with maintenance of the the actual database itself. records. High-level and Listing down all 7-9 The scenarios should map to Detailed possible scenarios the requirement specification Design (like reservation (i.e. for each requirement that application, is specified, a corresponding cancellation, search scenario should be there). automatic money crediting etc) and then

Copyright 2004-2005 Infosys Technologies Limited

Implementation of the front-end of the system

Integrating the front-end with the database

Integration Testing

Final Review

coming up with flowcharts or pseudocode to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options (application form, cancellation form etc). The front-end developed in the earlier milestone will now be able to update the database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). Issues found during the previous milestone are fixed and the system is ready for the final review.

10-12

During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

12-13

14-15

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)

16-18

Guidelines and References http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnasp/html/asptutorial.asp (ASP tutorial) http://www.functionx.com/sqlserver/ (SQL-server tutorial)

Copyright 2004-2005 Infosys Technologies Limited

http://heather.cs.ucdavis.edu/~matloff/UnixAndC/Unix/CShellII.html introduction)

(Shell

script

Copyright 2004-2005 Infosys Technologies Limited