CHAPTER 1:
THE DATABASE ENVIRONMENT AND
DEVELOPMENT PROCESS
Modern Database Management
12th Edition
Jeff Hoffer, Ramesh Venkataraman,
Heikki Topi
Copyright © 2016 Pearson Education, Inc.
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-2
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-3
Figure 1-1a Data in context
Context helps users understand data
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-4
Figure 1-1b Summarized data
Graphical displays turn data into useful
information that managers can use for
decision making and interpretation
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-5
Descriptions of the properties or characteristics of the
data, including data types, field sizes, allowable
values, and data context
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-7
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-8
Duplicate Data
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-9
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-10
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)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-11
DATABASE MANAGEMENT SYSTEM
■ A software system that is used to create, maintain, and provide
controlled access to user databases
Order Filing
System
Invoicing Central database
DBMS
System
Contains employee,
order, inventory,
Payroll pricing, and
customer data
System
DBMS manages data resources like an operating system manages hardware resources
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-12
ELEMENTS OF THE DATABASE
APPROACH
Data models
Graphical diagram capturing nature and relationship of
data
Enterprise Data Model–high-level entities and
relationships for the organization
Project Data Model–more 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), but
could also be one-to-one (1:1)
Relational Databases
Database technology involving tables (relations)
representing entities and primary/foreign keys
Chapterrepresenting
1 relationships
Copyright © 2016 Pearson Education, Inc. 1-13
Figure 1-3 Comparison of enterprise and project level data models
Segment of an enterprise data model
Segment of a project-level data model
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-14
One customer
may place many
orders, but each
order is placed by
a single customer
🡪 One-to-many
relationship
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-15
One order has many
order lines; each order
line is associated with
a single order
🡪 One-to-many
relationship
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-16
One product can
be in many
order lines, each
order line refers
to a single
product
🡪 One-to-many
relationship
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-17
Therefore, one
order involves
many products
and one product is
involved in many
orders
🡪 Many-to-many
relationship
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-18
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-19
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-20
Figure 1-5 Components of the database environment
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-21
COMPONENTS OF THE
DATABASE ENVIRONMENT
Data modeling and design tools -- automated tools used
to design databases and application programs
Repository–centralized storehouse of metadata
Database Management System (DBMS) –software for
managing the database
Database–storehouse of the data
Application Programs–software using the data
User Interface–text, graphical displays, menus, etc. for
user
Data/Database Administrators–personnel responsible
for maintaining the database
System Developers–personnel responsible for designing
databases and software
End Users–people who use the applications and
databases
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-22
ENTERPRISE DATA MODEL
First step in the database development process
Specifies scope and general content
Overall picture of organizational data at high level
of abstraction
Entity-relationship diagram
Descriptions of entity types
Relationships between entities
Business rules
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-23
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-24
SYSTEMS DEVELOPMENT LIFE CYCLE
(SEE ALSO FIGURE 1-7)
Planning
Analysis
Logical Design
Physical Design
Implementation
Maintenance
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-25
SYSTEMS DEVELOPMENT LIFE CYCLE
(SEE ALSO FIGURE 1-7) (CONT.)
Planning
Planning Purpose–preliminary understanding
Deliverable–request for study
Analysis
Logical Design
Physical Design
Database activity– Implementation
enterprise modeling and
early conceptual data
Maintenance
modeling
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-26
SYSTEMS DEVELOPMENT LIFE CYCLE
(SEE ALSO FIGURE 1-7) (CONT.)
Purpose–thorough requirements analysis and
Planning structuring
Deliverable–functional system specifications
Analysis
Analysis
Logical Design
Physical Design
Database activity–thorough Implementation
and integrated conceptual
data modeling
Maintenance
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-27
SYSTEMS DEVELOPMENT LIFE CYCLE
(SEE ALSO FIGURE 1-7) (CONT.)
Purpose–information requirements elicitation
Planning and structure
Deliverable–detailed design specifications
Analysis
Logical Design
Logical Design
Physical Design
Database activity– Implementation
logical database design
(transactions, forms,
Maintenance
displays, views, data
integrity and security)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-28
SYSTEMS DEVELOPMENT LIFE CYCLE
(SEE ALSO FIGURE 1-7) (CONT.)
Purpose–develop technology and
Planning organizational specifications
Analysis
Deliverable–program/data
structures, technology purchases,
organization redesigns
Logical Design
Physical Design
Physical Design
Database activity– Implementation
physical database design (define
database to DBMS, physical
Maintenance
data organization, database
processing programs)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-29
SYSTEMS DEVELOPMENT LIFE CYCLE
(SEE ALSO FIGURE 1-7) (CONT.)
Purpose–programming, testing,
Planning training, installation, documenting
Analysis Deliverable–operational programs,
documentation, training materials
Logical Design
Physical Design
Database activity–
database implementation, Implementation
Implementation
including coded programs,
documentation, Maintenance
installation and conversion
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-30
SYSTEMS DEVELOPMENT LIFE CYCLE
(SEE ALSO FIGURE 1-7) (CONT.)
Planning Purpose–monitor, repair, enhance
Deliverable–periodic audits
Analysis
Logical Design
Physical Design
Database activity–
database maintenance, Implementation
performance analysis
and tuning, error Maintenance
Maintenance
corrections
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-31
