Figures Part 2

ELECTRONIC TRANSPARENCIES
D I S K
ELECTRONIC TRANSPARENCIES
DISK 2
MODERN SYSTEMS
ANALYSIS
AND DESIGN
Jeffrey A. Hoffer Joey F. George Joseph S. Valacich
B
THE BENJAMIN/CUMMINGS PUBLISHING COMPANY, INC.
READING , MASSACHUSETTS M ENLO P ARK, C ALIFORNIA
NEW YORK DON MILLS , O NTARIO H ARLOW, U.K. A MSTERDAM
BONN P ARIS M ILAN M ADRID SYDNEY S INGAPORE T OKYO
SEOUL TAIPEI M EXICO CITY SAN JUAN , PUERTO RICO
Executive Editor: Michael Payne

Senior Acquisitions Editor: Maureen Allaire
Assistant Editor: Susannah Davidson
Marketing Manager: Melissa Baumwald
Production Editor: Teresa Thomas
Cover Design: Yvo Riezebos
Art Supervisor: Karl Miyajima
Artist: Mark Konrad
Senior Manufacturing Coordinator: Merry Free Osborn
Cover art: La belle jardinire, 1939, by Paul Klee, oil and tempura on burlap,
Kuntsmuseum Berne, Paul-Klee-Stiftung; 1996 ARS, New York/VG Bild-Kunst, Bonn.
USA Group, Inc., Atkinson Construction, Allison Engine Company, McHenry County,
IVI Publishing, Consensys Group, and Albertsons Inc. are not affiliated with The
Benjamin/Cummings Publishing Company, Inc.
Copyright 1996 by The Benjamin/Cummings Publishing Company, Inc.
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system,
or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording,
or any other media or embodiments now known or hereafter to become known, without the
prior written permission of the publisher. Manufactured in the United States of America.
Published simultaneously in Canada.
ISBN 0805324844
B
The Benjamin/Cummings Publishing Company, Inc.
2725 Sand Hill Road
Menlo Park, CA 94025
http://www.aw.com/bc/is/
CONTENTS
Disk 2
Part V Logical Design
Chapter 13 Designing Forms and Reports
Figure 13-8a
Contrasting customer information forms (Pine Valley Furniture): Poorly

designed form
Figure 13-8b
Contrasting customer information forms (Pine Valley Furniture):

Improved design for form
Figure 13-9
Customer account status display using various highlighting techniques

(Pine Valley Furniture)
Figure 13-10a Contrasting display of textual help information: Poorly designed form
Figure 13-10b Contrasting the display of textual help information: Improved design for
form
Figure 13-11a Contrasting the display of tables and lists (Pine Valley Furniture): Poorly
designed form
Figure 13-11b Contrasting the display of tables and lists (Pine Valley Furniture):
Figure 13-12
Tabular report illustrating numerous design guidelines (Pine Valley

Furniture)
Figure 13-14a How scaling can bias the meaning of information: No bias in scaling
Figure 13-14b How scaling can bias the meaning of information: Non-zero bottom of
scale
Figure 13-14c How scaling can bias the meaning of information: Too high top of scale
Chapter 14 Designing Interfaces and Dialogues

Figure 14-2
Specification outline for the design of interfaces and dialogues
Figure 14-5
Various types of menu configurations
Figure 14-7a
Contrasting menu designs: Poor menu design
Figure 14-7b
Contrasting menu designs: Improved menu design
Figure 14-9
Example of form interaction in the Netscape World Wide Web

browser
Figure 14-11
Paper-based form for reporting customer sales activity (Pine Valley

Furniture)
Figure 14-12
Computer-based form reporting customer sales activity (Pine Valley

Furniture)
Figure 14-13a Contrasting the navigation flow within a data entry form: Proper flow
between data entry fields
Figure 14-13b Contrasting the navigation flow within a data entry form: Poor flow
Figure 14-15a Contrasting help screens: Poorly designed help display
Figure 14-15b Contrasting help screens: Improved design for help display
Figure 14-16
Hypertext-based help system from Microsofts Visual Basic
Figure 14-19
Dialogue diagram illustrating sequence, selection, and iteration
Figure 14-21
Highlighting graphical user interface design standards
Figure 14-22
State-transition diagram for spell checker
Chapter 15 Designing Databases: Logical Data Modeling

Figure 15-3a
Simple example of logical data modeling: Highest volume customer

query screen
Figure 15-3b
Simple example of logical data modeling: Backlog summary report
Figure 15-3c
Simple example of logical data modeling: Integrated set of relations
Figure 15-3d
Simple example of logical data modeling: Conceptual data model and

transformed relations
Figure 15-3e
Simple example of logical data modeling: Final set of normalized

relations
Figure 15-6
Relation with redundancy
Figure 15-7
EMP COURSE relation
Figure 15-8
Steps in normalization
Figure 15-9
EXAMPLE relation
Figure 15-10
Table with repeating data
Figure 15-11a Removing transitive dependencies: Relation with transitive dependency

Figure 15-11b Removing transitive dependencies: Relations in 3NF
Figure 15-13a Representing a 1:N relationship: E-R diagram
Figure 15-13b Representing a 1:N relationship: Relations
Figure 15-14a Representing an M:N relationship: E-R diagram
Figure 15-14b Representing an M:N relationship: Relations
Figure 15-15a Two unary relationships: EMPLOYEE with Manages relationship (1:N)
Figure 15-15b Two unary relationships: Bill-of-materials structure (M:N )
Figure 15-18
Hoosier Burger inventory usage report
Figure 15-19
E-R diagram corresponding to normalized relations of Hoosier Burgers

inventory control system
Part VI
Physical Design
Chapter 16 Designing Physical Files and Databases

Figure 16-4
Example code look-up table (Pine Valley Furniture)
Figure 16-5a
Examples of referential integrity field controls: Referential integrity

between relations
Figure 16-5b
Examples of referential integrity field controls: Referential integrity

within a relation
Figure 16-7a
Possible denormalization situations: Two entities with one-to-one

relationship
Figure 16-7b
Possible denormalization situations: A many-to-many relationship with

nonkey attributes
Figure 16-7c
Possible denormalization situations: Reference data
Figure 16-9a
Comparison of file organizations: Sequential
Figure 16-9b
Comparison of file organizations: Indexed
Figure 16-9c
Comparison of file organizations: Hashed
Figure 16-10a File recovery approaches: Forward recovery

Figure 16-10b File recovery approaches: Backward recovery
Figure 16-12
Example hash file layout and size
Figure 16-14a Database architectures: Hierarchical

Figure 16-14b Database architectures: Network
Figure 16-14c Database architectures: Relational
Figure 16-14d Database architectures: Object-Oriented
Figure 16-15
Data volume chart
Chapter 17 Designing the Internals: Program and Process Design

Figure 17-3
Special symbols used in structure charts: (a) Data couples and control
flag; (b) Conditional call of subordinates; (c) Repetitive calls of
subordinates
Figure 17-3
Special symbols used in structure charts: (d) Pre-defined module;

(e) Embedded module
Figure 17-4a
How to read a structure chart: Non-overlapping arrows
Figure 17-4b
How to read a structure chart: Overlapping arrows
Figure 17-5
A transaction-centered system design
Figure 17-6
A central transform in a data flow diagram
Figure 17-7
A transaction center in a data flow diagram
Figure 17-9
The top-level structure chart derived from the data flow diagram in
Figure 17-8
Figure 17-11
Complete first refinement of the structure chart from Figure 17-9
Figure 17-13
PVF Purchasing Fulfillment System data flow diagram with central

transform circled
Figure 17-14
Top-level structure chart for the PVF Purchasing Fulfillment System
Figure 17-15
Refined afferent branches for the PVF Purchasing Fulfillment System

structure chart
Figure 17-16
Refined central transforms and efferent branch for the PVF Purchasing
Fulfillment System structure chart
Figure 17-19
Example of data coupling
Figure 17-20
Example of stamp coupling
Figure 17-21
Example of control coupling
Figure 17-22a Examples of communicational cohesion: Example of a communicational

cohesion module
Figure 17-22b Examples of communicational cohesion: Example of a communicationally cohesive module split into two functionally cohesive modules
Figure 17-24
Pseudocode description of Calculate New Balance module
Figure 17-25
Basic symbols in Nassi-Shneiderman charts
Figure 17-26
The contents of the module Calculate New Balance in the form of a

Nassi-Shneiderman chart
Chapter 18 Designing Distributed Systems

Figure 18-2
Outcomes and deliverables from designing distributed systems
Figure 18-3
File server model
Figure 18-4
File servers transfer entire files when data are requested from a client
Figure 18-5
Client/server architecture transfers only the required data after a

request from a client
Figure 18-7
Customer relation for a bank
Figure 18-8
Horizontal partitions: (a) Lakeview Branch; (b) Valley Branch
Figure 18-9
Part relation
Figure 18-10
Vertical partitioning of Part relation: (a) Engineering; (b) Manufacturing
Figure 18-13a Types of client/server architectures: Distributed presentation

Figure 18-13b Types of client/server architectures: Remote presentation
Figure 18-13c Types of client/server architectures: Remote data management
Figure 18-13d Types of client/server architectures: Distributed function
Figure 18-13e Types of client/server architectures: Distributed database
Figure 18-13f Types of client/server architectures: Distributed processing
Part VII Implementation and Maintenance

Chapter 19 System Implementation: Coding, Testing, and Installation
Figure 19-2
Steps in a typical code walkthrough
Figure 19-3
Comparing stub and integration testing
Figure 19-4
Test case description form
Figure 19-5
Test case results form
Figure 19-7a
Comparison of installation strategies: Direct installation
Figure 19-7b
Comparison of installation strategies: Parallel installation
Figure 19-7c
Comparison of installation strategies: Single location installation (with

direct installation at each location)
Figure 19-7d
Comparison of installation strategies: Phased installation
Figure 19-8
Scheins three-stage model of the change process
Chapter 20 System Implementation: Documenting the System, Training,

and Supporting Users
Figure 20-3a
Outlines of users guides from various popular PC software packages:

Microsoft Access
Figure 20-3b

WordPerfect for Windows 6.0
Figure 20-3c

CA Simple Tax 1993
Figure 20-4
Traditional information system environment and its focus on system

documentation
Figure 20-5
End user information system environment and its focus on user

documentation
Figure 20-6
Frequency of use of computer training methods
Figure 20-7
A Microsoft Cue Card for Microsoft Access
Chapter 21 Maintaining Information Systems

Figure 21-5
Types of maintenance
Figure 21-7
Quality documentation eases maintenance
Figure 21-8
How the mean time between failures should change over time
Figure 21-9
Flow chart of how to control maintenance requests
Figure 21-11
How Total Quality Management differs from Business Process

Re-engineering
Figure 13-8a Contrasting customer information forms (Pine Valley Furniture):

Poorly designed form
Hard to read:
information is
packed too tightly
Vague title
No navigation
information
No summary of
account activity
Figure 13-8b Contrasting customer information forms (Pine Valley Furniture):

Clear title
Summary of
account
information
Easy to read:
clear, balanced
layout
Clear navigation
information
Figure 13-9
Customer account status display using various highlighting techniques

Font size, intensity,

underlining, and italics
Boxing
All capital
letters
Intensity
differences
Figure 13-10a Contrasting the display of textual help information: Poorly designed form
Vague title
Hyphenated between
lines and abbreviated
Fixed, upper-case
text
Single spacing
Figure 13-10b Contrasting the display of textual help information: Improved design for form
Clear title
Mixed case
Spacing between
sections
Figure 13-11a Contrasting the display of tables and lists (Pine Valley Furniture):
Poorly designed form
No column
labels
Single column
for all types
of data
Numeric data is
left-justified
Figure 13-11b Contrasting the display of tables and lists (Pine Valley Furniture):
Clear and separate

column labels for
each data type
Numeric data is
right-justified
Figure 13-12 Tabular report illustrating numerous design guidelines

Place meaningful
labels on all
columns and rows
Alphabetic text
is left-justified
Use a
meaningful
title
Box the table data to

improve the appearance
of the table
Pine Valley Furniture

Salesperson Annual Summary Report, 1995
January 10, 1996
Region
Northwest & Mountain
Salesperson SSN
First
Page 1 of 2
Quarterly Actual Sales

Second
Third
Fourth
Baker
999-99-9999
Hawthorne 999-99-9999
Hodges
999-99-9999
195,000
220,000
110,000
146,000
175,000
95,000
133,000
213,000
170,000
120,000
198,000
120,000
Franklin
999-99-9999
Stephenson 1 999-99-9999
999-99-9999
Swenson
110,000
75,000
110,000
120,000
66,000
98,000
170,000
80,000
100,000
90,000
80,000
90,000
999-99-9999
999-99-9999
250,000
310,000
280,000
190,000
260,000
270,000
330,000
280,000
Midwest & Mid-Atlantic
New England
Brightman
Kennedy
1. Sales reflect May 1, 1995 December 31, 1995.

Superscript characters
can be used to alert
reader of more
detailed information
Sort columns in some

meaningful order
(names are sorted
alphabetically
within region)
Long sequence of
alphanumeric data
is grouped into
smaller segments
Right-justify
all numeric data
Try to fit table
onto a single page
to help in making
comparisons
Figure 13-14a How scaling can bias the meaning of information: No bias in scaling
Normal Scale
Bottom of Scale = 0
Top of Scale = near maximum value
30
25
Thousands
20
15
10
0
First
Second
Third
Fourth
Figure 13-14b How scaling can bias the meaning of information: Non-zero bottom
of scale
Biased Scale
Bottom of Scale = 10,000
Top of Scale = near maximum value
30
Thousands
25
20
15
10
First
Second
Third
Fourth
Figure 13-14c How scaling can bias the meaning of information: Too high top of scale
Biased Scale
Bottom of Scale = 0
Top of Scale = too much greater than maximum value
100
Thousands
80
60
40
20
0
First
Second
Third
Copyright 1996 by The Benjamin/Cummings Publishing Company, Inc-
Fourth
Figure 14-2
Specification outline for the design of interfaces and dialogues
Design Specification
1. Narrative overview
a. Interface/Dialogue Name
b. User Characteristics
c. Task Characteristics
d. System Characteristics
e. Environmental Characteristics
2. Interface/Dialogue Designs
a. Form/Report Designs
b. Dialogue Sequence Diagram(s) and Narrative Description
3. Testing and Usability Assessment
a. Testing Objectives
b. Testing Procedures
c. Testing Results
i)
Time to Learn
ii) Speed of Performance
iii) Rate of Errors
iv) Retention Over Time
v) User Satisfaction and Other Perceptions
Figure 14-5
Various types of menu configurations
Single Menu
Linear Sequence Menu
Multi-Level Tree Menu

with Multiple Parents

with Multiple Parents and
Multi-Level Traversal
(Adapted from Sheiderman, 1992)

Figure 14-7a Contrasting menu designs: Poor menu design
Vague title
SYSTEM OPTIONS
01
02
03
04
05
06
Vague command names
ORDER INFO
ORDER STATUS
SALES PERSON INFO
REPORTS
HELP
QUIT
ENTER OPTION (01):__
All upper-case letters

Common options
are not separated and
assigned a standard key
Vague exit statement
Two-key selection
Figure 14-7b Contrasting menu designs: Improved menu design
Clear Title
Customer Information System
Main Menu
1
2
3
4
Query Information on a Specific Order

Check Status of a Specific Order
Review Sales Person Information
Produce Order and Sales Reports
9
0
Help
Exit to DOS
Descriptive command
names with
mixed-case letters
Common options
are separated and
assigned a standard key
Clear exit statement
Type option number (1):__
One-key selection
Figure 14-9
Example of form interaction in the Netscape World Wide Web browser
Figure 14-11 Paper-based form for reporting customer sales activity

PINE VALLEY FURNITURE

Sequence and
Time Information
INVOICE No.
Date:
Sales Invoice
SOLD TO:
Customer Number:
Name:
Address:
City:
Phone:
Header
State:
Zip:
SOLD BY:
Product
Number
Description
Quantity
Ordered
Unit Total
Price Price
Body
Authorization
Total Order Amount

Less Discount____%
Total Amount
Customer Signature:
Date:
Totals
Figure 14-12 Computer-based form for reporting customer sales activity

Figure 14-13a Contrasting the navigation flow within a data entry form: Proper flow
Figure 14-13b Contrasting the navigation flow within a data entry form: Poor flow
Figure 14-15a Contrasting help screens: Poorly designed help display
Figure 14-15b Contrasting help screens: Improved design for help display
Figure 14-16 Hypertext-based help system from Microsofts Visual Basic
Figure 14-19 Dialogue diagram illustrating sequence, selection, and iteration
Display
A
Sequence
Display
B
Iteration
Display
C
Display
D
Display
E
Selection
Figure 14-21 Highlighting graphical user interface design standards
File menu item is always the

first item (if present)
Edit menu item is always
the second item (if present)
Window menu item is always

second from last item (if present)
Help menu item is always
last item (if present)
Right arrow ( )
shows that an
item leads to a
submenu
Display text prompt

for all menu items
Check mark shows that an item
is selected or a mode is turned
No checkmarks indicate Ellipsis (...) shows that a

that a command will be pop-up menu will appear
if selected
executed if selected
Figure 14-22 State-transition diagram for spell checker
(1) Load Spell Checker

(2) Display Spell Checker
Closed
(5) Close Spell Checker
Open,
but Idle
(3) Initiate Spell Checking
(4) Completed or Suspend Checking
Open and
Checking
Figure 15-3a Simple example of logical data modeling: Highest volume customer
query screen
HIGHEST VOLUME CUSTOMER

ENTER PRODUCT NO.: M128
START DATE:
11/01/93
END DATE:
12/31/93

CUSTOMER NO.:
1256
NAME:
Commonwealth Builder
VOLUME:
30
This inquiry screen shows the customer with the largest volume total
sales of a specified product during an indicated time period.
Relations:
CUSTOMER (CUSTOMER NO., NAME)
ORDER (ORDER NO., -CUSTOMER
- - - - - - - - - -NO.,
- - - ORDER DATE)
PRODUCT (PRODUCT NO.)
LINE ITEM (ORDER NO., PRODUCT NO., ORDER QUANTITY)
Figure 15-3b Simple example of logical data modeling: Backlog summary report
PAGE 1
BACKLOG SUMMARY REPORT
11/30/93
BACKLOG
PRODUCT NO. QUANTITY
0
B381
0
B975
6
B985
30
E125
...
M128
..
.
This report shows the unit volume of each product that has been ordered
less that amount shipped through the specified date.
Relations:
LINE ITEM (PRODUCT NO., ORDER NO., ORDER QUANTITY)
ORDER (ORDER NO., ORDER DATE)
SHIPMENT (PRODUCT NO., INVOICE NO., SHIP QUANTITY)
INVOICE (INVOICE NO., INVOICE DATE)
Figure 15-3c
Simple example of logical data modeling: Integrated set of relations
CUSTOMER (CUSTOMER NO., NAME)

INVOICE (INVOICE NO., INVOICE DATE)
ORDER (ORDER NO., CUSTOMER NO., ORDER DATE)
SHIPMENT (PRODUCT NO., INVOICE NO., SHIP QUANTITY)
Figure 15-3d Simple example of logical data modeling: Conceptual data model and
transformed relations
CUSTOMER NO.
NAME
CUSTOMER
Places
INVOICE NO.
ADDRESS
INVOICE
Bills
SHIP
QUANTITY
ORDER NO.
ORDER
SHIPMENT
ORDER
QUANTITY
LINE
ITEM
PRODUCT
PRODUCT NO.
DESCRIPTION
Relations:
CUSTOMER (CUSTOMER NO., NAME, ADDRESS)
PRODUCT (PRODUCT NO., DESCRIPTION)
ORDER (ORDER NO., CUSTOMER NO.)
INVOICE (INVOICE NO., ORDER NO.)
SHIPMENT (INVOICE NO., PRODUCT NO., SHIP QUANTITY)
Figure 15-3e Simple example of logical data modeling: Final set of normalized relations
CUSTOMER (CUSTOMER NO., NAME, ADDRESS)

PRODUCT (PRODUCT NO., DESCRIPTION)
ORDER (ORDER NO., CUSTOMER NO., ORDER DATE)
INVOICE (INVOICE NO., ORDER NO., INVOICE DATE)
SHIPMENT (INVOICE NO., PRODUCT NO., SHIP QUANTITY)
Figure 15-6
Relation with redundancy
Figure 15-6
EMPLOYEE2
EMPID
NAME
DEPT
SALARY
COURSE
DATE COMPLETED
100
100
140
110
110
190
150
150
Margaret Simpson
Margaret Simpson
Alan Beeton
Chris Lucero
Chris Lucero
Lorenzo Davis
Susan Martin
Susan Martin
Marketing
Marketing
Accounting
Info Systems
Info Systems
Finance
Marketing
Marketing
42,000
42,000
39,000
41,500
41,500
38,000
38,500
38,500
SPSS
Surveys
Tax Acc
SPSS
C++
Investments
SPSS
TQM
6/19/9X
10/7/9X
12/8/9X
1/12/9X
4/22/9X
5/7/9X
6/19/9X
8/12/9X
Figure 15-7
EMP COURSE relation
EMP COURSE
EMPID
100
100
140
110
110
190
150
150
COURSE
DATE
COMPLETED
SPSS
Surveys
Tax Acc
SPSS
C++
Investments
SPSS
TQM
6/19/9X
10/7/9X
12/8/9X
1/22/9X
4/22/9X
5/7/9X
6/19/9X
8/12/9X
Figure 15-8
Steps in normalization
Table With
Repeating
Groups
First
Normal
Form
Second
Normal
Form
Remove
Repeating
Groups
Remove
Partial
Dependencies
Remove
Transitive
Dependencies
Third
Normal
Form
Figure 15-9
EXAMPLE relation
EXAMPLE
A
X
Y
Z
Y
U
X
Y
Z
X
Z
Y
W
Y
X
Y
Z
Figure 15-10 Table with repeating data
Figure 15-10
EMPLOYEE2
SALARY
COURSE
DATE
COMPLETED
Marketing
42,000
Alan Beeton
Chris Lucero
Accounting
Info Systems
39,000
41,500
Lorenzo Davis
Susan Martin
Finance
Marketing
38,000
38,500
SPSS
Surveys
Tax Acc
SPSS
C++
Investments
SPSS
TQM
6/19/9X
10/7/9X
12/8/9X
1/12/9X
4/22/9X
5/7/9X
6/19/9X
8/12/9X
EMPID
NAME
DEPT
100
Margaret Simpson
140
110
190
150
Figure 15-11a Removing transitive dependencies: Relation with transitive dependency
SALES
CUST NO.
NAME
SALESPERSON
REGION
8023
9167
7924
6837
8596
7018
Anderson
Bancroft
Hobbs
Tucker
Eckersley
Arnold
Smith
Hicks
Smith
Hernandez
Hicks
Faulb
South
West
South
East
West
North
Figure 15-11b Removing transitive dependencies: Relations in 3NF
(b) Relations in 3NF
SPERSON
SALES1
CUST NO.
NAME
8023
9167
7924
6837
8596
7018
Anderson
Bancroft
Hobbs
Tucker
Eckersley
Arnold
SALESPERSON
Smith
Hicks
Smith
Hernandez
Hicks
Faulb
SALESPERSON
REGION
Smith
Hicks
Hernandez
Faulb
South
West
East
North
Figure 15-13a Representing a 1:N relationship: E-R diagram
ADDRESS
CITY STATE
ZIP
NAME
CUSTOMER
NO.
DISCOUNT
CUSTOMER
Places
ORDER
PROMISED
DATE
ORDER NO.
ORDER DATE
Figure 15-13b Representing a 1:N relationship: Relations
CUSTOMER
CUSTOMER NO.
NAME
ADDRESS
CITY STATE ZIP
DISCOUNT
1273
6390
Contemporary Designs
Casual Corner
123 Oak St.

18 Hoosier Dr.
Austin, TX 38405
Bloomington, IN 45821
5%
3%
ORDER
ORDER NO.
ORDER DATE
PROMISED DATE
57194
63725
80149
3/15/9X
3/17/9X
3/14/9X
3/28/9X
4/01/9X
3/24/9X
CUSTOMER
NO.
6390
1273
6390
Figure 15-14a Representing an M:N relationship: E-R diagram
ORDER
DATE
PROMISED
DATE
ORDER NO.
ORDER
QUANTITY
ORDERED
Requests
PRODUCT
(Other
Attributes)
PRODUCT
NO.
DESCRIPTION
ROOM
Figure 15-14b Representing an M:N relationship: Relations
ORDER
ORDER NO.
ORDER DATE
PROMISED DATE
61384
62009
62807
2/17/9X
2/13/9X
2/15/9X
3/01/9X
2/27/9X
3/01/9X
ORDER NO.
PRODUCT NO.
QUANTITY
ORDERED
61384
61384
M128
A261
2
1
ORDER LINE
PRODUCT
PRODUCT NO.
DESCRIPTION
M128
A261
R149
Bookcase
Wall unit
Cabinet
(OTHER
ATTRIBUTES)
-
Figure 15-15a Two unary relationships: EMPLOYEE with Manages relationship (1:N )
EMP ID
NAME
BIRTHDATE
EMPLOYEE
Manages
Figure 15-15b Two unary relationships: Bill-of-materials structure (M:N )
ITEM NO.
NAME
COST
ITEM
Contains
QUANTITY
Figure 15-18 Hoosier Burger inventory usage report
INVENTORY USAGE REPORT

for Sales Date 1Date 2
REGULAR
PRODUCT NO.
xxx
yyy
DESCRIPTION
Page x of n
Date Printed
CONSUMPTION
DATE
USED
REGULAR
HOOSIER
TOTAL
aaa
bbb
ccc
Figure 15-19 E-R diagram corresponding to normalized relations of Hoosier Burgers

inventory control system
Receipt No.
Invoice No.
Sale Date
Invoice Date
Vendor No.
Paid?
SALE
INVOICE
Includes
Sells
Is Sold on
ITEM
SALE
Quantity
Sold
Is Included on
Orders
INVOICE
ITEM
Quantity
Added
Product No.
Is Ordered on
Is Received for
PRODUCT
Product
Description
IS-A
HOOSIER
PRODUCT
Meal
Quantity
MEAL
IS-A
Quantity
Used
Received
on
REGULAR
PRODUCT
RECIPE
INVENTORY
ITEM
Minimum
Order Quantity
Hoosier
Product No.
Regular
Product No.
Type
of Item
Item No.
Item
Description
Quantity
in Stock
Figure 16-4
Example code look-up table (Pine Valley Furniture)
PRODUCT FILE
FINISH LOOK-UP TABLE
PRODUCT NO.
DESCRIPTION
B100
B120
M128
T100

Chair
Desk
Table
Bookcase

FINISH
C
A
C
B

CODE
VALUE
A
B
C

Birch
Maple
Oak

Figure 16-5a Examples of referential integrity field controls: Referential integrity between relations
CUSTOMER (CUSTOMER_ID, CUST_NAME, CUST_ADDRESS,...)
CUST_ORDER (ORDER_ID, CUSTOMER_ID, ORDER_DATE,...)

and CUSTOMER_ID may not be null since every order must be for some
existing customer
Figure 16-5b Examples of referential integrity field controls: Referential integrity within a relation
EMPLOYEE (EMPLOYEE_ID, SUPERVISOR_ID, EMPL_NAME,...)

and SUPERVISOR_ID may be null since not all
employees have supervisors
Figure 16-7a Possible denormalization situations: Two entities with one-to-one relationship
STUDENT-ID
STUDENT
CAMPUS
ADDRESS
APPLICATIONID
Submits
APPLICATION
DATE
SCHOLARSHIP
APPLICATION
FORM
QUALIFICATION
Normalized relations:
STUDENT (STUDENT-ID, CAMPUS-ADDRESS, APPLICATION-ID)
APPLICATION (APPLICATION-ID, APPLICATION DATE, QUALIFICATIONS, STUDENT-ID)
Denormalized relation:
STUDENT (STUDENT-ID, CAMPUS-ADDRESS, APPLICATION DATE, QUALIFICATIONS)
and APPLICATION DATE and QUALIFICATIONS may be null
(Note: We assume APPLICATION-ID is not necessary when all fields are stored in one record,
but this field can be included if it is required application data.)
Figure 16-7b Possible denormalization situations: A many-to-many relationship with nonkey attributes
VENDOR-ID
PRICE
ITEM-ID
VENDOR
PRICE QUOTE
ITEM
ADDRESS
CONTRACT
NAME
DESCRIPTION
VENDOR (VENDOR-ID, ADDRESS, CONTACT NAME)
ITEM (ITEM-ID, DESCRIPTION)
PRICE QUOTE (VENDOR-ID, ITEM-ID, PRICE)
Denormalized relations:
VENDOR (VENDOR-ID, ADDRESS, CONTACT NAME)
ITEM-QUOTE (VENDOR-ID, ITEM-ID, DESCRIPTION, PRICE)
Figure 16-7c
Possible denormalization situations: Reference data
WHERE
STORE
INSTR-ID
STORAGE
INSTRUCTIONS
CONTAINER
TYPE
Control for
ITEM-ID
ITEM
DESCRIPTION
Descirption
STORAGE (INSTR-ID, WHERE STORE, CONTAINER TYPE)
ITEM (ITEM-ID, DESCRIPTION, INSTR-ID)
Denormalized relation:
ITEM (ITEM-ID, DESCRIPTION, WHERE STORE, CONTAINER TYPE)
Figure 16-9a Comparison of file organizations: Sequential
Start of file
Aces
Boilermakers
Scan
Devils
Flyers
Hawkeyes
Hoosiers
..
.
Miners
Panthers
..
.
Seminoles
..
.
Figure 16-9b Comparison of file organizations: Indexed
Key
(Hoosiers)
Aces
Flyers
Miners
Boilermakers
Devils
Panthers
Hawkeyes
Hoosiers
Seminoles
Figure 16-9c
Comparison of file organizations: Hashed
Key
(Hoosiers)
Hashing
Algorithm
Miners
Hawkeyes
Aces
..
.
Relative
Record
Number
Hoosiers
Seminoles
Devils
Flyers
Panthers
..
.
Boilermakers
Figure 16-10a File recovery approaches: Forward recovery
Transactions
Backup
Transactions
Backup
Error
introduced
Transactions
Backup
Discover
error
Time
Restore
this backup
Rerun all these transactions

after correcting problem that caused error
Figure 16-10b File recovery approaches: Backward recovery
Transactions
Error
introduced
Discover
error
Time
Reverse effects of transactions
Correct problem that caused error
Rerun all these transactions
Figure 16-12 Example hash file layout and size
File characteristics
Record length = 240 bytes
Number of records = 172
Blocking factor = 4
Track length = 4000 bytes
Record block
960 bytes
Track number
Record = 240 bytes
Wasted space
160 bytes
Block number
Track = 4000 bytes
1
2
3
4
5
6
7
8
9
10
11
0
4
8
12
16
20
24
28
32
36
40
Wasted block
Figure 16-14a Database architectures: Hierarchical
Figure 16-14b Database architectures: Network
Figure 16-14c Database architectures: Relational
RELATION 1 (PRIMARY KEY, ATTRIBUTES...)

RELATION 2 (PRIMARY KEY, FOREIGN KEY, ATTRIBUTES...)
Figure 16-14d Database architectures: Object-Oriented
Object Class 1
Attributes
Object Class 2
Object Class 3
Attributes
Attributes
Methods
Methods
Methods
Figure 16-15 Data volume chart
SALE
INVOICE
260,400
4,340
(3)
ITEM SALE
781,200
(2)
INVOICE
ITEM
8,680
PRODUCT
30
IS-A
IS-A
(20%)
(80%)
HOOSIER
PRODUCT
REGULAR
PRODUCT
MEAL
18
(3)
RECIPE
24
144
(6)
INVENTORY
ITEM
21
Figure 17-3
Special symbols used in structure charts
Get
C
A
Error
making
C
Make
C
(a) Data couples and control flag
(b) Conditional call of subordinates
(c) Repetitive calls of subordinates

Figure 17-3
Special symbols used in structure charts (continued)
(d) Pre-defined module
(e) Embedded module
Figure 17-4a How to read a structure chart: Non-overlapping arrows
Boss
VA
VA
VB
Get Valid
A
Get Valid
B
VA
Read
A
VB
Validate
A
Make
C
Read
B
Put
C
VB
Validate
B
Legend:
VA valid A
VB valid B
Figure 17-4b How to read a structure chart: Overlapping arrows
Boss
VA
VA
VB
Get Valid
A
Read
A
VB
Get Valid
B
VA
VB
Validate
Data
Make
C
Put
C
Read
B
Legend:
VA valid A
VB valid B
Figure 17-5
A transaction-centered system design
Process
Transaction
Process
Savings
Deposit
Process
Savings
Withdrawal
Process
Checking
Deposit
Process
Checking
Withdrawal
Process
Car Loan
Payment
Figure 17-6
Source
1
A central transform in a data flow diagram
Get
Valid
A
Valid
A
Make
C
Source
2
Get
Valid
B
Print
C
Report
Valid
B
C
Report
Sink
Figure 17-7
Source
1
A transaction center in a data flow diagram
T1
Validate
T1
T2
Validate
T2
Process
Deposit
Payment
Process
Payment
Withdrawal
Process
Withdrawal
Valid
T1
Process
Transaction
Source
2
Deposit
Valid
T2
Out 1
Out 2
Out 3
Sink 1
Sink 2
Sink 3
Figure 17-9
The top-level structure chart derived from the data flow diagram in Figure 17-8
Boss
VA
VA
VB
Get Valid
A
VB
Get Valid
B
Make
C
Put
C
Legend:
VA valid A
VB valid B
Figure 17-11 Complete first refinement of the structure chart from Figure 17-9
Boss
VA
VA
VB
Get Valid
A
VB
Get Valid
B
Make
C
Put
C
FCR
VA
Read
A
Validate
A
Read
B
VB
Validate
B
FCR
Format C
Report
Print C
Report
Legend:
VA valid A
VB valid B
FCR formatted report
Figure 17-13 PVF Purchasing Fulfillment System data flow diagram with central
transform circled
Production
Schedulers
Suppliers
Production
Capacities
Production
Schedules
6.0
Order
Materials
Order
Suppliers
1.0
Forecast
Material
Needs
Preferred
Supplier
Bill of
Materials
4.0
Select
Preferred
Supplier
5.0
Produce
Bill of
Materials
2.0
Material
Forecasts
Plan
Purchase
Agreements
Price & Term

Quotes
Supplier
Material
Evaluations
Supplier
Description
Engineering
Criteria
Product
Design
3.0
Develop
Purchased
Goods Specs
Material
Specifications
Figure 17-14 Top-level structure chart for the PVF Purchasing Fulfillment System
Purchasing
Fulfillment
System
D
E
Get
Supplier
Data
Get
Material
Data
A
B
C
D
Plan
Purchase
Agreements
Develop
Purchased
Goods Specs
Legend:
price & term quotes
E material forecasts
supplier material evals.
F supplier description
material specs
G criteria
production schedule
H product design
Put
Materials
Orders
Figure 17-15 Refined afferent branches for the PVF Purchasing Fulfillment System structure chart
Material
specs
Supplier
material
evals
Production
schedule
Supplier
quotes
Material
forecasts
Get
Supplier
Data
Supplier
quotes
Get
Supplier
Quotes
Get
Material
Data
Supplier
material
evals
Material
forecasts
Get Supplier
Material
Evaluations
Material
specs
Get
Material
Forecasts
Get
Material
Specs
Production
capacities
Get
Production
Capacities
Production
schedule
Material
forecasts
Calculate
Material
Forecasts
Get
Production
Schedule
Figure 17-16 Refined central transforms and efferent branch for the PVF Purchasing Fulfillment System
structure chart
Production
schedule
Material
forecasts
Criteria
Price & term

quotes
Supplier
Material
evals
Supplier
description
Plan
Purchase
Agreements
Material
specs
Product
design
Product
design
Criteria
Supplier
description
Develop
Purchased
Goods Specs
Put
Materials
Orders
Preferred
supplier
BOM
Criteria
Product
design
Produce
Bill of
Materials
BOM
Supplier
description
Production
schedule
Select
Preferred
Supplier
Generate
Order
Order
Put
Order
Figure 17-19 Example of data coupling
Prepare
Customer
Bill
EOF
New
charges
Amount
paid
Current
balance
New
Balance
Calculate
New
Balance
Status
Figure 17-20 Example of stamp coupling
Prepare
Customer Bill
New charges
Amount paid
New balance
CUSTOMER
RECORD
CUSTOMER
RECORD
New balance
Calculate
New Balance
Formatted bill
Format
Customer Bill
Figure 17-21 Example of control coupling
Prepare
Customer Bill
Write amount is
30 days past due
Calculate
Amount Due
Figure 17-22a Examples of communicational cohesion: Example of a communicational cohesive module
Part supplier
Part cost
Part #
Part name
Find Part
Details
Using part-#
find part-name
find part-cost
find part-supplier
Figure 17-22b Examples of communicational cohesion: Example of a communicationally cohesive module split into
two functionally cohesive modules
Part cost
Part #
Part name
Find Part
Cost
Part supplier
Part #
Part name
Find Part
Supplier
Figure 17-24 Pseudocode description of Calculate New Balance module
Module name: Calculate New Balance

Receives: Current-balance, New-charges, Amount-paid, EOF
Returns: New-balance, Status
Set New-balance, Status to 0
Read Current-balance, New-charges, Amount-paid, EOF
Repeat
New-balance = Current-balance + New-charges Amount-paid
Beginif
If New-balance < 0
Then Status = 1
Else
Beginif
If New-balance = 0
Then Status = 2
Else Status = 3
Endif
Endif
Return New-balance, Status
Until EOF = YES
(Note: The data couple Status has three values, 1, 2, and 3. The value 1 corresponds to
credit, 2 to nothing due, 3 to amount due.)
Figure 17-25 Basic symbols in Nassi-Shneiderman charts
Do-while loop
Sequence
Do-until loop
condition
1
Conditional statement
Case statement
Figure 17-26 The contents of the module Calculate New Balance in the form of a Nassi-Shneiderman chart
Set New-balance to 0
Set Status to 0
Read Current-balance, New-charges, Amount-paid, EOF
New-balance = Current-balance + New-charges Amount-paid
New-balance < 0
No
Yes
New-balance = 0
Status = 1
Yes
Status = 2
Return New-balance, Status

Until EOF = YES
No
Status = 3
Figure 18-2
Outcomes and deliverables from designing distributed systems
1. Description of Site (for each site)

a. geographical information
b. physical location
c. infrastructure information
d. personnel characteristics (education, technical skills, etc.)
e.
2. Description of Data Usage (for each site)
a. data elements used
b. data elements created
c. data elements updated
d. data elements deleted
3. Description of Business Process (for each site)
a. list of processes
b. description of processes
4. Contrasts of Alternative IS Architectures for Site, Data, and
Process Needs (for each site)
a. pros and cons of no technological support
b. pros and cons of non-networked, local system
c. pros and cons of various distributed configurations
d.
Figure 18-3
File server model
Client
Process/scan tables
Application program
user interface
database processing
generate queries
Handle integrity and security
Full DBMS
Client
Client
Client
Local Area
Network
Requests
for data
Requests
to lock data
File Server
File storage
Record locking
Acts like extra
hard disk to client
Not very busy
Significant LAN traffic
Entire file
of data
Lock status
Data
File server
Figure 18-4
File servers transfer entire files when data are requested from a client
File Server Architecture

Server
Client
Entire file sent to client

Client request for data
Figure 18-5
Client/server architecture transfers only the required data after a request from a client
Client /Server Architecture

Server
Client
ONLY result of request

Client request for data
Figure 18-7
Customer relation for a bank
ACCT NO.
200
324
153
426
500
683
252
CUSTOMER NAME
BRANCH NAME
Jones
Smith
Gray
Dorman
Green
McIntyre
Elmore
Lakeview
Valley
Valley
Lakeview
Valley
Lakeview
Lakeview
BALANCE
1000
250
38
796
168
1500
330
Figure 18-8
Horizontal partitions
ACCT NO.
200
426
683
252
CUSTOMER NAME
BRANCH NAME
Jones
Dorman
McIntyre
Elmore
Lakeview
Lakeview
Lakeview
Lakeview
BALANCE
1000
796
1500
330
(a) Lakeview Branch

(a) Lakeview Branch
ACCT NO.
324
153
500
CUSTOMER NAME
BRANCH NAME
Smith
Gray
Green
Valley
Valley
Valley
(b) Valley Branch
(b) Valley Branch
BALANCE
250
38
168
Figure 18-9
Part relation
PART NO.
NAME
COST
DRAWING NO.
QTY ON HAND
P2
P7
P3
P1
P8
P9
P6
Cap
Lead
Spring
Clip
Body
Gripper
Eraser
100
550
48
220
16
75
125
123-7
621-0
174-3
416-2
321-0
400-1
129-4
20
100
0
16
50
0
200
Figure 18-10 Vertical partitioning of Part relation
PART
NO.
DRAWING
NO.
P2
P7
P3
P1
P8
P9
P6
123-7
621-0
174-3
416-2
321-0
400-1
129-4
(a) Engineering
PART NO.
NAME
COST
QTY ON HAND
P2
P7
P3
P1
P8
P9
P6
Cap
Lead
Spring
Clip
Body
Gripper
Eraser
100
550
48
220
16
75
125
20
100
0
16
50
0
200
(b) Manufacturing
Figure 18-13a Types of client/server architectures: Distributed presentation
FUNCTION
CLIENT
SERVER
Data management
All data management
Data analysis
All data analysis
Data presentation
Data for presentation on

server are reformatted
for presentation to user
Data delivered to client

using server presentation
technologies
Figure 18-13b Types of client/server architectures: Remote presentation
FUNCTION
CLIENT
SERVER
Data management
All data management
Data analysis
All data analysis
Data presentation
Data from analysis on

server are formatted for
presentation to user
Figure 18-13c Types of client/server architectures: Remote data management
FUNCTION
CLIENT
Data management
SERVER
All data management
Data analysis
Raw data from server are

retrieved and analyzed
Data presentation
All data presentation
Figure 18-13d Types of client/server architectures: Distributed function
FUNCTION
CLIENT
Data management
SERVER
All data management
Data analysis
Selective data from server

retrieved and analyzed
Data presentation
All data presentation,

from analyses on both
server and client
Selective data from server

retrieved and analyzed,
then transmitted to client
Figure 18-13e Types of client/server architectures: Distributed database
FUNCTION
CLIENT
SERVER
Data management
Local data management
Shared management of
data on server
Data analysis
Data retrieved from both

client and server for
analysis
Data presentation
Figure 18-13f Types of client/server architectures: Distributed processing
FUNCTION
CLIENT
SERVER
Data management
Local data management
Shared management of
data on server
Data analysis
Data retrieved from both

client and server for
analysis
Data retrieved from

server for analysis, then
sent to client for further
analysis and presentation
Data presentation
Figure 19-2
Steps in a typical code walkthrough
GUIDELINES FOR CONDUCTING A CODE WALKTHROUGH

1. Have the review meeting chaired by the project manager or chief
programmer, who is also responsible for scheduling the meeting,
reserving a room, setting the agenda, inviting participants, and so on.
2. The programmer presents his or her work to the reviewers. Discussion
should be general during the presentation.
3. Following the general discussion, the programmer walks through the
code in detail, focusing on the logic of the code rather than on specific
test cases.
4. Reviewers ask to walk through specific test cases.
5. The chair resolves disagreements if the review team cannot reach
agreement among themselves and assigns duties, usually to the
programmer, for making specific changes.
6. A second walkthrough is then scheduled if needed.
(Adapted from Yourdon, 1989)
Figure 19-3
Comparing stub and integration testing
Final
integration
testing
System
Initial
integration
testing
Get
Make
Stub
testing
Put
Figure 19-4
Test case description form
Pine Valley Furniture Company

Test Case Description
Test Case Number:
Date:
Test Case Description:
Program Name:
Testing State:
Test Case Prepared By:
Test Administrator:
Description of Test Data:
Expected Results:
Actual Results:
(Adapted from Mosley, 1993)

Figure 19-5
Test case results form
Pine Valley Furniture Company

Test Case Results
Test Case Number:
Date:
Program Name:
Module Under Test:
Explanation of difference between actual and expected output:
Suggestions for next steps:
(Adapted from Mosley, 1993)
Figure 19-7a Comparison of installation strategies: Direct installation
Current System
Install New
System
New System
Time
Figure 19-7b Comparison of installation strategies: Parallel installation
Current System
Install New
System
New System
Time
Figure 19-7c
Comparison of installation strategies: Single location installation
Current System
Install New
System
Location 1
New System
Current System
Install New
System
Location 2
New System
Figure 19-7d Comparison of installation strategies: Phased installation
Current
System
Install
Module 1
Current System
Without Module 1
Current System Without Modules 1 & 2 . . .
Install
Module 2
...
New Module 1
New Module 2
...
Figure 19-8
Scheins three-stage model of the change process
Stage 1:
Unfreezing
Creating motivation and readiness to change through

disconfirmation; creation of guilt or anxiety; provision
of psychological safety
Stage 2:
Changing Through
Cognitive Restructuring
Helping employees to see things, judge things, feel

things, and react to things differently based on a new
point of view
Stage 3:
Refreezing
Helping employees to integrate the new point of

view into their personal view and into their local
organizational relationships
(Adapted from Schein, 1987)
Figure 20-3a Outlines of users guides from various popular PC software packages:
Microsoft Access
MICROSOFT ACCESS HELP CONTENTS

Help Features
Whats New
Using Microsoft Access

Step-by-step instructions to help
you complete your tasks.
Cue Cards
The online coach that helps you
learn Microsoft Access as you do
your work.
General Reference
Guides to menu commands,
keyboard shortcuts, toolbars, and
windows and answers to common
questions.
Language and Technical Reference
Complete reference information
about properties, actions, events,
objects, and the Access Basic
language.
Technical Support
Available support options so that
you can get the most from
Microsoft Access.
Figure 20-3b Outlines of users guides from various popular PC software packages: WordPerfect for Windows 6.0
CONTENTS
Welcome to WordPerfect 6.0 for Windows Help
To find information, choose from the following items. To search for
information and to move through Help, use the buttons along the top of
the Help window.
Choose
For information about
Search (Index)
How Do I
Glossary
Menu Commands
WordPerfect Bars
Keystrokes
Whats New
Other Products
topics listed alphabetically

performing tasks
meanings of terms
features by menus
topics by Feature Bar, Power Bar, Ruler Bar, Button
Bar, and Status Bar
keystrokes and templates
features new to WPWin
other WPCorp products
Using Help
how to use Help

Figure 20-3c

CA Simple Tax 1993
CONTENTS
Getting Started
Using the Interview
Step by Step Overview
Tax Return Files
Opening a Taxpayer File
Creating a New Taxpayer File
Retrieving a Tax Return From Last Year
Saving Your Tax Return
Renaming Your Tax Return File
Erasing a Tax Return File
Completing Your Tax Return
Selecting Forms, Schedules and Worksheets
Entering Data
Deleting Data from a Form
Mini-Worksheets
Itemized List
Linking Between Forms
Tax Summary
Recalculating Your Return
Verifying Your Return
Importing Data from Other Programs
Importing Data from ASCII Files
Importing Data from Lotus Files
Importing Data from Quicken Files
Importing Data from CA-Simply Money
Importing Tax Exchange Format (TXF) Files
Tax Planning
Tax Forecasting
What If
Using CA-Simply Tax for Keeping Records
Printing Your Tax Return

Selecting a Printer
Printing a Complete Return
Printing Selected Forms
Printing Selected Itemized Lists
Printing Current Form, Schedules and Itemized Lists
Printing Multiple Copies
Printing Multiple Tax Returns
Printing 1040PC Format
Printing to Disk
Special Functions
Using Automatic Timed Backup
Tax Deadline Alarm
Tax Form and Tax Category Locator
ShoeBox
Filing Your Return
Filing By Mail
Filing Electronically
Getting Ready to Complete State Taxes
Creating State Resource File
Going to the State Tax Program
Troubleshooting
Efile Troubleshooting
Figure 20-4
Traditional information system environment and its focus on system documentation
Training
User
System
Documentation
Requests
Program
Documentation
Analyst/
Programmer
Data
File
Computer
System
Routine Report
Operations
(Adapted from Torkzadeh and Doll, 1993)

Programs
Figure 20-5
End user information system environment and its focus on user documentation
ApplicationOriented User
Documentation
Training
Interactive
Software
User
Consultation
Database
End-User
Tool Manual
(Adapted from Torkzadeh and Doll, 1993)

Computer
System
Programs
Figure 20-6
Frequency of use of computer training methods
Interactive
Training Manuals
5%
CAI
12%
Course
10%
Tutorial
7%
Resident
Expert
51%
External
5%
Help
Components
10%
(Nelson & Cheney, 1987)

Figure 20-7
A Microsoft Cue Card for Microsoft Access
CUE CARDS
Do your own work as you learn. Cue Cards can walk you through common Microsoft Access tasks
step by step.
What do you want to do?

> Build a Database with Tables
Build a database; create, import or attach tables.
> Work with Data
Add, view, edit, sort, or filter data in forms and datasheets.
> Design a Query
Create or troubleshoot queries.
> Design a Form
Create or customize forms.
> Design a Report or Mailing Labels
Create, customize, or print reports or mailing labels.
> Write a Macro
Design, run, or attach macros.
> Im Not Sure
Show me what a database is and what I can do with it.
To read about Cue Cards and how to use them, see About Cue Cards.
Figure 21-5
Types of maintenance
MaintenanceType
Corrective
Adaptive
Perfective
Non-Value Adding
Preventive
Value Adding
20
40
Percentage of the Maintenance Effort

(Adapted from Andrews and Leventhal, 1993)
60
80
Percent Change in Maintenance Effort from Norm
Figure 21-7
Quality documentation eases maintenance
400
400
300
200
200
125
100
Normal maintenance effort required

for average documentation quality
75
30
Norm 0
15
35
48
50
80
100
Poor
Average
Documentation Quality
(Adapted from Hanna, 1992)

High
Figure 21-8
How the mean time between failures should change over time
Average Days Between a Failure
25
20
15
10
0
1
Months Since System Was Installed
Figure 21-9
Flow chart of how to control maintenance requests
Change Request
Other
Adaptation
Type?
Evaluate,
Categorize,
Prioritize
Enhancement
Very
Evaluate,
Categorize
Kill
Inform
Requester
Error
Type?
Action
Severity
TOP
Priority
Do
Prioritize
Select next
task from
Top of Queue
(Adapted from Pressman, 1992)
Not very
Evaluate,
Categorize,
Prioritize
Figure 21-11 How Total Quality Management differs from Business Process Re-engineering
Process Improvement
Continuous
Improvement
BPR
Time

Figures Part 2

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Figures Part 2

Загружено:

Авторское право:

Доступные форматы

ELECTRONIC TRANSPARENCIES

Executive Editor: Michael Payne

Contrasting customer information forms (Pine Valley Furniture): Poorly

Contrasting customer information forms (Pine Valley Furniture):

Customer account status display using various highlighting techniques

Tabular report illustrating numerous design guidelines (Pine Valley

Chapter 14 Designing Interfaces and Dialogues

Specification outline for the design of interfaces and dialogues

Various types of menu configurations

Contrasting menu designs: Poor menu design

Contrasting menu designs: Improved menu design

Example of form interaction in the Netscape World Wide Web

Paper-based form for reporting customer sales activity (Pine Valley

Computer-based form reporting customer sales activity (Pine Valley

Hypertext-based help system from Microsofts Visual Basic

Dialogue diagram illustrating sequence, selection, and iteration

Highlighting graphical user interface design standards

State-transition diagram for spell checker

Chapter 15 Designing Databases: Logical Data Modeling

Simple example of logical data modeling: Highest volume customer

Simple example of logical data modeling: Backlog summary report

Simple example of logical data modeling: Integrated set of relations

Simple example of logical data modeling: Conceptual data model and

Simple example of logical data modeling: Final set of normalized

Relation with redundancy

EMP COURSE relation

Table with repeating data

Figure 15-11a Removing transitive dependencies: Relation with transitive dependency

Hoosier Burger inventory usage report

E-R diagram corresponding to normalized relations of Hoosier Burgers

Chapter 16 Designing Physical Files and Databases

Example code look-up table (Pine Valley Furniture)

Examples of referential integrity field controls: Referential integrity

Examples of referential integrity field controls: Referential integrity

Possible denormalization situations: Two entities with one-to-one

Possible denormalization situations: A many-to-many relationship with

Possible denormalization situations: Reference data

Comparison of file organizations: Sequential

Comparison of file organizations: Indexed

Comparison of file organizations: Hashed

Figure 16-10a File recovery approaches: Forward recovery

Example hash file layout and size

Figure 16-14a Database architectures: Hierarchical

Data volume chart

Chapter 17 Designing the Internals: Program and Process Design

Special symbols used in structure charts: (d) Pre-defined module;

How to read a structure chart: Non-overlapping arrows

How to read a structure chart: Overlapping arrows

A transaction-centered system design

A central transform in a data flow diagram

A transaction center in a data flow diagram

Complete first refinement of the structure chart from Figure 17-9

PVF Purchasing Fulfillment System data flow diagram with central

Top-level structure chart for the PVF Purchasing Fulfillment System

Refined afferent branches for the PVF Purchasing Fulfillment System

Example of data coupling

Example of stamp coupling

Example of control coupling

Figure 17-22a Examples of communicational cohesion: Example of a communicational

Pseudocode description of Calculate New Balance module

Basic symbols in Nassi-Shneiderman charts

The contents of the module Calculate New Balance in the form of a

Chapter 18 Designing Distributed Systems

Outcomes and deliverables from designing distributed systems