CHAPTER 1

FUNDAMENTALS OF DATABASE MANAGEMENT SYSTEM

1.3 UNDERSTAND DATA MODEL

1
LEARNING OUTCOMES :
At the end of this lecture, student should be able to :-
1. Define data model
2. Describe the evolution of Data Models
3. Describe the type of logical Data Model
4. Describe the three-schema architecture of DBMS
5. Describe the client-server architecture of DBMS
6. Identify the two categories of DBMS
7. Describe benefits using desktop database and server solution
8. Identify users of DBMS 2
DEFINITION OF DATA MODEL
 An abstraction of a complex real world environment.
 a collection of conceptual tools for describing data, data relationships, data semantics, and
consistency constraints.
 A data model provides a way to describe the design of a database at the physical, logical, and
view levels.
 Database designer use data models to communicate with applications programmers and end
users.
 The basic data modelling components are entities, attributes, relationships and constraints
 Business rules are used to identify and define the basic modelling components within a
specific world environment. 3
EVOLUTION OF DATA MODEL
Ref. 1

4
EVOLUTION OF DATA MODEL
Ref : Peter Rob, Carlos Coronel
(2012). (10th Edition)

5
TYPE OF LOGICAL DATA MODEL

a. Object Based Logical Model : Entity

- relationship data model
 Entity Relationship models are normally
represented in an entity relationship diagram
(ERD),
 ER Model is a graphical representation of
entities and their relationships in a database
structure

6
 TYPE OF LOGICAL DATA MODEL
b. Record Based Logical
Model :
 Hierarchical data model
 was developed in the 1960s to
manage large amounts of data for
complex manufacturing .
 Its basic logical structure is
represented by an upside-down
tree
7
TYPE OF LOGICAL DATA MODEL

b. Record Based Logical Model :

 Network data model
 was created to represent complex data
relationships more effectively than the
hierarchical model,
 to improve database performance,
 to impose a database standard.

8
TYPE OF LOGICAL DATA MODEL
b. Record Based Logical Model :
 Relational data model
 represented a major breakthrough for both
users and designers
 the relational model produced an “automatic
transmission” database to replace the
“standard transmission” databases that
preceded it.

9
10
THREE SCHEMA ARCHITECTURE OF DBMS

 Also known as ANSI-SPARC (American National

Standards Institute, Standards Planning And Requirements
Committee)
 Proposed to support DBMS characteristics of:
- The goal of the three-schema architecture is to
separate the user applications and the
physical database. In this architecture,
- Support of multiple views of the data.
- Program-data independence.
11
DBMS schemas at three
levels :
1. External schemas at the external level to describe the
various user views. Usually uses the same data model
as the conceptual level.
2. Conceptual schema at the conceptual level to
describe the structure and constraints for the whole
database. Uses a conceptual or an implementation
data model
3. Internal schema at the internal level to describe data
storage structures and access paths. Typically uses a
physical data model.
12

 Mappings among schema levels are also needed.

DBMS SCHEMAS AT THREE LEVELS
 EXTERNAL SCHEMA:-
 The external or view level includes a
number of external schemas or user
views
 User’s view of database.
 describes the part of the database that a
particular user group is interested in
and hides the rest of the database from
that user group.
 Describes that part of database that is
relevant to a particular user.
 Excludes irrelevant data as well as data
which the user is not authorized to 13

access.
DBMS SCHEMAS AT THREE LEVELS

 EXTERNAL SCHEMA (continue):-

 External level consists of many different external views.
 Each external view may have different representations.
 External views are described in External schemas which are written in the Data
Definition Language
 typically implemented using a representational data model

14
DBMS SCHEMAS AT THREE LEVELS

 EXTERNAL SCHEMA (continue):-

 External level consists of many different external views.
 Each external view may have different representations.
 External views are described in External schemas which are written in the Data
Definition Language
 typically implemented using a representational data model

15
DBMS SCHEMAS AT THREE LEVELS
 CONCEPTUAL SCHEMA:-
 Conceptual model is relatively constant
 DBA is responsible to design it.
 Conceptual model can be expanded.
 It is written in DDL, stored in data dictionary and
compiled by DBMS.
 It represents:
 All entities, attributes and relationships
 The constraints on the data
 User operations
 Security and integrity information. 16

 Semantic information about the data

DBMS SCHEMAS AT THREE LEVELS
 INTERNAL SCHEMA:-
 Describes the physical storage structure of the database.
 Uses a physical data model and describes the complete
details of data storage and access paths for the database
 Physical representation of the database on the computer.
 Describes how the data is stored in the database and on the
computer hardware.
 Concern in:
 Storage space allocation for data and indexes
 Record description for storage
 Record placement 17

 Data compression and data encryption technique

DBMS SCHEMAS AT THREE LEVELS

18
EXAMPLE

19
CLIENT SERVER ARCHITECTURE OF DATABASE

 A networked computing model that distributes processes between clients

and servers which supply requested services (model rangkaian komputer
yang mengedarkan proses di antara pelanggan dan pelayan di mana ia
membekalkan perkhidmatan yang diminta.)
 Client–Workstation (usually a PC) that requests and uses a service
 Server–Computer (PC/mini/mainframe) that provides a service
 For DBMS, server is a database server

20
 Client/server architectures that have evolved can be distinguished by the
distribution of application logic components across clients and servers. (seni bina
client / server yang telah berkembang boleh dibezakan oleh pengagihan komponen logik aplikasi di seluruh pelanggan dan pelayan.)

 Three components of application logic:

1. Input/output (I/O) @ presentation logic
2. Processing Logic
3. Storage Logic
21
 Formatting & presenting data on user’
screen or other output devices.

Managing user input from a keyboard or

other input devices

22
I/O @ data processing: Data
validation and identification of
processing errors.

23
 Business rules describe the
operations, definitions and
constraints that apply to an
organization in achieving its
goals.

BR that have not been coded

at the DBMS level may be
coded in the processing
component.

24
Identifies the data
necessary for processing
the transaction or query.

25
Responsible for data storage
& retrieval from physical
storage devices
Activities of a DBMS 26
 Client does
 File Server Architecture
extensive processing

 Database Server Architecture

(Two Tier Architecture)

 Three-tier Architecture

Client does little

processing
27
BENEFIT OF USING DESKTOP DATABASE AND SERVER
SOLUTION

 Two categories of DBMS:-

a) Desktop databases

Example : Microsoft Access, FoxPro, FileMaker Pro, Paradox, Lotus.

b) Server databases

Example : Oracle, Microsoft SQL Server, IBM, DB2.

28
DESKTOP DATABASE

 A DBMS designed to run on a personal computer, small computer and small servers.
 Support database used by small work teams and small business.
 The engines in these drivers generally have reduced support for SQL and transactions.
 Example :- Microsoft Access, FoxPro, FileMaker Pro, Paradox, Lotus.

29
BENEFIT OF DESKTOP DATABASE

 Desktop databases are inexpensive. You’ll find that most desktop solutions are available for around $100
(compared to thousands of dollars for their sever-based cousins). In fact, if you own a copy of Microsoft Office
Professional, you’re already a licensed owner of Microsoft Access.
 Desktop databases are user-friendly. Desktop DBMSs usually offer an easy-to-navigate graphical user interface.
 Desktop databases offer web solutions. Many modern desktop databases provide web functionality enabling you
to publish your data on the web in a static or dynamic fashion.

30
SERVER DATABASE

 A DBMS designed to be run in a client/server environment.

 Support database used by big organization.
 provides rich support for SQL and transactions.
 They are accessed through DBMS-based drivers.
 Example:- Oracle, Informix, IBM, DB/2, or Microsoft® SQL Server
 Benefits :-
 A database server performs complicated functions such as sorting, searching and indexing the server. This minimizes network traffic.
 Flexible data access
 Easy to manage
 Data security
 It allows synchronized access to data
31
USER OF DBMS
1. End user
 The end-users are the “clients” of the database, which has been designed and implemented and is
being maintained to serve their information needs. End-users can be classified according to the way
they use the system:
 Na¨ıve users : typically unaware of the DBMS. They are unsophisticated users who interact with the
system by invoking one of the application programs that have been written previouslyThey access the
database through specially written application programs that attempt to make the operations as simple as
possible. They invoke database operations by entering simple commands or choosing options from a menu.
This means that they do not need to know anything about the database or the DBMS. For example, the
checkout assistant at the local supermarket uses a bar code reader to find out the price of
the item.

 Sophisticated user : responsible for the physical realization of the database, including physical database
design and implementation, security and integrity control, maintenance of the operational system, and
ensuring satisfactory performance of the applications for users.
32
USER OF DBMS

2. Application programmer
 computer professionals who write application programs. Application programmers can choose from
many tools to develop user interfaces.
 Rapid application development (RAD) tools are tools that enable an application programmer to
construct forms and reports with minimal programming effort.

33
USER OF DBMS

3. Database administrator
 A person who has such central control over the system.
 responsible for the physical realization of the database, including physical database design and
implementation, security and integrity control, maintenance of the operational system, and ensuring
satisfactory performance of the applications for users.

34
REFERENCES

 Peter Rob, Carlos Coronel, (2009), Database System : Design, implementation and Management (Eight Edition),
Thomson Course Technology. (ISBN-13: 978-1-4239-0201-0 ISBN-10: 1-4239-0201-7)
 Peter Rob, Carlos Coronel, (2012), Database System : Design, implementation and Management (Ten Edition),
Thomson Course Technology. (ISBN-13: 978-1-4239-0201-0 ISBN-10: 1-4239-0201-7)
 Other internet resources

35