The Database Development

Process

1
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

2
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

3
Figure 2-1 Segment from enterprise data model

Enterprise data model

describes the
high-level entities in
an organization and
the relationship
between these entities
Information Systems Architecture
(ISA)
□ Conceptual blueprint for organization’s
desired information systems structure
□ Consists of:
■ Data (e.g. Enterprise Data Model–simplified ER
Diagram)
■ Processes – data flow diagrams, process
decomposition, etc.
■ Data Network – topology diagram
■ People – people 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)
5
Information Engineering
□ A data-oriented methodology to create
and maintain information systems
□ Top-down planning–a 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

6
 Information Systems Planning
(Table 2-1)

□ Purpose–align information technology

with organization’s business
strategies
□ Three steps:
1. Identify strategic planning factors
2. Identify corporate planning objects
3. Develop enterprise model

7
Identify Strategic Planning
Factors (Table 2-2)

□ Organization goals–what we hope to

accomplish
□ Critical success factors–what MUST
work in order for us to survive
□ Problem areas–weaknesses we now
have

8
Identify Corporate Planning
Objects (Table 2-3)

□ Organizational units–departments
□ Organizational locations
□ Business functions–groups of business
processes
□ Entity types–the things we are trying
to model for the database
□ Information systems–application
programs
9
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

10
 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
11
Systems Development Life Cycle
(see also Figures 2.4, 2.5)

Planning

Analysis

Logical Design

Physical Design

Implementation

Maintenance

12
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Purpose–preliminary understanding
Deliverable–request for study
Planning
Planning

Analysis

Logical Design

Database activity– Physical Design

enterprise modeling and
early conceptual data Implementation
modeling
Maintenance
13
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Purpose–thorough requirements analysis and
Planning structuring
Deliverable–functional system specifications
Analysis
Analysis

Logical Design

Physical Design

Database activity–Thorough
and integrated conceptual Implementation
data modeling
Maintenance

14
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (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,
displays, views, data Maintenance
integrity and security)
15
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Purpose–develop technology and
Planning organizational specifications
Deliverable–program/data
Analysis 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)
16
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (cont.)
Purpose–programming, testing, training,
Planning installation, documenting
Deliverable–operational programs,
Analysis documentation, training materials

Logical Design

Physical Design

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

17
Systems Development Life Cycle
(see also Figures 2.4, 2.5) (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

18
Prototyping Database Methodology
Prototyping Database Methodology
(Figure 2.6) (cont.)
Prototyping Database Methodology
(Figure 2.6) (cont.)

21
Prototyping Database Methodology
(Figure 2.6) (cont.)
Prototyping Database Methodology
(Figure 2.6) (cont.)

23
 CASE
□ Computer-Aided Software Engineering
(CASE)–software tools providing
automated support for systems
development
□ Three database features:
■ Data modeling–drawing entity-relationship
diagrams
■ Code generation–SQL code for table creation
■ Repositories–knowledge base of enterprise
information
24
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

25
Managing Projects

□ Project–a 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 commitment–review of
systems development project after
each development phase with
rejustification after each phase
26
Managing Projects: People Involved

□ Business analysts
□ Systems analysts
□ Database analysts and data modelers
□ Users
□ Programmers
□ Database architects
□ Data administrators
□ Project managers
□ Other technical experts
27
Database Schema
□ Physical Schema
■ Physical structures–covered in Chapters 5 and
6
□ Conceptual Schema
■ E-R models–covered 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

28
 Figure 2-7 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
Figure 2-8 Developing the three-tiered architecture

30
Figure 2-9 Three-tiered client/server database architecture

31
Pine Valley Furniture

Segment of project data model (Figure 2-11)

32
Figure 2-12 Four relations (Pine Valley Furniture)

33
Figure 2-12 Four relations (Pine Valley Furniture) (cont.)

34