基本信息出版社：清华大学出版社
页码：458 页
出版日期：2009年05月
ISBN：7302197997/9787302197997
条形码：9787302197997
版本：第1版(影印版)
装帧：平装
开本：16
正文语种：中文
丛书名：大学计算机教育国外著名教材系列
外文书名：Object-Oriented Systems Analysis And Design Second Edition

内容简介 《面向对象系统分析与设计》是本科和研究生“系统分析与设计”课程的教材。
本书为读者展示了系统分析师所需掌握的概念、技能和技术等知识。本书的焦点是面向对象的系统分析与设计，并且遵循UML 2标准，但也包含了来自其他方法的元素，比如关系数据库系统设计的元素，它们如今仍然是企业组织中系统开发的一部分。作者用一个系统开发周期模型作为贯穿本书的组织工具，为学生提供一个强有力的概念上的、系统化的框架。通过一个集成的、扩充的说明性案例（松谷家具WebStore）和一个章末案例（百老汇娱乐公司）介绍了基于因特网的系统设计与开发的有关知识。
作者简介 Joey F. George，佛罗里达州立大学商业学院信息系统的教授和Thomas L. Williams Jr.杰出学者。George博士1979年在斯坦福大学获得学士学位，1986年在加利福尼亚大学欧文分校获得管理博士学位。他曾是路易斯安那州立大学E. J. Ourso工商管理学院信息系统的Edward G. Schlieder教授。1995年到1998年，他还任职为佛罗里达州立大学信息与管理科学系的教授。
Dinesh Batra， 佛罗里达国际大学教授，他的研究方向主要是系统和数据库分析与设计中的可用性问题。他是佛罗里达国际大学MIS计划MS的负责人。目前，他是系统分析与设计AIS特别兴趣组（SIGSAND）的主席，
Joseph S. Valacich，George and Carolyn Hubman 杰出MIS教授，Marian E. Smith Presidential Endowed首任主席。他具有亚利桑那大学、香港城市大学、Buskerud学院（挪威）、Riga工学大学（拉脱维亚）和赫尔辛基经济与商业学校的客座教授职位。
Jeffrey A. Hoffer 是代顿大学工商管理学院MIS、经营管理与决策科学系的数据管理Sherman标准的注册教授。他还在印第安纳大学和Case Western Reserve大学执教。Hoffer博士1969年在迈阿密大学获得了学士学位，1975年在康奈尔大学获得了博士学位。Hoffer博士是“信息系统国际会议”和“信息系统协会（AIS）”的共同创办人。他担任智利圣地亚哥天主教大学和芬兰Mikkeli的赫尔辛基经济与商业学院的客座讲师。Hoffer博士目前是Teradata University Network的副董事。
编辑推荐 1．《面向对象系统分析与设计》符合UML 2标准：本教材现在从头到尾都符合UML 2标准，改进了各个UML图的讨论。
2．敏捷方法：第1版包括对极限编程的有限讨论，而本书则包含了对敏捷方法更广泛的论述。
3．用例：第6章对用例和书写用例的不同观点层次更广泛的论述。
4．OCL：在第9章引入了对象约束语言（OCL）来表达业务规则。
5．模式：在第12章，使用模式将顺序图从分析阶段转到设计阶段。
6．BEC案例：百老汇娱乐公司（Broadway Entertainment Company，BEC）案例已经被更新和改进，不仅在业务方面更通行，而且在案例中刻画了更多的面向对象系统分析与设计。
目录
第一部分 面向对象系统开发基础
第1章 面向对象系统开发环境
第2章 面向对象导论
第二部分 项目管理和计划
第3章 管理面向对象的信息系统项目
第4章 选择和计划项目
第三部分 系统分析
第5章 确定面向对象系统的需求
第6章 组织系统需求：用例描述和图
第7章 概念数据建模
第8章 关系对象建模
第9章 分析类
第10章 选取最佳的设计策略
第四部分 系统设计
第11章 物理数据库设计
第12章 设计元素
第13章 设计人机界面
第五部分 系统实现与运转
第14章 OOSAD实现与运转

PART I: FOUNDATIONS FOR OBJECT-ORIENTED
ovovFIVIS DEVELOPIVIENT 1
o /STEIVIS DEVELOPIVIENT 1
CHAPTER 1 The Object-Oriented SVstems Development
ject-Oriented Systems Development
Environment 1
What is information Systems Analysis and Design? 3
y items Analysis and Design? 3
qxrQfems Anallrcis and Design. Core Concep+s 3
systems Analysis and Design: Core Concepts 3
ystems Analysis and Design: Core Concepts 3
qxrQtems 5
aVstems 5
ybtems 5
Definitions of a System and its Parts 5
yinltions of a System and its Parts 5
Important Systems Concepts 6
portant Systems Conceits 6
Information Systems Analysis and Design 9
j items Analysis and Design 9
atal One: Proiprt, A faviaqpm
atep One: Protect bynamement and Planning 9
p One: Project management and Planning 9
step Two: Systems Analysis 9
atep Two: Systems Analysis 9
r totems Analysis 9
atal Three: SI'stems Design 7n
atal Three: Systems Design 10
p Three: Systems Design 10
al Four: SI'c, lmnlementation and OP
steP Four: Systems Implementation and Operation 10
p Four: Systems Implementation and Operation 10
Types of information SVstems and SVstems Development 11
y pos of information Systems and Systems Development 11
Transaction Processing Systems 12
g Systems 12
bananament information Systems 12
c, formation Systems 12
Decision Support Systems 13
pport Systems 13
The Analyst's Role in SVstems DevelODment 13
J ystems Development 13
qxrcfems AnalxrQ+c in +h qTrstems Dev
systems AnalVsts in the Systems DevelODment Process 15
ystems Analysts in the Systems Development Process 15
The Evolution of Systems Development Methodologies 16
ystems Development Methodologies 16
,,,:M,MZsc:7::):fT,",t
systems Development Life Cycle (SDLC) 17
y>tems Development Life Cycle (SDLC) 17
structured Analllcic ovid npciavi 1 7
atructured Analysis and Design 17
.fis and Design 17
Data-Oriented Methodologies 19
gles 19
The Obiect-Oriented methodology 19
]ect-Oriented Methodology 19
Agile Methodologies 19
gileMethodologies 19
Why Should We Use Object-Oriented Systems Analysis and Design
(OOSAD)? 20
Iterative and incremental Development 22
RUP'S Iterative, Incremental Approach to OOSAD 22
pproach to OOSAD 22
Our Approach to Object-Oriented Systems Analysis and Design 25
.
Key Points Review j,,;-:,i,"t,d Systems Analysis and Design 25
j
Key Terms CheckDoint 27
y Yerms Checkpoint 27
Review Questions 28
Problems and Exercises 28
Discussion Questions 29
Case Problems 29
CHAPTER 2 Introduction to Object Orientation 31
)
Object Orientation 32
,
What iS an Obiect? 32
,act? 32
Class 33
Overation 34
peration 34
Attribute 34
Encapsulation 35
r
Obiect identity 36
ject identity 36
Generalization 36
Polymorphism 37
ymorphism 37
...
1 1 1

Interface 38
jace 38
Component 38
ponent 38
Package 39
sc 39
Association 39
qxrQtems ModelinZ 40
Dvstems Modeling 40
y>tems Modeling 40
What iS Modeling? 40
6. &0
What iS United Modeling Language (UML)? 40
Vied Modeling Language (UML)? 40
Key Points Review 42
y Points Review 42
Key Terms Checkpoint 43
y ferms Checkpoint 43
Review Questions 43
Problems and Exercises 44
Discussion Questions 44
Case: BroadwaV Entertainment Company, Inc. 44
y entertainment Company, Inc. 44
Company Background 44
PART II: PROJECT IVIANAGEIVIENT
AND PLANNING 51
CHAPTER 3 Managing the Obiect-Oriented information
.lug the Object-Oriented information
Rtrstems Protect 51
Dvstems Protect 51
ystems Project 51
Managing an OOSAD Protect 52
ding an OOSAD Project 52
Characteristics of the OOSAD Protect 55
v the OOSAD Project 55
Initiating the Protect 62
s the Project 62
Planning the Protect 64
o foe Project 64
Executing the Protect 70
s the Project 70
Closing Down the Protect 72
o ]ect 72
Representing and Scheduling Project Plans 74
Understanding the Critical Path of a Network Diagmm 76
De6ning the WOrk Breakdown Structurefor OOSAD Projects 79
bining the WOrk Breakdown Structurefor OOSAD Projects 79
Calculating Expected Time Durations USing the Program Evaluation Review
Techniaue (PERT) 79
lue (PERT) 79
Constructing a Gantt Chart and NetWork Diagram for an OOSAD Project
.' x.
in Microsoft Protect 80
)ect 80
Establishing a Project Starting Date 81
g a Project Starting Date 81
Entering TaskS and Assigning Task Relationships 81
g TaskS and Assigning Task Relationships 81
selecting a Scheduling Method to Review Protect Reports 82
Defecting a Scheduling Method to Review Project Reports 82
s a Scheduling Method to Review Project Reports 82
KeV Points Review 84
y Points Review 84
Review Questions 85
Key Terms Checkpoint 85
j lerms Checkpoint 85
Problems and Exercises 86
Discussion Questions 87
Case Problems 88
Case: BroadwaV Enterta~ent Company, Inc. 89
J pany, Inc. 89
Managing an Oblect-Oriented information Systems Project 89
.lug an Object-Oriented information Systems Project 89
CHAPTER 4 Selecting and Planning Protects 92
o and Planning Projects 92
Identifying and Selecting OOSAD Projects 93
j a and Selecting OOSAD Projects 93
The Process olldentifying and Selecting OOSAD Projects 94
v identifying and Selecting OOSAD Projects 94
Deliverables and Outcomes 97
Initiating Planning and Executing OOSAD Projects 97
a, Planning, and Executing OOSAD Projects 97
The Process of initiating, Planning, and Executing OOSAD Projects 98
v s, Planning, and Executing OOSAD Projects 98
Deliverables and Outcomes 100
Pine Valley Furniture Company Background 101
y furniture Company Background 101
Identincation and Selection of the WebS tore 102
,ication and Selection Of the WebS tore 102
Initiating and Planning the WebS tore 102
g and Planning the WebS tore 102
Assessing Project reasibility 102
g Project reasibility 102
Assessing Economic Feasibility 104
Assessing Technical Feasibility 110
g Technical Feasibility 110
Assessing Other Feasibility Concerns 111
3 y
.
IV Contents

Building and ReviewinZ the Baseline Protect Plan 113
a and Reviewing the Baseline Project Plan 113
Building the Baseline Project Plan 113
g the Baseline Project Plan 113
Introduction Section of the Baseline Protect Plan 113
9 the Baseline Project Plan 113
Reviewing the Baseline Project Plan 117
g the Baseline Project Plan 117
Key Points Review 121
y Points Review 121
Key Terms CheckDoint 122
j. point 122
Review Questions 123
Problems and Exercises 123
Case Problems 124
Discussion Questions 124
Case: Broadway Entertainment ComDany, Inc. 126
y entertainment Company, Inc. 126
Initiating and PlanninZ a Web-Based Customer RelationshiD
o and Planning a Web-Based Customer Relationship
Management System 126
a ybtem 126
PrtRT III: SYSTEIVI ANALYSIS 1 3O
CHAPTER 5 Determining Obiect-Oriented Systems
a ject-Oriented Systems
Requirements 130
Performing Reauirements Determination 131
a Requirements Determination 131
What iS a Reauirement? 132
luirement? 132
The Process of Determining Reauirements 132
v Determining Requirements 132
Deliverables and Outcomes 133
Reauirements Structuring 133
luirements Structuring 133
Traditional Methods for Determining Reauirements 134
a Requirements 134
Interviewing and LiStening 134
g and LiStening 134
Directly Observing USers 138
y Observing USers 138
Analyzing Procedures and Other Documents 139
y~ing Procedures and Other Documents 139
Modem Methods for Determining System ReQuirements 144
a system Requirements 144
joint Application Design 144
USing Prototyping during Requirements Determination 147
g Prototyping during Requirements Determination 147
USing Agile Methodologies during Reauirements Determination 148
g Agile Methodologies during Requirements Determination 148
Agile USaal-Centered Design 148
gile USage-Centered Design 148
The Planning Gamefom eXtreme Progmmming 149
g Gamefom eXtreme Progmmming 149
PVF Webstore: Determining System Requirements 150
a system Requirements 150
Determining System Requirementsfor Pine Valley Furniture'S WebS tore 151
g System Requirementsfor Pine Valley Furniture'S WebS tore 151
Key Points Review 153
j Points Review 153
Key Terms CheckDoint 154
y Yerms Checkpoint 154
Review Questions 154
Problems and Exercises 155
Discussion Questions 155
Case Problems 155
Case: Broadway Entertainment Company, Inc. 156
j entertainment Company, Inc. 156
Determining Reouirements for the Web-Based Customer RelationshiD
a Requirements for the Web-Based Customer Relationship
Management System 156
a totem 156
CHAPTER 6 Structuring SVstem Requirements: Use-Case DescriDtion
a system Requirements: Use-Case Description
, ~.
and Diagrams 161
crams 161
Use Cases 162
What iS a USe Case? 163
Deliverables and Outcomes 163
Use-Case Diagrams 164
clams 164
De6nitions and Symbols 165
yinltions and Symbols 165
Developing USe-Case Diagmms: Three Examples 167
ping USe-Case Diagmms: Three Examples 167
Developing USe Cases for Pine Vallry Furniture'S WebS tore 171
ping USe Casesfor Pine Valley Furniture'S WebS tore 171
Written Use Cases 172
Level 172
The Rest olthe Temviate 173
V Lhe Template 173
Writing USe Cases for Pine Valley Furniture'S WebS tore 176
g USe Casesfor Pine Valley Furniture'S WebS tore 176
Developing USe Cases 179
ping USe Cases 179
Contents V

Key Points Review 180
Key Terms Checkpoint 180
y lerms Checkpoint 180
Review Questions 181
Problems and Exercises 181
Discussion Questions 182
Case Problems 182
Case: Broadway Entertainment Company, Inc. 183
y entertainment Company, Inc. 183
Use-Case Modeling for the Web-Based Customer Relationship
Management System 183
gement System 183
CHAPTER 7 Conceptual Data Modeling 187
ConceptUal Data Modeling 189
The Process of Conccotual Data Modeling 189
U conccytual Data Modeling 189
Gathering information for ConceptUal Data Modeling 190
Introduction to UML Data Modeling 192
Class 192
Obiect 193
]ect 193
Attributes 193
Identifiers 194
Viers 194
Important Considemtions for Selecting PrimarV Kegs (identifiers) 194
portant Considemtionsfor Selecting Primary Keys (identifiers) 194
MultinaluedAttributes 195
ComnositeAttributes 196
poslteAttributes 196
Relationships 196
ps 196
Association 200
Aggregation RelationshiP 202
sgregation RelationshiP 202
Composite Structure Diadem 204
r gcm 204
An Example of ConceptUal Data Modeling for PVF WebStore 207
Generalization Relationship 205
P 205
Key Points Review 208
y Points Review 208
Key Terms Checkpoint 209
y lerms Checkpoint 209
Review Questions 210
Problems and Exercises 210
Discussion Questions 211
Case Problems 211
Case: Broadway Entertainment Company, Inc. 213
y entertainment Company, Inc. 213
Conceptual Data Modeling for the Web-Based Customer Relationship
Management System 213
gement System 213
CHAPTER & Obiect-Relational Modeling 216
,ect-Relational Modeling 216
Object-Relational Data Modeling 218
,ect-Relational Data Modeling 218
Relational Data Model (RDM) 218
Well-Structured Relations 219
NOrmalization 220
Object Extensions to Relational Data Model 224
,
Genemlization/Specialization 225
I
MultivaluedAttributes 225
Mechanisms to Support Aggregation 225
pportAggregation 225
Obiect identifiers 226
,ect identifiers 226
Relationship by References 226
p by References 226
Incorporation olMethods in an Obiect Relation 226
poration Of Methods in an Object Relation 226
Richer Set of Types 226
v abpes 226
Translating Conceptual Data Models into Object Relations 227
Translating Classes 227
g Classes 227
Translating Relationships 228
a Relationships 228
Merging Object Relations 231
ging Object Relations 231
Logical Design of PVF WebStore 232
.ical Design of PVF WebStore 232
Key Points Review 233
y Points Review 233
Key Terms Checkpoint 234
y lerms Checkpoint 234
.
VI Contents

Review Questions 234
Problems and Exercises 235
Discussion Questions 237
Case Problems 237
Case: Broadway Entertainment ComDanv inc. 237
j. pany, Inc. 237
Designing the Obiect-Relational Data Model for the Customer
aning the Object-Relational Data Model for the Customer
Relationship Management System 237
'
CHAPTER 9 Analysis Classes 239
ysis Classes 239
Analysis Classes 241
y his Classes 241
qtereotirDing Classes 241
stereotyping Classes 241
j ping Classes 241
Entity Class 242
y class 242
Boundary Class 242
H class 242
Control Class 242
Drawing SeQuence DiaZrams 243
g Sequence Diagrams 243
qeallpnrp Diagmmfor the Place Order USe Case 245
sequence Diagmmfor the Place Order USe Case 245
iuence Diagmmfor the Place Order USe Case 245
Seauence Diagram for the Mike Reservation USe Case 249
sequence Diagramfor the Mike Reservation USe Case 249
luence Diagramfor the Mike Reservation USe Case 249
Robustness Analysis of SeQuence Diagrams 249
ysis of Sequence Diagrams 249
Drawing Communication Diagrams 251
a grams 251
Analysis Class Diagram 252
j .is Class Diagram 252
ActivitV Diagram 253
j Diagram 253
When to USe an Activity Diagram 255
. Ulagram 255
When Not to USe an Activity Diadem 256
y Diagram 256
abate (or Statechart) Diagram 256
atate (or Statechart) Diagram 256
When to USe State Diagrams 257
grams 257
Modeling Business Rules in Analysis Classes 258
a DUStness Rules in Analysis Classes 258
Constraints 258
Calculations 259
Value inferences 259
Yerences 259
Action Enablers 261
The Obiect Constmint Language (OCL) 261
ject Constmint Language (OCL) 261
Key Points Review 263
y Points Review 263
Key Terms CheckDoint 264
y lerms Checkpoint 264
Review Questions 265
Problems and Exercises 265
Discussion Questions 267
Case Problems 267
Broadway Entertainment ComDanv inc. 268
j entertainment Company, Inc. 268
Designing the Analysis Classes for the Customer RelationshiD
oning the Analysis Classes for the Customer Relationship
Management System 268
a ystem 268
CHAPTER 10 Selecting the Best Alternative DesiZn StrateZv 271
g the Best Alternative Design Strategy 271
selecting +he Best Alternative Design q+--'ocrl'
Defecting the Best Alternative Design StrateZxr 973
a Lhe Best Alternative Design Strategy 273
The Process of Selecting the Best Alternative Design Strategy 972
a the Best Alternative Design Strategy 273
Deliverables and Outcomes 274
Generating Alternative Design StrateZies 274
a Alternative Design Strategies 274
Issues to Consider in Generating Alternatives 276
& alternatives 276
Outsourcing ?76
8 276
sources of SOftware 277
sources of SOftware 277
v SOftware 277
Choosing Off-the-Shelf Software 281
g Off-the-Shelf Software 281
Hardware and System Software ISsues 283
totem Software ISsues 283
Implementation ISsues 284
plementation ISsues 284
selecting foe Best Alternative Design q+-rye c fi'
Defecting the Best Alternative Design StrateZxr for Pine Valle\r Furniture'Q
a Lhe Best Alternative Design Strategy for Pine Valley Furniture's
WebStore 285
selecting foe Most Likelll
Defecting the Most Likely Alternative 285
g the Most Likely Alternative 285
A Description of the Chosen Alternative 287
ption Of the Chosen Alternative 287
Contents Vii

Updating the Baseline Project Plan 287
Before and After Baseline Protect Plans for PVF's WebStore 290
ject Plans for PVF's WebStore 290
Key Points Review 293
j'
Key Terms Checkpoint 294
y lerms Checkpoint 294
Review Questions 294
Problems and Exercises 295
Discussion Questions 296
Case Problems 296
Case: Broadway Entertainment Company, Inc. 298
j. pany, Inc. 298
Formulating a Design Strategy for the Web-Based Customer Relationship
Management System 298
b ystem 298
PrtRT IV: SySTEIVIS DESIGN 3OI
CHAPTER 11 Physical Database Design 301
y.ical Database Design 301
Physical Database Design 303
y .ical Database Design 303
structured Query Language (SoL) 304
atructured Query Language (SoL) 304
Designing Fields 307
alling Fields 307
Choosing Data Types 309
g Data Types 309
Controlling Data integrity 310
s Data integrity 310
Designing Physical Tables and Denormalization 311
aning Physical Tables and Denormalization 311
File Organization 314
.anlzation 314
Secondaril Stooge Concepts 315
secondary Stooge Concepts 315
y storage Concepts 315
Hashed File Organizations 317
ganlzations 317
Indexed File Organizations 317
.anlzations 317
Design of Obiect-Relational Features 323
on of Object-Relational Features 323
Genemlization 323
Aggregation 324
ssregation 324
MultivaluedAttributes 325
Obiect identifier 326
]ect identifier 326
Relationship by Reference 326
r, Reference 326
Physical Database Design of PVF WebStore 327
y >ical Database Design of PVF WebStore 327
Key Points Review 329
y Points Review 329
Key Terms Checkpoint 329
y lerms Checkpoint 329
Review Questions 330
Problems and Exercises 330
Discussion Questions 331
Case: Broadway Entertainment Company, Inc. 332
y Entertainment Company, Inc. 332
Designing the Physical Database for the Customer Relationship
alling the Physical Database for the Customer Relationship
Management System 332
gement System 332
CHAPTER 12 Design Elements 334
Design Elements 336
an Elements 336
Design Architecture 337
an Architecture 337
Tiered Architecture 337
Two-Tier Architecture 338
Three-Tier Architecture 338
N-TierArchitecture 339
Mapping from Analysis Classes to Design Elements 340
i ping from Analysis Classes to Design Elements 340
Components 341
Component Standards 342
COb, COMI, and Distributed COb (DCOM) 342
Common Obiect Request Broker Architecture (CORBA) 343
,ect Request Broker Architecture (CORBA) 343
Enterprise lava Beaus (bIB) 343
prize java Beaus (are) 343
COb, CORBA, and EIB: Comparisons and Problems 346
XML/SOAP: An integmtion Solution 346
...
Vlll Contents

Frameworks 347
.NET Framework and Visual Studio .NET 347
lava 2 Enterprise Edition (IZEE) 349
Logic at the Browser: ScriDtinZ LanZuaZes 349
ale at the Browser: Scripting Languages 349
Encapsulation at the Database End 350
psulation at the Database End 350
Packages 352
ges 352
Design Class Diagrams 353
an Class Diagrams 353
Verifying Responsibility Allocation 353
Yying Responsibility Allocation 353
Visibilitv 354
y ac4
Attribute Types 356
apes 356
PVF Example 357
Key Points Review 358
j i oints Review 358
Key Terms Checkpoint 359
j lerms Checkpoint 359
Review Questions 361
Problems and Exercises 361
Discussion Questions 362
Case: Broadway Entertainment ComDany, Inc. 362
j' pany, Inc. 362
Developing Design Elements for the Customer Relationship
ping Design Elements for the Customer Relationship
Management System 362
a yDtem 362
CHAPTER 13 Designing the Human interface 364
.mug the Human interface 364
Designing Forms and Reports 365
oning Forms and Reports 365
The Process of Designing rorms and Reports 366
U Designing rorms and Reports 366
Deliverables and Outcomes 367
Formatting Forms and ReDorts 370
a forms and Reports 370
General Formatting Guidelines 371
8
Highlightinglnformation 372
khlightinglnformation 372
Displacing Text 373
playing Text 373
Designing Tables and Lists 374
.mug Tables and Lists 374
Paver Versus Electronic Reports 376
per Versus Electronic Reports 376
Designing Web Layouts 377
gning Web Layouts 377
Designing interfaces and DialoZues 378
.mug interfaces and Dialogues 378
The Process of Designing interfaces and Dialogues 379
U Designing interfaces and Dialogues 379
Deliverables and Outcomes 379
Designing interfaces 380
aning interfaces 380
Designing Layouts 380
suing Layouts 380
structuring Data Entnl adZ
atructuring Data Entry 383
g Data Entry 383
Controlling Data input 383
s Data input 383
Providing Feedback 385
g Feedback 385
Errors and Warning Messages 386
s Messages 386
Providing Hely 387
grIp 387
Designina Web interfaces 389
gning Web interfaces 389
Designing Dialogues 390
aning Dialogues 390
Designing the Dialogue Seauence 391
gning the Dialogue Sequence 391
Building Prototypes and Assessing USability 393
g Prototypes and Assessing USability 393
Key Points Review 394
j i oints Review 394
Key Terms CheckDoint 395
J point 395
Review Questions 395
Problems and Exercises 396
Discussion Questions 396
Case Problems 397
Case: Broadway Entertainment ComDany, Inc. 398
j. pany, Inc. 398
Designing the Human interface for the Customer RelationshiD
aning the Human interface for the Customer Relationship
Management System 398
s ybtem 398
Contents iX

PrtRT V: SySTEIVIS IIVIPLEIVIENTATION
AND OPERATION 4O3
CHAPTER 14 OOSAD Implementation and Operation 403
qxrQfems ImDlementation and ODeration 405
systems Implementation and Operation 405
ybtems Implementation and Operation 405
The Processes ofprogmm Coding, Testing, and installation 406
v Progmm Coding, Testing, and installation 406
Deliverables and Outcomes hem Program Development, Testing,
j rom Program Development, Testing,
and installation 406
The Processes o{Documenting the System, Training USers,
v Documenting the System, Training USers,
and Supporting USers 407
PPorting USers 407
Deliverables and Outcomes from Documenting the System, Training USers, and
j s she System, Training USers, and
qitvvortinq USers 407
supporting USers 407
pporting USers 407
The Process of maintaining Information Systems 408
V,dsintaining information Systems 408
Deliverables and Outcomes horn Maintaining information Systems 409
jrom Maintaining information Systems 409
Coding 409
8 109
Combining Coding and Testing 410
3 s and Testing 410
Reuse 410
Obiect FrameworkS 413
,ect FrameworkS 413
software ADnlication TestinZ 413
software Application Testing 413
Seven Different Tllnes of Tests 413
seven Different Types of Tests 413
Vjerent Types of Tests 413
The Testing Process 415
g Process 415
Acceptance Testing by USers 416
ptance Testing by USers 416
Installation 417
Planning installation 417
s Installation 417
Documenting the System 419
a the System 419
USer Documentation 420
Preparing USer Documentation 421
paring USer Documentation 421
Training and Supporting Users 422
o and Supporting Users 422
Training information System USers 422
c, formation System USers 422
quvvortinq Information System USers 424
supporting information System USers 424
r porting information System USers 424
Why Implementation Sometimes Fails 425
j. plementation Sometimes Fails 425
Protect Closedown 427
ject Closedown 427
Conducting Systems Maintenance 427
a systems Maintenance 427
Types of maintenance 428
,pos of maintenance 428
The Cost of maintenance 428
v ldeintenance 428
Measuring Maintenance Effectiveness 430
s Maintenance Effectiveness 430
Controlling Maintenance Reauests 430
s Maintenance Requests 430
Role of CASE and Automated Development TOols in Maintenance 432
v pment TOols in Maintenance 432
qxrstems ImDlementation and Operation for Pine Valle\r Furniture's
Dvstems Implementation and Operation for Pine Valley Furniture's
j items Implementation and Operation for Pine Valley Furniture's
WebStore 432
Developing Test Cases for WebS tore 432
ping Test Casesfor WebS tore 432
Bug Tracking and System Evolution 433
o c, totem Evolution 433
Alpha and Beta Testing the WebS tore 433
pha and Beta Testing the WebS tore 433
WebStore installation 434
KeV Points Review 434
j
Key Terms Checkpoint 436
y lerms Checkpoint 436
Review Questions 437
Problems and Exercises 437
Discussion Questions 438
Case Problems 438
Case: Broadway Entertainment Company, Inc. 439
j' pany, Inc. 439
Designing a Testing Plan for the Customer Relationship Management
huing a Yesting Plan for the Customer Relationship Management
qxrcfem 439
system 439
ystem 439
References 443
AcronVmn Glossary 449
ymn Glossary 449
Glossary 451
y 451
X Contents
……
序言 PREfaCE
OUR APPROACH
Today's business environment is dynamic, turbulent, and global. Information
systems have moved from back-office t6chnologies understood by only a few to
pervasive, essential support technologies that touch all aspects of business and all players
in the game. As the role of information technology in business has changed, so have
the underlying t6chnologies and the manner in which systems are developed. Long
predict6d to be the next big thing, object orientation has finally arrived. The adoption
of object orientation has not resulted in the dramatic paradigm shift that also was
predicted for so long. Instead, we are witnessing the emergence of a hybrid approach
to systems and their development--an approach that encompasses some aspects of
traditional systems development and some aspects of object orientation. Although
this book focuses on object-oriented systems analysis and design and it adheres to
UML standards, it contains elements from other approaches, such as elements of
relational database system design, that remain a part of systems development in
business organizations today.
Among the four of us, we have more than 80 years of combined teaching
experience in systems analysis and design, including teaching database management and
object-oriented approaches. We have used that experience to create Object--Oriented
Systems Analysis and Design, Second Edition. As was true in the first edition, we
provide a clear presentation of the concepts, skills, and techniques students need to
become effective systems analysts who work with others to create information
systems for businesses. We continue to use a systems development cycle model as an
organizing tool throughout the book to provide students with a strong conceptual
and systematic framework. Internet coverage is provided in each chapter via an
nit6grated, extended illustrative case (Pine Valley WebStore) and an end-of-chapter case
(Broadway Entertainment Company, Inc.).
Many systems analysis and design courses involve lab work and outside
reading. This means that lecture time can be limited. Based on market research and our
own teaching experience, we understand the importance of using a book that
combines depth of coverage with brevity. We have created a 14-chapter book that covers
key object-oriented systems analysis and design (OOSAD) content without
overwhelming students with unnecessary detail. The book is a compromise between
briefer approaches to OOSAD and larger, more comprehensive volumes.
Object--Oriented Systems Analysis and Design, Second Edition is characterized by
the following themes:
1' Systems development is finnly rooted in an organizational context. The
successful systems analyst needs a broad understanding of organizations,
organizational culture, and operation.
2' Systems development is a practical field. Coverage of current practices as
well as accepted concepts and principles is essential in a textbook.
3' Systems development is a profession. Standards of practice, a sense of
continuing personal development, ethics, and a respect for and collaboration with
the work of others are general themes in the textbook. These principles are
constant, regardless of the t6chnical approach to development.
xI

4' Systems development has changed significantly with the explosive growth in
the adoption of object-oriented approaches to systems development. In many
.
.
orb~ations, traditional tools that sllPDort svst6ms develODment such as data
aaruzations, traditional tools that support systems development, such as data
flow diagrams, have been replaced with obiect-oriented tools such as use-case
diagrams, have been replaced with object-oriented tools such as use-case
dia1., 1.,,. n.,
grams, sequence diagrams, and analysis class diagrams. Pure relational database
.
',,, 1,.', 1.
management approaches have been reDlaced with obiect-relational approaches.
bement approaches have been replaced with object-relational approaches.
Our approach in this book focuses exclusively on diagrams and tecboques
associpproach in this book focuses exclusively on diagrams and tecboques
associ.
.,.. 1
~+o 1 T 'f k OOSAD.
at6d with OOSAD.
R R,,ccess in slrstems anallrsis and desiZrt rorr
>' Success in sVstems analysis and design requires not onlV skills in
methodoloystems analysis and design requires not only skills in
methodolo. t' t.'
gies and techniques but also in the management of time, resources, and risks.
Thus, learning systems analysis and design requires a thorough understanding
of the process as well as the techniques and deliverables of the profession. Our
.
1',..
~ k aam k. +, 1 1 L 1..
approach to process emphasizes a systems development cycle as an organizing
i proach to process emphasizes a systems development cycle as an organizing
..,,. 1
principle and the focus on development iterations prevalent in object-oriented
1. 1 1.
~' ITTC;s and design
analysis and design.
ysls and design.
Given these themes, this textbook emphasizes the following:
. A business rather than a technology perSDective.
by perspective.
~, .,. 1.
. foe role, responsibilities, and mindset of the systems analyst as well as the
sVs, responsibilities, and mindset of the systems analyst as well as the
systems project manager, rather than those of the programmer or business managed
project manager, rather than those of the programmer or business managed
~1.
. foe methods and principles of sVstems development rather than the specific
principles of systems development rather than the specific
tools or tool-related skills of the field.
NEW TO THE SECOND EDITION
1' UML 2 compliant: The text is now UML 2 compliant throughout. Coverage of
I
, T T'
each UML diagram has been improved. Adequate coverage of UML diagrams is
clam has been improved. Adequate coverage of UML diagrams is
... r...
lmDortant for prospective systems analysts. A recent studV shows that systems
portant for prospective systems analysts. A recent study shows that systems
developers routinely rely on these diagrams in their work (Lang, 2006). Almost
1 1
~11 O7 yi r 1,CO q' L nTvi. k'
all, 97 percent, use screen prototypes, with the proportions using other analysis
percent, use screen prototypes, with the proportions using other analysis
1 1.,.
~ac 1 1. 1 i
and design diagrams as follows: 95 percent use activity diagrams: 74 percent
hi[ diagrams as follows: 95 percent use activity diagrams; 74 percent
'.' 1.. 1.,. --
.use entitV relationshiD diagrams; 72 percent rely on use-case diagrams: 62
bern relationship diagrams; 72 percent rely on use-case diagrams; 62
per.
',,. 1 qri.
cent use class diagrams; and 50 percent use state diagrams. All of these diagram
crams; and 50 percent use state diagrams. All of these diagram
types are covered in the book.
y pos are covered in the book.
~. ..,,... T. n .1' 1 r.
2' Agile methodologies: While the first edition included limited coverage of
gile methodologies: While the first edition included limited coverage of
1
extreme programming, the text now contains much more extensive treadment of
.
. 1. 1 1 1.., 1.,'
~ .l *k 1 1.. l, 1 1 iap k F yi'
agile methodologies, including but not limited to extreme DroRramminR
.lie methodologies, including but not limited to extreme programming.
Coverage extends across several chanters, including Chapters 1, 5, and 14.
ge extends across several chapters, including Chapters 1, 5, and 14.
~, T
1 tTse cases: ChaD+
J' Use cases: Chapter 6 now featheres a more extensive treadment of use cases
, r 1. r
aam 1 C Jittovivi 1 Is of'
and of differing levels of DerSDective from which use cases can be written.
a levels of perspective from which use cases can be written.
4' OCL: The obiect constraint language (OCL) is introduced to express business
)ect constraint language (OCL) is introduced to express business
1.
rules in Chapter 9.
pier 9.
R p.ftems: In Chaleter 12 no++ 1 1
>' Patterns: In Chapter 12, patterns are used to convert sequence diagrams from
pier 12, patterns are used to convert sequence diagrams from
the analysis to the design stage.
ysls to the design stage.
6' BEC case: The Broadway Entertainment ComDanv case has been uDdated and
y Entertainment Company case has been updated and
., 1. 1. 1
lmDroved, both to be more current in business terms. and to feature more
proved, both to be more current, in business terms, and to feature more
1.
object-oriented systems analysis and design in the case.
ject-oriented systems analysis and design in the case.
WU D I E NCE
Obiect-Oriented Systems Analysis and Design is written with the assumDtion that
sin]ect-Oriented Systems Analysis and Design is written with the assumption that
students have taken an introductory course on comDuter systems and have experience
j puter systems and have experience
.....
writing Drograms in at least one DroZramminZ language, preferably an
objects programs in at least one programming language, preferably an
object.. n
xll Preface

oriented language. We review basic system DrinciDles for those students who have
auage. We review basic system principles for those students who have
not been exposed to the material on which systems development methods are
ybtems development methods are
based. We also assume that students have a solid background in computing literacy
and a general understandinZ of the core elements .fraobusi::ZudC=
o g of the core elements of a business, including basic
terms associated with the production, marketing, finance, and accounting functions.
'
O R GuN IZnTI O N
The overall organization of the book is the same as it was in the first edition. The
outsanlzation of the book is the same as it was in the first edition. The
outline of the book begins with basic foundational material and then follows a slrstems
dins with basic foundational material and then follows a systems
development .;f e5 =:
pment cycle, which allows for a logical progression of topics. This cycle is

7. Managerial focus--Throughout the book, the treadment of systems
development and implementation is always within the context of management of
change, conversion strategies, and organizational factors in systems acceptance.
8. Database approach--Unique approach to data using object-relational database
management systems (DBMSs) featuring Oracle10g.
9. Diagrams--The diagrams used throughout the text were developed using the
Rational Rose CASE tool, Microsoft'S Visio, and Microsoft's Project.
illustrative Fictional Cases
Pine Valley Furniture (PVF) This case is introduced in Chapter 4 and revisited
throughout the book. As key systems development cycle and object-oriented
concepts are presented, they are applied and illustrated with this case. A margin
icon identifies the location of the case. PVF is a furniture company, founded in 1980,
and management has decided to explore electronic commerce as an avenue to
increase its market share. A case problem related to PVF is included in the end-
ofchapter material for many of the chapters.
Broadway Ent~inment Company. Inc. (BEC) This fictional video rental
and music company is used as an extended case at the end of each chapter,
beginning with Chapter 2. Designed to bring the chapter concepts to life, this case
illustrates how a company initiates, plans, models, designs, and implements a
Webbased customer relationship management system using an object-oriented systems
development approach. Discussion questions are included to promote critical
thinking and class participation. Suggested solutions to the discussion questions are
provided in the instructor's Resource Manual located in the Faculty area of the
Website: htto:/ /www.prenhall.com/george.
End-of-Chapter Material
We have developed an extensive selection of end-of-chapter material designed to
accommodate various learning and teaching styles.
Key PointS Review This repeats the learning objectives that appear at the opening
of the chapter and summarizes the key points related to the objectives.
Key Terms Checkpoint This is designed as a self-test feature. StUdents match each
key term in the chapter with its definition.
Review Questions These questions test students' understanding of key concepts.
Problems and Exercises These problems and exercises test students' analytical
skills and require them to apply key concepts.
Discussion Questions These questions promote class participation and discussion.
Case Problems These problems require stUdents to apply the concepts of the chapter
to three fictional cases from various industries. The illustrative case from the book-
Pine Valley Fundttireds revisit6d. Other cases are from various fields such as
medicine, agriculttire, and technology. Solutions are provided in the instructor's Manual
located in the Faculty area of the Website: hap: / / www.prenhall. corn / george.
Margin Term Definitions Each of the key terms and their definitions appear in the
margins. A glossary of terms appears at the back of the book.

References Located at the end of the text, references organized by chapter list more
I
than 100 books and journals that can provide stUdents and faculty with additional
,oumals that can provide stUdents and faculty with additional
coverage of toDics.
6 pies.
qricVWnRE PACKAGING OPTIONS
OOFTWnRE PACKAGING OPTIONS
T y. .,,',
. Visible Analyst
yst

. Microsoft Visio

. Microsoft Protect
)
. Oracle10g
g
To enhance the hands-on learning Drocess Prentice Hall offers the option to
a process, Prentice Hall offers the option to
,
package this text with a choice of Visible Analyst, Microsoft Visio, Microsoft Project,
or Oracle10g software. Your Prentice Hall sales representative can Drovide additional
o .oftware. Your Prentice Hall sales representative can provide additional
.
information on pricing and ordering.
pricing and ordering.
I NSTRUCTOR'S RESOURCE CENTER
The instructor's Resource Center found on the catalog page is a password protected
Faculty site that contains instructor subtlements for download.
y bite that contains instructor supplements for download.
1' Powerpoint presentation slides feature lecture notes that highlirkt keg text terms
presentation slidesfeature lecture notes that highlight key text terms
and concocts.
pts.
, m' x'
2' The instrUctor's Resource Manual is secured in the password-protected Faculty area.
password-protected Faculty area.
It contains teaching suggestions and answers to all text review questions, problems,
s suggestions and answers to all text review questions, problems,
.' 1'
exercises, and case problems.
problems.
~ al m' T.'
Z TIp Test It6m File also is secured in the Facultl' aams i+ ic f
D' The Test It6m File also is secured in the Faculty area. It is available in MicrosoH Word,
H area. It is available in MicrosoP Word,
converted WebCT, and BlackBoard files.
J
4' An Image Library is provided in the Faculty area. ThiS is a collection of amures and
ge Library is provided in the Faculty area. ThiS is a collection offigures and
tables horn the text to enhance class lectures and Powerpoint slides.
j rom the text to enhance class lectures and Powerpoint slides.
AC KN OWLE DG M E NTS
The authors have been blessed by considerable assistance from many poODle on all
y considerable assistance from many people on all
. r
~ +Q aam *; C.k' I 1 1 'I 1' T4'
aspects of preparation of this text and its supplements. We are, of course, responsible
poets of preparation of this text and its supplements. We are, of course, responsible
for what eventually appears between the covers, but the insights, corrections,
contriy appears between the covers, but the insights, corrections,
contributions, and proddings of others have greatly improved our manuscript. The people
.
., 11 1
we recognize here all have a strong commitment to stridents to the iS field and to
anlze here all have a strong commitment to stridents, to the iS field, and to
, 1 al.
excellence. Their contributions have stimulated us and frequently rejuvenated us
i j rejuvenated us
during Deriods of waning enerZv for this protect.
g periods of waning energy for this project.
We would like to recognize the efforts of the many facultV and practicing
svsgnlze the efforts of the many faculty and practicing
systems analysts who served as reviewers for this book. We have tried to deal with each
j his who served as reviewers for this book. We have tried to deal with each
.
reviewer comment, and although we did not always agree with specific points
(within the approach we wanted to take with this book), all reviewers made us stop
,' 1., r, 1,
and think carefully about what and how we were writing The reviewers were:
j a. Ihe reviewers were:
orchard Alien, mchland Community College
y 5
Alien Corbett, University of South Carolina-Columbia
J
Terry Fox, Baylor UniversitV
j box, Baylor University
Marilvn Griffin, Virginia Polytechnic instittite
yn Griffin, Virginia Polytechnic instittite
Russ Hanna, Johnson County Community College
y y College
David James Howe, Augusta Technical College
Preface xv

Robert Josefek, University of Southern California, Marshall School of
j, idarshall School of
Business
Leonardo Legorreta, California State University-Sacramento
gorreta, California State University-Sacramento
Mary Beth Zak Lohse, Ohio State Umversity
y Beth Zak Lohse, Ohio State University
Trevor Moores, University of Nevada, Las Vegas
J, Las Vegas
Alan Graham Peace, West Virgima State University
Vladimir V. mabov, ivier College
Torn Sakaguchi Northern Kentucky UniversitV
8, 1 j y
Carl Scott, University of Houston
y of Houston
Eileen Sellers, MaryVille University
J y
Deborah Smith, University of Nevada-Las Vegas
J bas
Ron Sones, James Madison University
j
Tei Wei Wang FlU-UniversitV Part CamDus
g, FlU-University Part Campus
Heinz Weistroffer, VirgAna Commonwealth University
Connie Wells, Roosevelt University
y
Elaine Weltz, Seattle Pacific University
y
Robert Wrembel, Poznan University of Technology
y of Technology
H. R. Weistroffef, Virginia Commonwealth University
We have been formulate to work with a large number of creative and insightful
5 .fitful
,
people at Prentice Hall, who have added much to the development, format, and
production of this text. We have been thoroughly imDressed with their commitment to
.ifly impressed with their commitment to
.
this text and to the iS education market. These people include Robert Horan,
Executive Editor; Debbie Clare, Marketing Manager; Ana Jankowski, Assistant
editor; Denise Culhane, Production editor; [designer]; and Laura Cirigliano, Marketing
Assistant. We also want to thank Ann Imhof and the folks at Carlisle
Communications, Ltd., for their hard work in getting this book ready for production.
Thanks also go to our faculty colleagues Fred McFadden (University of
Colorados i gUes Fred McFadden (University of
ColoradoColorado Springs), Mary Prescott (University of Tampa), and Dean Joyce Elam
.
(Florida international University).
We extend a special note of thanks to Jeremy Alexander of Web-X.com. Jeremy
.
.'
was instrumental in conceptualizing and writing the Pine Valley WebStore feature
ptUalizing and writing the Pine Valley WebStore feature

that appears throughout the book. Jeremy also built the installation procedures on
'
.
the Website for Oracle, and Saonee Sarker of Washington State University developed
.
the Oracle editorial modules.
The writing of this text has involved thousands of hours of time from the authors
5
1 r 11 r.
~ac 1 f-ac 11' ac
and from all of the aforementioned people. Although our names will be visibly
asso.
..,.. 1
claied with this book, we know that much of the credit goes to the individuals and
...,.', 1 f
organizations listed here for any success this book might achieve. It is imDortant for
ganlzations listed here for any success this book might achieve. It is important for
.
the reader to recognize all the individuals and organizations that have been
commitsnlze all the individuals and organizations that have been
commitI
ted to the preparation and production of this book.
'
ABOUT THE AUTHORS
Joey E George is professor and Thomas L. Williams JL Eminent Scholar in formation
Sxrst6ms in the College of Business at Florida State Universitir aam George earned his
ayst6ms in the CoheRe of Business at Florida State Universing Da GeorZe earned ins
yst6ms in the College of Business at Florida State University. Da George earned his
bachelor's degree at Stanford Universing in 1979 and his Ph.D. in manaZement at the
free at Stanford University in 1979 and his Ph.D. in management at the
Universing of Califonda at twine in 1986. He was Dreviouslv the Edward G. Schlieder
j previously the Edward G. Schlieder
Chair of information Svst6ms in the E. I. Ourso College of Business A~stration at
j items in the E. J. Ourso College of Business A~stration at
Louisiana State Universing He also served at Florida State University as chair of the
y. He also served at Florida State University as chair of the
Depa~nt of information and Management Sciences from 1995 to 1998.
l bement Sciences from 1995 to 1998.
Dr. George has published many articles in such iournals as information Systems
a published many articles in such journals as information Systems
Research, Communications of the ACe, us Quarterly, journal of MIS, and Communication
v the ACe us Quarterly, journal of MIS, and Communication
Research. His research interests focus on the use of thermation systems in the
workybtems in the
work,.,,..
place, including computer-based monitoring, comput6nmediat6d deceptive
communication, and group support systems.
. yi
xvi Preface

Da George, along with loseph Valacich and leffrev Hcffer is coauthor of the
texts, along with Joseph Valacich and Jeffrey Hcffer, is coauthor of the
textbooks Modern Systems Analysis and Design, fifth edition, published in 2007 by Prentice
totems Analysis and Design, fifth edition, published in 2007 by Prentice
Hall, and Essentials of Systems Analysis and Design, third edition, copyright 2006 by
.
Prentice Hall. He is also the editor of Commuters and Society: Privacy, Ethics, and the
puters and Society: Privacy, Ethics, and the
Internet, copyright 2004 by Prentice Hall. Da George is currently the Editor-in-Chief
for the journal Communications of the AlS' In the past, he has served as a senior editor
,ournal Communications of the AlS' In the past, he has served as a senior editor
,..,..
~yi 1 -. L h+rs- 'ri. +k. 1
and an associate editor for the ioumal MIS Quarterly and an associate editor for the
)oumal MIS Quarterly and an associate editor for the
. 1 T r
journal information Systems Research. He has also served on various other journal
editorial boards. Da George was the conference co-chair for the 2001 ICIS, held in New
a, ileld in New
Orleans, Louisiana, and he was the co-chair of the doctoral consortium for the 2003
ICIS, held in Seattle, Washington.
Dinesh Batra is professor at the Department of Decision Sciences and
Information Systems in the College of Business Administration at the Florida
j >terns in the College of Business Administration at the Florida
International UniversitV. He earned his B.Tech. from the indian institute of
y. He earned his B.Tech. from the indian institute of
Technology at Delhi in 1979, M.B.A. from Southern illinois UniversitV at Carbondale
gy at Delhi in 1979, M.B.A. from Southern illinois University at Carbondale
.'
in 1985, and Ph.D. from indiana University at Bloomington in 1989. After his
bachey at Bloomington in 1989. After his
bachelor's degree and during the Deriod 1979--1983, he worked for four years in a
consultblee and during the period 1979--1983, he worked for four years in a
consult.,..,,.
lug comDanv conducting Drocess and design of large engineering Drojects.
a pany conducting process and design of large engineering projects.
Da Batra has published over 25 articles in such journals as management Science,
Communication of the ACe, lournal of MIS, International lournal of Human Computer
7 the ACe, journal of MIS, International lournal of Human Computer
cflldipc Data Base FI'rovean [ournal of 11
studies, Data Base, European lournal of information SVstems, Iournal of Database
pean lournal of information Systems, Iournal of Database
bynamement Communications of the AlS, Decision Support Systems, Commuters and OR
o, U the AlS, Decision Support Systems, Computers and OR,
, T
~yi J IMInw~.';ri,
and information & Minaerment. His research interests focus on usability issues in
sysY scment. His research interests focus on usability issues in
sys.
terns and database analysis and design. He has served as an associate editor in the
ybis and design. He has served as an associate editor in the
. 1 ac.
journal Data Base, and is on the editorial board of the lournal of Database management
' T r'.
~yi 1 IMlriw~rs+;ri
and information Systems bynamement. He has also served as the director of the MS in
formation Systems management. He has also served as the director of the MS in
MIS program at the Florida international University. He is currently the president of
.
the AlS Special interest Group on Systems Analysis & Design (SIGSAND).
Joseph S. Valacich, The George and Carolyn Hubman Distinguished Professor
. - ATal. 1.,' r. v m.
in MIS and the inaugural Marian E. Smith Presidential Endowed Chair, joined the
.ural Marian E. Smith Presidential Endowed Chair, joined the
facultV at Washington State UniversitV in 1996. He was Dreviouslv an associate
brow aEon State University in 1996. He was previously an associate
professor with tenure (early) at indiana University, Bloomington, and was named the
caniner qubhedar Facultlr Fellow. He has had visiting fqcultxr aDDointments at the
aanlay Subhedar Faculty Fellow. He has had visiting faculty appointments at the
)ay Subhedar Faculty Fellow. He has had visiting faculty appointments at the
University of Arizona, City University of Hong Kong Buskerud College (Norway),
y of Arizona, City University of Hong Kong, Buskerud College (Norway),
Riga Technical University (Latvia), and the Helsinki School of Economics and
ga Yechnical University (Latvia), and the Helsinki School of Economics and
Business. He received the Ph.D. degree from the UniversitV of Arizona (MIS), and the
flee from the University of Arizona (MIS), and the
M.B.A. and B.S. (computer science) degrees from the University of Montana. His
'
teaching interests include systems analysis and design collaborative commuting
a Interests include systems analysis and design, collaborative computing,
..' 1' r.
project management, and management of information systems. Professor Valacich
,. 1..,. 1 r
served on the national task forces to design iS '97 and 2002: The Model Curriculum and
>erved on the national task forces to design iS '97 and 2002: The Model Curriculum and
gn iS '97 and 2002: The Model Curriculum and
Guidelines for Undergmduate Degree Progmms in information Systems, as well as MSIS
jor Undergmduate Degree Progmms in information Systems, as well as MSIS
, o
2000 and 2006: The Mister of Science in information Systems Model Curriculum. He also
7 oclence in information Systems Model Curriculum. He also
1. 1 w
served on the Executive Committee funded bar the National Science Foundation to
>erved on the Executive Committee, funded by the National Science Foundation, to
J
define the iS Progmm Accreditation Standards and on the Board of Directors for CSAB
gcm Accreditation Standards and on the Board of Directors for CSAB
(formally, the Computing Sciences Accreditation Board), representing the
Association for information Systems (AlS). He was the general conference co-chair
, items (AlS). He was the general conference co-chair
for the 2003 International Conference on information Systems (ICIS) in Seattle and
J
'
. 1.,.
was the vice-chair of ICIS 1999 in Charlotte, NC.
Jeffrey A. Hcffer is the Sherman-Standard Register Professor of Data
Management in the DeDartment of MIS, Operations Management, and Decision
gement in the Department of MIS, Operations Management, and Decision
sciences in the School of Business Administration at the Universitxr of Dalrton. He
sciences in the School of Business Administration at the University of Dayton. He
j yton. He
,' 1.. T 1. T T..
~1 q '~,, orb' ~ + Tri 1 i
also taught at Indiana UniversitV and Case Western Reserve University. Da Hcffer
ght at Indiana University and Case Western Reserve University. Da Hcffer
1 1.
earned his A.B. from Miami University in 1969 and his Ph.D. from Corned University
j in 1969 and his Ph.D. from Corned University
.' Q-c
In 1975.
Da Hcffer has published four other college textbooks: Modern Systems Analysis
and Design, fifth edition, with Joey George and Joseph Valacich; Essentials of Systems
gn, fifth edition, with Joey George and Joseph Valacich; Essentials of Systems
Analysis and Design, third edition, with loseph Valacich and Joey George; Modern
.ofs and Design, third edition, with loseph Valacich and Joey George; Modern
Preface xvii

Database Design, eighth edition, with Mary Prescott and Fred McFadden; and
an, eighth edition, with Mary Prescott and Fred McFadden; and
Information Technoloryfor managers: What managers Need to Know, fourth edition, with
,ormation Technologyfor managers: What managers Need to Know, fourth edition, with
Carol Brown, Daniel DeHayes, E. Wainright Martin, and William Perkins, all
pubJ, t. Wainright Martin, and William Perkins, all
published by Prentice Hall. His research articles have appeared in numerous ioumals,
y Prentice Hall. His research articles have appeared in numerous journals,
. 1,. 1
including MIS Quarterly Executive, Iournal of Database Management, Small Group
g MIS Quarterly Executive, Iournal of Database Management, Small Group
Research, Communications of the ACe, and Sloan management Review. He has received
J, and Sloan management Review. He has received
, 1.
research and equipment grants from IBM Corporation, U'S. Department of the Navy,

, NCR Teradata division.
~. I NCR Teradata division.
and NCR Teradata division.
Da Hcffer is cofounder of the international Conference on information Systems
y items
,. 1 N...
~. 1 +h & rtcri. +i '. Tab t J
and the Association for information Systems. He has served as a guest lecturer at
ystems. He has served as a guest lecturer at
Catholic UniversitV of Chile Santiago, and the Helsinki School of Economics and
y of Chile, Santiago, and the Helsinki School of Economics and
Business in Mikkeli, Finland. Dr. Hcffer is currently an associate director of the
j
Teradata UniversitV Network.
y Network.
Joey E George,
Florida State UniversitV
j
Dinesh Batra,
Florida international UniversitV
y
Joseph S. Valacich,
Washington State UniversitV
aEon State University
Jeffrey A. Hcffer,
University of Dayton
y of Dayton
R E FE R E N CE
Land M. 2006. "An EmDirical Study of Processes, Methods, and Techniques for Web/HyDermedia
s, lA. 2006. "An Empirical Study of Processes, Methods, and Techniques for Web/Hypermedia
qlrQfems Design. Information Systems management.
systems Design. Information Systems management.
. an. Information Systems management.
... n,
xvill Preface