07-08-2012, 01:25 PM
E-ticket System
[attachment=30366]
Goals and Objectives
The main purpose of our online 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 need not to due 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 provide refund which is not available in the existing system
3 To minimize the number of staff at the ticket box
4 To promote the film on the internet
5 To increase the profit
6 To obtain statistic information from the booking record.
System Statement of Scope
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 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 commit order by just clicking the seat (which is shown on the screen) and insert some card data.
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.
Interface Enhancements
Our web-based system needs about 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 webpage for an order).
System Context
Our online Ticket Booking System (TBS) 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.
Major Constraints
Data concurrence
Since two or more customers may request for the same seat at the same time. So, the system needs to remove the chance for two customer get the same seat.
Transaction
We cannot have a real bank account for the transaction. We can just simulate the process.
Time
Lots of the customer will buy tickets in ticket box and the customer use our web-based system still need to take the ticket in ticket box. So, the online ticket booking service and refund service will be stopped 1 hour before the show time. To do so, we can reduce the chance of 2 people book the same seat, also reduce the time for buying a ticket.
Compatibility
The new system need to be compatible with the existing ticket selling system(original) in the ticket box, because the web-base system and the original system will run on the same time and use the same database.
[attachment=30366]
Goals and Objectives
The main purpose of our online 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 need not to due 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 provide refund which is not available in the existing system
3 To minimize the number of staff at the ticket box
4 To promote the film on the internet
5 To increase the profit
6 To obtain statistic information from the booking record.
System Statement of Scope
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 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 commit order by just clicking the seat (which is shown on the screen) and insert some card data.
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.
Interface Enhancements
Our web-based system needs about 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 webpage for an order).
System Context
Our online Ticket Booking System (TBS) 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.
Major Constraints
Data concurrence
Since two or more customers may request for the same seat at the same time. So, the system needs to remove the chance for two customer get the same seat.
Transaction
We cannot have a real bank account for the transaction. We can just simulate the process.
Time
Lots of the customer will buy tickets in ticket box and the customer use our web-based system still need to take the ticket in ticket box. So, the online ticket booking service and refund service will be stopped 1 hour before the show time. To do so, we can reduce the chance of 2 people book the same seat, also reduce the time for buying a ticket.
Compatibility
The new system need to be compatible with the existing ticket selling system(original) in the ticket box, because the web-base system and the original system will run on the same time and use the same database.