Page 339 - Software and Systems Requirements Engineering in Practice

Index

A analysis
abstract classes, 27 coverage, 197, 198
abstract use case, 101, 103, defined, 40
107–110, 223–227 derivation, 197, 198, 200
abstraction, 74 vs. elicitation, 40
accuracy, 136 hazard, 276–283
active process, 36 impact, 197
activities, 59, 61, 78–82, 194 LEL-based, 181
activity diagrams, 105, 106, 224, performed by CCB members,
225–228, 244 196, 197
actors, 59 analysis models, 77–78, 80, 81,
acyclic directed graph, 94, 94, 115
99, 120 “analysis paralysis,” 6
adaptability, 137 analysis sessions
ADD (architecture design MDRE, 96–113
document), 259 UML, 99–113
ADD (Attribute-Driven Design), analysts
162–164 prioritizing/ranking
agile methodologies, 17, 18, 236, requirements, 53–55, 69
252–254 training for, 4
agreements, 197, 200 untrained, 42, 217
AHP (Analytic Hierarchy working with stakeholders, 47
Process), 53–54 Analytic Hierarchy Process
Akao, Yoji (Dr.), 55 (AHP), 53–54
ambiguity, 10–11, 14, 15, 217, 235 analyzability, 137

301