0% found this document useful (0 votes)
37 views

Chapter 1 Fundamental of Database System Updated

Uploaded by

dawitthecreator
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
37 views

Chapter 1 Fundamental of Database System Updated

Uploaded by

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

1-1

Fundamental of Database system


1-2

Chapter One:
Introduction to Database System
What is database
Database management system and its components
Database design life cycle
Roles in Database Design and Use
Database Architecture
1-3
1. What is Database
 A very large integrated Collection of data.
 A database is an organized collection of structured information, or data, typically stored
electronically in a computer system.
 A database is usually controlled by a database management system (DBMS).
 Database management system(DBMS) – a powerful tool(software package) for creating
and managing large amounts of data efficiently and allowing it to persist over long periods
of time, safely.
 Data management involves both definition and the manipulation of the data
 So the term database refers to a collection of data that is managed by a DBMS.
 Thus the DB course is about:
 How to organize data ;Supporting multiple users; Efficient and effective data

retrieval ;Secured and reliable storage of data; Maintaining consistent data


1-4

 What is a Database?- It is a collection of related facts


Filing Cabinet Hard disk full of data

Diary

Library DBMS + Database


=
Database System
1-5

 Data management passes through the different levels of development. The common are
three
1. Manual Approach
Data storage and retrieval follows the primitive and traditional way of information handling
where cards and paper are used for the purpose.
Example
 Files for as many event and objects as the organization has are used to store information.

 Each of the files containing various kinds of information is labelled and stored in one ore

more cabinets.
 The cabinets could be kept in safe places for security purpose based on the sensitivity of

the information contained in it.


 Insertion and retrieval is done by searching first for the right cabinet then for the right the

file then the information.


1-6

• Limitations of the Manual approach


 Prone to error

 Difficult to update, retrieve, integrate

 You have the data but it is difficult to compile the information

 Cross referencing is difficult

2. Traditional File Based Approach


 Uses computer for data processing to the business community, via the device for data
storage and processing increase.
 File based systems were an early attempt to computerize the manual filing system.

 This approach is the decentralized computerized data handling method.

 Since every application defines and manages its own data, the system is subjected

to serious data duplication problem.


1-7

Limitations of the Traditional File Based approach


Limited data sharing- every application maintains its own data.
Duplication or redundancy of data (money, time, cost and loss of data integrity)
The problem in “update anomalies”. three types of anomalies;
 Modification Anomalies: a problem experienced when one or more data value is
modified on one application program but not on others containing the same data
set.
 Deletion Anomalies: a problem encountered where one record set is deleted from

one application but remain untouched in other application programs.


 Insertion Anomalies: a problem experienced when ever there is new data item to be

recorded, and the recording is not made in all the applications.


1-8

3. Database Approach
 That database systems is presented for user with a view of data organized as tables
called relations.
 IT emphasizes the integration and sharing of data throughout the organization.
 Database is a collection of logically related data where these logically related data
comprises entities, attributes, relationships, and business rules of an organization's
information.
 Database is deigned once and used simultaneously by many users.
1-9
Benefits of the database approach
 Data can be shared: two or more users can access and use same data instead of storing data
in redundant manner for each user.
 Improved accessibility of data: by using structured query languages, the users can easily
access data without programming experience.
 Quality data can be maintained: the different integrity constraints in the database approach
will maintain the quality leading to better decision making
 Integrity can be maintained: data at different applications will be integrated together with
additional constraints to facilitate validity and consistency of shared data resource.
 Security measures can be enforced: the shared data can be secured by having different levels
of clearance
 Speed: data storage and retrieval is fast
 Centralized information control: since relevant data in the organization will be stored at one
repository, it can be controlled and managed at the central level.
1-10

 Limitations and risk of Database Approach


 Complexity in designing and managing data

 The cost and risk during conversion from the old to the new system

 High cost to be incurred to develop and maintain the system

 Complex backup and recovery services from the users perspective

 Reduced performance due to centralization and data independency

 High impact on the system when failure occurs to the central system.
1-11
2. Database Management System (DBMS)

 A full scale DBMS should at least have the following services to provide to the user
i. Data storage, retrieval and update in the database
ii. A user accessible catalogue
iii. Transaction support service: ALL or NONE transaction, which minimize data
inconsistency.
iv. Concurrency Control Services: access and update on the database by different users
simultaneously should be implemented correctly.
v. Recovery Services: a mechanism for recovering the database after a failure must be
available.
vi. Authorization Services (Security): must support the implementation of access and
authorization service to database administrator and users.
vii. Integrity Services: rules about data and the change that took place on the data,
correctness and consistency of stored data, and quality of data based on business
constraints.
viii. Services to promote data independency between the data and the application
1-12
Database Languages
 DBMS should have facilities to define the database, manipulate the content of the database
and control the database.
 It provides the following facilities:
 Data Definition Language (DDL):

• Language used to define each data element required by the organization.


• Commands for setting up schema or database
• These commands are used to setup a database, create, delete and alter table with
the facility of handling constraints
 Data Manipulation Language (DML):

• Is a core command used by end-users and programmers to store, retrieve, and


access the data in the database e.g. SQL
1-13

 Taking a DBMS as a system,To design and use a database, there will be the
interaction or integration of Hardware, Software, Data, Procedure and People.
i. Hardware: These components are comprised of various types of personal
computers, mainframe or any server computers to be used in multi-user system,
network infrastructure, and other peripherals required in the system.
ii. Software: are collection of commands and programs used to manipulate the
hardware to perform a function. Like the DBMS software, application programs,
operating systems, network software, language software and other relevant
software.
iii. Procedure: this is the rules and regulations on how to design and use a database.
 It includes procedures like how to log on to the DBMS, how to start and stop

transaction, how to make backup…


1-14

iv. Data:
 Data is the most important component to the user of the database.

 There are two categories of data in any database system: that is Operational and

Metadata.
• Operational data is the data actually stored in the system to be used by the user.
• Metadata is the data that is used to store information about the database itself.
 The structure of the data in the database is called the schema, which is composed of

the Entities, Properties of entities, and relationship between entities and business
constraints.
v. People:
this component is composed of the people in the organization that are responsible or play
a role in designing, implementing, managing, administering and using the resources in
the database.
1-15
3. Database Development Life Cycle (DDLC)
 Major steps in database design are:
i. Planning: that is identifying information gap in an organization and propose a
database solution to solve the problem.
ii. Analysis: that concentrates more on fact finding about the problem or the opportunity.
 Feasibility analysis, requirement determination and structuring, and selection of best
design method are also performed at this phase.
iii. Design:The phase is further divided into three sub-phases.
a. Conceptual Design: concise description of the data, data type, relationship
between data and constraints on the data.
» There is no implementation or physical detail consideration.

» Used to elicit and structure all information requirements


1-16

b. Logical Design: a higher level conceptual abstraction with selected specific data
model to implement the data structure.
» It is particular DBMS independent and with no other physical considerations.

c. Physical Design: physical implementation of the logical design of the database


with respect to internal storage and file structure of the database for the selected
DBMS.
» To develop all technology and organizational specification.

iv. Implementation: the testing and deployment of the designed database for use.
v. Operation and Support: administering and maintaining the operation of the database
system and providing support to users.
1-17
5. Roles in Database Design and Use
 There are group of roles played by different stakeholders of the designing and operation of
a database system. These are:
1. Database Administrator (DBA)
Responsible to oversee, control and manage the database resources
Authorizing access to the database & Involves in all steps of database development.

Coordinating and monitoring the use of the database.

Accountable for problems like poor security, poor performance of the system.

2. Database Designer (DBD)


Identifies the data to be stored and choose the appropriate structures to represent and store
the data.
Should understand the user requirement and should choose how the user views the
database.
Involve on the design phase before the implementation of the database system.
1-18

3. Application Programmer and Systems Analyst


 System analyst determines the user requirement and how the user wants to view the

database.
 The application programmer implements these specifications as programs; code, test,

debug, document and maintain the application program.


 The application programmer determines the interface on how to retrieve, insert,

update and delete data in the database.


 The application could use any high level programming language according to the

availability, the facility and the required service.


4. End Users
 Workers, whose job requires accessing the database frequently for various purposes,

there are different group of users in this category. Like Naïve Users and
Sophisticated Users.
1-19
Example of a Database
Part of a UNIVERSITY environment. Information concerning students, courses, and
grades in a university environment.
• Some mini-world entities:
• STUDENTs

• COURSEs

• SECTIONs (of COURSEs)

• DEPARTMENTs

• INSTRUCTORs

. ome mini-world relationships:


S
– SECTIONs are of specific COURSEs
– STUDENTs take SECTIONs
– COURSEs have prerequisite COURSEs
– INSTRUCTORs teach SECTIONs
– COURSEs are offered by DEPARTMENTs
– STUDENTs major in DEPARTMENTs
6-20
1-21
1-22
Data Abstraction(Categories of data models)
 Data can be described at three levels of abstraction
 Physical schema
 The lowest level schema

 Describes how data are stored and indexed

 Conceptual (or logical) schema


 What (not how) data are stored

 Describes data in terms of the data model

 External (or view) schema


 The highest level schema

 Describes how some users access the data

 There can be many different views


1-23
Levels of Abstraction

View 1 View 2 View 3

Conceptual Schema

Physical Schema

DB
1-24
Typical DBMS Structure/Database System

DBMS
Query Evaluation

Transaction File and Access Code


and Recovery
Buffer Manager
Lock Manager
Manager Disk Space Manager

Database
1-25
Database Components(Structure)
 Disk space (storage) manager – responsible for interaction with the OS file system.
 Buffer manager – responsible for bringing pages into main memory from disk.
 File and access code- allows the query evaluation system to request data from lower
levels
 Query evaluation – most modern DBMSs will optimize queries
 Transaction lock manager – responsible for allowing concurrent access
 Recovery manager – responsible for maintaining a log and restoring the system after a
crash.
1-26
Database System Architecture
i. Centralized and Client-Server Architectures
• Centralized DBMS: combines everything into single system including- DBMS
software, hardware, application programs and user interface processing software.
• it includes the following three things:

A. Specialized Servers with Specialized functions:


• File Servers
• Printer Servers
• Web Servers
• E-mail Servers
1-27

B. Clients:
• Provide appropriate interfaces and a client-version of the system to access and utilize the server
resources.
• Clients maybe diskless machines or PCs or Workstations with disks with only the client software
installed.
• Connected to the servers via some form of a network.
(LAN: local area network, wireless network, etc.)
C. DBMS Server
• Provides database query and transaction services to the clients
• Sometimes called query and transaction servers
1-28

ii. Two Tier Client-Server Architecture


• User Interface Programs and Application Programs run on the client side
• A client program may connect to several DBMSs.

Physical two-tier client-server architecture


1-29
iii. Three Tier Client-Server Architecture
• Common for Web applications
• Intermediate Layer called Application Server or Web Server:
• stores the web connectivity software and the rules and business logic (constraints) part of

the application used to access the right amount of data from the database server
• acts like a conduit for sending partially processed data between the database server and

the client.
• Additional Features- Security:
• encrypt the data at the server before transmission

• decrypt data at the client


1-30

Thanks!!!

You might also like