Index
A
ability to learn, 32
abstraction, in software design, 246
acceptance
criteria, 104 , 177 , 181 , 196 , 199 , 481 , 491
product, 104 , 491
testing, 104 , 460 , 481 , 490 –91 , 632
accept responsibility, 179
access control, 209 –10 , 351 –53 , 587
accessibility, 206 , 258 , 390 , 487 –88
accessible, data collection goal, 110
accessor operations, in object-oriented analysis and design (OOAD), 254
accident, 208 , 355 –58
accountability
data, 107 , 354
leadership characteristic, 31
accuracy
data quality, 204 , 390
metric, 369 , 395 , 410 , 412 –13
quality attribute, 206 , 449
ACID properties, information integrity, 204
acquirer, stakeholders, 89 , 96 , 100 , 268 , 456 , 632 . See also customers, stakeholders; users, stakeholders
acquisition criteria, 559 , 562 , 567 , 573 –74 , 587 –89
acquisition point, 311 , 545 –46 , 562 , 572 –73 , 587 – 89
acquisition process (software), steps in, 97 –105
accept product, 104 , 460 , 481 –82 , 490 –91 , 505 , 632
CMMI for, 23 –24
contract requirements, define, 101
determine approach, 99
identify and evaluate potential suppliers, 99 –100
initiate and plan, 97 –8
negotiate and award contract, 101 –3
preferred supplier relationships, 105
product requirements, define, 98 –9
project management, 103 –4
software use, 104
supplier management, 103
supplier selection, 101
verification and validation (V&V) plan, 457
action item, 326 –27 , 330
activities, 275 , 277 , 281 –83 , 285 –303 , 307 –8 , 312 –13 , 314 , 334
activity diagrams, 226 –27
activity networks
diagramming, 294 –96 , 441
line network, 294
node network, 294 –95
relationships, 295
actor, 216 –19
actual cost of work performed (ACWP), 316 –19 . See actual value (AV)
actual, 103 , 290 , 307 –9 , 312 , 314 –15 , 320 –22 , 541
actual value (AV), 316 –19
adaptive maintenance, 266 –67
adjourning stage, team development, 63
advocates, for change, 33
aesthetics, 258 , 488
affinity diagrams, 437 –39
agile
leadership skills, 57
manifesto, 172 –73
methods, 6 , 88 , 135 , 139 , 153 , 172 –82 , 266 , 320 , 460 , 465 , 514 , 547 , 583 , 593 , 616
extreme programming, 178 –82
Scrum, 174 –77
metrics, 408 –9
principles, 172 –73
requirements, 3 –4 , 196 , 199 , 215
Agile Alliance, 172
agile coach, 40 , 43 , 175 , 326 . See also Scrum master
Agile Manifesto, 172 –73
agile projects, 86 , 93 , 278 , 291 , 325 –28 , 392 , 546 , 623
aging, 401
algorithm, 461
allocated baselines, 582
alpha testing, 453 , 457 , 491 , 632
alternative scenarios, use cases, 217 , 219
ambiguous, 231
analysis, 449 –50 , 452 –54
analysis and design, 243 . See architectural design; component design; software analysis and design
anomaly report, 539 . See problem report
application layer, TCP/IP, 188
appraisal cost of quality, 114
architectural design, 183 –90 , 243 –52 , 255 –61
architectural design review, 323 –24
architectural structure, 250
architecture
process architecture, 84 –5
product architecture, 569
software architectural design, 239 , 243 –52 , 255 –61
system architectural design 183 –90
views, design, 250 –52
Kruchten’s 4+1 view model, 251
purposes of, 250
archival of build environment, 636
archival processes
archival of build environment, 636
archives, 635 –36
asset retrieval, 636 – 37
backups, 633 –34
data management, 112
offsite storage, 634 –35
archive library, 558 , 635 See static library
archives, 635 –36
area charts/graphs, 42 –3
arrival rates, 388 –89
ASQ Code of Ethics, 9 –10
for conflicts of interest, 10 –11
fundamental principles, 10
relations with employers and clients, 10
relations with peers, 10
relations with public, 10
assemblers, 555
asset retrieval, 636 –37
assignable cause variation, 375 , 435 . See special cause variation
assumption, 98 , 196 , 290 , 337 , 341 , 367 –68
assumption analysis, for risk identification 337
attack, on software security, 208 –10 , 256 –57 , 351 –54
attacker, 256 –57 , 351 –54
attributes, of entities 367 , 369 –71 , 382 , 397
audit corrective action and verification follow-up process, 137 , 142 , 146 –47 , 156 –57
audit criteria, 139 –41 , 143 –44 , 149 –50
auditee management, 145
auditees, 145
audit execution process, 146 –47 , 151 –54
closing meeting, 154
daily audit team meeting, 154
daily feedback meeting, 154
evidence collection, 152 –54 , 617 –18 , 619 –20
opening meeting, 151 –52
audit findings
best practices, 156
major nonconformance, 155
minor nonconformance, 155
observation, 155
process improvement opportunities, 156
audit implementation, 146 . See audit execution process
audit initiation process, 146 –49
audit objectives, 137 –38
auditor, lead, 131 , 143 –52 , 154 , 156 –57
auditor management, 143
auditors, 144 –45
audit performance, 146 . See audit execution process
audit planning process, 146 –47 , 149 –50
audit plan, 150
audit preparation process, 146 –47 , 150 –51
audit program, 138
audit purpose, 143 , 148
audit reporting process, 146 –47 , 155 –56
audit report, 155 –56
audits, 137 –56 , 545 , 615 –20
checklists, 150 –51 , 617 –18 , 619 –20
configuration audits, 545 , 615 –20
considerations, 138 –39
criteria, 139 –41 , 143 –44 , 149 –50
definition, 137
desk audit, 142
external second-party audits, 140 –41 , 148
external third-party audits, 141 , 148
finding
best practices, 156
major nonconformance, 155
minor nonconformance, 155
observation, 155
process improvement opportunities, 156
follow-up audit, 142
functional configuration audit (FCA), 104 , 450 , 452 –54 , 615 –18 , 627
inputs, 148 –49
internal first-party audits, 139 –40 , 148
objectives, 137 –38
physical configuration audit (PCA), 104 , 450 , 453 –54 , 615 , 618 –20 , 627
plan, 150
process, 147 –57
corrective action and verification follow-up, 137 , 142 , 146 –47 , 156 –57
execution, 146 –47 , 151 –54
closing meeting, 154
daily audit team meeting, 154
daily feedback meeting, 154
evidence collection, 152 –54 , 617 –18 , 619 –20
opening meeting, 151 –52
initiation, 146 –49
planning, 146 –47 , 149 –50
process audit, 141 –42
preparation, 146 –47 , 150 –51
reporting, 146 –47 , 155 –56
steps in, 146 –47
process audit, 141 –42
product audit, 142 , 450
program, 138
project audit, 142
purpose, 143 , 148
report, 155 –56
roles and responsibilities
auditee, 145
auditee management, 145
auditor management, 143
auditors, 144 –45
client, 143
escort, 145
lead auditor, 144
scope, 148
supplier audit, 141 –42
system, 141
audit scope, 148
audit team lead, 144 . See lead auditor
audit trail, 107 , 203 , 210 , 256 –57 , 390
authentication, 209 , 256 , 352
author, 512 –32 , 535 , 538 –39 , 558 –62 , 572 –74 , 590 –92
automated test framework, 503 . See test harness
automation, 213 , 240 , 412 , 523 , 576
of software builds, 579 –80
test, 467 –68
availability
data, 106 , 110 –11 , 353 , 390 , 414
quality attribute, 205 , 209 , 255 , 257 , 268 , 339 , 394 –95
in software design, 257
staff and resources, 288 , 326 , 340 , 601
average (X-bar) and ranges (R) charts, 436 –37
average (X-bar) and standard deviation (S) charts, 436
B
back door, 107 , 209 , 352
backlog
iteration/sprint, 86 , 175 –77 , 229
problem report backlog, metric, 389 –90
product backlog, 174 –77 , 229 , 237 –38 , 266 , 325 , 328 , 583 , 593
backlog refinement meeting, 57 , 176 –77 , 215 , 229
backup library, 558 , 634
backups, 107 , 204 , 558 , 633 –34
backward-compatible software, 625
backward traceability, 239 –40 , 602 –3 . See also forward traceability; traceability/ traceable
balanced scorecards, 425 . See dashboards
bar charts/graphs, 420 –22
baseline configuration items, 574 , 611
baselined requirements, software, 193 , 235 –37 , 393
baseline metadata, 611
baselines, 581 –83
base measures, 371 . See explicit measures
basic quality, in Kano model, 7
bell curve, 378 . See normal distribution
benchmarking, 119
competitive, 120
functional, 120
generic, 120
internal, 120
preventive action and, 136
requirements elicitation, 214
steps in, 119 –21
beta testing, 450 , 488 , 632 . See also pilots
bidirectional traceability, 238 –42 . See also traceability/traceable
black-box testing, 391 , 461 , 464 –65 , 489 , 491 , 493
Body of Knowledge (BOK)
Software Quality Engineer Certification, xxii , (Appendix A), 639 –47
Project Management Body of Knowledge Guide (PMBOK Guide), 90
bottom-up testing strategy, 463 –64
boundary value testing, 473 , 486 , 501
box-and-whisker diagrams, 423 . See box charts/plots
box charts/plots, 423
brainstorming, 66 –67 , 336
for risk identification, 336
branch coverage, 499 . See decision coverage
branching, library processes, 562 –64
branching identification scheme, 576
budgeted cost of work performed (BCWP), 316 –19 . See earned value (EV)
budgeted cost of work scheduled (BCWS), 316 –19 . See planned value (PV)
budgets
for phase transition control, 313 –14
project, 298 –99
bug report, 539 . See problem report
builders, SCM, 552 , 559 –60
build
automation, 579 –80
building, 551 –52 , 559 –60
builds, 579
continuous integration, 547 , 580
from controlled library, 558 , 559 –60
identification, 575 –78
labeling 562 –63 , 575 –76
metadata, 611
reproducibility, 580 –81
scripts, 555
testing, 560 –62
tools, 553 –55
verification and validation (V&V), 453 –54
build quality in, lean principles to software, 125 –26
burn charts, 320 –21 , 409
burn-down charts, 320 –21
burn-up charts, 320 –21
business continuity
defined, 105
management practices of, 106
technical practices of, 106
business requirements/needs, 98 , 194 , 243 , 282
business requirements document (BRD), 229
business rules, 194 , 207
business-to-business (B to B) architecture, 189
business-to-consumer (B to C) architectures, 188
business-to-employee (B to E) architecture, 189
C
c charts, 437
calendar time, 278 , 288 –89 , 296 –98 , 374
capability maturity model integration (CMMI), 23 –29
for acquisition (CMMI-ACQ), 23 –24
continuous representation, 28 , 408
definition components, 25
expected, 25
informational, 25 –26
required, 25
for development (CMMI–DEV), 23 – 24
process areas, 24
for service (CMMI-SVC), 23 –24
staged representation levels, 24 , 27 –29
capacity, quality attributes, 198 , 396 , 485
capital costs, in project planning, 298
capture-and-playback tool, 506
cardinality, 222 –24
cause-and-effect diagrams, 41 , 429 –30
cause-effect graphing (CEG), 476 –79
causes, of failure, 360
CCB charter, 598 –99
CCB leader (chair), 597
CCB members, 597
CCB recorder, 598
CCB screener, 598
certification testing, 481 –82
Certified Software Quality Engineer (CSQE), Body of Knowledge (BOK), xxii , (Appendix A) 639 –47
champion, 61
chance cause variation, 375 . See common cause variation
change advisory boards (CABs), 596 . See configuration control boards (CCBs)
change agents
informal, 33
official, 32
change and dependencies, 569 –70
change authority, 587
change control, 587 . See change request through CCB change control
acquisition, 590
baseline changed configuration item, 593
CCB disposition, 592
create work product, 590
incorporate change, 592
internal use, 590
release, 593
review and approve, 592 –93
use in operation, 593
change control boards (CCBs), 596 . See configuration control boards (CCBs)
change control type, 587
change management. See change control
change models, 34
change request (CR), 599 , 612 –14 . See also problem report
change request through CCB change control, 587 , 590 –93 , 599 –600
change request originator, 597
charter
CCB charter, 598 –99
project charter, 98 , 123 , 175 , 276 , 281 –82
charts, 420 –24
check-in, 559 , 606 , 634
checklists,
advantages, 135 , 151
audit, 150 –51 , 617 –20
communications, 304 –6
of common errors, in past software
products, 474 –75 , 507 , 519 , 522
peer review, 519 , 522 –23
standardized, 86 , 151
tailored, 88 , 151
testing, 495 , 507
check-out, 606
check sheets, 431
checksums, 209 , 256 , 630
circle charts, 420 . See pie charts
class, in object-oriented analysis and design (OOAD), 203 , 253
class diagrams, 226
clear and unambiguous, 231
clear-box testing, 461 . See white-box testing
client, of audit, 143
client–server architectures, 186 –87
closed-ended question, 56
closing meeting, audit, 154
coaching, 39 –41
agile, 40 – 41
GROW framework for, 40
Scrum methodology for, 40
cockpits, 425 . See dashboards
COCOMO/COCOMO II models, 293 . See constructive cost models (COCOMO/COCOMO II)
code. See source code
code coverage techniques, 498
condition coverage, 499 –501
decision coverage, 499 –501
modified condition/decision coverage (MC/DC), 501
multiple condition coverage, 501
statement coverage, 498 –99
code deliverable status metrics, 320
codelines, 558 , 561 –65
code of ethics, ASQ, 9 –10
coding standard, 18 , 142 , 182 , 260 , 512
cohesion, 248 –49
collaboration platforms, 190
co-location, of team, 180
command center, 425 . See dashboards
commercial off-the-shelf (COTS) software, 14 , 97 , 99 –101 , 490 –91 , 570
common cause variation, 375 , 379 , 435
communication plans, 288
communications, 178
communication skills, 49 –57
effective listening, 54 –55
impacts of on quality, 53 –54
interviews, 55 –56
leadership and agile, 57
multicultural environments, working in, 57
one-way, 50 –51
oral, 51 –52
for risk identification, 338
two-way, 50 –51
written, 52 –53
compact disk (CD) keys, 629 . See licensing keys
competitive benchmarking, 120
compilers, 555
completeness, 390 , 449 , 454
data, 413
of test coverage, 391
requirements, 230
completion criteria. See exit criteria
complexity, 244 –45 , 385 –87
complexity analyzers, 505
complex metrics, 372 . See derived measures
compliance/compliant
audits and, 137 , 149 , 155
data quality, 109 , 390
licensing agreements, 14
quality assurance, 305
requirements, 231
business rules, 194 , 207
regulatory requirements, 11 –12 , 15 , 109 , 207 , 619 , 637
safety requirements, 208
software, 15 , 481 , 512 , 544
component design, 183 , 252 –53
component design review, 324
component testing, 480 . See unit testing
composite items, 569
composite configuration item, 572
comprehensibility, 258 , 487
computer resources forecasting, 290
computer software configuration components (CSCCs), 572 . See constituent configuration items
computer software configuration items (CSCIs), 568 , 572 . See composite configuration item; configuration item (CI)
computer software configuration units (CSCUs), 572 . See constituent configuration items
concise, 231
concurrent development, 313 , 561 , 606 –10
condition and decision coverage, 501
condition coverage, 498 – 501
confidentiality, 106 , 209 , 256 , 353 , 390 , 508
configuration audits, 545 , 615 –20
functional configuration audit (FCA), 104 , 450 , 452 –54 , 615 –18 , 627
physical configuration audit (PCA), 104 , 450 , 453 –54 , 615 , 618 –20 , 627
configuration components, 572 . See constituent configuration items
configuration control, 544 –45 , 585 –86
change management tools, 555 –556
definition, 544
concurrent development, 606 –10
configuration control boards (CCBs), 596 –97
change control, 599 –600
charter, 598 –99
impact analysis, 600 –3 , 609 –10
member roles and responsibilities, 597 –98
multiple levels, 603 –6
configuration item attributes, 587
configuration item dependencies, 595 –96
item change and version control, 585
item change control process, 587 –93
tracking item changes, 594
version control, 595
configuration control boards (CCBs), 596 –97
change control, 599 –600
charter, 598 –99
impact analysis, 600 –3 , 609 –10
member roles and responsibilities, 597 –98
multiple levels, 603 –6
configuration identification, 567
items
acquisition criteria, 311 , 545 –46 , 562 , 572 –73 , 587 –89
acquisition point, 311 , 545 –46 , 562 , 572 –73 , 587 –89
baseline, 574
functional and physical characteristics, 572
identification methods, 574 –78
identifying configuration items, 570 – 72
work product control, 568
work product partitioning, 568 –70
software builds and baselines, 578
automation, 579 –80
builds, 579
continuous integration, 580
control points, 581 –83
reproducibility, 580 –81
configuration infrastructure, 549 –65
configuration item (CI), 568
acquisition criteria, 559 , 562 , 567 , 573 –74 , 587 –89
acquisition point, 311 , 545 –46 , 562 , 572 –73 , 587 –89
attributes, 587 –89
baseline, 574
categories, 587
dependencies, 595 –96 , 612
interrelationship, 612
functional and physical characteristics, 572
identification methods, 574 –78
identifying configuration items, 570 –72
metadata, 611
work product control, 568
work product partitioning, 568 –70
configuration management 544 –47
activities, 544
deviations and waivers data, 612
management of, 545 –46
plan, 86 , 311 , 546
planning, 545 –46
risk indicators, 571
configuration management library processes, 557
backup library, 558
branching, 562 –64
controlled library, 558
controlled work product, 560 –62
dynamic library, 557 –58
merging, 564 – 65
new software work product, 558 –59
software build, 559 –60
static library, 558
configuration management plan, 86 , 311 , 546
configuration management team, roles and responsibilities, 549
builder, 552
release manager, 522
SCM librarian, 552
SCM manager, 551 –552
SCM toolsmith, 552
software practitioners, 552
organizational-level SCM group, 550
project-level SCM group, 550 –51
configuration management tools, 553 –54
SCM build tools, 555
SCM change management tools, 507 , 553 –56
SCM library and version control tools, 554
SCM status accounting tools, 556
configuration reviews, 615 –16
configuration status accounting
data collection and recording, 611 –14
status reporting, 614
configuration testing, 495 –96 , 632
configuration units, 572 . See constituent configuration items
conflict of interest, 10 –11
conflicts
management, 43 –46
negative/destructive, 44 –46
positive/constructive, 43 –44
resolution, 43 –46
conformance, 3 , 87 , 109 , 139 , 141 –42 , 149 , 615
consistency, 110 , 150 , 230 , 252 , 260 , 269 , 369 , 390 , 449 , 523 , 544 , 617 –20
constituent configuration items, 572
constituent items, 569 –70
constraints
cause-and-effect graphing, 477 – 79
design, 200 , 493
project, 98 , 245
requirements, product, 191 , 194 , 196 , 200
constructive conflict 43 . See positive conflict
constructive cost models (COCOMO/COCOMO II), 293
constructor operations, in object-oriented analysis and design (OOAD), 254
containment plans, 335 . See risk mitigation plans
content management tools, 554
context diagram, 197 , 221
context-free questions, 55 –56
contingency plans, 335 , 344 , 348 –49 , 354
continuous distribution, 378
continuous improvement, xxi
continuous integration, 181 –82 , 547 , 580
contracts, 12 , 104 , 137 , 140 –41 , 284 , 305 , 340
negotiate and award, 101 , 103 , 172 , 268
requirements, 101 , 147 –48
contractual and legal risks, 340
control activities, of project, 307 –10 , 314 –15
checkpoints for, 310
for plans and estimates, 308 –9
PMI process for, 310
and program, 329
control charts, 378 , 434 –37
control flow graph, 385 –86
controlled library, 558 –63 , 574 , 594 , 635
controlled work product, 560 –62 , 568
control point baselines, 581 –82
control systems, 34 , 130 , 169 , 351 , 544
convenient, data collection goal, 110
conversion, 14
copyleft, 13 –14
Copyright Act, 13
copyrights, 13 –14
correction, 115 , 128 , 130 –33
corrective action plans, 130 – 33
corrective actions
audits, 156 –57
procedures, 127 –133
approval, 131
assign planning team, 128 , 130
closure, 132 –33
evaluation, 132
identification of problem, 128
implementation, 131
initiation of long–term correction, 130 –31
process, 133
process fix/correction, 133
product, 133
product fix/correction, 132 –33
project, 314 –15
steps to, 44 –45
corrective maintenance, 6 , 12 , 266
corrective release, 115 , 269 , 552 , 564 , 608 –10 , 621 –22
cost
budget, 298 –99 , 313 –14
deferring, 179
driver, for project management, 278 –79
estimates, 281 , 283 , 288 –90 , 293 –94
for project, 290
impacts, 456 , 601
metrics, 397
of ownership, 6 , 132 , 136 , 380 , 586
process metric, 397
project objectives, 284
reduction, 6 , 96
requirements prioritization, 233
reuse, 261
risk reduction, 347 –48
to fix a defect, 5 –6 , 405
verification and validation (V&V), 450 –51
cost/benefit analysis, 71 , 101 , 165 , 347 , 365 , 372
cost of poor quality, 113 . See cost of quality (COQ)
cost of quality (COQ), 113 –17 , 132 , 136 , 322
appraisal, 114
categories of, 114 –15
external failure, 115 –16
internal failure, 114 –15
model of optimal, 115 –16
prevention, 114
use, 117
cost performance index (CPI), 316 , 318
cost variance (CV), 316 , 318 –19
counting criteria, 368 , 371 –72 . See mapping system
coupling, in software design, 248 , 256 –57 , 260 , 396 , 601
courage, 31 , 65 , 178
coverage, test, 491
code coverage, 498 –501
data domain, 494
date and time domain, 494 –95
domain and boundary, 501
functional, 493
interface, 495
internationalization, 496 –97
metrics, 390 –91
platform configuration, 495 –96
requirements, 492 –93
security, 495
state, 494
create knowledge, lean principle, 125 , 127
credibility, 31 , 390
critical activity, 296
critical design review (CDR), 324 ,. See component design review
criticality, 255 , 353 , 361 , 449 , 452 –54 , 456 , 472 , 633
critical path, 296 –98 , 313 , 315
critical path analysis, 296 –98 , 337
for risk identification, 337
critical to x (CTx), 123 –24 , 132 , 136
cross-functional teams, 59 –60 , 305
cross-referencing code analyzers, 506
CRUD/CRUDL, for data management requirements, 203 , 494
Crystal, 172 , 408 –9
c-shaped matrix, 441
cultural competence, 57
culture, 57 , 62 –63 , 65 –66 , 106 , 120 , 134 , 161 , 284 , 304 , 496
currentness, 390
customer, of audit, 143 . See client, of audit
customer deliverables, 626
customer/user testing, 632
delivery, 630
development audits, 627 –28
development testing, 627
installation testing, 631
licensing keys, 629
localization, 629
ordering and manufacturing, 629 –30
pilots, 631
release packaging, 628 –29
release support, 632 –33
reviews, 627
software deliverables, 627
customer feedback, 270 –71
management, 271
customer problems, responsiveness to, 400 –1
customers, stakeholders, 89
customer satisfaction, 3 , 76 , 270 , 392 , 398 –400
customers of metrics, 379 –80
customer/user testing, 632
cyber crime, 352
cyber security, 209
cyber terrorism, 352
cyclic redundancy checks,(CRC), 630
cycle time, 398
cyclomatic complexity, 385 –86 , 391 , 431
D
daily audit team meeting, 145 , 154
daily briefing, 154 . See daily feedback meeting, audit
daily feedback meeting, audit, 154
dashboards, 425 –26
data
accessibility, 390 , 412 –13
accountability, 107 , 354
accuracy, 390 , 412 –13
availability, 353 , 390 , 414
backup, 107 , 204
completeness, 390 , 413
compliance, 390
confidentiality, 209 , 353 , 390
consistency, 390
coordination of multiple data stores, 204
efficiency, 390
credibility, 390
currentness, 390
efficiency, 390
and information security, 209
to information to knowledge, 368 –69
longevity, 204
mirroring, 204
portability, 390
precision, 390
provenance, 354
recovery, 204 , 390
requirements, 201 –2
data management, 203
integrity, 204
items and data relationships, defining, 202 –3
restore, 204
timeliness, 413 –14
traceability, 390
understandability, 390
verification, 204
data archiving, 112
database software, 507
data collection and storage, 107 , 110 , 611 –14
data collection plan, 109 , 123 –24 , 409 –10
how, 411 –12
who, 410 –11
data confidentiality, 209 , 353 , 390
data dictionary, 202 –3 , 494
data disposing/disposition, 112 , 204
data dissemination, 107 , 111 –12 . See also data reporting
data domain coverage, 494
data-driven testing, 464 . See black-box testing
data extraction, 411 , 414
data flow diagrams (DFD), 221 –22 , 443 –44
data flow modeling, 253
data integrity, 111 , 204 , 353 , 409 –17 , 461
data items, 201 –4 , 222 , 368 , 371 , 376 –78 , 409 –10
data maintenance, 107 , 110 –11
data management, 107 –8 , 203
architecture, 108 –110
data access, 107 , 111 , 203 , 351 –52
data archiving and disposition, 112
data collection and storage, 110
data dissemination, 111 –12
data maintenance, 110 –11
data refreshing, 203
data sharing 203
functions of, 107 –8
governance, 109
inputs, 107
outputs, 107
planning, 109 –10
principles, 107 –8
requirements, 203
data modeling, 253
data owners, 410 – 12
data privacy, 15 , 209
data protection/security, 106 –7 , 209
data quality, 390 , 412
data reporting, 111 , 414 , 419 –27 . See also data dissemination
data resource management, 107 . See data management
data security, 106 –7 , 209 –10
data set
distribution and, 378 –79
location, 376 –79
mean, 376
median, 377
mode, 377
range of, 377
standard deviation, 377
variance of, 377 , 379
data synchronization, 414
data tables, 392 , 420
date and time domain test coverage, 494 –95
debug, 114 –15 , 268 , 388 –89 , 515 , 534 , 580 , 613 , 636
debugger, 264 , 461 , 502 , 506
decision coverage, 499 –500
decision trees, 221 , 484 –85 , 505
decisiveness, 31
decoupled, 248 , 256 –57 , 260
defect containment effectiveness, 405 –8
defect density, 387 –88
defect detection effectiveness, 406 , See defect removal efficiency (DRE)
defect detection efficiency, 406 . See defect removal efficiency (DRE)
defect detection rate, measure, 372
defect detection, 5 –6 , 114 , 372 , 388 , 402 –8 , 443 –44 , 449 , 519
defect prevention, 5 –6 , 114 , 134 –36 , 397 –98 , 443 –44 , 515 , 518
defect removal efficiency (DRE), 406 –8
defect report 539 . See problem report
defect salting, 474 . See fault insertion
deferring commitment, lean principles, 125 , 127
delegating, leadership style, 42
deliverables, 79 , 82 –83 , 92 , 212 –13 , 277 , 286 , 302 , 319 –20 , 324 –25 , 382 , 450 , 471 , 513 , 583 , 616 –21 , 626 –33 , 617
metrics, 319 –20
deliver fast, lean principle, 125 , 127
delivery, 630
Delphi technique, 290 –91
Deming Circle, 121 . See plan–do–check–act (PDCA) model
denial of service, 106 , 209 , 352
departmental audit strategy, 149
Department of Energy (DOE), 12
dependability, 31
dependencies, 5 , 245 , 268 , 313 , 339 , 552 , 579 , 595 –96 , 601 , 612 , 624 –26
depth of structure, 286
derived measures, 372 –73
design, software. See software analysis and design
design constraints, 191 , 194 , 200 , 493
Design for Six Sigma (DFSS), 124 . See DMADV model
design verification and validation (V&V), 447 , 452 –53
desk audits, 142
desk checks, peer review, 519 –20 , 521 –24
destructive conflict, 44 . See negative conflict
destructor operations, in object-oriented analysis and design (OOAD), 254
detailed design, 183 , 252 . See component design
detailed design review, 324 . See component design review
detection controls, 360
detection score, 360 –61
developers, 4 , 49 , 89 –90 , 126 , 173 , 178 –80 , 206 , 251 , 410 , 459 , 464
developer, stakeholders, 90
developmental baselines, 582
development audits, 627 –28
development library, 557 . See dynamic library
development view, design, 251
deviation, 277 , 311 –15 , 612
direct-access media, 630
directing, leadership style, 42
direct metrics, 371 . See explicit measures
direct two-way communications, 211
disaster recovery, 106 , 634 , 637
discovery method audit strategy, 149
discrete distribution, 378
dispersion of data set, 377 . See variance, of data set
distributed work environments with virtual teams, 65 –66
distribution, 112 , 122 –23 , 378
distributor, stakeholders, 90
diversity, of teams, 57 , 59 , 65 , 180 , 516 –17
DMADV model, 124 –25
DMAIC model, 123 –25
documentation
agile, documentation in, 172 , 182
audit documentation 150 , 155 –56
data management documentation, 109 –111
design documentation, 250 –53 , 452
hierarchy, 77 –78 , 84 , 569
product documentation, 88 , 130 , 244
program documentation, 88
quality management system (QMS), 77 –88
industry standards, 77
quality policies, 78
quality/project plans, 86 –87 , 281 , 285 –88 , 468 , 546
processes, 78 –83 , 88 , 130
process architecture, 84 –85
work instructions, 84 –86 , 88
checklists, 86
forms, 84
guidelines, 84
templates, 84
training materials, 86
requirements specification, 191 , 229 –31 , 452
scope and limitations, 210 –11
size, metric, 384
testing documentation, 468 –71 , 533 –41
user/operator documentation, 244 , 324 –25 , 454
verification and validation of (V&V), 454
version description documentation, 625
documentation identification scheme, 578
documentation plan, 286
documentation/document study
audit preparation, 150 –51
requirements elicitation, 215
document audits, 142 . See desk audits
document control, 590 . See review and approval of the modified configuration items change control
documented information, 83 . See quality records
direct users, stakeholders, 89
drivers
for projects, 278 –79
for tests, 463 –64 , 502 –3 , 506
duration, 281 , 283 , 289 , 294 , 296 –298 , 312 –13
dynamic analysis method, for verification and validation (V&V), 450 , 459
dynamic analysis tools, 506
dynamic cycle time, 398
dynamic library, 557 –58
E
earned value (EV), 316 –19
ease of learning/learnability, 205 –6 , 215 , 258 , 396 , 488
ease of use, 205 –6 , 215 , 258 , 488
economics, 179
effective listening, 54 –55
effects, 128 –30 , 255 , 341 , 360 , 476 –79 , 489
efficiency
of the corrective action process, 132
of the product, 206 , 390 , 487
of the system and/or process, 155 –156
of the user, 258 , 396 , 489
efficiency of defect detection, 402 –8
effort, 5 , 18 , 35 , 54 , 59 , 87 , 105 , 126 , 131 , 152 , 154 , 175 –77 , 181 , 268 , 288 –94 , 296 , 299 , 303 , 308 , 316 , 320 , 425 –26
electronic transfer, 630 –31
element method audit strategy, 149
e-mail, 53 , 190
eliminate waste, lean principle, 125 –26
embedded systems, 185
emergency maintenance, 269
emotional stamina, 31
empathy, 31
encapsulation, 253 –55
encryption, 15 , 106 , 209 , 256
endurance testing, 486 . See volume testing
energized work, 180
engineering change boards (ECBs), 596 . See configuration control boards (CCBs)
engineering process group (EPG), 60
enhancement request, 231 , 268 , 270 , 396 , 555 –56 , 560 , 590 –92 , 612 , 623 , 633
enhancements, 193 , 266 , 271 , 325 , 590 –92 , 602 , 625
enterprise architecture, 184
enterprise data management, 107 . See data management
enterprise information management, 107 . See data management
entities, 3 , 110 , 197 , 222 , 250 , 253 , 367 , 369 –73 , 382 , 397 , 459 , 495
entity behavior modeling, 253
entity relationship diagrams (ERD), 222 –24
entry criteria, 79 –81 , 217 , 311 , 350
environmental factors, 281 –85
environmental load testing, 485 –86
environments
build, 552 , 559 , 580 –81 , 636
conformance of, 87
database, 111
development, 264 , 298 , 535
distributed work, 65 –66
multicultural, 57
stakeholder’s software, 183 , 185 , 206 –7 , 215 , 259 , 266 –67 , 269 –70 , 390 , 482 –84 , 488 , 595 –96 , 612 , 625 , 627 , 632
team, 59 , 62
test, 467 , 471 , 501 –4 , 508 , 534 –35 , 537 –38 , 621
controlling, 504
drivers, 502 –3
harnesses, 503
stubs, 502
test beds, 501 –2
work/organizational, 154 , 173 , 281 –82 , 289 , 294 , 304 , 602
equity theory, for motivation, 35
equivalence class partitioning, 472 –73
error guessing, 474
error rate, 206 , 396
error report, 539 . See problem report
errors, 4 , 111 , 167 , 195 , 257 , 412 , 466 –67 , 519 , 553
error handling, 84 , 221 , 246 , 252 , 256 –57 , 474 –75 , 523
error tolerance, 206 . See rebustness
escapes, 402 –5
escort, of audit, 145
espionage, 352
estimates, 87 , 98 , 131 , 150 , 161 , 171 , 176 , 181 , 280 –81 , 283 , 288 –94 , 296 –99 , 307 –9 , 313 , 320 –21 , 340 –41 , 365 , 397 –98
ETVX (Entry criteria, Tasks, Verification steps, eXit criteria) method, 79 –80
event/response tables, 221 , 228
evolutionary changes, 32 , 124 –25
evolutionary development, of software, 170 –71
versus incremental development, 170
strengths of, 170
weakness of, 171
evolutionary prototype, 214
exception handling, 474 –75
exception scenarios, use cases, 217 , 219
exciting quality, 8
executables, 243 , 269 , 382 , 448 , 460 , 522
exit criteria, 79 –80 , 83 , 217 , 311 , 334 , 350 , 449
expectancy theory, for motivation, 35
expected quality, 7
expert-judgment, 290 –92
explicit knowledge, 37 –38
explicit measures, 371 –72
exploratory auditing, 149 . See discovery method audit strategy
exploratory testing, 488 –89
expressed warranty, 12
external audit. See external second-party audits; external third-party audits
external failure cost of quality, 115 –16
external interface requirements, 197
external products testing, 490 –91
external second-party audits, 140 –41 , 148
external third-party audits, 141 , 148
external validity, of metric, 369 –70
extranets, 189
extra processes, lean waste, 126
extra features or code, lean waste, 126
extreme programming (XP), 178 –82
corollary practices, 181 –82
primary practices, 180 –81
principles, 179 –80
values, 178 –79
extrinsic motivation, 35
F
facilitated requirements workshops, 212 –13 , 229
facilitation skills
conflict management and resolution, 43 –46
facilitation, 43
meeting management, 48 –49
negotiation techniques, 46 –48
facilitators, 43 –45 , 48 –49
failure, 53 , 114 –15 , 180
failure mode and effects analysis (FMEA), 134 , 255 –56 , 359 – 61
failure mode effects and criticality analysis (FMECA) 359 . See failure modes and effects analysis
failure report, 539 . See problem report
fan-in metric, 386 –87 , 391
fan-out metric, 386 –87 , 391
fault-error handling, 474 –75 . See exception handling
fault insertion, 474
fault report. See problem report
fault seeding, 474 . See fault insertion
fault tolerance, 206 . See robustness
feasibility, 192 , 213 –14 , 221 , 232 , 250 , 252 , 264 , 298 , 336 –37 , 449 , 452 , 512 , 517 , 522
feasible, 231
feature-driven development (FDD), 172
feature release, 622
features, 126 , 175 , 201
Federal Aviation Administration (FAA), 12
Federal Communications Commission (FCC), 12
feedback, 6 , 39 , 41 , 50 –51 , 57 , 99 , 127 , 135 , 144 –46 , 154 , 163 , 167 –70 , 173 , 175 , 178 , 180 , 182 , 211 –12 , 216 , 230 , 258 . See also customer feedback
fibonacci sequence, 291
field-testing, 450 , 632 . See beta testing
financial risks, 340
findings, 54 , 121 , 138 –39 , 144 –45 , 155 –56 , 600 , 618 –19
finite, 231
firewall, 107 , 189 , 209 , 256
firmware, 185
first office verification, 450 , 632 . See beta testing; pilots
first-party audits, 139 –40 , 148
first-pass yield, 397 –98
fishbone diagram, 429 . See cause-and-effect diagrams
flexibility, 206 , 258
flow, 179
flowcharts, 428
focus groups, 211 –12
follow-up
audit corrective action and verification follow-up, 137 , 142 , 146 –47 , 156 –57
peer review, 514 , 522 , 525 , 532
Food and Drug Administration (FDA), 12
force field analysis, 33 , 70 –71
forecasts, 288 –90
forming stage, team development, 62 –63
forms, as work instruction, 84 –86
forward traceability, 239 , 603 . See also backward traceability; traceability/ traceable
fraud, 15
full release, 628
functional baseline, 582
functional benchmarking, 120
functional configuration audit (FCA), 104 , 450 , 452 –54 , 615 –18 , 627
checklist items and evidence-gathering techniques, 617 –18
functional coverage, 493
functional point model, 294
functional requirements, software, 194 –97
functional testing, 464 , 482 –85 . See black-box testing
function point churn, 393 . See requirements volatility
function points, 383 –84
functions, 201
G
Gantt charts, 312 –13
scheduling, 312
tracking, 312 –13
Gaussian distribution, 378 . See normal distribution
generic benchmarking, 120
generic goals (GG), for CMMI, 25 –26
generic practices (GP), for CMMI, 25 –26
Gilb’s risk principle, 331
glass-box testing, 461 . See white-box testing
globalization requirements, of product, 199 – 200
goal/question/metric paradigm, 380 –82
goals
data collection, 110
generic goals, for CMMI, 25
meeting, management of, 49
quality, 75 –76
specific goals, for CMMI, 25
gold copy, 635
“gold-plating,” 8 , 211 , 240
good-enough software, 466 –67
government-off-the-shelf (GOTS) software, 99
graphs, 420 –23
gray-box testing, 391 , 462 –64
bottom-up, 463 –64
top-down, 462 –63
group consensus, 59 , 66 , 124 , 130 , 152 , 290 –91 , 305 , 428 , 438 , 530 –31 , 599
group dynamics, 63 –64
grouped bar charts, 422
groups, diverse, working with, 65
GROW framework, for coaching, 40
guidelines, 18 , 38 , 78 , 207 , 253 , 285
work instruction, 84
H
hackers, 89 , 93 , 107 , 195 , 209 , 256 , 352
hacking tools, 506
happy path, 217 –18 . See main success scenario, use cases
hardware and software dependencies, 624 –26
harm. See accident
harnesses, test, 503
hash sums, 630
Hawthorne effect, 414
hazard, 356 –57
hazard analysis, software safety and, 357 – 59
help desk, 115 , 215 , 268 , 275 , 410 , 450 , 454 , 627 , 631
Herzberg’s motivation-hygiene model, 36 –37
high-level design, 250 . See architectural design
high-level design review, 324 . See architectural design review
histograms, 421 , 433 –34
horizontal prototypes, 214
hostile data injection, 352
hot fix, 621 . See corrective release
human factors, in metrics and measurement, 368 –69 , 414 –17
human factors studies, 215
humanity, 180
human resources, 275 –76 , 283 , 286 –87 , 297 , 303
humans, as users in functional testing, 482
hygiene factors, 36 –37
I
identifiers, 220 , 240 –41 , 469 , 476 , 536 , 538 –39 , 545 , 554 , 559 –60 , 567 , 569 , 574 , 578 , 594 , 612
IEEE software engineering standards, 17 , 20 –23 , 77 , 86 –87 , 120 , 134 , 150 , 229 , 250 , 252 , 285 , 369 , 456 –57 , 469 , 513 –14 , 533 , 538 , 544 –46 , 581
ilities, of software product, 4 , 191 . See quality attributes
impact analysis, 600 –3 , 609 –10
and concurrent development, 609 –10
implementation tools, 264
implied warranty, 12
improve, 180
incident report, 539 . See problem report
incomplete work, lean waste, 126
incremental change, 32 , 123 –24
incremental deployment, 182
incremental development model, 168 –70 , 181
strengths of, 169
weakness of, 169
independence, 87 , 137 –38 , 143 , 152 , 259 , 501
independent test/independent verification and validation (V&V), 164 , 464 –65 , 474 , 481
indirect users, stakeholders, 89
individuals and moving range (XmR) charts, 437
industry standards, 17 –23 , 77
informal change agents, 33
information, 365 –69
information asset management, 107 . See data management
information/data requirements, 201 –2 , 368 –69
data management, 203
integrity, 204
items and data relationships, defining, 202 –3
information hiding, in software design, 185 , 247 , 255 , 260
information management, 107 . See data management
information radiators, 408 –9
information resource management, 107 . See data management
information security, 106 –7 , 209
informative workspace, 180 , 408 –9
infrastructure, 111 , 119 –20 , 284
infrastructure plans, 288
inheritance, in object-oriented analysis and design (OOAD), 254
initiator, of audit, 143 . See client, of audit
input/output-driven testing, 464 . See black-box testing
inputs
into an audit, 148 –49
into data management, 107
into project planning 281 –85
to a process, 79 –81 , 375 , 428
to the software, 148 –50 , 153 , 195 , 197 , 202 , 257 , 466 , 472 –75 , 482 –84 , 486 , 494 , 535 –37
inputs, from stakeholders, 92 –94
inspections, peer reviews, 519 –21 , 525 –32
individual preparation step, 529
kickoff meeting step, 528 –29
meeting, 529 –31
planning step, 527 –28
post-meeting steps, 532
process, 526 –32
roles
author, 525 –32
inspectors, 525 –26 , 528 –31
moderator, 525 –32
observer 527
reader, 525 –26 , 528 –31
recorder, 525 –26 , 529 –32
inspection leader, 526 . See moderators, inspections
inspectors, 525 –26 , 528 –32
installability, 206
installation, 612 , 624 –25 , 627 –31
installation testing, 627 , 631
instant messaging (IM), 53 , 190
integrated master schedules, 313
integrated product team (IPT), 103 –4
integration, 104 , 181 , 386 –87 , 462 –64 , 480 –81 , 547 , 580
integration testing, 104 , 324 , 386 –87 , 391 , 460 , 462 –64 , 480 –81 , 491 , 495
integrity
conceptual, 126
data, 204 , 353
level, 456 –57 , 505 , 536
perceived, 126
intellectual property, 13 , 108 , 209 , 352 , 545 , 549 , 558 , 635
rights, 13 –14
interaction diagrams, 226 . See sequence diagrams
interface, 84 , 110 , 183 –86 , 214 , 243 , 246 –47 , 250 , 252 –53 , 255 , 258 , 260 , 462 , 481 –84, 495
coverage, 495
requirements, 194 , 197 , 201 , 220 , 229
intermediate installation media, 630
internal benchmarking, 120
internal failure cost of quality, 114 –15
internal first-party audits, 139 –40 , 148
internal validity, of metric, 369
international configuration coverage, 496 – 97
International Electrotechnical Commission (IEC), 3 , 4 , 17
International Function Point Users Group (IFPUG), 383
internationalization requirements, of product, 199 –200
internationalization testing, 496 –97
International Organization for Standardization (ISO), 18
9000 family, 18 –19
internet, 188 –89
internet layer, TCP/IP, 188
interoperability, 110 , 203 , 206 , 259 , 465
quality attribute, 206 , 259
in software design, 259
interrelationship digraph, 441 –42
interval scale measurement, 374
interviews, 55 –56 , 145 , 153 , 211 , 336
intranet, 189
intrinsic motivation, 35
introductory notes, CMMI, 25
in-use testing, 632 . See operational testing
Ishikawa diagram, 429 . See cause-and-effect diagrams
ISO/IEC 25000 Software Engineering— Software Product Quality Requirements and Evaluation (SQuaRE) standards, 4 , 205 , 390
ISO 9001:2015 standard, 18 –19
Quality Management Principles, 76
and quality management system, 19 –20
issue/issue report 539 . See problem report
item change and version control, 585
configuration control, 585 –86
configuration item attributes, 587
configuration item dependencies, 595 –96
item change control process, 587 –93
tracking item changes, 594
version control, 595
item metadata, configuration, 611
iteration baseline, 583
iterative model, 167 –68
J
joint application development (JAD), 212 –13 . See facilitated requirements workshops
joint application design, 212 –13 . See facilitated requirements workshops
K
kanban, 172
Kano’s model, 6 –8
basic quality, 7
exciting quality, 8
expected quality, 7
Kiviat chart, 425 , 427
KLOC (thousands of lines of code), 382
knowledge, 32 , 37 –38 , 127 , 134 , 304 , 354 , 367 –69
knowledge transfer, 37 –38
knowledge management system, 38
mechanisms for, 37
steps, 38
types of
explicit knowledge, 37
tacit knowledge, 37
Kruchten’s 4+1 view model, design, 251
L
labeling, 562 –66 , 575 –76 , 606 –9 , 611
labor costs, in project planning, 298
lagging indicator metrics, 400 –1
laws. See business rules
lead auditor, 131 , 143 –52 , 154 , 156 –57
leader, team, 48 –49 , 61
leadership. See also situational leadership
communication skills and, 49 –57
agile, 57
definitions, 31
facilitation skills and, 43 –49
organizational, 32 –42
qualities and characteristics, 31 –32
leading indicator metrics, 401
lean techniques, for process improvement, 125 –27
learnability, 396 . See ease of learning/learnability
legacy software, 262 , 265
lessons learned, 60 , 78 , 97 , 120 –21 , 124 , 133 , 136 , 151 , 161 , 215 , 327 –28 , 448 , 530 –31 , 541 , 550 , 552
lessons learned sessions, 136 . See also post-project reviews; retrospectives; reflections
level-of-effort work activities, 275
librarians, SCM, 552
libraries, SCM, 557
backup library, 558
controlled library, 558
dynamic library, 557 –58
processes
archive, 635 –36
backup, 633 –34
branching, 562 –64
controlled work product, 560 –62
merging, 564 –65
new software work product, 558 –59
software build, 559 –60
static library, 558
license, 12 –14
licensing keys, 629
life cycle/process model, 161 –82
likeability/user preference, 206 , 396
limitations, product, 210 –11
line graphs, 420 –21
line network, 294 , 297
lines of code (LOC), 382 , 391
linkers/loaders, 555
listening
effective, 54 –55
nonverbal, 55
verbal, 55
load testing, 485 –86
localization, 199 –200 , 496 –97 , 629
localization requirements, of product, 199 –200
localization testing, 496 . See internationalization testing
location
of configuration item, 587
of data set, 376 –77
mean, 376
median, 377
mode, 377
logical view, design, 251
logic bomb, 107 , 209 , 352
L-shaped matrix, 440
M
McCabe’s cyclomatic complexity, 385 –86 , 391 , 431
main success scenario, use cases, 217 –18
maintainability
quality attribute, 206 , 260 , 396
in software design 245 , 260
maintenance management, 265 –70
data maintenance, 110 –11
maintenance types
adaptive, 266 –67
corrective, 266
perfective, 266
preventive, 267
strategy
emergency maintenance, 269
maintenance process implementation, 267 –68
migration, 269 –70
modification implementation, 269
problem and modification analysis, 268
product discontinuance, 270
release review/acceptance, 269
software retirement, 270
maintenance release, 269 , 621 . See corrective release
major milestone reviews, 323 . See phase gate reviews
malicious code, 107 , 209 , 256 , 352
malpractice, 15 , 209
management reviews, 326 –27 , 511
management risks, 339
managers, SCM, 551 –52
manually-controlled library, 594
manual tracking of item changes, 594
manufacturing 629 –30 , See replication
manufacturing perspective of quality, 3 –4
mapping system, 368 , 371 –72
marketing surveys, 214
Maslow’s hierarchy of needs, 36
master library, 558 . See controlled library
mathematical proofs, 449
matrix diagrams, 440 –41
mean, 376 –79
mean time to change, 396
mean time to fix, 396
measurable, 231
measurement method, 368 . See mapping system
measurement
defined, 367 –68
error, 412
scales, 373 –74
median, 374 , 377 –78 , 398 , 423 , 435
meeting, management of, 48 –49
agenda, 48 –49
design stage for, 48
distribution of objective and agenda, 48
goals, 49
list of action items, 49
objectives, 48 –49
record (meeting minutes), 49
set up verification, 48 –49
time keeping, 49
members, of team, 61
memorability, 396
mentoring, 38 –39
merging, library processes, 564 –65
messaging system architectures, 190
metadata, 110 , 203 , 572 , 611
method, in object-oriented analysis and design (OOAD), 254
methodologies for quality management, 113
benchmarking, 119 –21
corrective actions, 127 –33
cost of quality, 113 –17
defect prevention, 134 –36
DMADV model, 124 –25
DMAIC model, 123 –24
lean techniques, 125 –27
plan–do–check–act (PDCA) model, 121 –22
return on investment, 117 –18
Six Sigma, 122 –25
methods, in object-oriented analysis and design (OOAD), 254
metrics
complex, 372 . See derived measures
customer, 379 –80
definition, 366 –67
goal/question/metric paradigm, 380 –82
measurement functions, 372 –73
measurement scales, 373 –74
model, 372 –73
primitive, 371 . See explicit measures reliability, 369 –71
reporting tools, 419
charts and graphs, 420 –23
dashboards, 425 –26
Kiviat chart, 425 , 427
stoplight charts, 424
selecting, 380 –82
software process, 397
agile metrics, 408 –9
capability, 408
cost, 397
customer satisfaction, 398 –400
cycle time, 398
defect containment, 405 –6
defect removal efficiency (DRE), 406 –8
escapes, 402 –5
first-pass yield, 397 –98
phase containment effectiveness, 405 –6
project and risk metrics, 289 , 408
project estimation metrics
calendar time, 289
cost, 290
critical computer resources, 290
effort, 289
productivity, 289 –90
project tracking metrics
earned value, 316 –19
productivity, 320 –21
resource utilization, 321 –22
staff turnover, 8 , 322
tracking deliverables, 319 –20
velocity, 320 –21
risk metrics
risk exposure (RE), 342 –43 , 347
risk probability, 341
risk reduction leverage (RRL), 347 –48
risk loss, 341
risk tracking, 350
reported problems, responsiveness to, 400 –1
total defect containment effectiveness (TDCE), 406
software product, 366 –67
arrival rates, 388 –89
availability, 394 – 95
customer, 379 –80
cyclomatic complexity, 385 –86 , 391 , 431
data quality, 390
defect density, 387 –88
entities, 382
maintainability, 396
problem report backlog, 389 –90
reliability, 393 –94
requirements volatility, 237 , 307 , 392 –93
size, 289 , 382 –84
function points, 383 –84
lines of code (LOC), 382
structural complexity
depth, 386
fan-in, 386 –87 , 391
fan-out, 386 –87 , 391
width, 386
system performance, 395 –96
test coverage, amount of, 390 –91
usability, 396
statistics and statistical process control, 376 –79
validity, 369 –71
variation, 374 –76
migration, 269 –70 , 625
milestones, 280 , 284 , 303 , 312
milestone reviews, 323 . See phase gate reviews
mishap, 357 –59
mission control, 425 . See dashboards
mistake, 5 , 134 –36 , 178 , 297 , 456 , 474 –75
mitigation
disaster recovery, 106 , 634 , 637
risk mitigation, 335 , 343 –49
security risk mitigation, 353 –55
safety risk mitigation, 361
mock-up, 214 . See horizontal prototypes
modality, 222 –24
mode, 374 , 377 – 78
model, definition, 18
model-based estimating techniques, 292 –94
moderators, inspections 525 –32
modifiable, 230
modifiability, in software design, 260
modifiable-off-the-shelf (MOTS) software, 99
modifier operations, in object-oriented analysis and design (OOAD), 254
modularity, 247
module testing, 480 . See unit testing
Monte Carlo estimation techniques, 291 , 342
motivation, 34
elements, 34
equity theory for, 35
expectancy theory for, 35
extrinsic, 35
Herzberg’s motivation-hygiene model, 36 –37
intrinsic, 35
Maslow’s hierarchy of needs, 36
recognition and rewards, 35
reinforcement theory for, 35
types of, 35
multicultural environments, 57
multiple condition coverage, 500 –1
multi-tier architecture, 185 . See n-tier architectures
multi-voting method, 68
mutual benefit, 179
N
negative conflict, 44 –46
negative observation, audit, 148 , 155 –56
negative risks, 331
negative testing, 474 . See exception handling
negligence, 14 –15
negotiation, 46 – 48
objectives for, 46 –48
skills required for, 46 –47
steps in
closing, 48
debating and bargaining, 48
preparing, 47
proposing, 47
network access layer, TCP/IP, 188 . See network
interface layer, TCP/IP
network interface layer, TCP/IP, 188 –89
new software work product, 559
node network, 294 –95
nominal group technique (NGT), 67 –68
nominal scale, 373
nonconformance
major, 155
minor, 155
non-functional requirements, 175 , 191 , 197 –200 , 229 , 251 . See quality attributes; interface requirements; data/information requirements
non-locking check-in/check-out processes, 606
non-project activities, 275
nonverbal listening, 55
normal distribution, 122 –23 , 378
norming stage, team development, 63
n-tier architectures, 185 –86
O
objective, data collection goal, 110
objective evidence, 142 , 144 , 146 , 152 –54
examining physical properties for, 153
examining quality records, 152
finding patterns, 153
functional configuration audit (FCA), 616 –18
gathering plans, 150 – 51
interview auditees, 153
physical configuration audits (PCA), 619 –20
reviewing documents, 152
tracing for, 153 –54
for verification and validation (V&V), 447 –48 , 540
witnessing event/process, 153
objectives
audit, 137 –38
meeting, 48 –49
negotiation, 46 –48
project, 282 –84
quality, 75 –76
reviews, 512
security requirements, 209 –10
SMART, 76
testing, 459
objectivity, of audits, 138
object-oriented analysis and design (OOAD), 253 –55
object-oriented models, 221
objects, in object-oriented analysis and design (OOAD), 253
observation, audit, 155
negative, 155
positive, 155
observation of work in progress, requirements elicitation, 214
observers
focus group, 212
inspections/peer reviews, 517 , 527
testing, 539
occurrence score, 360 –61
official change agents, 32
offshore, outsourcing, 96
offsite outsourcing, 96
offsite storage, 634 –35
one-way communication, 50 –51
onsite, outsourcing, 96
open-ended questions, 55 –56
opening meeting, audit, 144 , 146 , 151 – 52
open source license, 13
open source software, 99 , 490 –91
operational profile testing, 470 , 484 –85
operational testing, 632
operation baseline, 583 . See product baseline
operations, in object-oriented analysis and design (OOAD), 254
opportunities, 180 , 331 –32
optimize whole, lean principles, 125 , 127
oral communication
formal meetings, 51
formal presentations, 52
informal verbal interchanges, 51
telephone calls, 52
video conferencing, 52
voice mail, 52
ordering and manufacturing, 629 –30
ordinal scale, 373 –74
organizational leadership, 32 –42
coaching and, 39 –41
knowledge transfer and, 37 –38
mentoring and, 38 –39
motivation and, 34 –37
organizational change management, 32 –34
recognition and, 34 –37
situational leadership, 41 –42
organizational change management, 32 –34
force field analysis, 33
Satir change model, 34
steps to, 32 –34
types
evolutionary change, 32 , 124 –25
incremental change, 32 , 123 –24
organizational-level SCM group, 550
organizational process assets, 78 , 161 , 281 , 284 –85 , 637
organizational quality goals, 75 –76
organizational quality objectives, 75 –76
organizational quality planning, 77
oscilloscopes, 502 , 507
outputs
from a process, 79 , 83
from the software 197 , 202 , 257 , 464 , 472 –73 , 483 –84 , 494 , 497 , 535 –37
outsourcing, 96 –105
acquisition process, 97 –104
accept product, 104
define contract requirements, 101
define product requirements, 98 –99
determine approach, 99
identify and evaluate potential suppliers, 99 –100
initiate and plan, 97 –98
manage project, 103 –4
manage supplier, 103
negotiate and award contract, 101 , 103
project management, 103 –4
select supplier, 101 –2
use software, 104 –5
advantages, 96 –97
preferred supplier relationships, 105
overview meeting, 528 . See kickoff meeting step under inspections, peer reviews
owner, configuration, 587