基本信息作者:(美国)(George)乔治
出版社：清华大学出版社
页码：458 页
出版日期：2009年
ISBN：9787302197997
装帧：平装
开本：16
丛书名：大学计算机教育国外著名教材系列
外文书名：Object-Oriented Systems Analysis And Design Second Edition
定价：46.00
内容简介《面向对象系统分析与设计》是本科和研究生“系统分析与设计”课程的教材。
本书为读者展示了系统分析师所需掌握的概念、技能和技术等知识。本书的焦点是面向对象的系统分析与设计，并且遵循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
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
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
……