datanormalization.ppt

* * Pet Store sample sales form. Separate sections for selling animals and merchandise reflect a business rule to treat them differently. * Pet Store sample purchase order for animals. More information will be collected later—particularly data on each animal’s health and lineage. * Pet Store sample purchase order for merchandise. Note the similarities and differences between the two types of orders. Keep in mind that additional data will have to be collected later. * Pet Store normalized tables for the basic sales form. You should do the normalization first and see if your results match these tables. * Pet Store view integration. Data columns from similar tables can be combined into one table. For example, we need only one Employee table. Look for tables that have the same keys. The goal is to have one set of normalized tables that can hold the data for all the forms and reports. * Pet Store class diagram. The tables become entities in the diagram. The relationships verify that the tables are interconnected through the data. Some new data has been added for the employees. Also, cities have been defined in a single table to simplify data entry. Likewise, the new Breed and Category tables ensure consistency of data. * Bicycle Assembly form. The main EmployeeID control is not stored directly, but the value is entered in the FrameAssembler column of the Bicycle table when the employee clicks the Frame box. * Notation for the BicycleAssembly form. There are two repeating groups, but they are independent. The 4NF tables from this form are displayed, but you should try to derive the tables yourself. * Purchase Order form. Only the items ordered is a repeating group. The Look for Products section is a convenience for users and does not store data. The Date Shipment Received box is initially blank and is filled in when the product arrives at the loading dock. * Tables from the Purchase Order form. Note that the computed columns extension is price * quantity are not stored