this pdf excerpt

More documents

Recommendations

Info

7- 58 Chapter 3 Data Modeling Using the Entity-Relationship (ER) Model conceptual design of database applications, and many database design tools emplor' its concepts. We describe the basic data-structuring concepts and constraints of tht ER rnodel and discuss their use in tl-re design of cor.rceptual schemas for database applictrtions. We also present the diagrammatic notation associated with the ER model, known as ER diagrams. Object modeling methodologies such as the Universal Modeling Language (UMLr are becoming increasingly popular in software design and engineering. These methodologies go beyond database design to speci$, detailed design of software modules and their interactions using various types of diagrams. An irnportant part of these methodologies-namely, class diagran 15)-i11g similar in many rvays to the ER diagrams. In class cliagrams, opcratiotts on objects are specified, in addition to specilying the database schema structure. Operations can be used to specify the functional recluiretttents during database design, as discussed in Section 3.1. We presellt some of the UML notation and concepts for class diagrams that are particularh' relevant to database design in Section 3.8, and briefly compare these to ER notation and concepts. Additional UML notation and concepts are presented in Section 4.6 and itr Chapter 12. This chaprter is organized as follorvs: Section 3.1 discusses the role of high-level conceptual data models in database design. We introduce the requirements fbr an example database application in Section 3.2 to illustrate the use of concepts fionr the ER model. This example databirse is also used in subsequent chapters. In Section 3.3 we present the concepts of entities and attributes, and we gradually introduce the diagrammatic technique tbr displaying an ER scherna. In Section 3.4 we introduce the concepts ofbinary relationships and their roles and structural constraints. Section 3.5 introduces weak entity types. Section 3.6 shows how a schema design is refined to include relationships. Section 3.7 reviews the notation for ER diagrams, summarizes the issues that arise in schema design, and discusses how to choose the names for database schemtr constructs. Section 3.8 introduces some UML class diagram concepts, compirres thenr to ER model concepts, and applies them to the sarne database exarmple. Section 3.9 discusses more complgx types of reiationships. Section 3.10 summarizes the chapter. The material in Sections 3.8 and 3.9 may be excluded from an introductory course; if a more thorough coverage of data modeling concepts and conceptual database design is desired, the reac-ler should continue from Section 3.7 to Chapter 4, where we describe extensions to the ER nrodel that lead to the Enhanced-ER (EER) model, which inclucies concepts such as specialization, generalization, inheritance, and union types (categories). We also introduce some adclitional Ulv{L concepts and notation in Chapter 4. 1, A class is similar Io an entity type in many ways.
luy the 'ilSe ER '{L) r-Se 'il re )ilrt the lto the )re- :rly lon -1.6 on- 'an 'om .lon uce tronts. .n is lTls, the dia- Itne ipr s. lrse; lase :)ere ,iel, and and .fl 3.1 Using High-Level Conceptual Data Models for Database Design 59 3.1 Using High-Level Conceptual Data Models for Database Design Figure 3.1 shows a simplified description of the database design process. The first step shown is requirements collection and analysis. During <strong>this</strong> step, the database designers interview prospective database users to understand and document their data requirements. The result of <strong>this</strong> step is a concisely written set of users' requirements. These requirements should be specified in as detailed and complete a form as possible. In parallel with specifring the data requirements, it is useful to specify the known functional requirements of the application. These consist of the userdefined operations (or transactions) that will be applied to the database, including Functional Requirements + @ + DBMS-independent I DBMS-specific I High-Level Transaction Specification Application Programs @ @ REOUIREMENTS COLLECTION AND ANALYSIS Data Requirements t V Conceptual Schema (ln a high-level data model) + | (DATA MODEL MAPPTNG) | V Logical (Conceptual) Schema - (ln the data model of a specific DBMS) ernal Schema Figure 3.1 A simplified diagram to illustrate the main phases of t^+^f,^^^ t^^i^^ udr4uass uE>19il.
Page 1: .-" clrapter 3 Data Modeling Using
Page 5 and 6: t diaiional sually nrc of create ro
Page 7 and 8: 't ---,--:-.: JmoeI -_==-?' T :5o11
Page 9 and 10: aJr. or a .lc vi.rlue, ()l hal\re a
Page 11 and 12: .rre the ,.d into sofan .rsually it
Page 13 and 14: )n cov- ,llue is r bcing rr.rlued t
Page 15 and 16: pes. Jme oan rt of visor the The hi
Page 17 and 18: ..itionship ..i..ler the 'utc calle
Page 19 and 20: nbina- These _rs repployee s con- ,
Page 21 and 22: lr. - ;ip'.-::.rl hh F* F | )r -ll
Page 23 and 24: I ,' :i r€p- G. .'.iIlO[ ;i .::d
Page 25 and 26: Ll,L2 rrilr 3.7.2 Proper Naming of
Page 27 and 28: ., i:ed or ri :C\'€I3l TQ. and :;
Page 29 and 30: }.!r :lJnY F.' : the ) '.)nle nl-':
Page 31 and 32: '( .ipplied .:.tlrred, ' 'r each ,
Page 33 and 34: lr .3 1C ,1,.r' x - =FERS ' . :tast
Page 35: : t- Ft- I t T. &- F ,. t, p)' .tra

this pdf excerpt

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?