The Database Environment

and Development Process

Database Management Systems 1
(ITEDBASE1)

Objectives
Define terms
Name limitations of conventional file
processing
Explain advantages of databases
Identify costs and risks of databases
List components of database environment
Identify categories of database applications
Describe database system development life
cycle
Explain prototyping and agile development
approaches
Explain roles of individuals
Explain the three-schema architecture for

Definitions
Database: organized collection of
logically related data

Data: stored representations of

meaningful objects and events
Structured: numbers, text, dates
Unstructured: images, video, documents

Information: data processed to increase

knowledge in the person using the data
Metadata: data that describes the
properties and context of user data

Figure 1-1a Data in context

Context helps users understand

data
4

Figure 1-1b Summarized data

Graphical displays turn data into

useful information that managers
can use for decision making and
interpretation
5

Descriptions of the properties or

characteristics of the data, including data
types, field sizes, allowable values, and
data context
6

Disadvantages of File
Processing

Program-Data Dependence

All programs maintain metadata for each file they use

Duplication of Data
Different systems/programs have separate copies of the same
data

Limited Data Sharing

No centralized control of data

Lengthy Development Times

Programmers must design their own file formats

Excessive Program Maintenance

80% of information systems budget

Problems with Data

Dependency

Each application programmer must

maintain his/her own data
Each application program needs to
include code for the metadata of each file
Each application program must have its
own processing routines for reading,
inserting, updating, and deleting data
Lack of coordination and central control
Non-standard file formats

Duplicate Data

Problems with Data

Redundancy

Waste of space to have duplicate

data
Causes more maintenance
headaches
The biggest problem:
Data changes in one file could
cause inconsistencies
Compromises in data integrity

SOLUTION: The DATABASE Approach

Central repository of shared data

Data is managed by a controlling
agent
Stored in a standardized,
convenient form

Requires a Database Management System (DBMS

Database Management
A software system that is used to create, maintain, and
System

provide controlled access to user databases

Order Filing
System

Invoicing
System

Payroll
System

DBMS

Central database
Contains employee,
order, inventory,
pricing, and
customer data

DBMS manages data resources like an operating system manages

hardware resources

Advantages of The Database

Approach
Program-data independence
Planned data redundancy
Improved data consistency
Improved data sharing
Increased application development productivity
Enforcement of standards
Improved data quality
Improved data accessibility and responsiveness
Reduced program maintenance
Improved decision support

Costs and Risks of the Database Approach

New, specialized personnel
Installation and management cost and
complexity
Conversion costs
Need for explicit backup and recovery
Organizational conflict

Elements of the Database

Approach

Data models

Graphical system capturing nature and relationship of data

Enterprise Data Modelhigh-level entities and relationships for
the organization
Project Data Modelmore detailed view, matching data
structure in database or data warehouse

Entities
Noun form describing a person, place, object, event, or concept
Composed of attributes

Relationships
Between entities
Usually one-to-many (1:M) or many-to-many (M:N)

Relational Databases
Database technology involving tables (relations) representing
entities and primary/foreign keys representing relationships

Figure 1-5 Components of the Database

Environment

Components of the
Database Environment
CASE Toolscomputer-aided software engineering
Repositorycentralized storehouse of metadata
Database Management System (DBMS) software
for managing the database
Databasestorehouse of the data
Application Programssoftware using the data
User Interfacetext and graphical displays to users
Data/Database Administratorspersonnel
responsible for maintaining the database
System Developerspersonnel responsible for
designing databases and software
End Userspeople who use the applications and
databases

Two Approaches to Database

and IS Development
SDLC
System Development Life Cycle
Detailed, well-planned development process
Time-consuming, but comprehensive
Long development cycle

Prototyping
Rapid application development (RAD)
Cursory attempt at conceptual data modeling
Define database during development of initial
prototype
Repeat implementation and maintenance
activities with new prototype versions

Systems Development Life

Cycle
Planning
Analysis
Logical Design
Physical Design
Implementation
Maintenance

Systems Development Life Cycle (cont.)

Purposepreliminary understanding
Deliverablerequest for study

Planning
Planning
Analysis

Logical Design
Physical Design

Database activity
enterprise modeling
and early conceptual
data modeling

Implementation
Maintenance

Systems Development Life

Cycle (cont.)

Purposethorough requirements analysis

and structuring
Deliverablefunctional system specifications

Planning

Analysis
Analysis
Logical Design
Physical Design

Database activitythorough
and integrated conceptual
data modeling

Implementation
Maintenance

Systems Development Life

Cycle (cont.)

Purposeinformation requirements elicitation

and structure
Deliverabledetailed design specifications

Planning
Analysis

Logical Design
Logical
Design
Physical Design

Database activity
logical database design
(transactions, forms,
displays, views, data
integrity and security)

Implementation
Maintenance

Systems Development Life

Cycle (cont.)
Purposedevelop technology and
organizational specifications

Planning

Deliverableprogram/data
structures, technology purchases,
organization redesigns

Analysis
Logical Design

Physical
Design
Physical Design
Database activity
physical database design
(define database to DBMS,
physical data organization,
database processing programs)

Implementation
Maintenance

Systems Development Life

Cycle (cont.)

Purposeprogramming, testing,
training, installation, documenting

Planning
Analysis

Deliverableoperational programs,
documentation, training materials
Logical Design
Physical Design

Database activity
database implementation,
including coded programs,
documentation,
installation and conversion

Implementation
Implementation
Maintenance

Systems Development Life Cycle

(cont.)
Purposemonitor, repair, enhance

Planning

Deliverableperiodic audits

Analysis
Logical Design

Physical Design

Database activity
database maintenance,
performance analysis
and tuning, error
corrections

Implementation
Maintenance
Maintenance

Prototyping Database
Methodology
(Figure 1-8)

Prototyping Database
Methodology
(Figure 1-8) (cont.)

Prototyping Database
Methodology
(Figure 1-8) (cont.)

Prototyping Database
Methodology
(Figure 1-8) (cont.)

Prototyping Database
Methodology
(Figure 1-8) (cont.)

Database Schema
External Schema
User Views
Subsets of Conceptual Schema
Can be determined from business-function/data
entity matrices
DBA determines schema for different users

Conceptual Schema
E-R models

Internal Schema
Logical structures
Physical structures

Figure 1-9 Three-schema architecture

Different people
have different
views of the
databasethese
are the external
schema

The internal
schema is the
underlying
design and
implementation

Managing Projects
Project a planned undertaking
of related activities to reach an
objective that has a beginning
and an end
Initiated and planned in planning
stage of SDLC
Executed during analysis, design,
and implementation
Closed at the end of
implementation

Managing Projects:
People Involved

Business analysts
Systems analysts
Database analysts and data modelers
Data/Database administrators
Project managers
Users
Programmers
Other technical experts

Evolution of Database
Systems

Driven by four main objectives:

Need for program-data
independence reduced
maintenance
Desire to manage more complex
data types and structures
Ease of data access for less
technical personnel
Need for more powerful decision
support platforms

Figure 1-10a Evolution of database technologies

Figure 1-10b Database architectures

Figure 1-10b Database architectures (cont.)

Figure 1-10b Database architectures (cont.)

The Range of Database

Applications
Personal databases
Two-tier and N-tier Client/Server databases
Enterprise applications
Enterprise resource planning (ERP) systems
Data warehousing implementations

Figure 1-11 Two-tier database with local

area network

Figure 1-12 Three-tiered client/server database

architecture

Enterprise Database
Applications

Enterprise Resource Planning

(ERP)
Integrate all enterprise functions
(manufacturing, finance, sales,
marketing, inventory, accounting,
human resources)

Data Warehouse
Integrated decision support system
derived from various operational
databases

FIGURE 1-13 Computer

System for Pine Valley
Furniture Company

Summary
Database is an organized collection of
logically related data.
The approaches to data management are
file processing system and database
management system.
DBMS is a software system that is used to
create, maintain, and provide controlled
access to user databases.

Summary
Database applications can be arranged into
the following categories: personal, twotire, multitier, and enterprise databases.
The systems development life cycle can be
represented by five methodical steps: (1)
planning, (2) analysis, (3) design, (4)
implementation, and (5) maintenance.

Reference
Hoffer, J., Ramesh, V., Topi, H. (2013).
Modern Database Management 11th
Edition, Prentice Hall.