Scribd
Upload
28 views

Database Model

This document discusses conceptual data modeling which involves determining user data requirements, integrating individual views into an overall conceptual view, and translating the conceptual design into physical database structures. It describes key concepts like entities, attributes, relationships, and schemas. Specifically, it defines a data model as an abstraction of a dataset, discusses how data modeling involves abstraction and documentation, and outlines the different modeling activities and types of relationships that can exist between entities.

Uploaded by

shashwat2010
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
28 views

Database Model

This document discusses conceptual data modeling which involves determining user data requirements, integrating individual views into an overall conceptual view, and translating the conceptual design into physical database structures. It describes key concepts like entities, attributes, relationships, and schemas. Specifically, it defines a data model as an abstraction of a dataset, discusses how data modeling involves abstraction and documentation, and outlines the different modeling activities and types of relationships that can exist between entities.

Uploaded by

shashwat2010
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 24

Shashwat Shriparv

[email protected]
InfinitySoft
A data model is a model describing the data in an
organization
Abstraction tool
Abstracts essential qualities of a
dataset
Data modeling is the process of abstraction and
documentation using a data model
Determination of the data requirements (views)
of individual users & applications
For e.g.
Project building process /customer requirements
specs
Integration of the individual user (customer) &
application (s/w) views into an overall
conceptual views.
Customer reviews – Conflict resolution.
2 types:
Unconstrained/Natural Conceptual Design
Constrained/Conceptual Design
The internal structure of the database
Translating the Conceptual Design(previous
steps) into physical structures; basically stacks,
queues etc…
Data abstraction creates hierarchies of
abstractions along 2 dimensions
Aggregation
Generalization
Aggregation
Identifies a data items as a part of a higher
level, more aggregate descriptor
e.g. Project -> Project -> Assignment
Generalization
It creates categories into which a data item
may be classified
e.g. Employee can be categorized into
age
Type of job
Type of pay plan, etc…
Conceptual Model:
designed to promote user understandable
Specifications of data.
Physical Model
designed to aid in physical database design.
Info logical
for human understanding and requirements level.
Data logical
deals with physical and database implementation.
Some models can contain elements of both models.
Terms used in Data definition
Entity: Any type of "thing" about which info. Is
being maintained.
Attribute: A characteristic of an entity.
Instance: instance of an entity or relationship.
Relationship: Association between entities.
Identifiers: Set of attributes which uniquely identify
an instance of an entity or relationship.
EMPLOYEE is an entity
A person who works for the company is an
instance of EMPLOYEE.
His/her age is an attribute of the entity type.
Employee OF company, here "of" is a
relationship.
Employee Id is an identifier.
Three types amongst activities
recorded during conceptual data modeling.
has adverse effects on the physical database
design
Basically

1:1 1:M M:N


Instance of an entity has a given relationship
with only one instance of a 2nd entity.

ENDOWED
PROCESSOR CHAIR

HELD BY
An entity has relationships with many instances
of another entity.

S1 UNIVERSITY S5
S5

S2 S3
S3 S4
S4

University -> many students


Students -> one university.
An entity has relationships with many instances
of another entity and vice-versa.

REGISTERED

STUDENT CLASS
Defines conditions that must be met for the data to be
complete and correct.
Three types:
 On values
 On dependencies
 On referential integrity
• Values: allowable, valid values for attribute
• Dependencies: allowable values for attributes may
depend on some other value.
• E.g. allowable values for an employee skill
classification are a part of allowable skills of the
department he/she works in.
Entities and relationships often have reference
conditions that must be met.

A sales order; for an order to exist there must be a


customer.
Defines categories of data and their property.

A schema is an outline or representation of


a plan, a theory, or an assignment.
Classification
External (User's view)
Conceptual (Overall logic)
Internal schema or Data storage Defn.
(Physical organization)
Also known as user's schema(appl prg/ person
formulating a query) is concerned with only a
small portion of the database
It’s the user view of data being used in the
system.
Only a very few of the total entities or its
attributes are taken into consideration.
The logical view of the Database
The closest view of the real entities and their
relationships.
Contains integrity rules & authorization rules.
But no data about how data is stored in the
Database.
Describes how the database is organized for
physical storage and access.
Includes information on ordering of records,
block sizes, storage indexes, use of pointers
and access strategies being used.
Translations from one schema to another.
For user access of data
the user view of the data as shown in the
external schema must be translated into the overall
conceptual schema. This is done by
external\conceptual mapping.
In the same way conceptual\internal mapping
translates logical descriptions of data in the
conceptual schema to physical location and access
paths in the internal schema.
Shashwat Shriparv
[email protected]
InfinitySoft

You might also like