Views of Data, Data Models, DB Development Life Cycle
Views of Data, Data Models, DB Development Life Cycle
UNIT-1
Views of Data
• Physical Level
• Lowest level
• how the data are actually stored
• describes complex low-level data structures
• Logical Level
• Next higher level
• physical data independence.
• what data are stored in the database, and what relationships exist among
those data
• Used by Database Administrators
• View Level
• Highest level
• describes only part of the entire database
• simplify interaction with the system
• Can be many views for same database
Views of Data
Students can view Name, Roll no, Marks but they can not edit
Course instructor can view Name, Roll no, Marks and can edit marks, but not
the Roll no and name
Mentor can do modifications in Roll no and Name, but not on Marks
Instance and Schema
• Instance
• The collection of information stored in the database at a particular moment
• Schema
• The overall design of the database
• Physical schema
• describes the database design at the physical
• Logical schema
• describes the database design at the logical level.
• Subschemas
• describe different views of the database.
Data Models
• Data Model is the modeling
of the data description, data
semantics, and consistency
constraints of the data.
• It provides the conceptual
tools for describing the
design of a database at each
level of data abstraction.
• 4 data models used for
understanding the structure
of the database
Relational Data Model
• The model designs the data in the form of rows and
columns within a table.
• uses tables for representing data and in-between
relationships.
• Tables are also called relations. This model was initially
described by Edgar F. Codd, in 1969.
• used model which is primarily used by commercial data
processing applications
Entity-Relationship Data Model
• An ER model is the logical representation of data as
objects and relationships among them.
• objects are known as entities, and relationship is an
association among these entities.
• It was widely used in database designing. A set of
attributes describe the entities.
Object-based Data Model
• Object-based Data Model:
• An extension of the ER model with notions of functions,
encapsulation, and object identity, as well.
• supports a rich type system that includes structured
and collection types.
• Here, the objects are nothing but the data carrying its
properties.
Semistructured Data Model
• This data model is different from the other three data models
• The semi structured data model allows the data
specifications at places where the individual data items of
the same type may have different attributes sets.
• The Extensible Markup Language, also known as XML, is
widely used for representing the semistructured data.
• Although XML was initially designed for including the
markup information to the text document, it gains
importance because of its application in the exchange of
data.
Hierarchical Model
• In hierarchical model,
data is organised into
tree-like structure
with one one-to-many
relationship between
two different types of
data,
Network Model
• This is an extension of
the Hierarchical model.
In this model data is
organised more like a
graph, and are allowed
to have more than one
parent node.
Database
Development Life
Cycle
Thank you