Scribd
Upload
10 views

Database Beginners guide

Chapter 3 of 'Modern Database Management' focuses on data modeling within organizations, emphasizing the importance of defining business rules, entities, relationships, and attributes. It covers the creation of E-R diagrams, the distinction between various types of relationships, and the classification of attributes. The chapter also discusses identifiers and keys that uniquely identify instances of entity types.

Uploaded by

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

Database Beginners guide

Chapter 3 of 'Modern Database Management' focuses on data modeling within organizations, emphasizing the importance of defining business rules, entities, relationships, and attributes. It covers the creation of E-R diagrams, the distinction between various types of relationships, and the classification of attributes. The chapter also discusses identifiers and keys that uniquely identify instances of entity types.

Uploaded by

ayeshanoor777325
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 15

Chapter 3:

Modeling Data in the


Organization

Modern Database
Management
8th Edition
Jeffrey A. Hoffer, Mary B. Prescott,
Fred R. McFadden

© 2007 by Prentice Hall 1


Objectives
 Definition of terms
 Importance of data modeling
 Write good names and definitions for entities,
relationships, and attributes
 Distinguish unary, binary, and ternary relationships
 Model different types of attributes, entities,
relationships, and cardinalities
 Draw E-R diagrams for common business situations
 Convert many-to-many relationships to associative
entities
 Model time-dependent data using time stamps

Chapter 3 © 2007 by Prentice Hall 2


Business Rules
 Statements that define or constrain
some aspect of the business
 Assert business structure
 Control/influence business behavior
 Expressed in terms familiar to end
users
 Automated through DBMS software
Chapter 3 © 2007 by Prentice Hall 3
Chapter 3 © 2007 by Prentice Hall 4
A Good Business Rule is:
 Declarative–what, not how
 Precise–clear, agreed-upon meaning
 Atomic–one statement
 Consistent–internally and externally
 Expressible–structured, natural
language
 Distinct–non-redundant
 Business-oriented–understood by
business people
Chapter 3 © 2007 by Prentice Hall 5
Chapter 3 © 2007 by Prentice Hall 6
E-R Model Constructs
 Entities:
 Entity instance–person, place, object, event, concept (often
corresponds to a row in a table)
 Entity Type–collection of entities (often corresponds to a
table)

 Relationships:
 Relationship instance–link between entities (corresponds to
primary key-foreign key equivalencies in related tables)
 Relationship type–category of relationship…link between
entity types

 Attribute–property or characteristic of an entity or


relationship type (often corresponds to a field in a table)

Chapter 3 © 2007 by Prentice Hall 7


Entity type: A collection of entities that share
common properties or characteristics.
Entity instance: A single occurrence of an entity
type

Strong entity type: An entity that exists


independently of other entity types.
Weak entity type: An entity type whose existence
depends on some other entity type.

Identifying owner: The entity type on which the


weak entity type depends.
Identifying relationship: The relationship between
a weak entity type and its owner.

Chapter 3 © 2007 by Prentice Hall 8


Sample E-R Diagram (Figure 3-1)

Chapter 3 © 2007 by Prentice Hall 9


Basic E-R notation (Figure 3-2)

Entity
Attribute
symbols
symbols

A special entity
that is also a Relationship
relationship symbols

Relationship
degrees specify
number of
entity types Relationship
involved cardinalities
specify how
many of each
entity type is
allowed
Chapter 3 © 2007 by Prentice Hall 10
What Should an Entity Be?
 SHOULD BE:
 An object that will have many
instances in the database
 An object that will be composed of
multiple attributes
 An object that we are trying to model
 SHOULD NOT BE:
 A user of the database system
 An output of the database system
(e.g., a report)
Chapter 3 © 2007 by Prentice Hall 11
Figure 3-4 Example of inappropriate entities

System System
user Inappropriate output
entities

Appropriate
entities

Chapter 3 © 2007 by Prentice Hall 12


Attributes
 Attribute–property or characteristic of
an entity or relationahip type that is of
interest to the organization.
 Classifications of attributes:
 Required versus Optional Attributes
 Simple versus Composite Attribute
 Single-Valued versus Multivalued Attribute
 Stored versus Derived Attributes
 Identifier Attributes

Chapter 3 © 2007 by Prentice Hall 13


• Required attribute: An attribute that must have a
value for every entity (or relationship) instance with
which it is associated.
• Optional attribute: An attribute that may not have a
value for every entity (or relationship) instance with
which it is associated
 composite attribute :An attribute that has meaningful
component parts (attributes).
 simple (or atomic) attribute: An attribute that cannot
be broken down into smaller components that are
meaningful to the organization.
 Multivalued attribute: An attribute that may take on
more than one value for a given entity (or relationship)
instance.
 Single-valued attribute has only one value for each
entity (e.g., Employee ID).
 Derived attribute An attribute whose values can be
calculated from related attribute values.
 Stored attribute is physically saved in the database
(e.g., Date Employed).
Identifier: An attribute (or combination of attributes)
whose value distinguishes instances of an entity type.
Chapter 3
composite identifier: ©An identifier
2007 by Prenticethat
Hall consists of a 14
Identifiers (Keys)
 Identifier (Key)–An attribute (or
combination of attributes) that
uniquely identifies individual
instances of an entity type
 Simple versus Composite Identifier
 Candidate Identifier–an attribute that
could be a key…satisfies the
requirements for being an identifier

Chapter 3 © 2007 by Prentice Hall 15

You might also like