Deck 01 Database Technology

Database

Systems
DECK 01
Low Yin Jye
Database
Technology
45 Minutes
Learning Outcomes
• Introduction to Database
• File-Based Systems
• File-Based Processing
• Limitation of File-Based Approach
• The Database Approach
• What is a Database?
• Database Management System (DBMS)
• Generations of Database
• Advantages of DBMS
• Disadvantages of DBMS
• ANSI-SPARC Three-Level Architecture
• Database Application Life Cycle
Introduction to Database

What are some database examples?

File-Based Systems
• Collection of application programs that perform
services for the end users (e.g. reports).
• Each program defines and manages its own data.
File-Based Processing
Limitations of File-Based Approach
• Separation and isolation of data
• Duplication of data
• Data dependence
• Incompatible file formats
• Fixed Queries/Proliferation of application
programs
The Database Approach
• Arose because:
 Definition of data was embedded in application
programs, rather than being stored separately and
independently.
 No control over access and manipulation of data
beyond that imposed by application programs.
• Result:
 The database and Database Management System
(DBMS).
What is a Database?
• Shared collection of logically related data (and a

description of this data), designed to meet the
information needs of an organization.
• System catalog (metadata) provides description

of data to enable program–data independence.
• Logically related data comprises entities,

attributes, and relationships of an organization’s
information.
Database Management System (DBMS)
• A software system that enables users to define,

create, and maintain the database and that
provides controlled access to this database.
Database Management System (DBMS)
Generations of Database
• First generation • Third generation

 Hierarchical  Object Relational
 Network  Object-Oriented
• Second generation • Fourth generation

 Relational  Graph
 NOSQL
Advantages of DBMS
• Control of data redundancy

• Data consistency
• More information from the same amount of data
• Sharing of data
• Improved data integrity
• Improved security
• Enforcement of standards
• Economy of scale
Advantages of DBMS
• Balanced conflicting requirements

• Improved data accessibility and responsiveness
• Increased productivity
• Improved maintenance through data
independence
• Increased concurrency
• Improved backup and recovery services
Disadvantages of DBMS
• Complexity
• Size
• Cost of DBMS
• Additional hardware costs
• Cost of conversion
• Performance
• Higher impact of a failure
ANSI-SPARC Three-Level Architecture
• The ANSI-SPARC Architecture (American National
Standards Institute, Standards Planning And
Requirements Committee), is an abstract design
standard for a database management system (DBMS),
first proposed in 1975.
• The ANSI-SPARC model however never became a

formal standard. No mainstream DBMS systems are
fully based on it (they tend not to exhibit full physical
independence or to prevent direct user access to the
conceptual level), but the idea of logical data
independence is widely adopted. https://en.wikipedia.org/wiki/ANSI-SPARC_Architecture
ANSI-SPARC Three-Level Architecture
User Objectives of Three-Level Architecture
• All users should be able to access same data.
• A user’s view is immune to changes made in

other views.
• Users should not need to know physical

database storage details.
DBA Objectives of Three-Level Architecture
• Database Administrator (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.
Three-Level Architecture in Details
• External Level
 Users’ view of the database.
 Describes that part of database that is relevant to a
particular user.
• Conceptual Level
 Community view of the database.
 Describes what data is stored in database and
relationships among the data.
• Internal Level
 Physical representation of the database on the
computer.
 Describes how the data is stored in the database.
Three-Level Architecture in Details (Table)
INTERNAL LEVEL CONCEPTUAL LEVEL EXTERNAL LEVEL
Physical Storage in It describes the This level is the closest to
database structure of whole the users
database for users
This level is close with It represent all entities, It is the way how the data is
physical storage of attributes and their view by individual users
data relationship
It can view in the form It contain all the Describes the segment of
of files information to build the database that is required
the relevant external for a particular user group
records and hides the rest of the
database from that users
Data compression and It hides the internal Describe part of database,
encryption techniques details of physical that is relevant to each
are applied at this level storage users.
Data Independence
Logical Data Independence
• Logical Data Independence

 Refers to immunity of external schemas to changes in
conceptual schema.
 Conceptual schema changes (e.g. addition/removal of
entities).
 Should not require changes to external schema or
rewrites of application programs.
Physical Data Independence
• Physical Data Independence

 Refers to immunity of conceptual schema to changes
in the internal schema.
 Internal schema changes (e.g. using different file
organizations, storage structures/devices).
 Should not require change to conceptual or external
schemas.
Database Application Life Cycle
Database Application Life Cycle
Database Application Life Cycle (List)
1. Database Planning Developers verify the needs for database, goals and
the tools to accomplish its goals.
2. Requirement Analysis Determine all objectives of the database and how
does it support the application?
3. Database Design Organising all the pieces of data in tables and deciding
how best to link its data to each other.
4. Prototype Example of database system but lack features for final system.
It is to allow users identify features that work well or not
5. Implementation Apply the solution to the existing problem
6. Data Conversion & Loading Migrate existing data to the new database
and convert any existing application to connect to the new database
7. Testing Before it is release, we have to test its features and eliminate
errors & bugs.
8. Operation Maintenance After testing, continue to monitor the
performance of the system and to make changes if required
Stages in Database Design
END

Deck 01 Database Technology

Uploaded by

Copyright:

Available Formats

Deck 01 Database Technology

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Deck 01 Database Technology

Uploaded by

Copyright:

Available Formats

Database

What are some database examples?

• Shared collection of logically related data (and a

• System catalog (metadata) provides description

• Logically related data comprises entities,

• A software system that enables users to define,

• First generation • Third generation

• Second generation • Fourth generation

• Control of data redundancy

• Balanced conflicting requirements

• The ANSI-SPARC model however never became a

• All users should be able to access same data.

• A user’s view is immune to changes made in

• Users should not need to know physical

• Database Administrator (DBA) should be able to

• Internal structure of database should be

• DBA should be able to change conceptual

• Logical Data Independence

• Physical Data Independence

You might also like