30-04-2011, 10:17 AM
Submitted By:
Kabir Adatia
Paras Pugalia
Aanchal Agarwal
Aayushi Jain
Avneet Singh Kochar
Ridhi Bubna
Ashwani Poddar
[attachment=13083]
INTRODUCTION
Goals and Objectives
The main purpose of our online ticket booking system is to provide an alternate and convenient way for a customer to buy cinema tickets. It is an automatic system. After the data has been fed into the database, the staff does not need to do anything with the order once it is received 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 minimize the number of staff at the ticket box
3 To promote the film on the internet
4 To increase the profit
5 To obtain statistic information from the booking record.
About this project
Our online E-Ticket System (ETS) 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). To enhance the refund function, all the customers have to registration become a member before buying ticket.
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.
General Requirements (functional)
1. The web page (e.g. The time table page, the main page) will be generated automatically according to the data in database.
2. A way in which the customer can create its own account(member registration).
3. A way in which the users (both customer and staff) can login to the system to perform different operation.
4. A way in which the customer can modify its own data.
5. A way in which the customer can place a order by just clicking the seat (which is shown on the screen) and insert some card data.(some simple operation)
6. A way in which the customer can cancel the order and get the refund.
7. A way in which the customer can check the ticket record according to the transaction number.
8. A way in which the staff can use the system to add data(e.g. film description) to the database.
9. The system can verify the data before transaction.
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)
Entity Relationship Diagram
Our E-ticket system is highly related to the database, most of the fields and variables used in the webpage will also appear in the database (except some flags and temporary variables ). So, in our Data Modeling part, we will only concern about the data appear in the database.
