Chapter 1:
The Database Environment and
Development Process
Modern Database Management
Jeff Hoffer, Ramesh Venkataraman,
Heikki Topi
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-1
Objectives / Self-study outline
Define terms (Slides #3-6)
Name limitations of conventional file processing
Explain advantages of databases
Identify costs and risks of databases
Elements of the Database Approach (Slides #12-20)
List components of database environment (Slide #24)
Enterprise data model (Slides #25-26)
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 (Slides #40-41)
Running example in the book (Slides #53-55)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-2 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
of the person using the data
Metadata: data that describes the properties and
context of user data – P.7 @ top
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-3 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,
pricing, and
Payroll
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 (1)
• Data models
– Graphical system capturing nature and
relationship of data
1.Enterprise Data Model–high-level entities
and relationships for the organization
2.Project Data Model–more detailed view,
matching data structure in database or data
warehouse
• Entities – we met these concepts Week 1
– Noun form describing a person, place,
object, event, or concept
– Composed of attributes
UnderstandCopyright
Chapter 1 entity© 2016
type vs entity
Pearson instance
Education, Inc. 1-13
Elements of the Database Approach (2)
• 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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-14
Fig 1-3 Comparison of enterprise and project level data models
Segment of an enterprise data model
high-level entities and relationships
Segment of a project-level data model
detailed view, matching data structure
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-15 15
Note the expression of the relationship
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-16
Note the expression of the relationship
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-17
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-18
Therefore, one
order involves
many products
and one product is
involved in many
orders
Many-to-many
relationship
A many-to-many relationship can be “decomposed” to two 1-M
relationships
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-19
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-20
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-21
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
on data definitions, formats and coding, rights to
update…
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-22
Figure 1-5 Components of the database environment
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-23
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-24
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 (ERD)
Descriptions of entity types
Relationships between entities
Business rules
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-25
FIGURE 1-6 Example business function-to-data entity matrix
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-26
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-27
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-28
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
Maintenance
data modeling
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-29
Systems Development Life Cycle
(see also Figure 1-7) (cont.)
Purpose–thorough requirements analysis
Planning and 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-30
Systems Development Life Cycle
(see also Figure 1-7) (cont.)
Purpose–information requirements elicitation
Planning and structure
Deliverable–detailed design specifications
Analysis
Logical
Logical Design
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-31
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,
Maintenance
physical data organization,
database processing programs)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-32
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-33
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-34
Prototyping Database Methodology
(Figure 1-8)
Prototyping is a
classical Rapid
Application
Development
(RAD) approach
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-35
Prototyping Database Methodology
(Figure 1-8)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-36
Prototyping Database Methodology
(Figure 1-8)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-37
Prototyping Database Methodology
(Figure 1-8)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-38
Prototyping Database Methodology
(Figure 1-8)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-39
Database Schema
External Schema
Can be determined from business-function/data entity
matrices (Fig 1-6)
Enterprise model + User Views
During the Analysis and Logical Design phases
Conceptual Schema
E-R models–covered in Chapters 2 and 3
A single, coherent definition of enterprise’s data
The view of data architect or data admin
During the Analysis phase
Internal Schema
Logical structures–covered in Chapter 4
Physical structures–covered in Chapter 5
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-40
Figure 1-9 Three-schema architecture
Different people
have different
views of the
database…these
are the external
schema
The internal
schema is the
underlying
design and
implementation
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-41
Managing People and 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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-42
Managing Projects:
People Involved
Business analysts
Systems analysts
Database analysts and data modelers
Users
Programmers
Database architects
Data administrators
Project managers
Other technical experts
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-43
Figure 1-10a Evolution of database technologies
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-44
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-45
Figure 1-10b Database architectures
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-46
Figure 1-10b Database architectures (cont.)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-47
Figure 1-10b Database architectures (cont.)
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-48
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-49
Figure 1-11 Multi-tiered client/server database
architecture
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-50
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
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-51
FIGURE 1-13 Computer
System for Pine Valley
Furniture Company
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-52
FIG 1-14 PRELIMINARY DATA MODEL
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-53 53
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-54
FIGURE 1-15 Project data model
for Home Office product line
marketing support system
Chapter 1 Copyright © 2016 Pearson Education, Inc. 1-55
