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
1
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
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 2
Figure 1-1a Data in context
Context helps users understand data
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 3
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 4
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 5
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 6
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 7
Duplicate Data
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 8
PROBLEMS WITH DATA REDUNDANCY
Waste of space to have duplicate data
Causes more maintenance headaches
The same data item may have
different names in different files or the
same name may be used for different
data items in different files
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 9
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 10
DATABASE MANAGEMENT SYSTEM
A software system that is used to create, maintain, and provide
controlled access to user databases
Order Filing
System
Invoicing Central database
DBMS
System
Contains employee,
order, inventory,
pricing, and
Payroll
customer data
System
DBMS manages data resources like an operating system manages hardware resources
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 11
ELEMENTS OF THE DATABASE APPROACH
Data models
Graphical system capturing nature and relationship of data
A typical data model is made up including entities,
relationships, and relationships
The most common data modeling representation is the entity
relationship diagram (ERD)
Enterprise Data Model–high-level entities and relationships for
the organization
Project Data Model–more detailed view, matching data
structure in database
Entities
Noun form describing a person, place, object, event, or concept
Composed of attributes (characteristics)
Relationships
Between entities
Usually one-to-many (1:M), many-to-many (M:N), and one to
one (1:1)
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 12
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 13
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 14
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 15
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 16
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 17
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 18
ADVANTAGES OF THE DATABASE
APPROACH
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 19
The Database Development Process
Enterprise data model: First step in the database
development process
Specifies range and general content of
organization’s database
Overall picture of organizational data at high
level of abstraction
Entity-relationship diagram
Descriptions of entity types
Relationships between entities
Business rules
Entity-business function matrix
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 20
FIGURE 1-6 Example business function-to-data entity matrix
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 21
