**_A Theatre Reservations System_**
A theatre accepts bookings for its forthcoming performances up to a period of six months in advance. About half of these are from the general public, the remainder being from commercial agencies.
Members of the public can make bookings either by internet, post, telephone or by a personal visit to the booking office. If such a booking is made using either a credit card or by paying in cash, the booking is considered to be definite and the ticket has the status ‘Sold’. If no cash or credit card is used, a booking has the status ‘Reservation’. Reserved tickets must be collected no later than 45 minutes before the performance ??" otherwise the reservation is cancelled. Half an hour before the actual performance, any remaining tickets are sold for cash at the ticket office.
Agencies are allowed to make block bookings. When such a booking is received, the theatre checks to see which seats are available and also does a credit check on the agency account. Assuming that this is satisfactory, the booked seats are marked as sold and a confirmation note is then printed and sent to the agency as both a confirmation and an invoice. At the end of each calendar month a ‘statement of account’ is sent to each agency for all bookings (and payments received, if any) in that month.
1. Design a database which meets the information need described above. This must be documented as a set of entity definitions and an ERD. *Groups are advised to submit a draft version as soon as they are ready. This reduces the risk of a student spending a lot of time building a database which cannot work.*
2. Build a sample database to illustrate what they have designed. *Note: use of the autonumber data type is not allowed.*
3. Create a document describing your solution. This needs to include a design section showing the final entity definitions and ERD; a description of the tables and any forms, queries, and reports used in the sample database; and Instructions for using the database.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).