Page 352 - 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
w
o
f
t
314 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
a
314
RDMS tools, 199 REAM diagrams, 27–30
RE (requirements engineering) reconciliation worksheet, 188
conclusion, 287–290 reconciling stakeholder input,
definition of, 8 188–189
distributed, 257–273 recoverability, 136
early phases of, xxii, 207–208, relationships
236–237, 239, 253 analyzing, 181
importance of, xxi, 2–3 customer, 64
industrial challenges, 4–5 project team. See
introduction to, 1–17 project teams
key success factors, 5–7 realization, 108
metrics and, 15–16 tracing, 115–116
misconceptions, 3–4 use cases, 108
in parallel with prototyping, release-based organizational
240–243 approach, 261
for platforms. See platform releases
projects allocating requirements to,
quality and, 15–16 199–200
vs. requirements analysis, 8 overlapping, 261
taxonomies, 21–27 pairwise ranking and, 53–54
traditional business processes planning, 53, 199–200
and, 8 “scope creep” and, 6
RE processes. See also processes strategies for, 214
establishing policies for, 199 reliability, 136
measuring savings with, 209 REMP (requirements
OEMs, 270–271 engineering management
scalability of, 4, 6 plan), 208, 210
suppliers, 270–271 replaceability, 137
RE workshops, 266 requests
realization relationships, 108 change, 195–197, 200,
REAM (RE artifact model). See 237, 247
also artifact modeling ECRs, 196
creating, 28–30 MRs, 196
described, 27 vs. requirements, 44
dynamic tailoring of, 34 separating from context, 44, 68
elements of, 27–28 requirement quality metric, 206
organizational models, 34–35 requirements
process definition support, ambiguity, 10–11, 14, 15,
30, 32 217, 235
system life cycle process, 35–37 architectural, 126–129
templates for, 30–33 characteristics of, 9–15
using, 30 completeness, 12–13, 133–135