Page 351 - Software and Systems Requirements Engineering in Practice

d
n
e
I I n d e x 313 313
x
rapid, 236–240 building automation system,
storyboarding, 246–248 156–168
time constraints, 243 described, 128, 131
tips for, 252–254 integrated model for, 130–132
visual, 247 practice/experience, 168–170
when to prototype, 236–240 scenarios, 131, 143–145, 171
stages of quality attribute
Q grief, 139
QAMs (quality assessment stakeholder selection,
methods), 50 140–142
QAR. See quality attribute terminology, 127–130
requirements tips for, 170–171
QAS (quality attribute scenario), quality attribute scenario (QAS),
131, 143–145, 155, 171 131, 143–145, 155, 171
QAW (quality attribute quality attribute workshop
workshop), 143–145, (QAW), 143–145,
159–160, 171 159–160, 171
QFD (Quality Function quality attributes, 128–145
Deployment) method, 55 Quality Function Deployment
quality (QFD) method, 55
artifact, 15 quality in use, 132, 133
described, 136 quality indicators, 7
external, 132 quality metrics, 205–206
internal, 132 query retrieval, 217
metrics for, 86 questionnaires, 180–181,
notion of, 169–170 186–187, 190
process, 132
quantifying, 128–129 R
requirements engineering, ranking, 53–55
15–16 rapid development techniques,
quality assessment methods 233–255
(QAMs), 50 overview, 234–236
quality assurance checks, 117–118 prototyping, 236–240
quality assurance scripts, 281 recommended practices,
quality attribute measure, 136 240–252
quality attribute requirements tips for, 252–254
(QARs), 125–173, 128, 131 Rational Unified Process (RUP)
architectural requirements, techniques, 7
126–129 RDB. See requirements database
architecturally significant RDMS (requirements data
requirements, 154–156 management system), 198–199,
basics, 132–140 212–213