Chapter 2:
The Database
Development Process
Modern Database
Management
8th Edition
Jeffrey A. Hoffer, Mary B. Prescott,
Fred R. McFadden
2007 by Prentice Hall
Objectives
Definition of terms
Describe system development life cycle
Explain prototyping approach
Explain roles of individuals
Explain three-schema approach
Explain role of packaged data models
Explain three-tiered architectures
Explain scope of database design projects
Draw simple data models
Chapter 2
2007 by Prentice Hall
Enterprise Data Model
First step in database development
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 2
2007 by Prentice Hall
Figure 2-1 Segment from enterprise data model
Enterprise data model
describes the highlevel entities in an
organization and the
relationship between
these entities
Chapter 2
2007 by Prentice Hall
Information Systems
Architecture
(ISA)
Conceptual blueprint for organizations
desired information systems structure
Consists of:
Data (e.g. Enterprise Data Modelsimplified ER
Diagram)
Processesdata flow diagrams, process
decomposition, etc.
Data Networktopology diagram (like Fig 1-9)
Peoplepeople management using project
management tools (Gantt charts, etc.)
Events and points in time (when processes are
performed)
Reasons for events and rules (e.g., decision tables)
Chapter 2
2007 by Prentice Hall
Information Engineering
A data-oriented methodology to create
and maintain information systems
Top-down planninga generic IS planning
methodology for obtaining a broad
understanding of the IS needed by the
entire organization
Four steps to Top-Down planning:
Planning
Analysis
Design
Implementation
Chapter 2
2007 by Prentice Hall
Information Systems
Planning
(Table 2-1)
Purposealign information
technology with organizations
business strategies
Three steps:
1. Identify strategic planning factors
2. Identify corporate planning objects
3. Develop enterprise model
Chapter 2
2007 by Prentice Hall
Identify Strategic Planning
Factors (Table 2-2)
Organization goalswhat we hope to
accomplish
Critical success factorswhat MUST
work in order for us to survive
Problem areasweaknesses we now
have
Chapter 2
2007 by Prentice Hall
Identify Corporate Planning
Objects (Table 2-3)
Organizational unitsdepartments
Organizational locations
Business functionsgroups of business
processes
Entity typesthe things we are trying to
model for the database
Information systemsapplication
programs
Chapter 2
2007 by Prentice Hall
Develop Enterprise Model
Functional decomposition
Iterative process breaking system
description into finer and finer detail
Enterprise data model
Planning matrixes
Describe interrelationships
between planning objects
Chapter 2
2007 by Prentice Hall
10
Figure 2-2 Example of process decomposition of an
order fulfillment function (Pine Valley Furniture)
Decomposition = breaking
large tasks into smaller tasks
in a hierarchical structure
chart
Chapter 2
2007 by Prentice Hall
11
Planning Matrixes
Describe relationships between
planning objects in the organization
Types of matrixes:
Function-to-data entity
Location-to-function
Unit-to-function
IS-to-data entity
Supporting function-to-data entity
IS-to-business objective
Chapter 2
2007 by Prentice Hall
12
Example business functionto-data entity matrix (Fig. 23)
Chapter 2
2007 by Prentice Hall
13
SDLC
Two Approaches to
Database and IS
Development
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 2
2007 by Prentice Hall
14
Systems Development Life Cycle
(see also Figures 2.4, 2.5)
Planning
Analysis
Logical Design
Physical Design
Implementation
Maintenance
Chapter 2
2007 by Prentice Hall
15
Systems Development Life Cycle
(see also Figures 2.4, 2.5)
(cont.)
Purposepreliminary understanding
Deliverablerequest for study
Planning
Planning
Analysis
Logical Design
Physical Design
Database activity
enterprise modeling
and early conceptual
data modeling
Chapter 2
Implementation
Maintenance
2007 by Prentice Hall
16
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Purposethorough requirements analysis
and structuring
Deliverablefunctional system specifications
Planning
Analysis
Analysis
Logical Design
Physical Design
Database activityThorough
and integrated conceptual
data modeling
Chapter 2
2007 by Prentice Hall
Implementation
Maintenance
17
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (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)
Chapter 2
Implementation
Maintenance
2007 by Prentice Hall
18
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Purposedevelop technology and
organizational specifications
Deliverableprogram/data
structures, technology purchases,
organization redesigns
Planning
Analysis
Logical Design
Physical
Design
Physical Design
Database activity
physical database design
(define database to DBMS,
physical data organization,
database processing programs)
Chapter 2
2007 by Prentice Hall
Implementation
Maintenance
19
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Purposeprogramming, testing, training,
installation, documenting
Deliverableoperational programs,
documentation, training materials
Planning
Analysis
Logical Design
Physical Design
Database activity
database implementation,
including coded programs,
documentation,
installation and conversion
Chapter 2
Implementation
Implementation
Maintenance
2007 by Prentice Hall
20
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Purposemonitor, repair, enhance
Deliverableperiodic audits
Planning
Analysis
Logical Design
Physical Design
Database activity
database maintenance,
performance analysis
and tuning, error
corrections
Chapter 2
Implementation
Maintenance
Maintenance
2007 by Prentice Hall
21
Prototyping Database
Methodology
(Figure 2.6)
Chapter 2
2007 by Prentice Hall
22
Prototyping Database
Methodology
(Figure 2.6) (cont.)
Chapter 2
2007 by Prentice Hall
23
Prototyping Database
Methodology
(Figure 2.6) (cont.)
Chapter 2
2007 by Prentice Hall
24
Prototyping Database
Methodology
(Figure 2.6) (cont.)
Chapter 2
2007 by Prentice Hall
25
Prototyping Database
Methodology
(Figure 2.6) (cont.)
Chapter 2
2007 by Prentice Hall
26
CASE
Computer-Aided Software Engineering
(CASE)software tools providing automated
support for systems development
Three database features:
Data modelingdrawing entity-relationship
diagrams
Code generationSQL code for table creation
Repositoriesknowledge base of enterprise
information
Chapter 2
2007 by Prentice Hall
27
Packaged Data Models
Model components that can be purchased,
customized, and assembled into full-scale
data models
Advantages
Reduced development time
Higher model quality and reliability
Two types:
Universal data models
Industry-specific data models
Chapter 2
2007 by Prentice Hall
28
Managing Projects
Projecta planned undertaking of related
activities to reach an objective that has a
beginning and an end
Involves use of review points for:
Validation of satisfactory progress
Step back from detail to overall view
Renew commitment of stakeholders
Incremental commitmentreview of systems
development project after each development
phase with rejustification after each phase
Chapter 2
2007 by Prentice Hall
29
Managing Projects: People
Involved
Chapter 2
Business analysts
Systems analysts
Database analysts and data modelers
Users
Programmers
Database architects
Data administrators
Project managers
Other technical experts
2007 by Prentice Hall
30
Database Schema
Physical Schema
Conceptual Schema
Physical structurescovered in Chapters 5 and 6
E-R modelscovered in Chapters 3 and 4
External Schema
User Views
Subsets of Conceptual Schema
Can be determined from business-function/data
entity matrices
DBA determines schema for different users
Chapter 2
2007 by Prentice Hall
31
Figure 2-7 Three-schema architecture
Different people
have different
views of the
databasethese
are the external
schema
The internal
schema is the
underlying
design and
implementation
Chapter 2
2007 by Prentice Hall
32
Figure 2-8 Developing the three-tiered architecture
Chapter 2
2007 by Prentice Hall
33
Figure 2-9 Three-tiered client/server database architecture
Chapter 2
2007 by Prentice Hall
34
Pine Valley Furniture
Segment of project data model (Figure 2-11)
Chapter 2
2007 by Prentice Hall
35
Figure 2-12 Four relations (Pine Valley Furniture)
Chapter 2
2007 by Prentice Hall
36
Figure 2-12 Four relations (Pine Valley Furniture) (cont.)
Chapter 2
2007 by Prentice Hall
37
