anchor.diff:  
   The requirements ran to 16 pages, but I can't show them to you because they were under strict lock-n-key: the intellectual property belongs to the RAD RACE organizers.  But I can, I think, tell you what I remember:
   
  -* allow the club administrator to be able to define an event, with a menu, of various menu items (we had some example menus to get the idea)
  -
  -* members of the club would get a different price from non-members
  -
  -* the app would be accessible via web browser for regular users (ie not administrator) to decide to attend an event and to select their food selection from the menu (eg 3 x meat, 1 x fish, 2 x salads etc).
  -
  -* the app would allow the regular user to print out the available menu (eg to show to their family and friends so that they could decide what they want), and also to print out an order once made
  +* allow the club administrator to be able to define an event, with a menu, of various menu items (we had some example menus to get the idea). +
  ++
  +Members of the club could potentially get a different price from non-members
  +
  +
  +* allow non-administrators (whether members of the club or non-members) to self-register and to sign in. +
  ++
  +The idea was that there would be a link from the club's website to the sign-in page.
  +
  +* allow registered users to place orders for attending an event, making their food selection from the event's menu (eg 3 x meat, 1 x fish, 2 x salads etc).
  +
  +* the app should allow the registered user to print out the available menu (eg to show to their family and friends so that they could decide what they want), and also to print out an order once made
   
   * the app would also allow the administrator to print out the order once placed, with an appropriate purchase order reference, and would also allow the administrator to print out a "pick list" for the items to purchase from each of the suppliers.
   
  +* the app should also allow the administrator to indicate when an order has been paid.  Out of scope was any integration with back-end payment systems.
  +
  +In addition, we were provided with a spreadsheet of 5,000 users, each with a user/password.  The requirement was to upload that data such that the user could log into the system.  You'll find that spreadsheet https://github.com/incodehq/radrace2015/tree/master/data[here] (we checked it was okay to commit to our repo).
  +
  +
   There were some further requirements that I'm a bit more vague about:
   
   * be able to perform "marketing actions" so that the administrator could figure out how well their campaign for a particular event
  
positive.code: 
  pass:[<br/><br/>]
  
  yada yada:
  
  image::https://raw.githubusercontent.com/incodehq/radrace2015/master/images/550-inspect-order.png[link="https://raw.githubusercontent.com/incodehq/radrace2015/master/images/550-inspect-order.png"]
  
  
  
  pass:[<br/><br/>]
  
  yada yada:
  
  image::https://raw.githubusercontent.com/incodehq/radrace2015/master/images/560-open-basket.png[link="https://raw.githubusercontent.com/incodehq/radrace2015/master/images/560-open-basket.png"]
  
  
negative.code: 
  pass:[<br/><br/>]
  
  The two top-level menu items that *would* be relevant to a regular user would have been the "Events" menu:
  
  image::https://raw.githubusercontent.com/incodehq/radrace2015/master/images/530-available-events.png[link="https://raw.githubusercontent.com/incodehq/radrace2015/master/images/530-available-events.png"]
  
  to view any up-coming events, and also
  
  
  pass:[<br/><br/>]
  
  the "Orders" menu, to view any orders that they had placed:
  
  image::https://raw.githubusercontent.com/incodehq/radrace2015/master/images/540-orders-for-events.png[link="https://raw.githubusercontent.com/incodehq/radrace2015/master/images/540-orders-for-events.png"]
  
  