Case Study points

Original problems:
The frogs:

  • too much manual labour
  • too much software
  • no actual booking software
  • no overview of money-related gubbins

The √úbermench:

  • IT guys wised up and left
  • ancient soft/hardware
  • user UNfriendly system
  • reports are too technical
  • lack of web 2.0


  • unified ticketing system
  • box office ticket collection w/ identification
  • user friendly system FOR the theater
  • user friendly site for visitors
  • multi-language support
  • deadline of 1 March 2014 (under 2 years)
  • cross-browser support

Features for solution:

  • data migration
  • web-based content management system
  • customer relationship management
  • sales and data analysis
  • INTEGRATED online bookings, telephone bookings and those made from the booking offices
  • multi-language system
  • user-friendly system
  • support for ancient people
  • ‘suppliers of ticketing systems’
  • database
  • ACID (atomicity, consistency, isolation, durability)
  • database data-migration
  • human readable output

Real world examples:

  • contact Forum Cinemas AS and ask how their ticket system works
  • contact the cinemas in Solaris and ask how their ticket system works