Page 357 - Software and Systems Requirements Engineering in Practice

319
e
n
d
I I n d e x 319
x
extending, 26–27 Tester role, 201
FURPS+, 169–170 test-first development,
vs. glossaries, 22 250–251
team members. See also project testing. See also requirements-
teams driven system testing
authority issues, 148 applications, 129
central team, 268 ASRs, 154–156
communication issues, 211, black-box, 223
269–270 early stages, 250–251
core team, 7 guidelines, 251
cultural considerations, improving efficiency, 230
269–270 model-based, 222–227
experience, 87 NFRs, 185, 190
interviewing, 269 performance requirements,
language issues, 260 227–228
paired programming, 240 scalability requirements,
project roles, 37, 262 227–228
proximity considerations, 270 specification-based, 223
recruiting, 269 use cases for, 223–227
remote team, 259, 268–269 white-box, 223
teams. See project teams Texas Instruments Information
tech support, 140 Engineering Facility
teleconferences, 268 (IEF), 67
telephone communications, 269 threat modeling, 284–286
templates, 30–33, 191, 199 vs. hazard analysis, 284
terminal use case, 90–91 MDRE and, 285
terminology. See also glossaries metrics, 286
hazard analysis, 276–277 overview, 284–286
platform projects, 181, scenarios, 284
187–188 terminology, 284
quality attribute requirements, threats, 284
127–130 “throwaway code,” 235
requirements database, “throwaway” prototypes, 236,
293–295 243, 249, 252
threat modeling, 284 time behavior, 137
unifying, 181, 187–188 time boxed prototypes, 239
test cases, 217 time-boxed scheduling, 154
test coverage, 229 time-to-market, 169, 238–239,
test engineers, 220–223 259, 261
test model, 74–75 TM. See threat modeling
testability, 137, 185, 190 trace matrix, 4