Page 340 - 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
a
302
302 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
o
S
f
w
t
applications described, 28
defects, 129 early planning for, 207–208
failure rates, 128 factors, 132
integrating existing, integrated model for,
157–158 130–132
platforms for. See platform issues, 132
projects MDRE and, 82, 85
prototypes for. See prototypes multiple, 251–252
replacing, 157 process, 30, 32
testing, 129 quality, 15, 204, 260
time-to-market, 239–240 strategies, 132
web, 244, 249, 253 templates for, 30–33
Architect role, 201 visibility of, 101–102
architectural drivers, 128, ASRs (architecturally significant
161–162 requirements), 127, 128,
architectural requirements, 154–156
126–129 assets, 284
architectural requirements association, artifacts, 28
engineering attractiveness, 137
artifacts, 130 attribute scenarios, 131
methods for, 142–154 Attribute-Driven Design (ADD),
architecturally significant 162–164
requirements (ASRs), 127, attributes
128, 154–156 downward propagation of,
architecture design, 298–299
162–164, 259 quality, 128–145
architecture design document requirements database,
(ADD), 259 297–299
artifact classes, 130 taxonomies, 24
artifact modeling, 19–38. See also upward propagation of,
REAM 297–298
introduction, 20–21 authority, 148
key components, 21 automation strategies, 207
purpose of, 20
tips for, 36–37 B
artifact models, 82, 215 Bachman Analyst Workbench, 67
artifact taxonomies. See backward from requirements, 202
taxonomies backward to requirements, 202
artifact tracing, 115–116 BAS (Building Automation
artifacts System) project, 156–168, 176
association, 28 baselines, 195, 198, 199
cardinality, 28 benchmark values, 205