Chapter 2: The Database Development Process

Modern Database Management 7th Edition

Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden

2005 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 Draw simple data models
2005 by Prentice Hall
2

Chapter 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
2005 by Prentice Hall
3

Chapter 2

Figure 2-1 Segment from enterprise data model (Pine Valley Furniture Company) [simplified E-R diagram, repeat of figure 1.3] Enterprise data model describes the high-level entities in an organization and the relationship between these entities

Chapter 2

2005 by Prentice Hall

Information Systems Architecture (ISA)

Conceptual blueprint for organizations 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 (like fig 1.9) 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)
2005 by Prentice Hall
5

Chapter 2

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

2005 by Prentice Hall
6

Chapter 2

Information Systems Planning (Table 2-1)

Purpose: align information technology with organizations business strategies Three steps:
1. 2. 3.

Identify strategic planning factors Identify corporate planning objects Develop enterprise model

Chapter 2

2005 by Prentice Hall

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

Chapter 2

2005 by Prentice Hall

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
2005 by Prentice Hall
9

Chapter 2

Develop Enterprise Model

Functional decomposition

See Figure 2-2 See Figure 2-1 See Figure 2-3

2005 by Prentice Hall
10

Enterprise data model

Planning matrixes

Chapter 2

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

2005 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
2005 by Prentice Hall
12

Chapter 2

Example business function-todata entity matrix (Fig. 2-3)

Data Entity Types
Business Function (users) Business Planning Product Development Materials Management Order Fulfillment Order Shipment Sales Summarization Production Operations Finance and Accounting
Chapter 2

X X X X

2005 by Prentice Hall

Customer Product Raw Material Order Work Center Work Order Invoice Equipment Employee X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
13

Two Approaches to Database and IS Development

SDLC

System Development Life Cycle Detailed, well-planned development process Time-consuming, but comprehensive Long development cycle
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
2005 by Prentice Hall
14

Prototyping

Chapter 2

Systems Development Life Cycle (Figures 2-4, 2-5)

Project Identification and Selection Project Initiation and Planning Analysis

Logical Design Physical Design Implementation Maintenance

Chapter 2

2005 by Prentice Hall

15

Systems Development Life Cycle (cont.) (Figures 2-4, 2-5)

Project Project Identification Identification and and Selection Selection Project Initiation and Planning Analysis

Purpose --preliminary understanding Deliverable request for project

Logical Design Physical Design

Database activity enterprise modeling

Implementation Maintenance

Chapter 2

2005 by Prentice Hall

16

Systems Development Life Cycle (cont.) (figures 2-4, 2-5)

Project Identification and Selection Project Project Initiation Initiation and and Planning Planning

Purpose state business situation and solution Deliverable request for analysis

Analysis

Logical Design Physical Design

Database activity conceptual data modeling

Implementation Maintenance

Chapter 2

2005 by Prentice Hall

17

Systems Development Life Cycle (cont.) (figures 2-4, 2-5)

Project Identification and Selection Project Initiation and Planning

Purpose thorough analysis Deliverable functional system specifications

Analysis Analysis

Logical Design Physical Design

Database activity conceptual data modeling

Implementation Maintenance

Chapter 2

2005 by Prentice Hall

18

Systems Development Life Cycle (cont.) (figures 2-4, 2-5)

Project Identification and Selection Project Initiation and Planning

Purpose information requirements structure Deliverable detailed design specifications

Analysis

Logical Logical Design Design Physical Design

Database activity logical database design

Implementation Maintenance

Chapter 2

2005 by Prentice Hall

19

Systems Development Life Cycle (cont.) (figures 2-4, 2-5)

Project Identification and Selection Project Initiation and Planning Analysis

Purpose develop technology specs Deliverable program/data structures, technology purchases, organization redesigns

Logical Design Physical Physical Design Design

Database activity physical database design

Implementation Maintenance

Chapter 2

2005 by Prentice Hall

20

Systems Development Life Cycle (cont.) (figures 2-4, 2-5)

Project Identification and Selection Project Initiation and Planning Analysis

Purpose programming, testing, training, installation, documenting Deliverable operational programs, documentation, training materials

Logical Design Physical Design

Database activity database implementation

Implementation Implementation Maintenance

Chapter 2

2005 by Prentice Hall

21

Systems Development Life Cycle (cont.) (figures 2-4, 2-5)

Project Identification and Selection Project Initiation and Planning Analysis

Purpose monitor, repair, enhance Deliverable periodic audits

Logical Design Physical Design

Database activity database maintenance

Implementation Maintenance Maintenance

Chapter 2

2005 by Prentice Hall

22

Chapter 2

2005 by Prentice Hall

23

Chapter 2

2005 by Prentice Hall

24

Chapter 2

2005 by Prentice Hall

25

Chapter 2

2005 by Prentice Hall

26

Chapter 2

2005 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

2005 by Prentice Hall

28

CASE

Computer-Aided Software Engineering (CASE) software tools providing automated support for systems development Three database features:

Data modeling entity-relationship diagrams Code generation SQL code for table creation Repositories knowledge base of enterprise information
2005 by Prentice Hall
29

Chapter 2

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:

Incremental commitment review of systems development project after each development phase with rejustification after each phase
2005 by Prentice Hall
30

Validation of satisfactory progress Step back from detail to overall view Renew commitment of stakeholders

Chapter 2

Managing Projects: People Involved

Systems analysts Database analysts Users Programmers Database/data administrators Systems programmers, network administrators, testers, technical writers
2005 by Prentice Hall
31

Chapter 2

Figure 2-8a Gantt Chart

Shows time estimates of tasks

Chapter 2
2005 by Prentice Hall
32

Figure 2-8b PERT chart

Shows dependencies between tasks

Chapter 2
2005 by Prentice Hall
33

Database Schema

Physical Schema

Physical structures covered in chapters 5 and 6 E-R models covered in chapters 3 and 4 User Views Subsets of Conceptual Schema Can be determined from business-function/data entity matrices DBA determines schema for different users
2005 by Prentice Hall
34

Conceptual Schema

External Schema

Chapter 2

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

The internal schema is the underlying design and implementation

Chapter 2

2005 by Prentice Hall

35

Figure 2-11 Three-tiered client/server database architecture

Chapter 2

2005 by Prentice Hall

36

Pine Valley Furniture

Preliminary data model (Figure 2-12)

Chapter 2

2005 by Prentice Hall

37

Chapter 2

2005 by Prentice Hall

38