乔伊·F·乔治-现代系统分析与设计（第6版）hoffer_msad6e_ch09.pptVIP

* * * * * * * * * * * * * * * * * * * * * * * * ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 9 FIGURE 9-13 Two unary relationships (a) EMPLOYEE with Manages relationship (1:N) (b) Bill-of-materials structure (M:N) ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 9 Merging Relations Purpose is to remove redundant relations The last step in logical database design Prior to physical file and database design ? 2011 Pearson Education, Inc. Publishing as Prentice Hall View Integration Problems Must understand the meaning of the data and be prepared to resolve any problems that arise in the process Synonyms: two different names used for the same attribute When merging, get agreement from users on a single, standard name * Chapter 9 ? 2011 Pearson Education, Inc. Publishing as Prentice Hall View Integration Problems (Cont.) Homonyms: a single attribute name that is used for two or more different attributes. Resolved by creating a new name Dependencies between nonkeys— dependencies may be created as a result of view integration To resolve, the new relation must be normalized * Chapter 9 ? 2011 Pearson Education, Inc. Publishing as Prentice Hall View Integration Problems (Cont.) Class/Subclass — relationships may be hidden in user views or relations Resolved by creating a new name * Chapter 9 ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 9 FIGURE 9-16 Class diagram corresponding to normalized relations of Hoosier Burger‘s inventory control system ? 2011 Pearson Education, Inc. Publishing as Prentice Hall Relations for Hoosier Burger * Chapter 9 ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 9 Physical File and Database Design The following information is required: Normalized relations, including volume estimates Definitions of each attribute Descriptions of where and when data are used, entered, retrieved, deleted, and updated (including frequencies) Expectations or requirements for