OK I see
http://webserver2.kncc.com/index.php[
^] is for cinema, so you're going to need some sort of database to hold all the details required
* How many
screens does the cinema hold?
* How many
seats does each screen hold?
* In each screen, what
films are being shown and at what times?
When it comes to
booking, you're going to need to think about the workflow
* What
film does the customer want to see
* What
screens is the film showing in
* How many
seats are currently available in each screen
* What seats are available (e.g some cinemas show you a seating plan and let you choose where you want to sit)
If the
customer completes the transaction, you need to store the details that the customer selected and update all information accordingly
* Decrease amount of available seats for the selected film at showing at the time.
* Update the seating plan so that certain seats are no longer available
Using the words I've bolded above, you can probably start to think about what tables you need in your database and their relation to each other.
Think about what objects you can use in your booking system to represent these entities and the details you need to capture. You can either start with a database model or object model, whatever you are more comfortable with.
Data Model vs Object Model
http://www.agiledata.org/essays/drivingForces.html[
^]
Otherwise, as mentioned - try out a few cinema websites that offer this functionality, see how they work!
Submit an article or tip