INDEX
A
Abuse cases, 134
Activity diagram, 393, 395, 401, 403, 404
Actor, 8, 14, 31, 67, 68, 88, 94, 96, 119, 247, 263
goals, 241
key, 67
See also Role; Stakeholders
Affinity diagram, 190
See also User stories
Air Traffic Control (ATC), 364
Alternative courses, 161–164, 166, 168, 169, 174, 364, 370, 373
See also Use case scenarios
Alternative scenarios, 103–116, 146
applicability, 103
features, 104
strengths, 104
technique, 105
weaknesses, 104
Alternative world, 10
See also Situation
Alternative world scenarios, 106
Analysis, 4, 228, 249, 250, 252, 254
bottom-up, 397
object/action, 224
top-down, 397
Anti-scenarios, 136
Architecturally Significant Requirements (ASR), 384, 385
Architecture Trade-off Analysis Method (ATAM), 384
applicability, 161
approach, 164
comparisons, 176
features, 162
process and environment, 162
research, 163
software environment, 166
strengths, 162
structure and representation, 164
weaknesses, 162
worked example, 173
ASR. See Architecturally Significant Requirements
Assumptions, 77, 105–110, 215, 300, 365, 393, 401, 409, 411
ATHOC, 411
Automatic Teller Machine (ATM), 284
Automatic Train Control (ATC), 402, 404
Automotive industry, 334
Automotive software development, 331, 334
strengths, 330
weaknesses, 330
B
Bayesian Belief Networks (BBNs), 176
Black-Box Test, 296
British Telecom (BT), 61
Business event, 40
identification, 44
alternative case scenario, 50
identification, 44
C
Claims analysis, 447
Class-Responsibility-Collaborator (CRC), 278
Collaboration patterns, 90
Collaborative (or facilitated) requirements workshop, 85, 90, 99
Combining process models
evolutionary and high risk, 319
evolutionary and incremental, 318
evolutionary, incremental and high risk, 322
incremental and high risk, 321
Commercial-Off-The-Shelf (COTS), 296, 302, 473
Compliance Arguments (CA), 400
Concept of Operations. See Operational concept
Concept, Assessment, Demonstration, Manufacture, In-service, and Disposal (CADMID), 312
Conceptual Design (CD), 222, 229, 448
Conceptual scenarios, 153, 211, 215, 223, 226
Concrete scenarios, 211, 214, 215, 217, 223
Condition, 76, 146, 189, 281, 286, 289, 290, 295, 336
pre-conditions, 61, 154, 204, 401
trigger, 189
COnflict Resolution Assistant. See CORA-2
Constraints, 51, 61, 66, 68, 351, 401, 413
cost, 329
economic, 387
explicit, 157
financial, 310
implicit, 157
organizational, 206
physical, xiv
potential, 68
quality, 383
system, 468
Contextual Design (CD), 179, 206, 207
applicability, 180
comparisons, 206
consolidation, 190
features, 181
interpretation sessions, 187
lessons learnt, 205
storyboard, 194
strengths, 181
technique, 185
visioning, 192
weaknesses, 185
work modeling, 188
worked example, 186
Controlled Flight into Terrain (CFIT), 110
Cooperative Requirements Engineering With Scenarios (CREWS), 163, 363
background, 366
Corpus of scenarios, 211
Create-Read-Update-Delete (CRUD), 155
CREWS-L'ECRITOIRE, 176
CREWS-SAVRE, 363–366, 370, 371, 373, 375, 376
features, 364
strengths, 364
weaknesses, 365
Critical Design Review (CDR), 307
Customer collaboration, 82
Customer-centered design, 179, 180
Customers, 64, 81, 156, 157, 187, 189, 202, 206, 239, 266, 270, 414, 416
behavior, 77
contacts, 51
contracts, 157
goals, 82
information, 156
priorities, 98
requirements, 64, 97, 188, 396
role, 207
satisfaction/dissatisfaction, 52
D
Day in the Life of (DILO), 61
Design elements, 219
Developer story, 265, 268–270, 273
Development projects, 18
Device Unifying Service (DUS), 73
Domain knowledge, 396, 401, 408, 409, 473
E
Early requirements, 414
Electrical Control Unit (ECU), 332
Eliciting requirements, 119
Embedded systems, 329, 334, 340, 343
End-to-End Conditions, 401
assumptions, 401
constraints, 401
frequency, 401
goal, 401
possible failure conditions, 401
rationale, 402
success end conditions, 401
Envisioning process, 66
Equivalence, 349
functional, 349
physical, 349
alternative flow, 244
course, 13, 146, 168, 285, 292
exception, 123
flow, 244
start and end, 164, 168, 169, 371
time-triggered, 15
Exception, 4, 123, 124, 137, 364, 366
courses, 282
See also Use case extensions
See also Alternative courses; Exception
Extreme Programming (XP), 266–268, 270, 273, 278, 310
F
Facets, 26
classification, 26
Facilitated workshop, 86
Facilitator, 172
Failure Modes Effects Analysis (FMEA), 132, 133, 472
Failure Modes Effects and Criticality Analysis (FMECA), 133
Fault Tree Analysis (FTA), 132, 133
Feature interactions
identification, 338
FMEA. See Failure Modes Effects Analysis
FMECA. See Failure Modes Effects and Criticality Analysis
Framework, 26
contents view, 27
form view, 27
life-cycle view, 27
purpose view, 27
FTA. See Fault Tree Analysis
Functional Hazard Analysis (FHA), 132, 133
G
General Requirements Document (GRD), 398
Generator-conjecture-analysis, 426
Graphical User Interface (GUI), 11
See also Condition
Guidelines
scenario/use case, 149
H
HazOp, 132
Home information centre (HIC), 211
Hubris, 292
Human–Centred Interaction Design (HCI), 211
abstraction, 220
aggregation, 220
applicability, 211
classification, 220
comparisons, 232
design constraints, 221
envisionment, 222
evaluation, 223
method, 213
object model, 219
other artifacts, 218
physical design, 223
processes, 220
prototyping, 222
requirements and problems, 218
requirements specification, 221
strengths, 213
weaknesses, 213
worked example, 224
Human–Computer Interaction (HCI), 12, 445, 446
HW Drivers, 389
I
i* and GRL, 136
Ill-structured problems, 425
Innovation, 62
Integrated Project Teams, 438
Interaction patterns, 220
J
Joint Application Design/Development (JAD), 85
Journey music, 290
L
Life cycle, 17, 212, 299, 302, 303, 433, 434, 436, 438, 440, 441
Lifestyle Due Diligence (LDD), 77
Live Sequence Chart, 11, 15, 136
M
Main scenario, 285
Marketing, 335
Message Sequence Chart (MSC), 289
Minimum Safe Altitude Warning (MSAW), 110
Misuse Cases, 19, 99, 119, 121, 137, 337, 354–361
applicability, 119
comparisons, 131
elicitation, 122
eliciting hostile roles, 121
failure cases, 131
hazard and operability analysis, 133
metaphorical roles, 127
worked example, 128
Mitigation, 119
N
National Engineering Education Delivery System (NEEDS), 459
Needs Hierarchy, 66
Negative scenarios, 98, 119, 135–137
applicability, 119
features, 120
strengths, 120
technique, 120
weaknesses, 120
Non-Functional Requirements (NFR), 124, 240, 468
nonfunctional requirements, user, 306
Normal course, 105, 164, 166, 169, 173, 293, 364, 370
O
Object-Oriented Analysis and Design (OOAD), 213, 237, 246
On-Line Partner Lens (OPaL), 224, 225, 229
OPaL. See On-Line Partner Lens
P
Path, 4, 13, 16, 49, 62, 148, 249, 281, 287
People, Activities, Contexts, Technologies (PACT), 215
Personal Digital Assistants (PDAs), 163, 167
Principles of composition, 219
Process models project structure, 320, 323
Product, 65
Product Use Cases, 40
Project, 18, 299, 329, 435, 437, 438, 441, 442
Project life cycle
applicability, 299
criticisms, 301
features, 300
strengths, 300
technique, 300
weaknesses, 300
Prototype, 11, 12, 29, 83, 202, 222
Q
Quality models, 383
R
Rapid Application Development (RAD), 63
Rational Unified Process (RUP), 31, 180, 237
Real time, 394
Reliability, Availability, Maintainability and Safety (RAMS), 132
Requirement elicitation, 371, 373, 393
Requirement stability, 103
assessment, 106
review, 108
Requirement validation, 373
Requirements, 39–41, 51, 52, 54, 107, 123, 239, 240
doneness testing, 92
iteration, 92
models, 83
operational, 401
using scenarios, 228
worked example, 93
workshop 2, 97
workshop pre-work, 94
Requirements analysis, 447
Requirements assessment
comparisons, 115
propagation, 113
worked example, 110
Requirements discovery, 39–59, 173, 176, 347, 348
applicability, 39
features, 40
strengths, 40
weaknesses, 41
See also Eliciting requirements
Requirements documentation, 337, 339, 341, 344
Requirements Engineering (RE), 411, 415
framework, 415
Requirements negotiation, 334
Requirements workshops, 81–100
applicability, 81
comparisons, 99
disadvantages, 82
features, 82
framework, 86
ground rules, 86
iteration process, 83
location, 88
participants, 86
principles, 86
process, 88
products, 88
purpose, 86
retrospective, 97
strengths, 83
tailoring, 100
technique, 85
unhappy scenarios, 99
weaknesses, 84
RESCUE, 366
Restow Thrust Reverser, 132
Rich context diagrams, 398
Role, 14
RUP. See Rational Unified Process
S
Satisfaction Argument (SA), 394, 395, 398, 399
Scenario content guidelines, 147
Scenario generator, 168
Scenario modelling, 465
Scenario process models, 57
advantages, 57
disadvantages, 58
Scenario simulation
applicability, 412
case study, 413
strengths, 412
weaknesses, 412
Scenario steps, 14, 47, 52, 56, 288
Scenario style guidelines, 147
Scenario techniques, 432, 433, 434, 443
Scenario types
domain-specific, 467
Scenario walkthroughs, 89, 363–366, 370, 373, 375, 376
Scenario workshops, 81–100, 163
Scenario-Based Design (SBD), 446
applicability, 211
features, 212
key activities, 224
strengths, 213
weaknesses, 213
Scenario-Based User Needs Analysis (SUNA), 61
Scenarios, 3–21, 25–32, 39–59, 61–79, 351–353, 363–376
activity scenarios, 448
after-braking, 344
allusory, 467
building techniques, 55
business event, 42
business systems and processes, 20
case studies, 349, 355, 381, 408, 413, 439, 450
claim, 452
content guidelines, 151
context facet, 31
description, 226
detailed design, 448
domain-specific, 373
effectiveness, 465
episodic, 467
examples, 73, 93, 110, 128, 155, 173, 186, 224, 239, 275, 290, 387
flow of interactions, 151
flows of actions content, 153
fragmentary models, 466
getting started, 443
goal content, 154
how scenarios were used, 401
information scenarios, 448
initial and final states, 154
initial states style, 150
interaction, 448
contents, 152
interaction styles, 149
knowledge, 468
lessons learnt, 408
level of context, 154
meaning, 6
modernist view, 16
normal case, 43
playthroughs, 58
practice, 431
presenter component, 168, 169, 171
problem scenarios, 447
process models, 57
requirements workshops, 86
sequence, 12
short example, 155
sketch, 47
structure, 14
terminology style, 150
the future, 471
traditionalist view, 17
validation, 69
workshop environment, 173
writing, 68
writing informal sketch, 46
See also User stories, Conceptual, Concrete, Use case scenarios
Scenarios for Acquiring and Validating Requirements (SAVRE), 363
Scenarios in Air Traffic Control
applicability, 363
Scenarios in Rail
applicability, 393
case study, 396
end-to-end conditions, 401
features, 394
goal, 402
specifications, 404
strengths, 394
weaknesses, 395
Scene, 41
Schedule of Manoeuvre, 19
Scripted sequence diagram, 247
Separation of concerns, 394
Service, 65
Service points, 420
Short-Term Conflict Alert (STCA), 134
Software architecture, 382, 385, 386
Software Engineering Institute (SEI), 384
Spike, 277
communication with, 15, 169, 172
conflicting viewpoints, 119, 360, 369, 374, 375, 481
viewpoints (conflicting) See also Conflicting viewpoints
cultural background, 467
mental models, 425
onion model, 7
reading scenarios, 431
requests, 240
requirements, 161, 162, 171, 284
technical, 237
validating assumptions and requirements of, 412
See also Scenario walkthroughs
workshops, 425
See also Scenario workshops
writing scenarios, 431
See also User needs
Story/Stories, 3, 4, 8, 9, 41, 271, 329–345, 436
automotive software development, 334
collaborative, 272
composite, 272
conversation, 270
driving system development (story driven), 433
design decisions, 344
discrete, 271
fuzzy, 273
graphics, in pictures, figures, diagrams, 20
in agile software development, 265–278
in work redesign, 181, 189, 190
lessons learnt, 342
level (high, detaied), 192
narration, 5, 8, 62, 65, 338, 341
Native American storytelling, 270
requirements analysis, 336
requirements discovery, negotiation and communication, 334
side effects, consequences, 345
skill of storytelling, 268, 271, 273
storyboard cell, 194, 196, 200, 202
See also User stories; Storytelling
Storyboard, 12, 56, 89, 194, 195, 200, 204
wall modeling, 89
Sub-System Requirements Documents (SSRD), 398
Subject Matter Experts (SMEs), 82
Synchronisation Matrix, 19
System Design/Architecture (SD/A), 306
System development
process, 472
V-model, 283
System requirements, 64
System Requirements Definition (SRD), 306
System specification, 333, 381, 393, 394, 401
Systematic scenario walkthroughs, 161–177
See also Scenario walkthroughs
Systems, 7, 20, 65, 240, 438, 441
combining models, 315
meta-process, 316
Systems Engineering, 301–304, 313, 316
‘in the large’ process models, 307
evolutionary model, 308
high-risk model, 310
incremental model, 309
‘in the small’ process models, 304
acceptance and certification, 307
detailed design, 307
implementation, 307
preliminary design, 307
system design/architecture, 306
test and integration, 307
user requirements definition, 305
Systems Integration for Major Projects (SIMP), 163
T
Tailoring, 316
Task-artifact cycle, 447
Teaching scenarios
strengths and weaknesses, 458
Telematics development, 335
Templates, 81, 89, 90, 153, 173, 352
Use Case, 147
Test Case Class, 289
generation, 294
identification, 292
applicability, 281
environmental conditions, 295
features, 282
generating acceptance, 126
prioritising, 287
strengths, 282
technique, 284
tool support, 288
weaknesses, 282
worked example, 290
Test Scenario, 281, 282, 290, 294
Test script, 13
Test step, 294
Threat, 126
Trade-off and Conflict Analyses, 126
Train Control Unit (TCU), 347, 349
U
Undergraduate education, 446, 448
Unhappy case scenarios, 98
Unified Modeling Language (UML). See UML
Usability engineering, 445–447, 449, 450, 452, 456
Use and Misuse Cases
railway systems, 347
Use Case Authoring, 148
applicability, 141
comparisons, 158
features, 142
strengths, 143
technique, 143
weaknesses, 143
Use Case Workshop, 89
Use Cases, 15, 16, 72, 141, 146, 166, 204, 211, 224, 229, 237–262, 281–297, 343, 347–353, 364–366, 368, 373, 436, 437, 441, 442
alternative cases, 49
analysis and design, 246
application, 244
content guidelines, 151
design, 256
diagrams, 242
documentation, 246
enforce password regime, 123
exception cases, 50
general guidelines, 148
generation, 204
goals and requirements, 239
interactions, 247
object-oriented analysis, 246
object-oriented design, 256
planning and management, 244
requirements validation, 373
role playing, 88
scope event, 44
software architecture, 256
specification component, 167
specifications, 243
system boundaries, 240
technique, 284
technique and worked example, 239
test cases, 281
usability engineering, 449
wall modeling, 89
worked example, 290
Use Cases in Railway Systems, 347
applicability, 348
approach, 350
case study, 349
lessons learnt, 352
strengths, 348
weaknesses, 348
Use Cases scenarios, 218
Use of scenarios
film-making, 20
military operations, 19
User, 305
User data transfer, 384
User Environment Design (UED), 199
User Interface (UI), 248
User needs, 69
extraction, 69
hierarchy, 70
mapping technologies, 69
User stories, 211, 223, 225, 265–278, 297
characteristics and typography, 271
communication, 275
comparisons, 278
confirming, 274
features, 267
ordering and completing, 273
scenarios, 214
splitting, 273
strengths, 268
technique, 269
users, 269
weaknesses, 268
worked example, 275
User-Experience (UX), 248
Using scenarios
challenges, 445
Value Attribution Process (VAP), 77
Venue operations system, 413
concepts, 415
Verification, 13, 54, 136, 254, 270, 283, 350, 490
Vignettes, 68
Vision document, 240
Visioning, 192
W
Walkthroughs, 92, 169, 171, 172
Work models, 188
artifact model, 189
cultural model, 188
flow model, 188
physical model, 188
sequence model, 188
See also Requirements workshops; Scenario workshops
X
XP. See Extreme Programming
XPVM, 275