GOFA INDUSTRIAL COLLEGE

DEPARTMENT of ICT
WEB DEVELOPMENT AND DATABASE ADMINISTRATION
LEVEL – III
1
 Module Title: Modeling Data Object
Unit1. Identify entities and
relationships
Unit 2. Develop normalization
Unit 3. Validate model
Unit 1:- Identify entities and relationships

Analyzing business data to understand operations

 identifying boundaries of the system
identifying entities, attributes, data types and
relationships of data
Reviewing business rules to determine impact
Documenting relationships in an entity relationship
diagram
Understanding and analysing business operations
When a database development company is asked to build a database
application for a client, it needs to take its time to diligently (attentively)
learn client’s operations. Developers must take a deeper look into details of
the business to understand clients’ desires and how they manage their data.
The first step to improving a process is to analyse it in order to understand
the activities, their relationships, and the values of relevant metrics.
Process analysis generally involves the following tasks:
Define the process boundaries.
Construct a process flow diagram that illustrates the various process
activities and their interrelationships.
Evaluate limitations in order to quantify/compute the impact of the
limitation.
Use the analysis to make operating decisions and to improve the process.
 Cont..
Identify Entity types entity sets, attributes and keys
What is entity in a database?
 An Entity is an object with a physical existence or a conceptual
existence.
 It can be roles, events, locations, tangible things or concepts.
 For example, a user's login information (username and password) is an intangible entity
in database management because it is not an actual object that can be viewed and
interacted with. Intangible entities also include elements like thoughts, emotions, and
memories.
In database terms, an entity is a table which is responsible for storing
data in the database.
 Entity type is the set of all possible values for an entity.
An entity set is a set of entities of the same type (collection of instances.
represented by (e1, e2, e3, ... en).
It is also called an extension of the entity type.
Types of Entity in DBMS

There are two types of entity in database management: tangible and

intangible. Here, we will explore both types of entities in greater detail so that you
can better understand how they work in a DBMS.
1. Tangible Entity with Example
A tangible entity in database management is a physical object that can be touched,
seen, or measured. For example, a table in a database is a tangible entity because
it is an actual object that can be viewed and interacted with. Examples of tangible
entities include cars, buildings, and people.
2. Intangible Entity with Example
An intangible entity in database management is a nonphysical object that cannot
be touched, seen, or measured. For example, a user's login information (username
and password) is an intangible entity in database management because it is not an
actual object that can be viewed and interacted with. Intangible entities also
include elements like thoughts, emotions, and memories.
Cont..
 Entity Instance is a single occurrence of a particular entity type.

 Entity type name EMPLOYEE PROJECT

 Attributes name Name, Age, salary Pname, Pcode, Location
 Cont..
In E-R Diagram, an entity type is represented by a rectangle, and the name is indicated in
capital letters.

example : DEPARTMENT EMPLOYEE

 Attributes:-
An attribute is a property that describes an entity.
Each attributes has a particular value based on the defined data type.
The set of all possible (allowable) values of an attribute is called attribute domain.
In E-R Diagram, attributes are named with an initial capital letter followed by lowercase letters.
An attribute can be represented by an ellipse (oval) shape with a line connected it to the
associated entity.

Example :
 Cont..
It can also be represented by listing them within the entity rectangle, under the entity name(entity type).
Example:
EMPLOYEE
Emp_Id
Fname

Types of attributes lname

• An attribute can be: - simple or composite, single-value or multi-value, stored or derived
or Null Values.

1. Simple (Atomic) vs Composite attribute

Simple attributes cannot be further divisible.
Example: SSN, Sex
In E-R Diagram, simple attributes can be represented by an ellipse shape. Example:
 Cont..
 Composite attributes can be divided into smaller subparts
 Example :- address (street address, city, state, zip code)
 - Name (first name, last name, initial name)
 - Name (first name, last name, initial name)
In E-R Diagram, composite attributes can be represented by:
The value of composite attribute is the concatenation of the values of its
constituent simple attributes.