Page 347 - Software and Systems Requirements Engineering in Practice

309
d
e
x
I I n d e x 309
n
requirements database, 217, content correctness, 113
294–295 creation of, 74
requirements engineering, described, 77, 222
15–16 design, 74, 81, 115, 117–120
requirements management, determining completeness of,
204–206 113–114
threat modeling, 286 diagram quality, 113
tips for, 205 domain, 164, 165
used early in project, 205 elicitation, 77–78
volatility, 198, 206 extracting requirements from,
metrics summaries, 15 94–96
mitigation techniques, 215 fault trees, 74
Mizuno, Shigeru (Dr.), 55 faults, 113–114
mock-up prototypes, 252 feature, 74, 81
model reviews, 98 formal, 75
model-based testing (MBT), goal, 81, 89
222–227 implementation, 74, 81
model-driven architecture integrated, 130–132
(MDA) initiative, 223 lightweight, 84
Model-Driven Requirements metamodels, 27, 203–204, 215
Engineering. See MDRE NFR, 183–184
model-driven techniques, 58–62 organization of, 96
modeling process, 77
artifact. See artifact modeling quality checks, 117–118
business, 80, 95 REAM. See REAM
business object, 108–109 requirements, 222
challenges, 235 requirements analysis, 74
distributed, 98 reviewing, 229
feature, 78 test, 74–75
goal, 49–51, 78, 145–146, 153 types of, 74–75, 222–227
Kano, 52 UML, 75, 227–228
performance, 164–168 usage, 222
SysML modeling, 79 use case, 80, 81, 92–94
threat. See threat modeling “V” model, 202–204, 220, 221
use case, 85 modifiability, 11, 14, 152, 164
modeling sessions, 96–116 modification optimization,
models 251–252
analysis, 77–78, 80, 81, 94, 115 modification requests
artifact, 101–102 (MRs), 196
business, 74, 79, 80–81, 95 MRs (modification requests), 196
constructed from source multidimensional support,
code, 222 299, 300