Page 349 - Software and Systems Requirements Engineering in Practice
P. 349
e
x
d
n
I I n d e x 311 311
P priority
package diagrams, 224 assigning, 53
packages, 101, 102, 118, 261 impact of dependencies on, 199
paired programming, 240 vs. ranking, 53
pairwise ranking, 53–54 process artifacts, 30, 32
Parker boiler, 75–77 process modeling, 58–62, 78, 79
passive objects, 112 process models, 77
passive process, 36 process quality, 132
performance, 164, 227–228 process steps organizational
performance modeling, 164–168 approach, 261
performance targets, 138 processes. See also RE processes
PG (planning game) active, 36
technique, 54 business, 86
planning game (PG) hazard analysis, 277–280
technique, 54 low-level, 112
platform initiatives, 176 MDRE, 82, 83–84, 88–98
Platform NFR Development passive, 36
(PND) process, 178–179, requirements management,
186–187 207–208
platform organizational processing overhead, 167–168
approach, 261 product architecture, 132
platform projects, 175–192 product development, 67–68
challenges, 177–178 product features, 10, 11, 157–159
example of, 186–190 product life cycle, 8
nonfunctional requirements, product lines, 213–215
182–186, 190 product maps, 299–300
overview, 176 product safety, 13
practices, 178–186 product structure organizational
tips for, 190–191 approach, 261
platform-level NFRs, 183, 184 productivity, 98, 137
platforms, 176, 178 products
PND (Platform NFR accelerated creation
Development) process, process, 2, 3
178–179, 186–187 analyzing features, 92–94
policies, 63, 210 defect rates, 129
policy changes, 210 government regulations, 3
postconditions, 59 identifying customer needs,
PowerPoint, 246 46–47
preconditions, 59 introduction of new
prioritization, 53–55, 69, products, 5
154, 199, 210 legacy, 182
