You are on page 1of 1

CST 363 Final Project Summary

Team Members: John Coffelt, Michael Rose


The company we are working for is called Neatflix. Neatflix is a new company that works similarly to ticket selling
websites like Fandango. They want us to build a database that will store all the theatre and ticketing information so
that visitors to the website can purchase said tickets.
The purpose of the database system is to store all of the online ticketing information for each movie shown at a
theatre that has agreed to be on the site. The database will also store information about the theatre itself such as
where it’s located and any special features of each auditorium within each theatre. The special auditorium features
would include Dolby 5.1 Surround Sound, UltraHD projection, 3-D viewing capability, deluxe seating, etc. Tracking
which theatre auditorium has a special feature allows our company, Neatflix, to draw customers to our customers
by including these features in the advertisements for the movies on the Neatflix website. Tracking these features
also allows for determining which features are more popular than others. Along with ticketing, movie, theatre, and
auditorium feature information, the database will also store customer information for various purposes.
Some questions would be what type of reports the company is looking to generate and how easily accessible that
information is within the database. This can be resolved with the addition of views into the database. Some
information the company will need to add a theatre to their website would be general information such as location,
number of auditoriums, and any special capabilities each auditorium has. Movies and showtimes will be constantly
updated.
We do not show remaining seats for each showtime in the showtimes table to avoid duplication of data. The data
can already be found using the ticket_purchases table. Instead, we created a view to show that information.
Here is an ER diagram of the database we have proposed:

You might also like