Modern Database Management
12th Edition
Global Edition
Jeff Hoffer, Ramesh Venkataraman,
Heikki Topi
Figure 1-1a Data in context
Context helps users understand data
Figure 1-1b Summarized data
Graphical displays turn data into useful
information that managers can use for
decision making and interpretation
Descriptions of the properties or characteristics of the
data, including data types, field sizes, allowable
values, and data context
Duplicate Data
Requires a Database Management System (DBMS)
n 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,
Payroll pricing, and
System customer data
DBMS manages data resources like an operating system manages hardware resources
Figure 1-3 Comparison of enterprise and project level data models
Segment of an enterprise data model
Segment of a project-level data model
One customer
may place many
orders, but each
order is placed by
a single customer
One-to-many
relationship
One order has many
order lines; each order
line is associated with
a single order
One-to-many
relationship
One product can
be in many
order lines, each
order line refers
to a single
product
One-to-many
relationship
Therefore, one
order involves
many products
and one product is
involved in many
orders
Many-to-many
relationship
Figure 1-5 Components of the database environment
Comparison of enterprise and
project-level data models
FIGURE 1-6 Example business function-to-data entity matrix
Planning
Analysis
Logical Design
Physical Design
Implementation
Maintenance
Planning
Planning Purpose preliminary understanding
Deliverable request for study
Analysis
Logical Design
Physical Design
Database activity Implementation
enterprise modeling
and early conceptual
Maintenance
data modeling
Purpose–thorough requirements analysis and
Planning structuring
Deliverable–functional system specifications
Analysis
Analysis
Logical Design
Physical Design
Database activity–thorough Implementation
and integrated conceptual
data modeling
Maintenance
Purpose–information requirements elicitation
Planning and structure
Deliverable–detailed design specifications
Analysis
Logical Design
Logical Design
Physical Design
Database activity– Implementation
logical database design
(transactions, forms,
Maintenance
displays, views, data
integrity and security)
Purpose–develop technology and
Planning organizational specifications
Analysis
Deliverable–program/data
structures, technology purchases,
organization redesigns
Logical Design
Physical Design
Physical Design
Database activity– Implementation
physical database design
(define database to DBMS,
Maintenance
physical data organization,
database processing programs)
Purpose–programming, testing,
Planning training, installation, documenting
Analysis Deliverable–operational programs,
documentation, training materials
Logical Design
Physical Design
Database activity–
database implementation, Implementation
Implementation
including coded programs,
documentation, Maintenance
installation and conversion
Planning Purpose–monitor, repair, enhance
Deliverable–periodic audits
Analysis
Logical Design
Physical Design
Database activity–
database maintenance, Implementation
performance analysis
and tuning, error Maintenance
Maintenance
corrections
Prototyping is a
classical Rapid
Application
Development
(RAD) approach
Agile – emphasizes “individuals and interactions over processes and
tools, working software over comprehensive documentation, customer
collaboration over contract negotiation, and response to change over
following a plan.” (The Agile Manifesto)
Examples of agile programming methodologies
eXtreme programming
Scrum
DSDM Consortium
Feature-driven development
Figure 1-9 Three-schema architecture
Different people
have different
views of the
database…these
are the external
schema
The internal
schema is the
underlying
design and
implementation
Figure 1-10a Evolution of database technologies
Figure 1-10b Database architectures
Figure 1-10b Database architectures (cont.)
Figure 1-10b Database architectures (cont.)
Figure 1-11 Multi-tiered client/server database
architecture
FIGURE 1-13 Computer
System for Pine Valley
Furniture Company
FIGURE 1-15 Project data model
for Home Office product line
marketing support system
Agile software development Database Metadata
Conceptual schema Database application Physical schema
Database management
Constraint system Prototyping
(DBMS)
Data Enterprise data modeling Relational database
Enterprise resource planning
Data independence Repository
(ERP)
Systems development life
Data model Entity
cycle (SDLC)
Data modeling and design
Information User view
tools
Data warehouse Logical schema
