Sommerville-Software-Engineering-10ed

Subject Index 779
availability
security and, 374, 375, 413
system availability, 172, 288, 309–12
availability metric (AVAIL), 313–314
avoidance
error discovery and, 300–01
fault, 308
hazard, 342, 351
strategies (risk management), 650
vulnerability, 378
B
B method, 49, 300, 301, 357
banking system, Internet, 505
baselines, 734, 735, 736
batch processing systems, 25
behavioral models, 154–59, 163
beta testing, 58, 60, 249–250
bidding (projects), 669, 671–72
bindings, 527–28
blackboard model, 180
block diagrams, 170, 199
Boehm’s spiral process model, 48
Booch’s software architecture catalog, 170
boundaries (system models), 141–42, 163,
199, 556–57
branching, 734, 739
broadcast (listener) models, 202
Brownfield systems, 94, 256
BSD (Berkeley Standard Distribution)
license, 220
Bugzilla, 216
build system, 741–42
burglar alarm system, 614, 622, 629–31
business-critical system, 287
business process layer, 292
Business Process Modeling Notation (BPMN),
544–46
business process models, 544–46
businesses
activity diagrams (UML) for processes, 143–44
interrelated 4 R’s approach, 426–27
legacy system evolution, 261–68
maintenance costs, 274–76, 279
C
modeling workflow, 67–68
open-source software and, 221
policies (rules), 262
process maturity models, 67–68
process reengineering, 276–78
processes, 262
rapid software development and, 73–74
requirements changes, 131
resilience and, 426–27
security and, 380–382
services, 534, 541–47, 548
social change and, 24
software systems, 24, 27, 45, 68, 267–68
system construction by composition, 543–44
system values, 267–68, 280
web-based applications, 27
workflow, 542, 543, 544–46
C and C ++ programming languages, 197, 327, 330,
359, 360, 401, 444, 619
callbacks, 445
catalog interface design, 537–538
centralized systems, version management of,
735, 737
certification (software dependability), 294, 299, 302,
354, 355–56, 474, 477, 709–10
change, 61–65. See also process change
agile methods and, 73–74, 78, 90–91, 97
business and social needs, 24
cost effectiveness of, 133
cultural (social), 24, 97
customers and, 748–49
effects on software engineering, 27–28
extreme programming (XP) and, 78
implementation, 134, 259–60, 280
incremental delivery, 62, 64–65
plan-driven process and, 73
problem analysis and, 133
prototyping, 62–63
rapid software development for, 73–74
requirements management for, 111, 130–34
reuse, 27–28
rework for, 61, 73