Database

Design
Learning Objectives
 In this chapter, you will learn:
 That successful database design must reflect the information system of which the
database is a part
 That successful information systems are developed within a framework known as the
Systems Development Life Cycle (SDLC)
 That within the information system, the most successful databases are subject to
frequent evaluation and revision within a framework known as the Database Life
Cycle (DBLC)
 How to conduct evaluation and revision within the SDLC and DBLC frameworks
 About database design strategies: top-down vs. bottom-up design and centralized vs.
decentralized design

2
The Information
System
 Provides for data collection, storage, and
retrieval
 Composed of:
 People, hardware, software
 Database(s), application programs,
procedures
 Systems analysis: Process that
establishes need for and extent of
information system
 Systems development: Process of
creating information system
3
 Database Application
design and design and
implementation implementation
Performance Factors
of an Information
Database
System Administrative
development:
Process of
procedures database
design and its
implementation

4
 Traces history of an information
system
Systems
Development
Provides a picture within which
Life Cycle database design and application
development are mapped out
(SDLC) and evaluated

Iterative rather than sequential

process

5
The Systems Development Life Cycle
(SDLC)

6
Computer-Aided
Systems
Engineering
(CASE)
 Tool that produces:
 Time and cost-effective systems
 Structured, documented, and
standardized applications

7
The Database
Life Cycle
(DBLC)

8
Purpose of Database Initial Study

Analyze company Define problems

situation and constraints

Define scope and

Define objectives
boundaries

9
A Summary of Activities in the Database
Initial Study

10
 Supports company’s operations and
objectives

Checks the ultimate final product from all

perspectives

Database
Design Pointers for examining completion
procedures

• Data component is an element of whole system

• System analysts/programmers design procedures to
convert data into information
• Database design is an iterative process

11
Two Views of Data: Business Manager and
Database Designer

12
Database Design Process
Conceptual • Data analysis and requirements
Design • Entity Relationship modeling and normalization
• Data model verification
• Distributed database design

DBMS Select the

Selection DBMS

Logical • Map conceptual model to logical model components

Design • Validate logical model using normalization
• Validate logical model integrity constraints
• Validate logical model against user requirements

Physical • Define data storage organization

Design • Define integrity and security measures
• Determine performance measures
Implementation and Loading

1 2 3
Install the DBMS Create the databases Load or convert the data
• Virtualization: Creates logical • Requires the creation of • Requires aggregating data
representations of computing special storage-related from multiple sources
resources independent of constructs to house the end-
underlying physical computing user tables
resources

14
 Physical security

Password security

Access rights

Testing Audit trails

Factors Data encryption

Diskless workstations

Optimization

15
 Differential
Full
backup: Only
backup/dump: All
modified/updated
database objects
objects since last
are backed up in
full backup are
their entirety
backed up

Levels of Database
Backups Transaction log
backup: Only the
transaction log Backups are
operations that are provided with high
not reflected in a security
previous backup
are backed up

16
Sources of Database Failure
Software

Hardware

Programming exemptions

Transactions

External factors
17
 Preventive maintenance (backup)

Corrective maintenance (recovery)

Adaptive maintenance

Periodic Assignment of access permissions and their maintenance for new

and old users
Maintenance
Activities Generation of database access statistics

Periodic security audits

Periodic system-usage summaries

18
Parallel Activities in the DBLC and the
SDLC

19
 Designs a database independent of
database software and physical details

Conceptual data model - Describes main

data entities, attributes, relationships, and
constrains

Conceptual
Design Designed as software and hardware
independent

Minimum data rule: All that is needed is

there, and all that is there is needed

20
Conceptual Design Steps

21
Description of Operations

Provides precise, up-to-date, and reviewed

description of activities defining
organization’s operating environment

22
Developing the Conceptual Model Using
ER Diagrams

23
ER Modelling is an Iterative Process Based on Many
Activities

24
Conceptual Design Tools and Information
Sources

25
 Verified against
proposed system
processes
Careful reevaluation
of entities
Revision of original
Data Model design
Detailed examination
Verification of attributes
Module: Information describing entities
system component
that handles specific
business function

26
The ER Model Verification Process

Cengage Learning © 2015

27
Iterative ER Model Verification Process

28
Cohesivity and Module Coupling
 Cohesivity: Strength of the relationships among the module’s entities
 Module coupling: Extent to which modules are independent to one
another
 Low coupling decreases unnecessary intermodule dependencies

29
 Portions of database may
reside in different physical
locations

Distributed Database Database fragment:

Subset of a database
Design stored at a given location

Ensures database integrity,

security, and performance

30
 Cost

DBMS features and tools

Factors
Affecting Underlying model
Software
Purchasing Portability

Decision
DBMS hardware requirements

31
Logical and Physical Design
 Logical design: Designs an enterprise-wide database that is based on a specific data
model but independent of physical-level details
 Validates logical model:
 Using normalization
 Integrity constraints
 Against user requirements
 Physical design: Process of data storage organization and data access characteristics
of the database

32
Logical Design Steps

33
Mapping the Conceptual Model to the
Relational Model

34
Physical Design Steps

35
 Clustered Tables

Technique that stores related rows from

two related tables in adjacent data
blocks on disk

36
 Database Role

Set of database privileges that could be

assigned as a unit to a user or group

37
Top-down vs. Bottom-up Design
Sequencing

39
Centralized Design

40
Decentralized Design

41
Summary of Aggregation Problems

42