Functional Requirements

1. Reservation System 1.1. The website application will allow customers to book a room as required. 1.2. The website application will allow customers to book for local attractions through the website with their booking. 1.3. The website application will allow customers to review their orders history on website. 1.4. The website application will allow customers to cancel their reservations and fully refund. 1.5. The payment system shall produce a receipt detailing a customers purchase information and include name of customer, items purchased, cost of each item an shall produce a receipt detailing a customers purchase information and include name of customer, items purchased, cost of each item and total cost. 1.6. The payment system shall accept all types of card payment which contain: Visa Debit, Master, American Express, etc. 1.7. The payment system should accept GBP currency and other major currency such as US dollars and Euro. 2. Food and local attractions 2.1. The website application shall update daily about the prices and information about food and local attractions. 2.2. The website application will allow customers to book tickets for any local attractions and able to review them in their history orders. 2.3. The website application will allow customers to make reservations for any recommended restaurants on the website. 2.4. The website application shall produce original links for each food and local attractions that are clickable so that customers can get more information. 2.5. The system has to automatically sync any booking tickets or reservations to relevant original website so that all orders are authorised and useable. 3. Management functions 3.1. The customer service system shall produce a starred hotel reviews for former customers. 3.2. The customer service system shall update daily about the prices and information about hotels rooms.

3.3. The customer service system shall accept any enquiries and directly send them to appropriate staff in order to response as quickly as possible. 3.4. The customer service system shall produce a list of FAQs (Frequently Asked Questions).

Non-Functional Requirements
1. Operational Requirements 1.1. The web application shall be easy to use by all employees including sales representatives and managers. 1.2. The web application can run on handheld devices. 1.3. The web application should be able to work on any Web browser. 2. Performance Requirements 2.1. The web application shall allow multiple reservation orders to be made at the same time without downgrading performance. 2.2. Any interaction between the user and the system should not exceed 3 seconds. 2.3. The web application should be available for use 24 hours per day, 365 days per year. 3. Security Requirements 3.1. Only direct managers can see personnel records of staff. 3.2. The web application includes all available safeguards from viruses, Trojan, etc. 3.3. The payment system must process securely whenever customers make payments. 4. Cultural and Political Requirements 4.1. The web application shall be available in several languages such as English, France, Spain, etc. 4.2. The web application should be able to distinguish between GBP currency and currency from other nations. 4.3. Personal information is protected in compliance with the Data Protection Act.