CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS

Modern Database Management 11th Edition

Jeffrey A. Hoffer, V. Ramesh, Heikki Topi

2013 Pearson Education, Inc. Publishing as Prentice Hall

OBJECTIVES

Define terms Name limitations of conventional file processing Explain advantages of databases Identify costs and risks of databases List components of database environment Identify categories of database applications Describe database system development life cycle Explain prototyping and agile development approaches Explain roles of individuals Explain the three-schema architecture for databases

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

DEFINITIONS

Database: organized collection of logically related data Data: stored representations of meaningful objects and events

Structured: numbers, text, dates Unstructured: images, video, documents

Information: data processed to increase knowledge in the person using the data Metadata: data that describes the properties and context of user data
3

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

Figure 1-1a Data in context

Context helps users understand data

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

Figure 1-1b Summarized data

Graphical displays turn data into useful information that managers can use for decision making and interpretation
Chapter 1 2013 Pearson Education, Inc. Publishing as Prentice Hall
5

Descriptions of the properties or characteristics of the data, including data types, field sizes, allowable values, and data context
Chapter 1 2013 Pearson Education, Inc. Publishing as Prentice Hall
6

DISADVANTAGES OF FILE PROCESSING

Program-Data Dependence

All programs maintain metadata for each file they use

Duplication of Data

Different systems/programs have separate copies of the same data

Limited Data Sharing

No centralized control of data

Lengthy Development Times

Programmers must design their own file formats

Excessive Program Maintenance

80% of information systems budget

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

PROBLEMS WITH DATA DEPENDENCY

Each application programmer must maintain his/her own data Each application program needs to include code for the metadata of each file Each application program must have its own processing routines for reading, inserting, updating, and deleting data Lack of coordination and central control Non-standard file formats

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

Duplicate Data

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

PROBLEMS WITH DATA REDUNDANCY

Waste

of space to have duplicate data Causes more maintenance headaches The biggest problem:
Data

changes in one file could cause inconsistencies Compromises in data integrity

Chapter 1 2013 Pearson Education, Inc. Publishing as Prentice Hall
10

SOLUTION: THE DATABASE APPROACH

Central

repository of shared data Data is managed by a controlling agent Stored in a standardized, convenient form
Requires a Database Management System (DBMS)
Chapter 1 2013 Pearson Education, Inc. Publishing as Prentice Hall
11

DATABASE MANAGEMENT SYSTEM

A software system that is used to create, maintain, and provide controlled access to user databases
Order Filing System Central database Contains employee, order, inventory, pricing, and customer data

Invoicing System

DBMS

Payroll System

DBMS manages data resources like an operating system manages hardware resources

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

12

ADVANTAGES OF THE DATABASE APPROACH

Program-data independence Planned data redundancy Improved data consistency Improved data sharing Increased application development productivity Enforcement of standards Improved data quality Improved data accessibility and responsiveness Reduced program maintenance Improved decision support
13

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

14

ELEMENTS OF THE DATABASE APPROACH

Data models

Graphical system capturing nature and relationship of data Enterprise Data Modelhigh-level entities and relationships for the organization Project Data Modelmore detailed view, matching data structure in database or data warehouse Noun form describing a person, place, object, event, or concept Composed of attributes Between entities Usually one-to-many (1:M) or many-to-many (M:N)

Entities

Relationships

Relational Databases

Database technology involving tables (relations) representing entities and primary/foreign keys representing relationships

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

15

Figure 1-3 Comparison of enterprise and project level data models

Segment of an enterprise data model

Segment of a project-level data model

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

16

One customer may place many orders, but each order is placed by a single customer One-to-many relationship

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

17

One order has many order lines; each order line is associated with a single order One-to-many relationship

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

18

One product can be in many order lines, each order line refers to a single product One-to-many relationship

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

19

Therefore, one order involves many products and one product is involved in many orders Many-to-many relationship
Chapter 1 2013 Pearson Education, Inc. Publishing as Prentice Hall

20

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

21

Figure 1-5 Components of the Database Environment

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

22

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
23

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

ENTERPRISE DATA MODEL

First step in the database development process 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 1 2013 Pearson Education, Inc. Publishing as Prentice Hall

24

FIGURE 1-6 Example business function-to-data entity matrix

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

25

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 prototype versions Chapter 1 new 2013 Pearson Education, Inc. Publishing as Prentice Hall

26

SYSTEMS DEVELOPMENT LIFE CYCLE (SEE ALSO FIGURE 1-7)

Planning Analysis Logical Design Physical Design Implementation Maintenance

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

27

SYSTEMS DEVELOPMENT LIFE CYCLE (SEE ALSO FIGURE 1-7) (CONT.)

Planning Planning Analysis Logical Design Physical Design

Purposepreliminary understanding Deliverablerequest for study

Database activity enterprise modeling and early conceptual data modeling

Implementation Maintenance

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

28

SYSTEMS DEVELOPMENT LIFE CYCLE (SEE ALSO FIGURE 1-7) (CONT.)

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

29

SYSTEMS DEVELOPMENT LIFE CYCLE (SEE ALSO FIGURE 1-7) (CONT.)

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)

Implementation Maintenance

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

30

SYSTEMS DEVELOPMENT LIFE CYCLE (SEE ALSO FIGURE 1-7) (CONT.)

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)
Implementation Maintenance

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

31

SYSTEMS DEVELOPMENT LIFE CYCLE (SEE ALSO FIGURE 1-7) (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

Implementation Implementation Maintenance

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

32

SYSTEMS DEVELOPMENT LIFE CYCLE (SEE ALSO FIGURE 1-7) (CONT.)

Planning Analysis Logical Design Physical Design

Purposemonitor, repair, enhance

Deliverableperiodic audits

Database activity database maintenance, performance analysis and tuning, error corrections

Implementation Maintenance Maintenance

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

33

Prototyping Database Methodology (Figure 1-8)

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

34 34

Prototyping Database Methodology (Figure 1-8) (cont.)

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

35

Prototyping Database Methodology (Figure 1-8) (cont.)

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

36

Prototyping Database Methodology (Figure 1-8) (cont.)

37

Prototyping Database Methodology (Figure 1-8) (cont.)

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

38

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

Conceptual Schema

E-R modelscovered in Chapters 2 and 3

Logical structurescovered in Chapter 4 Physical structurescovered in Chapter 5
39

Internal Schema

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

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

40

MANAGING PROJECTS
Projecta

planned undertaking of related activities to reach an objective that has a beginning and an end Initiated and planned in planning stage of SDLC Executed during analysis, design, and implementation Closed at the end of implementation
Chapter 1 2013 Pearson Education, Inc. Publishing as Prentice Hall
41

MANAGING PROJECTS: PEOPLE INVOLVED

Business analysts Systems analysts Database analysts and data modelers Users Programmers Database architects Data administrators Project managers Other technical experts
42

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

EVOLUTION OF DATABASE SYSTEMS

Driven

by four main objectives:

Need for program-data independence reduced maintenance Desire to manage more complex data types and structures Ease of data access for less technical personnel Need for more powerful decision support platforms
Chapter 1 2013 Pearson Education, Inc. Publishing as Prentice Hall
43

Figure 1-10a Evolution of database technologies

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

44

Figure 1-10b Database architectures

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

45

Figure 1-10b Database architectures (cont.)

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

46

Figure 1-10b Database architectures (cont.)

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

47

THE RANGE OF DATABASE APPLICATIONS

Personal databases Two-tier and N-tier Client/Server databases Enterprise applications

Enterprise resource planning (ERP) systems Data warehousing implementations

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

48

Figure 1-11 Two-tier database with local area network

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

49

Figure 1-12 Three-tiered client/server database architecture

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

50

ENTERPRISE DATABASE APPLICATIONS

Enterprise
Integrate

Resource Planning (ERP)

all enterprise functions (manufacturing, finance, sales, marketing, inventory, accounting, human resources)

Data

Warehouse

decision support system derived from various operational databases Chapter 1

2013 Pearson Education, Inc. Publishing as Prentice Hall

Integrated

51

FIGURE 1-13 Computer System for Pine Valley Furniture Company

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

52

CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS

Modern Database Management 11th Edition

Jeffrey A. Hoffer, V. Ramesh, Heikki Topi

2013 Pearson Education, Inc. Publishing as Prentice Hall

53