Page 354 - Software and Systems Requirements Engineering in Practice

q
u
i

R
e
e
n
t
r
e
m
&

S
r
e

e
m
s
y
s
t
s
n

P
:

I
t
i
c
r
a
c
g
i
n

E
n
i
n
g
e
e
r
f
t
w
o
a
316 S S o f t w a r e & S y s t e m s R e q u i r e m e n t s E n g i n e e r i n g : I n P r a c t i c e e
316
requirements discovery, 244 scalability, 207
requirements elicitation. See traceability, 200–204
elicitation version control, 195–198, 208,
requirements engineering. See RE 210–211
requirements engineering volatile requirements, 198
management plan (REMP), requirements management
208, 210 processes, 207–208
requirements engineers requirements modeling, 73–124
communication with from analysis to design, 115
stakeholders, 47, 68 clarity/completeness, 113
questionnaires used by, 180 content correctness, 113
training/experience, 4, 6 conversion guidelines,
requirements evolution, 233–255 115–116
requirements hierarchies, 215, design models, 115, 117–120
293–294 determining model
requirements levels, 42–43 completeness, 113–114
requirements management model faults, 113–114
(RM), 193–218. See also model-driven requirements.
change management See MDRE
best practices, 215–217 overview, 74–79
coverage analysis, 197, 198 quality assurance checks,
critical success factors in, 6 117–118
data flow diagram, 59, 60 tips for, 120–121
derivation analysis, 197, 198 requirements models, 222
distributed engineering requirements relationships, 86
and, 210 requirements reviews, 6, 41,
documenting decisions, 66, 69
199, 200 requirements specifications, 9,
impact analysis, 197 12–15
measurement practices, requirements-driven system
204–206 testing, 219–232
metrics, 204–206 best practices, 228–230
nonprioritized requirements, model-based testing, 222–227
237–238 overview, 220–221
organizational issues, 210–215 performance/scalability
overview, 194 requirements, 227–228
planning releases, 199–200 RE inputs for, 222
prioritizing requirements, “V” model, 220, 221
53–55, 69, 199, 210 resource utilization, 137
for product lines, 213–215 return-on-investment (ROI), 214
purpose of, 194 reuse requirements, 254
routine activities for, 198–200 reviewing models, 229