Scribd
Upload
5 views

Lecture Notes 1.1

The document provides an introduction to database management systems and outlines the ANSI-SPARC three-level architecture for database systems including the external, conceptual, and internal levels. It also discusses different categories of data models including object-based, record-based, and physical models as well as relational, network, and hierarchical data models.

Uploaded by

huzaifa40894089
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
5 views

Lecture Notes 1.1

The document provides an introduction to database management systems and outlines the ANSI-SPARC three-level architecture for database systems including the external, conceptual, and internal levels. It also discusses different categories of data models including object-based, record-based, and physical models as well as relational, network, and hierarchical data models.

Uploaded by

huzaifa40894089
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Introduction to Database

Database Management Systems


Instructor: Maryam Munawar
Outline
• The Need for Databases
• Data Models
• Relational Databases
Objectives of Three-Level Architecture
• All users should be able to access same data but have a different customized view
• A user’s view is immune to changes made in other views
• Users should not need to know physical database storage details
• DBA should be able to change database storage structures without affecting the users’
views
• Internal structure of database should be unaffected by changes to physical aspects of
storage
• DBA should be able to change conceptual structure of database without affecting all
users
ANSI-SPARC (American National Standards Institute, Standards
Planning And Requirements Committee) Three-Level Architecture
ANSI-SPARC Three-Level Architecture..
External Level
• Users’ view of the database
• Describes that part of database that is relevant to a particular user
• Different views may have different representation of same data
(e.g. different date formats, age derived from DOB etc.)
ANSI-SPARC Three-Level Architecture..
• Conceptual Level
• Community view of the database
• Describes what data is stored in database and relationships among the
data
• Along with any constraints on data
• Independent of any storage considerations
ANSI-SPARC Three-Level Architecture..
• Internal Level
• Physical representation of the database on the computer
• Describes how the data is stored in the database
• physical implementation of the database to achieve optimal runtime
performance and storage space utilization
• Data structures and file organizations used to store data on storage devices
• Interfaces with the operating system access methods to place the data on the
storage devices, build the indexes, retrieve the data, and so on
Differences between Three Levels of ANSI-
SPARC Architecture
Data Model
• Integrated collection of concepts for describing data, relationships
between data, and constraints on the data in an organization
Purpose of Data Model
• To represent data in an understandable way
• Represents the organization itself
• Helps in unambiguous and accurate communication between between
database designers and end-users about their understanding of the
organizational data
Components of a Data Model
• A data model comprises:
• A structural part
• A manipulative part
• Possibly a set of integrity rules
• ANSI-SPARC architecture related models
• External data model (Universe of Discourse)
• Conceptual data model (DBMS independent)
• Internal data model
Categories of Data Models
Categories of data models include:
• Object-based
• Entity-Relationship
• Semantic
• Functional
• Object-Oriented
• Record-based
• Relational Data Model
• Network Data Model
• Hierarchical Data Model
• Physical
Relational Data Model
Network Data Model
Hierarchical Data Model
Conceptual Modeling
• Conceptual modeling is process of developing a model of information use
in an enterprise that is independent of implementation details
• Should be complete and accurate representation of an organization’s
data requirements
• Conceptual schema is the core of a system supporting all user views
• Conceptual vs. logical data model

You might also like