Page 346 - Software and Systems Requirements Engineering in Practice

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

&
s
s

m
t
e

P
n

I
r
i
c
t
a
c
:
i
n
g
E
n
e
n
g
i
e
r
e
o
f
t
308
308 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
S
w
a
r
interface class, 111 MBT (model-based testing),
interface tracing, 115, 116 222–227
internal quality, 132 MDA (model-driven
interoperability, 136 architecture) initiative, 223
ISO-9126 standard, 186 MDRE (Model-Driven
issues, 132, 146, 149–150, 153–154 Requirements Engineering)
advantages of, 84–86
J analysis sessions, 96–113
Jones, Capers, 23, 45, 239 artifacts and, 82, 85
cross-cutting requirements,
K 85–86
Kano, Noriaki, 52 elicitation, 96–98
Kano modeling, 52 estimating project size/cost, 85
Kano values, 211 hazard analysis and,
281–282, 283
L initiating MDRE effort, 96
Language Extended Lexicon overview, 79–84
(LEL), 181 prerequisites for, 87–88
language/communication threat modeling and, 285
issues, 47–48, 68 use of tooling for, 120
languages MDRE artifacts, 82, 85
constraint, 226 MDRE processes, 82, 83–84, 88–98
English language skills, 260 measurement practices, 204–206
natural, 59, 85, 122, 288 meetings
OCL, 226 elicitation, 187
UML, 4, 75, 99–113 face-to-face, 154, 269
URML, 86, 88 prioritization, 154
learnability, 137 team, 268
legacy products, 182 metamodels, 27, 203–204, 215
LEL (Language Extended metrics
Lexicon), 181 artifact quality, 15
life cycle, 229–230 categories, 205–206
life cycle process, 35–37 completeness, 206
localizability, 187 coverage, 206
loquacious objects, 112 derivation, 206
examples of, 205, 206
M function points, 16
maintenance, 208 hazard analysis, 279
maintenance costs, 178 obtaining, 204–206
marketing organization, 6 progress, 86
Marketing role, 201 project, 205, 206
maturity, 136 quality, 86, 205–206