MANAGEMENT INFORMATION SYSTEMS 7/E

Raymond McLeod, Jr.

Chapter 10
The Database and Database
Management System

Copyright 1998 Prentice-Hall, Inc.

The Traditional Hierarchy of Data

File
Record
Element
Data Management Activities

 Data collection
 Integrity and verification
 Storage
 Maintenance
 Security
 Organization
 Retrieval
 Secondary Storage
 Two types
1.Sequential
» Magnetic tape storage
» Media
 Reels
 Cartridges
» A tape record
» Blocks of records
2.Direct access
» Magnetic disk
Disk stack; access mechanism, track, cylinder concept
A Magnetic Tape Record
 A Magnetic Tape File
Used to attach
to take-up reel The First
(about 25 feet) data record

Leader Header Blank Data Blank Data Blank Data

(blank tape) Label Gap Record 1 Gap Record 2 Gap Record 3

Used to identify
Take-up the tape
reel

Contains control totals

of data on the tape
Source reel

Data Blank Trailer Leader

Record n Gap Label (blank tape)
The last Used to attach tape
data record to source reel
(usually about 16
feet)
 File Maintenance

 Transaction file must be in sequence

 Generations of master files

Updating a Magnetic Tape File

Transaction
file
Old master file

Update
master file New master file
 Direct Access Storage (DASD)
- Reading and writing
- The disk address
- Record addressing schemes
» Direct
» Hashing scheme or randomizing formula
» Indexed sequential
- Used as a master file medium, intermediate
storage medium, and input medium
- Compact disks
 A Disk Stack
Access 10 Access 404 Tracks 11 disks
mechanism arms
000 403

20 20 Tracks
Read/write
heads
 A DASD Address

2 0 9 0 7 0 0 3
Track Read/write Record
number head number number
Updating a Master File

Transaction
data

Enter
Step 1 transaction data

Update
Master
Step 2 master
file file
Optical Disks ( laser, compact )
 5¼" compact disk = 650 MB average

 540 times floppy diskette capacity

 WORM -- Write-once, read-many

 Late 1980s rewritable disks

 Current and future uses

Relationship of Secondary Storage
to Processing
 Batch processing - hold transactions in a
group and once a ‘batch’ has been
accumulated, process all the transactions
- many batches are on a daily, weekly, or
monthly cycle
 Online processing - as a transaction is
received, process the transaction without
waiting for a batch of them to accumulate
 Realtime systems - often used to control
a physical system
 Batch
transaction Batch
Processing
data

Sort into item

Step 1 number sequence

Sorted
transaction
data Old
Inventory
Step 2 Update inventory file
file

New
Transaction Inventory
data file

Step 3 Sort into customer

number sequence
Batch Sorted
transaction
Old
Processing data
Accounts
Receivable
(continued) file
Update
Step 4 Accounts Receivable file
New
Accounts
Transaction Receivable
data file

Step 5 Sort into salesperson

number sequence

Sorted
transaction Old
data Sales
Analysis
Update Sales
Step 6 Analysis file
file
New
Sales
Analysis
file
 Online Processing

Enter single
transaction Files
record

Inventory

Accounts
Update Receivable
Sales
Analysis
Applications Determine Media

Applications

Batch Online

Realtime

Sequen- Direct
tial
Dawn of the Database Era (Mid-1960s)
Use logical organization to overcome
limitations of physical organization
 Inverted files
- Inverted file index
 Linked lists
- Link (pointer) field
- Head, tail
Logical integration of files
- GE’s IDS (Integrated Data Store)
 The Database Concept
 Database definition
An integrated collection of computer data,
organized and stored in a manner that
facilitates easy retrieval.
 Database concept
 Data independence -- keep data
specifications separate from programs, in
tables and indexes
 Data hierarchy; database, file, record, data element
Salesperson Salesperson Customer Customer Customer Customer
number name 1 2 3 n
16 17042 21096
20 41854
23 23694 25410 30102 30111
31 31002

56 34107 13109
92 20842
98 61634

104 10974
110 16342 64210 51263 41782

An Inverted File Index

 A Linked List
Customer Salesperson Salesperson
number number link

22504
23694 23 25410
24782
25409
25410 23 30102
26713
28914
30004
30102 23 30111
30111 23
30417
*
31715

Data Record
Salesperso Sale Customer Accounts
statistics
s
n file file
file receivable
file

Accounts
Buyer Inventory Vendor
payable
file file file
file

Purchase General
order ledger
file file

A Database Consists of One or More Files

 Database Structures
 Hierarchical structure (explicit relationship)
- Uses the ‘parent / children’ concept
- Limitation: Cannot handle ad hoc requests

 Implicit relationships (relational structure)

- Flat file; rows and columns
- Strength: Frees designers from need to specify
relationships prior to building the database
Explicit Relationships Between Files
Salesperson record

Sales statistics record Customer record

Accounts receivable
record

SALESPERSON RECORD CUSTOMER RECORD

Salesperson number Customer number
Salesperson name Customer name
Sales office number Salesperson number
Etc. Credit limit
Link to sales statistics record Etc.
Link to customer record Link to salesperson record
Link to accounts receivable record
SALES STATISTICS RECORD
Salesperson number ACCOUNTS RECEIVABLE RECORD
Item number Customer number
Customer number Invoice number
Amount of sale Invoice date
Link to salesperson record Invoice amount
Link to customer record
 An Example of Two Flat Files
Table A Table B
SALES
TERR SALES NO NAME
NO
112 1 112 ADAMS

128 3 128 WINKLER

153 2 153 HOUSE

159 1 159 FRANCIS

162 1 162 WILLIS

166 2 166 GROVETON

 Database Software

 DBMS
 Examples
- IBM’s IMS
- Intel’s SYSTEM 2000
- SQL/DS
- QBE
- Oracle
 Creating a Database

 Two approaches:

1. Process oriented approach (problem-

solving)
2. Enterprise modeling
 Define
1. the Problem

2. Identify necessary Data Needs

Can Be
decisions

3.
Describe
information needs
Defined by
Taking a
4.
Determine
the necessary Problem-
Oriented
processing

Specify Approach
5. data needs

Data
6. Specifications
 Data Documentation

 Describe the data

- Data description language (DDL)
- Schema, subschema

 Enter the data

Strategic Planning for Information Resources
Create
enterprise
1. data model

Enterprise
Data Model
Data Needs Can
Develop
Be Defined by
2. Database Creating an
Enterprise
Model
Database
Describing the Database Contents
Data dictionary

Enter
Step 1 dictionary data

Data description
Step 2 language (DDL)

Schema
 Using a Database

 Database user
- Person (query language)
- Application program (data manipulation
language, DML)

 DBMS events
 DBMS Events
Primary storage
Operating system

Schema Subschema

Step 3 Step 2 Step 1

Application
Step 4 DBMS program
Step 6
Step 7
Buffer storage area Step 5 User’s input, output, and
working areas
Step 4

Data flow

Databas Control signals

e
 Data
description

A DBMS
language
processor

Model Database
description
(schema)

Database manager
Query Data manipulation
Database
language language (DML)
Performance
statistics

Application programs
Performance
statistics
processor Transaction
log
Information
Information
Performance requests
statistics Backup/recovery
module
The Database Administrator
(DBA)
D B A Duties
 Database planning; work with users and
others, define schema, etc.
 Database implementation; creating the
database and enforcing policies and
procedures
 Database operations
 Database security
 DBA Duties
4.
Security
3.
Operation

Use
Imple- Planning
mentation
Analysis
2. Design
Implementation

1.
Planning
 Knowledge Discovery in
Databases
 Data warehousing
- refinement in the database concept to make it
» very large
» very pure
» very retrievable
 Data mart
- a more modest approach than data
warehousing, generally only one segment of
the firm
 Knowledge Discovery in
Databases (continued)

 Data mining
- the process of finding relationships in data
that are unknown to the user
- may be for
» verification
» discovery
» combination of verification and discovery
 The Knowledge Discovery in
Database Process
1. Define the data and the task
2. Acquire the data
3. Clean the data
4. Develop the hypothesis and search model
5. Mine the data
6. Test and verify
7. Interpret and use
 DBMS Advantages

 Reduce data redundancy

 Achieve data independence
 Enable integration of data from multiple
files
 Retrieve data and information quickly
 Improve security
 DBMS Disadvantages

 Resource demands
 Software
 Hardware
 Information specialists
 Putting it all Together
 The ideal situation
Enterprise planning Executives

Enterprise Data Modeling Executives, Users, DBA

Entity-relationship diagram DBA, Systems Analysts

Data dictionary DBA, Systems Analysts

Select DBMS DBA, MIS Steering committee

Specify schema, subschema DBA, Users

Store in DASD DBA, Computer operations