The Travellers Break Restaurant chain is a large chain of roadside eateries. They are planning on installing a new food ordering system.
Currently the restaurant has waiters writing orders on pads which are taken to the kitchen. The problem with this method is that at busy times, customers might wait a long time to have their order taken, sometimes the waiter forgets to add extra drinks and late orders to the bill; when they are putting the items through the till they don’t always remember to check for multiples eg 2 x fish and chips. On occasion, items have been added to the wrong person’s bill.
Outline of user requirements
With the planned system, when the customer arrives, they are welcomed and seated by a waiter who enters a PIN to start the order for that table. The menu is then shown on a small touchscreen which uses a menu driven interface to allow selection of items.
· Position at the table
· Starter (if desired)
· Main course
· Sweet (if required)
· Items cost per person for meal (to allow splitting of bill)
· Next person at the table or finish and display final bill.
The final cost is displayed but only the waiter can “finish” the order, take the payment and clear the screen.
Only the waiter can cancel the order – there is a two minute time slot before the kitchen begins preparing the order. If a person cancels later than that they must tell the waiter who will let the kitchen know.
Only item from each course for each seat is allowed.
Up to three drinks for each seat.
Written report; These tasks should all be included within a single report with designated sections and referenced appropriately.
Produce a document which describes and compares the following life cycle models (1.1). Ensure you discuss each methods strengths and weaknesses – and justify their suitability for a specific situation (1.2).
Undertake an investigation and create a requirement specification. This should include the following;
- Input, Output and Processes (2.1), with use of diagramming/charting techniques
- Discussion with end users (1.3)
- Description of 3 alternative systems, with explanation of when each solution could be applied (2.3, 2.4)
- Explanation of fundamental difficulties when producing a user requirements specification (2.5)
- Choosing one system as a preferred choice, choose four pieces of formal design documentation (3.1)
Testing is a vital part of every system development – it is essential to find and correct errors in systems before release.
- Create a testing plan with 20 tests which covers the whole of the proposed system (3.2)
- Justify why the testing plan shows whether the proposed system meets the user requirements in the scenario (3.3)
- Using the testing plan, undertake the proposed systems fitness for purpose. Justify using the results of the testing plan (3.4)
· Using the afore mentioned items, select two items from your testing plan and review to improve – provide full documentation for these. (3.5, 3.6)
1.3, 2.1, 2.2, 2.3, 2.4, 2.5, 3.1
3.2, 3.3, 3.4, 3.5, 3.6