Deadly Bite Foods
Deadly Bite Foods is a small catering firm with 12 full time employees. The company also has about 40 casual employees that it can call on at short notice. Deadly Bite Foods caters for private functions e.g. weddings, parties and picnics. During a typical summer weekend they would cater for up to 10 functions. The company takes orders for functions and buys the required supplies and also cooks the food.
Deadly Bite Foods has a set of 10 standard menus and also caters for special requirements such as wedding cakes, birthday cakes etc. When potential customers call, the receptionist describes the menus to them. The customer will also be provided with a drinks menu. If the customer decides to make a booking the receptionist records the customer information and the information about the function (e.g. place, date, type, number of guests, which standard menu is required, drinks, extras and the total price). A faxed copy of the booking form is then sent to the customer, which must be signed and returned with a deposit before the function is officially booked. The remaining money is collected when the function is complete. If the customer does not reply within 1 week they are sent a friendly reminder.
Each week the owner looks through the functions scheduled and orders the supplies – e.g. plates, and the raw ingredients needed such as bread, chicken, wine etc. The owner will also make an assessment of the staffing requirements and will schedule the staff in advance. The casual staff are paid by cheque a few days after a function has taken place. The hourly rate for casual staff is £10.00.
The owner has requested an information system in order to manage the processing of the various types of booking, cancellations, ordering supplies and payment of casual staff. You should produce a system specification for Deadly Bite Foods.
1. You should submit a Requirement Specification for Deadly Bite Foods. It should be aimed at the owner and should not be overly technical. This should include:
• An introduction detailing the purpose of the specification and the user environment.
• A description of the operating environment including software and hardware requirements.
• A description of the issues or problems to be solved, functional and non-functional requirements and the software behaviour necessary to address these problems.
2. You should expand your Requirement Specification to a System Specification. This should be aimed at the developer of the system. This should include:
• Models of the current system and of the proposed system
o Data Models,
o A Data Dictionary detailing the data requirements,
o Process Models,
o Behaviour Models – these should include an account of the implications on the data structure
• A decomposition of the problem into component parts
• The user interfaces – a description of the screens required and some sample screenshots of any forms, reports or other GUIs with a description of the functionality.
3. A discussion of problems you encountered and how you endeavoured to solve them.