340 Index
control flow structure, 88
coordination structure, 87
data elements, 115
data flow structure, 88
description, 111
description languages, 112, 128
descriptive model, 85, 101
diagrams, 54
execution view, 88, 89, 101
logical structure, 87
module structure, 87
module view, 88–89, 101
multiple view models, 86
passive elements, 112
physical structure, 87
prescriptive model, 84, 101
process structure, 87
relationships, 114
uses structure, 87
Software Architecture Analysis Method
(SAAM), 249
Software Architecture Visual Notation, 112
software production lines, 36
solution space, 21, 25, 36, 199
Soni, D., 85, 88, 101
spiral model, 56, 57
sporadic events, 236
SSA/SD, 64
SSADM, 59, 64, 68
stakeholder, 18–19, 34–35, 85, 90, 102, 111, 226,
279, 291
auditors, 34
customers, 34
designers, 34
developers, 30, 34
programmers, 34
project managers, 34
requirements analysts, 34
software architect, 34
support technicians, 34
system administrator, 34
testers, 34
users, 19, 30, 34, 194, 196
state chart, 53
state retention, 207, 222
state space, 48, 49
state transition diagrams, 53, 328
static connection, 211, 213, 223
static features, 205, 210, 222, 223
stepwise refinement, 59
symbolic representation, 19, 37
symmetry, 38, 74, 182
synchronicity, 150, 167,, 217, 218
synchronisation, 34, 57, 87, 89, 139, 142, 174
syntactic shell, 162
syntax analysis, 144
synthesis, 199, 203, 204, 221, 222
system load, 235
system’s functionality
amendment, 229
enhancement, 229
ways of delivery, 229
temporal relationships, 206, 221
testability, 29, 35, 42, 43
text capitalisation, 196
text wrapping, 195
thread of control, 152, 180, 205–208
throughput, 141, 235, 284
time to market, 40, 42
Tomasi, C., 93
topological structure, 61, 86, 99, 105, 135, 145,
152, 155, 203, 216, 284
Torunoglu, I., 93
trade-off, 32, 192, 277, 286–293, 304, 318, 319,
327, 328
transaction streams, 86
transformation, 66, 140, 141, 175
trial-and-error, 61, 62
UML, 64
uncertainty, 20, 21, 25
UniCon, 128
usability, 29, 37, 42, 43, 302–304, 310, 314–319,
327, 328
usage, 35, 36, 74, 86, 89, 190, 191, 226, 236
utility tree, 284–286, 291, 292, 295
V model, 55, 57
van Vlient, H. , 122, 245, 274
virtual control address space, 212
virtual data address space, 212
visibility, 53, 112, 153
visual notation, 53, 105, 111, 112–128, 138, 140
visualisation, 50, 53, 66
von Neumann architecture, 77, 78, 80
Wasserman, A. I., 36
waterfall model, 55
WBM axioms, 51–52, 67
Weiss, D. M., 39, 42, 50
what-if question, 306
wicked problem, 22, 25
Willem, R. A., 19, 20, 333
Witt, B., 38, 39, 42, 51, 53, 66
Wolf, A. L., 76, 84, 85, 101, 103
Woods, S., 245
Wright, 128
WWW client-server, 83, 117, 118, 316, 320
Yoshikawa, H., 203, 221, 222
Get Software Design Methodology now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
