Professional Documents
Culture Documents
Page - 1 -
E-ticket System
Requirements Specification
by
Lai Chi Wa
03011674
Chung Wang Leong
03011615
Group 3
COMP 2221
Lecturer : Prof. Jiming Liu
October 11, 2004
E-ticket System Requirements Specification
Page - 2 -
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:
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).
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.
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.
E-ticket System Requirements Specification
Page - 5 -
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.
E-ticket System Requirements Specification
Page - 6 -
2.2 Use-case
The Read/Write/Modify own group are the main user of this software.
Staff
1. Insert data to database(film name, description)
2. Delete data from database
3. Modify data in the database.(adding new movie section, changing
movie description)
4. Obtain statistic information
3.1 Customer
The following diagram is the main page of the system, which most of the customer
will start using the system from this page. In this page, the customer can check the
film detail by clicking on each film(e.g. film description, seat booking situation). The
customer can start the buy ticket process after checking the film detail. Also, the
customer can register as a member of the system. After registration, customer can
login to its own account to modify its own data and return ticket if they have order a
ticket before.
4. System check the time weather it is possible for the customer to cancel the seat(by
system)
5. If the seat is cancelled successfully, increase the cancelled amount of money to
customer’s record. (by system)
6. Return to the user main page.
3.2 Staff
The system for the staff part is not shown in the main page. Before the staff to
perform any operation, he/she must login to the system first. Once the staff login to
the system, the statistic information will be shown. And the staff can choose function
by clicking the button on left hand side. The functions are:
1. Insert film data.
2. Delete film data.
3. Modify film data.
4. Add new section to current showing film.
The function ‘Obtain the statistic information’ just like reading data from database,
we will not describe here.
Automatic mode
In this mode, the time table will generate automatically according to the length of the
movie. The system will show the time table and then ask the staff to confirm. After
confirm, the data will insert to the database.
Manual mode
E-ticket System Requirements Specification
Page - 10 -
In this mode, staff need to insert the begin time of movie one by one. Using this
mode, the cinema can make special arrangement.
4.1 Assumptions
Ticket type
Every film has 3 ticket types(adult /student /elderly or children). That means there are
3 different prices for each film. Also, this assumption is work in the whole year, even
in Tuesday and public holiday.
Web server
We need to have a real web server to run the system. This server must able to support
dynamic webpage(E.g. php). And we must associate enough bandwidth for this server,
so multi-user (customer) can use the system at the same time.
DBMS compatibility
We need to have a real DBMS to run the system. Since multi-user will use the system
at the same time, the DBMS must able to due with the data concurrency problem.
Hardware compatibility
Since we cannot use a machine to read the card information and print the ticket to the
customer, we just assume the cinema have such device. So, staff in the ticket box need
not to handle the booking through the web.
4.2 Constraints
Transaction
We cannot do a real transaction, so we can only simulate the process of transaction
and save the necessary data in the database
Customer information
Customer_id:
The key for each customer.
Customer_name:
The customer’s name.
Customer_tel:
The customer’s telephone number.
Customer_address:
The customer’s address.
Customer_email:
The customer’s email address.
Customer_password:
The customer’s password for login the system.
Customer_amount:
The amount of money that the customer have refund and will be use in next time.
Customer_creditcard:
The customer’s credit card number.
Movie information
Movie_id:
The key for each movie.
Movie_name:
The name of the movie.
Movie_director:
The director of the movie.
E-ticket System Requirements Specification
Page - 13 -
Movie_casting:
The actor of the movie.
Movie_duration:
The length of the movie.
Movie_cateory:
The cateory of movie like I,II,III.
Movie_language:
The language of the movie.
Movie_synopsis:
The main description of the movie.
Record Information:
Record_id:
The key for each record.
Record_seat:
The seats which is sold in this record.
Sale Information
Sale_id:
The key for each record.
Sale_time:
The time for this sale.
Sale_seat_sold
The seat which is sold.
Sale_seat_available:
The seat which is available.
Staff Information
Staff_id:
The key for each record.
Staff_name:
The name of the staff
Staff_password:
The password of the staff.
Ticket Information
Ticket_type_id:
The key for each record.
E-ticket System Requirements Specification
Page - 14 -
Ticket_type_name:
The name of each ticket type.
Ticket_price:
The price for each ticket type.
5.1.2 Relationships
E-ticket System Requirements Specification
Page - 15 -
Appendix