Sommerville-Software-Engineering-10ed

Subject Index 785
software, 18, 22, 26, 287, 308, 310,
340–41, 351–52
system failure costs, 286
fault (system faults), 307–09
avoidance, 308
costs of removal, 308–09
detection and correction, 308
error and failure v., 308
repair, 271
tolerance, 308
fault-tolerant architectures, 318–25, 491
distributed systems, 491
diversity of software, 323–25
N-version programming, 322–23
protection systems, 319–20
self-monitoring, 320–22
fault tree analysis, 349–51
feasibility studies, 54, 104
Federal Aviation Administration, 92, 290
federated systems, 589
film library, client-server architecture for, 182
firewalls, 413–14
flight control software, 296, 321–22, 340, 341
floating-point numbers, 329
formal (mathematical) models, 139
formal methods (software development), 49, 139,
299–302, 303, 356–58
B method, 49
dependability and, 299–302, 303
error avoidance and discovery from, 300–01
mathematical approach, 300, 301
model-checking, 300, 358–59
safety engineering, 356–59
security testing, 404
system models and, 139, 299–301
verification and, 300, 356–58
formal specifications, 109, 300–02
Fortify tool, 404
4 Rs model, 410–11, 414–15, 432
4+1 view model, 173–74
frameworks, 443–46, 600–02, 708–10
Free Software Foundation, 219
frequency (real-time systems), 627
fuel delivery system, 618–19
functional requirements, 105–07, 134, 312, 317–18,
335, 344
functional specialization (software product lines),
450
functionality, 286
G
‘Gang of Four,’ 209–12
General Public License (GPL), 220
generalization of structural models, 152–53, 205
generator-based reuse, 443
Git system, 216, 737, 740
GitHub, 476, 478
‘glue code,’ 466, 481, 487
GNU build system, 216
GNU General Public License (GPL), 220
Google Apps, 27
Google Code, 478
governance complexity, SoS, 586–87,
588–90, 606
graphical models, 140
graphical notations, 121
groups, see teamwork
growth modeling, 334
guideline-based testing, 234
guidelines
hiring, 661
dependable programming, 325–31
system security, 401–02, 405
H
handlers, exceptions, 327–28
hardware (system), 262
hardware failure, 287, 560–61
hazard-driven approaches, 342, 349–51, 368
hazards, 342, 343, 345–51
analysis of, 345, 349–51
assessment, 345, 346–49
avoidance, 342, 351
damage limitation, 342, 351
detection and removal, 342, 351
fault tree analysis, 349–51
identification of, 345–46
probability, 343
safety-critical system development, 342, 368
severity, 343
heterogeneity, software development and, 24
hierarchical composition, 480
hierarchical groups, 661–62