EXPLAIN AND CREATE ERD DIAGRAM 1. AN EXMAPLE FOR YOU TO DO: NORMALIZATION Given the following relation

EXPLAIN AND CREATE ERD DIAGRAM

 

Transcribed Image Text:

1. AN EXMAPLE FOR YOU TO DO: NORMALIZATION Given the following relation and functional dependencies: COORDINATES (UnitCode, Semester, Option, Coordinator) FD: UnitCode, Semester, Option Coordinator What is (are) the candidate key(s)? Which NF is the relation in? Convert the relation into a relation or set of relations in at least 3NF 2. AN EXAMPLE FOR YOU TO DO: THE PLUMBING BUSINESS CASE An information system is required for a small plumbing business. A customer will contact the business with a request for work to be carried out. Acustomer has a unique customer number, a name, and a billing address (street, suburb, state, postcode). Awork order has a unique work order number, a creation date, a completion required date, a completion date, an optional supervising employee, an address where the work is undertaken, and a set of tasks. Each task has a unique task ID, a task name, an hourly rate, and estimated hours. Tasks are standardised across work orders so that the same task may be performed on many work orders. Each task on a work order has a status (not started, in progress, or completed), actual hours, and a completion date. The completion date is not entered until the status changes to complete. Complete an ERD including all the legends according to the above instruction 1. AN EXMAPLE FOR YOU TO DO: NORMALIZATION Given the following relation and functional dependencies: COORDINATES (UnitCode, Semester, Option, Coordinator) FD: UnitCode, Semester, Option Coordinator What is (are) the candidate key(s)? Which NF is the relation in? Convert the relation into a relation or set of relations in at least 3NF 2. AN EXAMPLE FOR YOU TO DO: THE PLUMBING BUSINESS CASE An information system is required for a small plumbing business. A customer will contact the business with a request for work to be carried out. Acustomer has a unique customer number, a name, and a billing address (street, suburb, state, postcode). Awork order has a unique work order number, a creation date, a completion required date, a completion date, an optional supervising employee, an address where the work is undertaken, and a set of tasks. Each task has a unique task ID, a task name, an hourly rate, and estimated hours. Tasks are standardised across work orders so that the same task may be performed on many work orders. Each task on a work order has a status (not started, in progress, or completed), actual hours, and a completion date. The completion date is not entered until the status changes to complete. Complete an ERD including all the legends according to the above instruction