0% found this document useful (0 votes)
10 views14 pages

DBMS 5

The document provides an overview of the database design process, focusing on the Entity-Relationship (ER) model, which is used to create a conceptual schema of a database. It explains key concepts such as entities, attributes, relationships, and various attribute types, including simple, composite, single-valued, multi-valued, stored, and derived attributes. Additionally, it discusses mapping cardinality representations, including M:N, 1:M, and 1:1 relationships.

Uploaded by

Aman Aaryan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views14 pages

DBMS 5

The document provides an overview of the database design process, focusing on the Entity-Relationship (ER) model, which is used to create a conceptual schema of a database. It explains key concepts such as entities, attributes, relationships, and various attribute types, including simple, composite, single-valued, multi-valued, stored, and derived attributes. Additionally, it discusses mapping cardinality representations, including M:N, 1:M, and 1:1 relationships.

Uploaded by

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

ER Modeling

KALINGA INSTITUTE OF INDUSTRIAL


TECHNOLOGY

School Of Computer
Engineering

Dr. Pradeep Kumar Mallick


Associate Professor [II]
School of Computer Engineering,
Kalinga Institute of Industrial Technology (KIIT),
Deemed to be University,Odisha

4 Credit Lecture Note 05


Chapter Contents
2

 Overview of the Database Design Process


 Entity- Relationship(ER) Model
 Attribute Types
 Mapping Cardinality Representation
Overview of the Database Design Process
3
 The initial phase of database design is to characterize fully the data needs of the
prospective database users. It usually involves in textual description.
 Next, the designer chooses a data model and, by applying the concepts of the
chosen data model, translates these requirements into a conceptual schema of
the database. The ER model is typically used to represent the conceptual
design.
 The designer reviews the schema to confirm that all data requirements are
satisfied and are not in conflict with one another.
 At this stage of conceptual design, the designer can review the schema to
ensure it meets all the functional requirements.
 The process of moving from an abstract data model to the implementation of
the database proceeds in two final design phases:
In the logical design phase, the designer maps the high-level conceptual
schema onto the implementation data model of the database system that will be
used. The implementation data model is typically the Relational data model
Finally, the designer uses the resulting system-specific database schema in the
subsequent physical-design phase, in which the physical features of the
database are specified.
Entity-Relationship(ER) Model
4
 The ER model was developed to facilitate the database design by allowing
specification of an enterprise schema that represents the overall logical
structure of a database. The ER model is very much useful in mapping the
meaning and interactions of real-world enterprises onto a conceptual
schema.
 Entity: An entity is a thing or object in the real world that is
distinguishable from all other objects, i.e. an entity is an object of interest
to the end user. The set of similar types of entities is called entity set;
which is represented by a rectangle containing the entity set’s name. The
entity set name, a noun, is usually written in all capital letters.
 Attributes: Attributes are characteristics of entities. Attributes are
represented by ovals and are connected to the respective entity set with
lines. In the conceptual modeling, the value of an attribute comes from a
domain of possible values.
 Relationship: In modeling, the association between entities are referred to
as relationship. The relationship name is a verb. A relationship set is a set of
relationships of the same type. Relationship sets are represented by
diamonds and are connected to the participant entity sets.
Entity-Relationship(ER) Model….
5
 Null Values: An attribute takes a NULL value when an entity doesn’t have
a value for it. The NULL values may indicate not applicable, i.e. the value
doesn’t exist for the entity. NULL can also designate that an attribute value
is unknown. An unknown value may be either missing or not known.
NULL value is an entry in all the domains.
Attribute Types
6
 Simple and Composite Attribute: An attribute that has a discrete factual
value and cannot be meaningfully subdivided is called an atomic or
simple attribute. On the other hand, a composite attribute can be
meaningfully subdivided into smaller subparts (i.e. simple attributes)
with independent meaning.

6
Attribute Types…
7
 single-valued attribute and multi-valued attributes: Most attributes have
a single value for a particular entity and are referred to as single-valued
attribute. However, attributes that can have more than one value are
known as multi-valued attributes. It is represented by double oval.

7
Attribute Types…
8
 Stored attribute and derived attribute: The attribute with independent
existence is called as stored attribute where as the attribute, whose value
is depending on other stored attribute, is called as derived attribute. The
derived attribute is represented by the dotted oval.

8
Attribute Types…
9
 Descriptive attribute: A relationship may also have attributes called
descriptive attributes for representing the description about the association.

9
Mapping Cardinality Representation
10

 M:N Relationship: An entity in A is associated with any number (zero or


more) of entities in B and vice versa.
 An M:N relationship occurs when multiple records in one entity are
associated with multiple records in another entity.

10
Mapping Cardinality Representation…
11

 1:M Relationship: An entity in A is associated with any number (zero or


more) of entities in B; an entity in B, however, is associated with no more
than 1 entity set of A.
 A One-to-Many relationship exists when one record in an entity is
associated with multiple records in another entity.

11
Mapping Cardinality Representation…
12
 1:1 Relationship: An entity in A is associated with no more than 1 entity of
B; and an entity in B is associated with no more than 1 entity of A.
 A One-to-One relationship exists when a single record in one entity
is associated with exactly one record in another entity, and vice
versa.

12
Symbols of ER-Model
13
14

You might also like