Features Revised...

I have redone my features according to the guidelines. The image is the same, however I have made changes too.

Justification of Design:

The above design of the button should be in relation to the overall web systems theme. The size of the button should be noticeable and users should be able to identify what the function of the button is by reading the text on the button. The above design may change slightly depending on the final decided layout as a cohort which is yet to be decided.


Functionality/Interaction with other Features:

To store all the information entered or selected in the following fields:

Customer ID
Event ID/Name
Type of Ticket
Price of Ticket
Quantity
Date of Event.


Once the “check out” button is pressed it will save the above information so that it can be calculated on the payments page. It can be designed so that once the button is pressed it calculates the total straight away, or it can just transfer the information on to the Payments page.

This button’s main function is too collect all the information from the following features which are on the same page, they include:

Search Criteria
Quantity of Tickets

Those features will contain information regarding the event name, time, price of ticket and quantity of tickets. This information is vital, as it is needed for the next page.

Implementation:

I would use xhtml and PHP to implement the design of this feature. PHP can be useful with its Session and Cookies feature too, for example so that it can remember existing users. A database created using SQL can be used to store the information entered into the fields. The button could also be used as a validation tool, for example it cannot proceed unless all the required fields are filled in.