Page 342 - Software and Systems Requirements Engineering in Practice

u
i
r
R
e
q
n
t
s
e
m
e

S
y
e

&
m
s

s
t
e
n

P
:

I
t
i
c
r
a
c
g
i
n

E
n
i
n
g
e
e
r
r
304 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
f
o
304
a
w
t
communications, 234–235, cross-cutting requirements,
259–270 85–86, 128
competence center cultural issues, 269–270
organizational approach, 261 customer communications, 64
competence centers, 258, 261, customer management, 7, 197
263, 265 customer relationships, 64
competitors, 140 customers
completeness metric, 206 brainstorming sessions, 55–58
component-level NFRs, identifying product needs,
183, 184 46–47
computing speed, 259 model reviews, 98
concrete classes, 111, 116 customer-specific business rules,
concrete use cases, 94, 102–110, 62–63
224–226
concurrency, 164 D
concurrent requirements data flow diagrams (DFDs),
development, 240–243 59, 60
consistency, 11–12, 14 databases
constraint language, 226 content generation, 86
constraints, 185, 190, 191, 226 RDMS, 198–199, 212–213
content correctness, 113 requirements. See
context requirements database
ambiguity and, 10–11 decision points, 224
defining, 9 decision tables, 57
separating from requests, decisions, documenting,
44, 68 199, 200
understanding, 90–92 defect indicators, 209
context diagrams, 99–101 defect rates, 15, 129
contractors, 200 defects, 209, 221
contradiction, 11–12 delivery dates, 195, 196, 267
core project team, 7 “demo effect,” 250
corporate security Denne, Mark, 214
requirements, 14 dependencies
cost drivers, 129 determining, 102
cost estimation, 67 features, 78
cost/schedule estimation impact on priority, 199
methods, 271 packages, 102
COV (change of value) RE artifacts, 20
events, 181 requirements, 214
coverage analysis, 197, 198 derivation analysis, 197,
coverage metric, 206 198, 200