Page 341 - Software and Systems Requirements Engineering in Practice

303
I
x
e
d
n
I n d e x 303
Berry, Dan, 41 CCB (change control board), 6,
bidirectional hyperlinks, 102 195–197
black-box testing, 223 change control, 197
blueprints, 78 change control board (CCB), 6,
book, use of, 16 195–197
boundaries, 109–118 change management, 6, 195–198,
boundary class, 111 217. See also requirements
boundary reports, 110 management
brainstorming sessions, 55–58 change of value (COV)
branch prototypes, 249 events, 181
Brooks, Fredrick P., Jr. (Dr.), 40 change requests, 195–197, 200,
bugs, 129, 209 237, 247
Building Automation System changeability, 137
(BAS), 156–168, 176 CHAOS report, 2
business goals chief architect, 5, 266–267
eliciting, 49–51 chief requirements engineer, 266
features derived from, 158 class diagrams, 224
goal modeling, 49–51 class methods, 111
goal refinement, 157–158 classes
goal-based traceability, 202 abstract, 27
goals vs. subgoals, 202 artifact, 130
high quality, 8 on class diagrams, 27, 107
impact of, 168–169 combining, 107
including in change concrete, 111, 116
management, 217 defining for objects,
low cost, 8 108–109
scenarios derived from, 161 equivalence, 224, 226
business model, 74, 79, 80–81 software, 116, 117
business modeling, 80, 95 splitting, 107
business object modeling, stakeholder, 141, 142
108–109 Cleland-Huang, Jane, 214
business objects, 91, 108–109, CMMI (Capability Maturity
112, 114, 116 Model Integration), 6, 7, 220
business processes, 86 code
business rules, 62–63, 210 models constructed from, 222
buyers, 200 reusing, 235
“throwaway,” 235
C code inspections, 129
Capability Maturity Model co-existence, 137
Integration (CMMI), 6, 7, 220 collaboration diagrams, 105–107
cardinality, 28 collaboration web site, 267–269
CASE tool, 61, 102, 115 collaborations, 260