DATABASE PRINCIPLES: FUNDAMENTALS OF

DESIGN, IMPLEMENTATIONS AND

MANAGEMENT

Stephen Morris, Keeley Crockett, Peter Rob and Carlos Coronel

CHAPTER 1
DATABASE SYSTEMS
Lecture 1
T: 051 401 2754 [email protected] www.ufs.ac.za/it
IN THIS LECTURE, YOU WILL LEARN

• About flaws in file system data management

• What the database system’s main
components are and how a database system
differs from a file system
• The main functions of a database
management system (DBMS)
HISTORICAL ROOTS: FILES AND DATA PROCESSING

• Managing data with file systems is out of date,

there are several reasons for studying them in
some detail:
– Understanding file system characteristics
makes database design easier to understand
– Awareness of problems with file systems
helps prevent similar problems in DBMS
– Knowledge of file systems is helpful if you
plan to convert an out of date file system to a
DBMS.
HISTORICAL ROOTS: FILES AND DATA PROCESSING (CONTINUED)

Manual File systems:

• In the recent past, a manager of almost any small organization was able to
keep track of necessary data by using a manual file system.
• Such file system was composed of a collection of file folders kept in file
cabinet.
• Organization within folders based on data’s expected use (content of each
file was logically related)
– E.g. a file folder in a doctor’s folder office might contain patient data, one
file folder for each patient. All of the data in that file folder would describe
only that particular patient’s medical history.
– A personal manager might organize personnel data by category of
employment ( e.g. clerical, technical, or sales)
• Manual system is only adequate for small amounts of data with few reporting
requirements
– Problem - Finding and using data in growing collections of file folders
became time-consuming and difficult to manage.
HISTORICAL ROOTS: FILES AND DATA PROCESSING (CONTINUED)

Conversion from manual to computer system:

• Could be technically complex.
• requiring hiring of data processing (DP)
specialists.
HISTORICAL ROOTS: FILES AND DATA
PROCESSING (CONTINUED) FIGURE 1.3
• Cotents of the CUSTOMER file
HISTORICAL ROOTS: FILES AND DATA PROCESSING (CONTINUED)
HISTORICAL ROOTS: FILES AND DATA PROCESSING (CONTINUED)

• Using the CUSTOMER file’s contents, the DP

specialist wrote programs for reports:
– Monthly summaries of types and amounts of
insurance sold by agents
– Monthly reports about which customers
should be contacted for renewal
– Reports that analyzed ratios of insurance
types sold by agent
– Customer contact letters summarizing
coverage
HISTORICAL ROOTS: FILES AND DATA PROCESSING (CONTINUED)

• Other departments requested databases be

written for them
– SALES database created for sales
department
– AGENT database created for personnel
department
EXAMPLE OF EARLY DATABASE DESIGN (CONTINUED)

• As system grew, demand for DP’s

programming skills grew
• Additional programmers hired
• DP specialist evolved into DP manager,
supervising a DP department
• Primary activity of department (and DP
manager) remained programming
PROBLEMS WITH FILE SYSTEM
DATA MANAGEMENT

• Every task requires extensive programming in

a third-generation language (3GL)
– Programmer must specify task and how it
must be done
• Modern databases use fourth-generation
languages (4GL)
– Allow users to specify what must be done
without specifying how it is to be done
PROBLEMS WITH FILE SYSTEM
DATA MANAGEMENT
FILE SYSTEM LIMITATIONS
• Limitations of file system data management:
– requires extensive programming
– system administration complex and difficult
– making changes to existing structures is difficult
– security features are likely to be inadequate
– independent files tend to contain redundant data
STRUCTURAL AND DATA DEPENDENCE
• Structural dependence
– Access to a file depends on its structure
• Structural independence
– Exists when it is possible to make changes in the file structure
without affecting the application program’s ability to access the data.
• Data dependence
– Exist when all data access programs are subject to change when any
of the file’s data storage characteristics change (that is, changing the
data type)
• Data independence
– Exists when its possible to make changes in the data storage
characteristics without affecting the application program’s ability to
access the data
• Logical data format
– How the human being views the data
• Physical data format
– How the computer “sees” the data
FIELD DEFINITIONS AND NAMING CONVENTIONS

• Selecting proper field names is important

– E.g. make sure that the field names are
reasonably descriptive.
• With proper naming conventions, the file
structure becomes self-documenting.
– For instance by simply looking at the field
names, you determine which files the fields
belong to and what information the fields
are likely to contain.
FIELD DEFINITIONS AND NAMING
CONVENTIONS (CONTINUED)
DATA REDUNDANCY
• Data redundancy exists when the same data are stored
unnecessarily at different places.
• Uncontrolled data redundancy results in data
inconsistency
– Exits when different and conflicting versions of the
same data appear in different places
• There is poor data security
• Data entry errors are more likely to occur when complex
entries are made in several different files and/or recur
frequently in one or more files
• Data anomalies develop when required changes in
redundant data are not made successfully
DATA REDUNDANCY
• Types of data anomalies:
– Update anomalies
• Occur when changes must be made to
existing records
– Insertion anomalies
• Occur when entering new records
– Deletion anomalies
• Occur when deleting records
DATABASE SYSTEMS
• File system
– Traditional file system has many separate
and unrelated files
• Database
– Consists of logically related data stored in
a single logical data repository
DATABASE SYSTEMS
THE DATABASE SYSTEM ENVIRONMENT

• Database system is composed of five main parts:

– Hardware
– Software
• Operating system software
• DBMS software
• Application programs and utility software
– People
• System administrators, database administrators, database
designers, systems analysts and programmers and end users
– Procedures
• Instructions and rules that govern the design and use of the
database system
– Data
• Check Page 22 to 23
DBMS FUNCTIONS
• DBMS performs functions that guarantee
integrity and consistency of data, namely:
– Data dictionary management
• defines data elements and their
relationships
– Data storage management
• stores data and related data entry forms,
report definitions, etc.
DBMS FUNCTIONS (CONTINUED)
– Data transformation and presentation
• translates logical requests into
commands to physically locate and
retrieve the requested data
– Security management
• enforces user security and data privacy
within database
DBMS FUNCTIONS (CONTINUED)
– Multiuser access control
• uses sophisticated algorithms to ensure
multiple users can access the database
concurrently without compromising the
integrity of the database
– Backup and recovery management
• provides backup and data recovery
procedures
– Data integrity management
• promotes and enforces integrity rules
DBMS FUNCTIONS (CONTINUED)
– Database access languages and
application programming interfaces
• provide data access through a query
language such as SQL
– Database communication interfaces
• allow database to accept end-user
requests via multiple, different network
environments, for example a browser
SUMMARY
• Data are raw facts. Information is the result of
processing data to reveal its meaning.
• To implement and manage a database, use a DBMS.
• Database design defines the database structure.
• A well-designed database facilitates data
management and generates accurate and valuable
information.
• A poorly designed database can lead to bad decision
making, and bad decision making can lead to the
failure of an organization.
SUMMARY (CONTINUED)
• Databases were preceded by file systems.
• Limitations of file system data management:
– requires extensive programming
– system administration complex and difficult
– making changes to existing structures is difficult
– security features are likely to be inadequate
– independent files tend to contain redundant data
• DBMS’s were developed to address file systems’
inherent weaknesses