See also modeling
languages
probe, 211??“214, 325
process. See software process
process controller (case study). See reactive
system
project. See software process
projection, 126??“127, 132??“136
product, 121, 325
program structure, 67, 281??“282
progress, 7, 32, 47, 325
protocol, 14??“16, 223??“226, 326
property checking, 246. See also temporal
property
pruning, 7, 186??“190, 218, 326
pure, 69, 326
purpose, 61, 72??“73, 82
random strategy, 191??“193, 202??“203, 326
reachable
object, 249, 252, 290, 326. See also object
graph
state, 136, 228, 249, 326
reactive system, 4, 8, 32, 137, 259??“274, 277,
326
reactive system (process controller case study),
32??“52, 82??“92, 106??“113, 134??“136, 326
reference (assembly), 23
reference equality, 158, 326
refinement, 246, 277
regular languages, 123, 150
requirement, 61, 228??“229, 267, 291??“292
Requirement, 228, 291??“292. See also
Attributes, NModel
restricted model, 197, 326
review. See inspection
revision control system (case study), 169??“182
reward, 206??“209, 217, 218, 326
run, 7, 58, 96??“97, 326. See also trace
run-time check 70, 326
safety, 106, 326. See also liveness
safety analysis, 6, 48??“49, 94, 106??“108, 326
safety condition. See safety requirement
Index 347
safety requirement, 34, 106??“107, 246, 326.
See also invariant
sample. See case study
sample protocol (client/server case study),
224??“244, 260??“261, 264??“268
sampling, 7, 190, 217, 326
sandbox, 8, 28, 41, 327
scenario, 6??“9, 25??“27, 59, 96??“97, 115, 212,
327
scenario control, 115??“123, 127??“132, 138, 188,
244??“245, 271, 276, 282, 327
scenario FSM, 97, 133??“134, 253, 254, 257,
327
scenario model program, 59, 127??“129,
132??“134, 238, 327
self-loop, 124, 241, 327
sequence, 164??“166, 172, 298??“301, 327.
Pages:
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441