Data design

4.3 A logical level business function (process) to physical design technique matrix that cross references the processes defined in your functional decomposition diagram with the seven physical design techniques (de-normalisation (one-to-one, one-to-many with reference data, associative entity with non-key attributes, and the duplication of non-key attributes), indexing and partitioning (both vertical and horizontal)). Please state clearly which physical design techniques cannot be used and why they cannot be used in the application. 4.4 Considerations for using those physical design techniques that you have identified (in your business function (process) to physical design technique matrix) as being possible to use to improve the data retrieval performance of the nine processes. This section should be the largest and most detailed part of your report. You will need one subsection for each of the nine processes in the application. In each subsection you will examine each of the physical design techniques that you can use for that process and discuss how it can be used, discuss the benefits of using it, discuss the disadvantages of using it (with reference to other processes), and finally discuss whether or not you will use it. 4.5 Final ERD (and a set of relations in standard relation notation) that reflect that any changes you have made to the entities and/or the attributes. If a relation has a foreign key, state the appropriate on-delete action in the child table. 4.6 The SQL queries needed to implement the data retrieval operational business rules for each process. 4.7 Two re-written data usage maps – one for each of the two most important processes. 4.8 A data dictionary, containing details about each table for the case study (e.g. field name, field description, data type, size, domain, range, example, required, indexed, primary key, foreign key, format and default value), organised for easy reference. The data dictionary must reflect the Final ERD.