Sommerville-Software-Engineering-10ed

780 Subject Index
change anticipation, 61
change control board (CCB), 748–49
change management, 97, 731, 745–50, 753
agile methods and, 97, 748, 750
change requests, 747–50
dependability and, 299
development environments and, 217
requirements and, 111, 130–34
change proposals, 90, 258–59
change request form (CRF), 747–48
change tolerance, 61
characteristic error checking, 359–60
check array bounds, 330
checking requirements, 317
checklists, 403, 713–714
checksums, 745
circular buffer, 616–17
class diagrams, 141, 149–51, 163
class identification, 202–04
Cleanroom process, 230, 332
client-server architecture, 180–82, 428, 501,
503–06, 517
client-server systems, 499–501, 517
clouds, 25, 27, 532
COBOL code, 263
COCOMO II modeling, 276, 476, 686–96
application composition model, 688–89
cost drivers, 692
early design model, 689–90
post-architectural level, 692–94
project duration and staffing, 694–96
reuse model, 690–92
code coverage, 243–44, 252
code inspection and review, 83, 715
Code of Ethics and Professional Practice (software
engineering), 29–30
codelines, 734, 735, 736, 739
collaborative systems, 588
collective ownership, 78
COM platform, 466
Common Intermediate Language (CIL),
470–71
communication
data management layer and, 292
message exchange, 496–97, 526–29, 537
stakeholder, 169
communication latency, 218
compartmentalization, 399
competence, 28
completeness, 107, 129
complexity, 18, 93–96, 274–75, 278, 584–87, 606
governance, 586–87, 588–90, 606
large systems, 93–96
maintenance prediction and, 274–75
management, 585, 586–87, 587–90, 606
reductionism for systems, 590–93, 606
refactoring, 278
scaling agile methods and, 93–96
system releases, 751–52
systems of systems (SoS), 584–87, 606
technical, 585, 586–87, 590
compliance to software regulation, 294–95
component-based software engineering (CBSE), 442,
464–489
component certification, 474, 477
component management, 474, 476
development for reuse, 473, 474–77
development with reuse, 473, 477–80
middleware and, 465, 472–73
service-oriented software v., 466–67
component level (reuse), 214
components (software), 52–53, 188, 190, 295, 424,
465–73, 487, 526–29
architectural design and, 172
communications, 172, 218, 526–29
composition, 480–86, 487
defined, 465, 467, 487
deployment, 471, 472–73
design and selection of, 57, 424, 452
external, 330–31
implementation, 465, 466, 471–72, 475, 487
incompatibility, 481–83
interfaces, 208–209, 237–239, 465, 468–69
measurement (analysis), 722–23
models, 470–73, 487
open-source, 220–21
platforms for, 466–67
remote procedure calls (RPCs)
for, 470, 471
reuse, 52–53, 212, 214, 221, 438–439,
452, 468, 487
services v., 521
service-oriented architectures (SOA), 526–29
testing, 59, 232, 237–239
timeouts, 330–31
timing errors, 238–239
components (system), procurement (acquisition) of,
567–68