Lecture 9

Chapter 2: The Database Development Process

Modern Database Management 9th Edition

Jeffrey A. Hoffer, Mary B. Prescott,

Heikki Topi

Presentation Adapted by Dr. Mahmoud Youssef

2009 Pearson Education, Inc. Publishing as Prentice Hall
1

Objectives

Definition of terms Describe system development life cycle Explain prototyping approach Explain agile software development 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

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

Advantages of the Database Approach I

Program-data independence Planned data redundancy (possibly to improve efficiency) Improved data consistency Improved data sharing Increased application development productivity Enforcement of standards (e.g., SQL language)
3

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

Advantages of the Database Approach II

Improved data quality (data types which is part of the metadata enforce what contents are accepted) Improved data accessibility and responsiveness (e.g., through indexes) Reduced program maintenance Improved decision support

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

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

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

Figure 1-5 Components of the Database Environment

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

Components of the Database Environment

CASE Toolscomputer-aided software engineering Repositorycentralized storehouse of metadata Database Management System (DBMS) software for managing the database Databasestorehouse of the data Application Programssoftware using the data User Interfacetext and graphical displays to users Data/Database Administratorspersonnel responsible for maintaining the database System Developerspersonnel responsible for designing databases and software End Userspeople who use the applications and databases
7

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

The Range of Database Applications

Personal databases Workgroup databases Departmental/divisional databases Enterprise database

Enterprise resource planning (ERP) systems Data warehousing implementations

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

Table 1-6 Summary of Database Applications

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

10

Figure 1-7 Workgroup database with wireless local area network

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

11

Enterprise Database Applications

Enterprise Resource Planning (ERP)

Integrate all enterprise functions (manufacturing, finance, sales, marketing, inventory, accounting, human resources) Integrated decision support system derived from various operational databases

Data Warehouse

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

12

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
13

Chapter 1 2009 Pearson Education, Inc. Publishing as 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 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

14

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 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

15

Database Schema

External Schema

User Views Subsets of Conceptual Schema Can be determined from business-function/data entity matrices DBA determines schema for different users
E-R modelscovered in Chapters 3 and 4 Logical structurescovered in Chapter 5 Physical structurescovered in Chapter 6
16

Conceptual Schema

Internal Schema

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

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 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

17

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

18

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

19

Pine Valley Furniture

Segment of project data model (Figure 2-11)

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall
20

Figure 2-12 Four relations (Pine Valley Furniture)

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

21

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

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

22

Chapter 3: Modeling Data in the Organization

Modern Database Management 9th Edition
Jeffrey A. Hoffer, Mary B. Prescott, Heikki Topi

2009 Pearson Education, Inc. Publishing as Prentice Hall

23

Objectives

Definition of terms Importance of data modeling Write good names and definitions for entities, relationships, and attributes Distinguish unary, binary, and ternary relationships Model different types of attributes, entities, relationships, and cardinalities Draw E-R diagrams for common business situations Convert many-to-many relationships to associative entities Model time-dependent data using time stamps
24

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

Business Rules

Statements that define or constrain some aspect of the business Assert business structure Control/influence business behavior Expressed in terms familiar to end users Automated through DBMS software

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

25

A Good Business Rule Is:

Declarativewhat, not how Preciseclear, agreed-upon meaning Atomicone statement Consistentinternally and externally Expressiblestructured, natural language Distinctnon-redundant Business-orientedunderstood by business people
26

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

A Good Data Name Is:

Related to business, not technical, characteristics Meaningful and self-documenting Unique Readable Composed of words from an approved list Repeatable Follows standard syntax
27

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

Data Definitions

Explanation of a term or fact

Termword or phrase with specific meaning Factassociation between two or more terms Gathered in conjunction with systems requirements Accompanied by diagrams Concise description of essential data meaning Achieved by consensus, and iteratively refined

Guidelines for good data definition

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

28

E-R Model Constructs

Entities:

Entity instanceperson, place, object, event, concept (often corresponds to a row in a table) Entity Typecollection of entities (often corresponds to a table)

Relationships:

Relationship instancelink between entities (corresponds to primary key-foreign key equivalencies in related tables) Relationship typecategory of relationshiplink between entity types

Attributeproperty or characteristic of an entity or relationship type

(often corresponds to a field in a table)

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

29

Sample E-R Diagram (Figure 3-1)

Chapter 1 2009 Pearson Education, Inc. Publishing as Prentice Hall

30