Scribd
Upload
15 views

Chapter 3 Data Modelling Using the Entity–

Chapter 3 discusses the phases of database design, including requirements collection, conceptual design, implementation, and physical design, focusing on the Entity-Relationship (ER) model. It explains key concepts such as entities, attributes, relationships, and constraints, using a COMPANY database example to illustrate the design process. The chapter also covers various types of attributes, relationships, and the significance of key attributes in ensuring entity uniqueness.

Uploaded by

agoncillobrai2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
15 views

Chapter 3 Data Modelling Using the Entity–

Chapter 3 discusses the phases of database design, including requirements collection, conceptual design, implementation, and physical design, focusing on the Entity-Relationship (ER) model. It explains key concepts such as entities, attributes, relationships, and constraints, using a COMPANY database example to illustrate the design process. The chapter also covers various types of attributes, relationships, and the significance of key attributes in ensuring entity uniqueness.

Uploaded by

agoncillobrai2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 12
‘Chapter-3_ Data Modeling Using the Entity-Retationship Model 3.1 INTRODUCTION Conceptual Database Design ‘The main phases of database design are: © Requirements Collection and Analysis: purpose is to produce a description of the users’ requirements. © Conceptual Design: purpose is to produce a conceptrat schema for the database, including detailed descriptions of entity hpes, relationship types, and constraints. All these are expressed in lens provided by the data model being used, + Lmplemeittation: pupose is to transform the conceptiial schema (which i at a high/abstract eve) intto a (lower-level) representatonal/imp lementational model supported by whatever DBMS B to be used, ‘© Physical Design: purpose is to deeide upon the internal storage structures, access paths (indexes), etc.. that swill be used in realizing the representational model produced in previous phase. Figure 3.1 shows the database design process, 3.2. Example COMPANY Database We need to create a database schemm design based on the following (simplified) requirements of the COMPANY Database: Employees, departments, and projects Company is organized. ito: departments Department controts several projects Empbyce: require each emphyee’s name, Social Securiy number, address, salary, sex (gender), and birth date © Keep track of the dependents of each employee 3.3. Enlity-Relationship (ER) Model The ER model is a high-level conceptual data model The ER model was introduced by Peter Chen in 1976, and is now the must widely wed conceptual data model Itrepresents real work situations using concepts, Which are commonly used by people. It allows defining a representation of the real world at logical levelL.ER model has no facilities to deseribe machine-related aspects, In ER model the logical structure of data is captured by indicating the grouping of data into entities. The ER model abo supports a top-down approach by which details can be given in successive stages, Inthe ER model, the main concepts are entity, attribute, and relationship. Entity Types, Entity Sets, Attributes, and Keys, 1. Entities and Attributes 2. Entity Types, Entity Sets, Keys, and Value Sets 3. Initial conceptual Design for the COMPANY Database Figures Reena wigs Figure 3.2: An ER Diagram of COMPANY database fovine Qo =e SUMMARY OF ER DIAGRAM SYMBOLS( figure 7.14 Navathe) ‘Symbol © 2 OS 2g oo Oho a

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy