e-ticket booking j2ee code containing 5 modules
Posts: 14,118
Threads: 61
Joined: Oct 2014
INTRODUCTION
Goals and objectives
The main goal of our online reservation system to provide an alternative and convenient way for customers to buy movie tickets. This automatic system. After the data was fed into a database, staff do not need to do anything with it when it is received through the system. In fact, there is such a system on the Internet, but there is no way to return the found in the existing system. The goal of our system are:
1 to provide anytime, anywhere service for the client
2 To minimize the number of staff members in the box tickets
3 To promote the film on the Internet
4 to increase profit
5 to obtain statistical information from the record book.
About the project
Our online E-Ticket System (ETS) is a Web-based system. Customers can buy a ticket online and Cancel in good time (for 2 days prior to the show at 1:0 prior to the show). To improve back function, all customers registering to become a member before purchasing the ticket.
Staff can use the system to insert and delete data (for example, a description of the film, calendar), which will update the page (Web pages are dynamic pages, changing in accordance with the data in the database). In addition, employees can check the statistical information from the system.
General requirements (functional)
1. Web page (for example, page table times home page) will be generated automatically in accordance with the data in the database.
2. the way in which the client can create your own account (registration of members).
3. the way in which users (both clients and staff) may be logged in to perform various operations.
4. the way in which the client can change its data.
5. the way in which a customer can place an order, simply clicking into place (which is shown on the screen) and insert the data card. (Some simple operation)
6. the way in which the client may cancel the order and get a refund.
7. the way in which the client can check the record of tickets according to the number of operations.
8. the way in which staff can use the system to add data (for example, a description of the film) to the database.
9. the system can validate data before the deal.
10. the system can automatically generate a time table (just at the entrance of the length of the film) or a time table established staff. (2 hours for staff to paste your data).
11. the system can generate statistical information under reservation and ticket sales on record.
12. user can check these films by clicking on a specific film on the main page (for example, the movie will show this movie).
13. user can check movies data by clicking on a particular movie on the home page (for example, a film now shows)
Entity-relationship Diagram
Our E-ticket is closely associated with the database, then most of the fields and variables used by the Web page also appear in the database (except for some temporary variables and flags). So, in our data modeling part, we only care about the data appear in the database.