Briefly describe how you would generate alternate design strategies for your proposed system. Additionally, include some specific examples. see in the text: Section 7.7 Selecting the Best Alternative Design Strategy and Section 7.8 Generating Alternative Design Strategies.

7.7 example and 7.8

Transcribed Image Text:

Now, suppose that we also need to know which price quote is in effect for each part shipment received. This additional data requirement necessitates that the relationship between VENDOR and PART be transformed into an associative entity. This new relationship is represented in Figure 7-8B. FIGURE 7-7 Example of an associative entity. EMPLOYEE Employee_ID Employee_Name (...) Birth_Date A CERTIFICATE Certificate Number Date Completed B COURSE Course_ID + Course_Title {Topic) In this case, PRICE QUOTE is not a ternary relationship. Rather, PRICE QUOTE is a binary many-to-many relationship (associative entity) between VENDOR and PART. In addition, each PART RECEIPT, based on Amount, has an applicable, negotiated Price. Each PART RECEIPT is for a given PART from a specific VENDOR, and the Amount of the receipt dictates the purchase price in effect by matching with the Quantity attribute. Because the PRICE QUOTE pertains to a given PART and given VENDOR, PART RECEIPT does not need direct relationships with these entities. FIGURE 7-8 (A) Many-to-many relationship with attributes. (B) Associative entity with separate relationship. A B VENDOR VENDOR ++ Quantity Price PART PRICE QUOTE Quantity Price PART RECEIPT Order_Number Date Amount PART Now, suppose that we also need to know which price quote is in effect for each part shipment received. This additional data requirement necessitates that the relationship between VENDOR and PART be transformed into an associative entity. This new relationship is represented in Figure 7-8B. FIGURE 7-7 Example of an associative entity. EMPLOYEE Employee_ID Employee_Name (...) Birth_Date A CERTIFICATE Certificate Number Date Completed B COURSE Course_ID + Course_Title {Topic) In this case, PRICE QUOTE is not a ternary relationship. Rather, PRICE QUOTE is a binary many-to-many relationship (associative entity) between VENDOR and PART. In addition, each PART RECEIPT, based on Amount, has an applicable, negotiated Price. Each PART RECEIPT is for a given PART from a specific VENDOR, and the Amount of the receipt dictates the purchase price in effect by matching with the Quantity attribute. Because the PRICE QUOTE pertains to a given PART and given VENDOR, PART RECEIPT does not need direct relationships with these entities. FIGURE 7-8 (A) Many-to-many relationship with attributes. (B) Associative entity with separate relationship. A B VENDOR VENDOR ++ Quantity Price PART PRICE QUOTE Quantity Price PART RECEIPT Order_Number Date Amount PART