Page 350 - 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
312
o
w
312 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
products (continued) projects
managing requirements for, distributed, 261–266
214–215 estimating size/cost, 85
vs. product lines, 214–215 failure rate, 128
use case model, 92–94 global, 260
use of, 90–92 platform. See platform projects
product-specific characteristics, REAMs for. See REAM
13–14 schedules, 128
programming, paired, 240 size, xxi, 215
progress indicators, 7 project-specific characteristics,
progress metrics, 86 13–14
project failure, 15 prototypes
project glossary. See glossaries advantages of, 235
project manager, 266, 267 branch, 249
project measurements, 205 defined, 246
project metamodels, 215 “demo effect,” 250
project metrics, 205, 206 disposable, 239
project plans, 15, 86 executable, 237, 248–250
project teams. See also team feedback on, 242, 251, 252
members mock-up, 252
authority issues, 148 multiple features, 243
central team, 268 physical, 236
collaboration tools, 267–269 reviewing, 237, 242, 245
communication issues, 211, size, 236
259–270 software, 236
core team, 7 “throwaway,” 236, 243, 249, 252
cultural differences, 269–270 time boxed, 239
e-mail, 268 transparency and, 250
isolation and, 4 validity of, 239
language issues, 260, versions, 242
269–270 prototyping, 112–113
meetings, 268 advantages of, 235, 237
paired programming, 240 concurrent development,
project roles, 37, 262 240–243
proximity considerations, 270 early elicitation for,
relationships between, 263 236–237, 253
remote team, 259, 268–269 guidelines for, 239
roles, 262 iterative nature of, 244–245
scrum, 268 optimizing process for, 251–252
size, 270 output of, 243
tips for, 271–272 in parallel with RE, 240–243
virtual RE teams, 266, 271 project size and, 239