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

Chapter 2

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) 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)
2007 by Prentice Hall
5

Chapter 2

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

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

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

Organizational unitsdepartments Organizational locations Business functionsgroups of business processes Entity typesthe things we are trying to model for the database Information systemsapplication programs
2007 by Prentice Hall
9

Chapter 2

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

2007 by Prentice Hall
10

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

Chapter 2

Example business function-todata entity matrix

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
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
2007 by Prentice Hall
14

Prototyping

Chapter 2

Systems Development Life Cycle

Planning Analysis Logical Design Physical Design Implementation Maintenance

Chapter 2

2007 by Prentice Hall

15

Systems Development Life Cycle

Planning Planning Analysis Logical Design Physical Design

Purposepreliminary understanding Deliverablerequest for study

Database activity enterprise modeling and early conceptual data modeling Chapter 2

Implementation Maintenance

2007 by Prentice Hall

16

Systems Development Life Cycle

Planning

Purposethorough requirements analysis and structuring Deliverablefunctional system specifications Analysis Analysis
Logical Design Physical Design

Database activityThorough and integrated conceptual data modeling

Implementation Maintenance

Chapter 2

2007 by Prentice Hall

17

Systems Development Life Cycle

Planning Analysis Logical Design Logical Design Physical Design

Purposeinformation requirements elicitation and structure Deliverabledetailed design specifications

Database activity logical database design (transactions, forms, displays, views, data integrity and security) Chapter 2
2007 by Prentice Hall

Implementation Maintenance

18

Systems Development Life Cycle

Planning Analysis Logical Design

Purposedevelop technology and organizational specifications Deliverableprogram/data structures, technology purchases, organization redesigns

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.)
Planning Analysis Logical Design Physical Design

Purposeprogramming, testing, training, installation, documenting Deliverableoperational programs, documentation, training materials

Database activity database implementation, including coded programs, documentation, installation and conversion Chapter 2
2007 by Prentice Hall

Implementation Implementation Maintenance

20

Systems Development Life Cycle (see also Figures 2.4, 2.5) (cont.)
Planning Analysis Logical Design Physical Design

Purposemonitor, repair, enhance Deliverableperiodic audits

Database activity database maintenance, performance analysis and tuning, error corrections Chapter 2
2007 by Prentice Hall

Implementation Maintenance Maintenance

21

Prototyping Database Methodology

Chapter 2

2007 by Prentice Hall

22

Prototyping Database Methodology

Chapter 2

2007 by Prentice Hall

23

Prototyping Database Methodology

Chapter 2

2007 by Prentice Hall

24

Prototyping Database Methodology

Chapter 2

2007 by Prentice Hall

25

Prototyping Database Methodology

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
2007 by Prentice Hall
27

Chapter 2

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:

Incremental commitmentreview of systems development project after each development phase with rejustification after each phase
2007 by Prentice Hall
29

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

Chapter 2

Managing Projects: People Involved

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

Chapter 2

Database Schema

Physical Schema

Physical structurescovered in Chapters 5 and 6 E-R modelscovered 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
2007 by Prentice Hall
31

Conceptual Schema

External Schema

Chapter 2

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

Developing the three-tiered architecture

Chapter 2

2007 by Prentice Hall

33

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

Four relations (Pine Valley Furniture)

Chapter 2

2007 by Prentice Hall

36

Four relations (Pine Valley Furniture) (cont.)

Chapter 2

2007 by Prentice Hall

37