Demonstration Schedule

Location: Ritterstraße 12, Zimmer 5-10 (Uni Gästehaus)

Simple Ticket Sales Site

General Requirements

• The project is developed on your laptop.
• The language of the site is either in English or German.
• You must work with exactly one other classmate on this project. If you are a Montana State student, that other classmate must be from the University of Leipzig.
• Apache, php, MySQL and XHTML must be used.
• The described functionality below is accessible through a web browser.

Specific Requirements

Assume that an organization has contacted you to put together a ticket sales site for the month of July 2008. The organization is a small one and has only 10 seats in its event center. The organization wishes to hold events on Tuesdays at 7 p.m., Wednesdays at 7 p.m., Thursdays at 7 p.m., Fridays at 7 p.m., Saturdays at 2 p.m., Saturdays at 7 p.m. and Sundays at 2 p.m.

Of the 10 seats, 5 seats are standard and cost 10 euros each while the other 5 seats are premium and cost 20 euros each.

The site should be able to accommodate three types of users: browsers, registered users and the event coordinator. The events database and the account for the event coordinator can be set up however you like.

Browsers

• Should be able to learn what events are coming up and how many tickets are available.
• Should be able to sign-up to be a registered user by supplying a first name (one or more alphabetical characters), a last name (one or more alphabetical characters), an e-mail address (in a valid form such as xxx@xxx.xxx) and a desired password (six or more alphanumeric characters). The system will register the user by giving him or her a unique id.

Registered Users

• Should be able to login using a unique id and password.
• Should be able to learn what events are coming up and how many tickets are available.
• Should be able to purchase any number of available tickets to one or more events.
• Should be able to display his or her previously purchased tickets.
• Should be able to logout.

Event Coordinator (1 person)

• Should be able to login using a unique id and password.
• For a specific event, can check how many tickets are unsold.
• For a specific event, can check how many tickets are sold and how much revenue has been generated.
• For a specific event, can check who has purchased tickets.
• For all events, can check the total percentage of tickets unsold, the total percentage of tickets sold and the total revenue that has been generated.
• Should be able to logout.

Demonstration

Everyone must give a 30 minute demonstration of their system. A sign-up sheet for the demonstration will be brought to class on Friday, June 6th. Both programming partners should be present for the demonstration. The demonstration should be done on your computer so that you can ensure that the environment is set up correctly.

Material to Submit at your Demonstration

Produce a word-processed document that contains the following sections:

• A list of any technologies that you used in addition to Apache, php, MySQL and JavaScript.
• A list and description of any enhancements you made to your system, above and beyond the minimal requirements.
• A list and description of all known weaknesses of your system. Weaknesses might include incorrect functionality, poor design decisions, etc. You will receive more points if you identify a weakness correctly than if you don't identify it at all.

Grading

In order to receive a B+ (MSU students) or a 1.7 (Leipzig students), the following must be true:

• You are prepared for the demonstration and do it successfully.
• The write-up is well-written and accurate.
• The site allows the above functionality.
• The site is easy to use.
• The site looks reasonably good.
• Users can not do illegal things such as buying more tickets than are available for a given event.
• The underlying XHTML is of high quality.
• The underlying php and JavaScript are of high quality.
• Security considerations have been incorporated. At the very least, sensitive information in the database (such as passwords) should be encrypted with sha1.

In order to receive a higher grade, you must go above and beyond the requirements in a non-trivial manner (for example, allowing the event coordinator to add events, allowing events to occur outside of July 2008, providing a seating chart, incorporating fancy graphics, etc.). How you decide to do this is up to you. Have fun!