1
01 Introduction to Database
CAK1OAB3
Database Modelling
2
Learning Outcomes
Students can explain the concepts of data, data model, advantages
of database approach, the process of database development life
cycle, people involved in the development process, and the
evolution of database system
Topics
3
Traditional
Basic Concepts Database
Database
and Definitions Approach
Processing
People Involved Evolution of
Database
in Database Database
Lifecycle
Development System
4
Basic Concepts and
Definitions
Data vs Information vs Knowledge
5
DEFINITION
6
• Database
• An organized collection of logically related data.
• Data
• Facts concerning objects and events that could be recorded and stored on computer
media
• Stored representations of objects and events that have meaning and importance in the
user’s environment.
• Information
• Data that have been processed in such a way as to increase the knowledge of the person
who uses the data.
Examples
7
• List of facts
Data
• Data in context
Useful information to some
users, such as the course
instructor and the registrar’s
office.
Figure 1. Data in context
Examples (2)
8
• Summarized Data
Data presented as graphical
information.
This information could be used as a
basis for deciding whether to add
new courses or to hire new faculty
members.
Figure 2. Summarized Data
Real
World
Facts about world and behaviour of
world
represented in
contents and operations of a database
fa cts a bo ut the wor ld in a m or e so me mo re r ath er lon g fact s ab ou t th e wo rl d in th e d ata bse
fa cts a bodut
atab
thease
wor ld in a fa or
m ctse
so me mo re r ath er lon g fact s ab ou t th e wo rl d in th e d ata bse
fa cts a bodut
atab
thease
wor ld in a fa or
m ctse
so me mo re r ath er lon g fact s ab ou t th e wo rl d in th e d ata bse
fa cts a bodut
atab
thease
wor ld in a fa or
m ctse
so me mo re r ath er lon g fact s ab ou t th e wo rl d in th e d ata bse
fa cts a bodut
atab
thease fa or
ctse
Database
wor ld in a m so me mo re r ath er lon g fact s ab ou t th e wo rl d in th e d ata bse
fa cts a bodut
Users
atab
thease
wor ld in a fa or
ctse
m so me mo re r ath er lon g fact s ab ou t th e wo rl d in th e d ata bse
d atab ase fa or
ctse
fa cts a bo ut the wor ld in a m
fa cts a bodut
atab
thease
wor ld in a fa or
m ctse
fa cts a bodut
atab
thease
wor ld in a fa cts
m or e fa cts a bo ut the wor ld in a
fa cts a bodut
atab
thease
wor ld in a fa or
m ctse
fa cts a bodut
atab
thease
wor ld in a
fa cts a bodut
atab
thease
wor ld in a fa cts fa cts a bodut
atab
thease
wor ld in a
fa cts a bodut
atab
thease
wor ld in a fa cts a bodut
atab
thease
wor ld in a
d atab ase fa cts a bodut
atab
thease
wor ld in a
fa cts a bo ut the wor ld in a
fa cts a bodut
atab
thease
wor ld in a
fa cts a bodut
atab
thease
wor ld in a
d atab ase
d atab ase
10
• Databases today may contain either data or information (or both).
• For example, a database may contain an image of the class roster document
shown in Figure 1.
• Also, data are often pre-processed and stored in summarized form in
databases that are used for decision support.
• Throughout this course we use the term database without distinguishing its
contents as data or information.
Metadata
11
• Metadata
• Data that describe the properties or characteristics of end-user data and the
context of those data.
12
Traditional File Processing
Systems
Traditional File Processing Systems
13
• When computer-based data processing was first available, there were no
databases
• To be useful for business applications, computers had to store, manipulate,
and retrieve large files of data.
• Computer file processing systems were developed for this purpose.
Disadvantages of File Processing Systems (1)
14
1. Program-data dependence
2. Duplication of data
3. Limited Data Sharing
4. Lengthy development times
5. Excessive program maintenance
Figure 3. Example of File Processing Systems
15
The Database Approach
Data Models
16
• Data models is graphical systems used to capture the nature and
relationships among data.
• Entity is a person, a place, an object, an event, or a concept in the user
environment about which the organization wishes to maintain data.
• The data you are interested in capturing about the entity (e.g., Customer
Name) is called an attribute.
• Data are recorded for many customers. Each customer’s information is
referred to as an instance of CUSTOMER.
• A well-structured database establishes the relationships between entities
that exist in organizational data so that desired information can be retrieved.
Example of Data Model
17
Figure 4. Segment of Figure 5. Segment of a project data model
an enterprise data model
18
Relational Database
• Relational database is a database
that represents data as a
collection of tables in which all
data relationships are
represented by common values
in related tables.
• Relational databases establish
the relationships between
entities by means of common
fields included in a file, called a
relation
Database Management System (DBMS)
19
• A database management system (DBMS) is a software system that enables
the use of a database approach.
• The primary purpose of a DBMS is to provide a systematic method of
creating, updating, storing, and retrieving the data stored in a database.
• It enables end users and application programmers to share data, and it
enables data to be shared among multiple applications rather than
propagated and stored in new files for every new application (Mullins, 2002).
• A DBMS also provides facilities for controlling data access, enforcing data
integrity, managing concurrency control, and restoring a database.
Advantages of DBMS
20
1. Program-data independence
2. Planned Data Redundancy
3. Improved Data Consistency
4. Improved Data Sharing
5. Enforcement of Standards
6. Improved Data Quality
7. Increased productivity of application development
8. Improved data accessibility and responsiveness
9. Reduced program maintenance
10. Improved decision support
Figure 3. Example of File Processing Systems
21
Costs and Risks of the Database Approach (1)
• New, specialized personnel
• Installation and management cost and complexity
• Conversion costs
• Need for explicit backup and recovery
• Organizational conflict
22
Database Life Cycle
23
Planning
Database
Life Cycle
Maintenance Analysis
Implementation Design
Planning
24
Planning
Purpose
To develop a preliminary understanding of
a business situation and how information
Maintenance Analysis
systems might help solve a problem or
make an opportunity possible
Consist of two steps:
• Enterprise modelling
Implementation Design
• Conceptual modelling
Planning
25
Enterprise Modelling Conceptual Data Modelling
• Analyse current data • Identify scope of database
processing requirements for proposed
• Analyse the general business information system
functions and their database • Analyse overall data
needs requirements for business
• Justify need for new data and function(s) supported by
databases in support of database
business
Analysis
26
Planning Purpose
To analyse the business situation
thoroughly to determine requirements, to
Maintenance Analysis structure those requirements, and to select
among competing system features
Implementation Design
Conceptual Data Modelling (part 2)
27
• Develop preliminary conceptual data model, including entities and
relationships
• Compare preliminary conceptual data model with enterprise data model
• Develop detailed conceptual data model, including all entities,
relationships, attributes, and business rules
• Make conceptual data model consistent with other models of information
system
• Populate repository with all conceptual database specifications
Design
28
Purpose
Planning
To elicit and structure all information
requirements; to develop all technology and
organizational specifications
Maintenance Analysis
Consist of two step:
• Logical database design
• Physical database design and definition
Implementation Design
Design
29
Physical Database Design and
Logical Database Design
Definition
• Analyse in detail the • Define database to DBMS
transactions, forms, displays, (often generated from
and inquiries (database views) repository)
required by the business • Decide on physical
functions supported by the organization of data
database
• Design database processing
• Integrate database views into programs
conceptual data model
• Identify data integrity and
security requirements, and
populate repository
Implementation
30
Purpose
Planning To write programs, build databases, test and
install the new system, train users, and
finalize documentation
Maintenance Analysis The Steps:
• Code and test database processing
programs
• Complete database documentation and
training materials
Implementation Design
• Install database and convert data from
prior systems
Maintenance
31
Purpose
To monitor the operation and usefulness of
Planning the system, and to repair and enhance the
system
The Steps:
Maintenance Analysis
• Analyse database and database
applications to ensure that evolving
information requirements are met
• Tune database for improved performance
Implementation Design
• Fix errors in database and database
applications and recover database when it
is contaminated
32
People Involved in
Database Development
33
Managing People Involved in Database
Development
• Business analysts
• Systems analysts
• Database analysts and data modelers
• Users
• Programmers
• Database architects
• Data administrators
• Project managers
• Other technical experts
34
Evolution of Database
System
Evolution of Database System
35
Hierarchical Database Model
36
In the hierarchical model, files are
organized in a top-down structure
that resembles a tree or genealogy
chart.
Network Database Model
37
In the network model, each file can be
associated with an arbitrary number of
other files.
Relational Database Model
38
The relational model (the primary focus
of this course) organizes data in the
form of tables and relationships among
them.
Object-oriented Database Model
39
The object-oriented model is based on
object classes and relationships among
them. As shown in the figure, an object
class encapsulates attributes and
methods
Multidimensional Database Model
40
Multidimensional databases, which form the basis for data warehouses, allow
us to view data in the form of cubes or a star schema
41
Evolution of Database System - Resume
The development and evolution of database technology generally drove by:
1. The need to provide greater independence between programs and data,
thereby reducing maintenance costs
2. The desire to manage increasingly complex data types and structures
3. The desire to provide easier and faster access to data for users who have
neither a background in programming languages nor a detailed understanding
of how data are stored in databases
4. The need to provide ever more powerful platforms for decision support
applications
42
Reference
Hoffer, Jeffrey A., [Link]., "Modern Database Management", Twelfth Edition,
Pearson, 2016. Chapter 1
Questions
43