1. Online Restaurant Booking System James Beck (EC) Hardware & CMS John Charlton (EC) XHTML & CSS Design Jamie Hart ( EC) PDA Diary Design Gareth Davies (EC) PHP MySQL Lead Developer Dorota Pryszlak (EC) Project Manager & Database Design

2. Initial Scope Nationwide Restaurant Directory Ratings & Comments Menus & information Restaurant Admin Section Universal Booking System Flexible Table Management Instant Booking Confirmation Universal Application Reasons for Change No Client Huge Project Massively Complex Risk of Incompletion

3. Revised Scope Online Brochure for Laze Daze Menus & information Content Management System Bespoke Booking System Flexible Table Management Instant Booking Confirmation Replaces Existing Paper Based System Based on the Rules of Current System How we got our Client Laze Daze were the first establishment to respond to a selection of Emails sent to local restaurants. They are very keen to see the system implemented and are more than happy to spend time with us to help develop the system.

4. Our Client Family run business since 2005. Modern European food with Mediterranean influence. Middle size restaurant with 12 tables seating max 40 people, basement bar area and top floor dedicated to private functions. Manual booking system based on paper diary. Open 7 days a week during lunch and evening hours. Basic web site presence www.laze-daze.co.uk.

5. Requirements Software Requirements PHP / MySQL MS Project Dreamweaver, Fireworks, Photoshop UML Tool – Posidon Hardware Requirements Linux Server Broadband Connection Wireless Router PDA

6. View all booking Information Confirm Customer Arival Booking Stats (e.g. Total Customers) Table Allocation Input Bookings Taken by other means (e.g. Telephone) The aim of the PDA is to provide a portable yet efficient user interface for both viewing and maintaining booking information.

7. Client Booking Process Client Visits Website Makes Booking (Chooses Date & Time) Confirmation via EmailDeclined via Email Waits for manual confirmation from Laze Daze If Unavailable If Available If Flagged (e.g. Over 75% Capacity)

9. Restaurant Booking Management 1.Bookings Viewed on PDA 2.Bookings Flagged, Manually Confirmed or Declined 3.All Confirmed Bookings are Manually Allocated Tables 4.Customer Arrives 5.Details of Booking Checked on PDA 6.Customer Arrival Confirmed on PDA 7.Client Eats 8.Client Information Stored for Future Visits & Marketing

10. Testing 1.W3C Validated Code 2.Development Site Available for Developers and Restaurant 3.System Stress Testing 4.Mock Evening of Bookings made by Developers, Trial by Restaurant.

11. Team Communication Methods 1.Weekly Group Meetings 2.Monthly Group & Client Meetings 3.Constant Email Communication 4.FodderMe Forum – Online Group Forum Project Documentation Meeting Minutes Disucussion

13. Thank You