You need to produce a Data Model for the Green Bite Foods Company described below.

Green Bite Foods

Green Bite Foods is a small catering firm with 20 full time employees. Company also has about 50 casual employees which it can call on at very short notice. Green Bite Foods caters for private functions like weddings, parties and picnics. During a typical summer weekend they will cater for up to 15 functions or events. The company takes orders for functions and buys the needed supplies and also cooks and prepares the food.

Green Bite Foods has a set of 8 standard menus and also caters for special requests like wedding cakes, birthday cakes, retirement cakes etc. When potential customers call, the advisor would describe the available menus and corresponding prices. The customer would also be provided with a drinks menu.   If the customer decides to make a booking the advisor records the customer information and the information about the function (e.g. place, date, type, number of guests, which standard menu is needed, drinks, extras and the total price).  A copy of the booking form is then sent or faxed to the customer, which should 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 one 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 would also make an assessment of the staffing requirements and will schedule the staff in advance.  The casual staffs are paid by cheque a few days after a function has taken place. The hourly rate for casual staff is £8.00.

The owner of Green Bite Foods has requested an information system in order to manage the processing of the various types of booking, cancellations, ordering of food supplies and payment of casual staff.  You must produce a data model for Green Bite Foods.

Deliverables

A report should includes the following sections:

1. An introduction detailing the purpose of the specification and the user environment. This should include a description of the issues or problems to be solved.

2. You must expand your specification to a System Specification. This must be aimed at the developer of the system and should include:

• Data Models of the proposed system
Conceptual Model – EERD (This must include entities, relationships, primary key constraints, cardinality and participation constraints, specialisation and generalisation.)

Logical Model – Mapped EERD (Map the conceptual model to a logical model using the relevant steps.  Carry out normalisation to 3rd normal forms and discuss the progression through 1st, 2nd and 3rd normal forms.  This mapped model also must additionally include all attributes and foreign keys.

• Use either the extended Crow’s Foot notation or Chen’s notation but do not mix the notations (i.e. use either one or the other but not both).

• Use any design tool which you feel most familiar with (i.e. Visio, MS Word or IBM Rational etc.)

3. A Data Dictionary detailing the data requirements of your proposed system.

4. A discussion of problems you encountered and how you endeavoured to solve them.