UML Weekend Crash Course™ - To Parent Directory

354
Index
relationships, software modules (continued)
elements, 95
generalization, 121–126
for inventory control system case study,
129–137, 258–260
logical design, mapping to physical implementation,
260–261
Model 2 Architecture, 298, 328
notation, 256–258
operation, modeling, 98–100
patterns, 133–137
problem statement, 129–130
round-trip engineering, 311–312
Sequence and Collaboration diagram elements,
mapping, 200–201
views, creating different, 102
Web development, 290–291, 302
XML (eXtensible Markup Language) modeling, 303
reliability, 288
repository, modeling tools, 310
requirements
categories, 318
features, defining (Use Cases), 54–55
inventory control system case study, gathering,
36–39, 40–42
link, showing, 189
misunderstandings, avoiding, 82
preferences, confusing, 43, 318
Web development, gathering, 288–291
resources. See also Class diagram
inventory control system case study
requirements, 41–42
referenced by executable during runtime, 256
Use Case model, 50, 51–52
response
Object diagram, modeling, 187, 190
synchronous, 197
time, modeling over, 170, 172
returns, 223, 242, 323
reverse engineering, 311–312, 328
review process, speeding, 137
role
associations (Class Diagram), 109
behavior, defining, 322
names, when to use, 321
Use Case system, 54
rule. See also aggregation; composition
attributes, 97
constraint, 9, 320
defined, 317
inventory control system case study requirements,
38–39, 41
Rumbaugh, James, 6, 317
RUP (Rational Unified Process), 14–16, 318
saving orders, 78
scalability, 289
scenario
defined, 81, 320
execution, CRC, 18–19
Sequence diagram, building, 179–185, 326
XP (extreme programming), 20–21
screen flow, displaying, 73
security
checking, Fill Order case study, 75
requirements, 289
self-assessment test, back-of-the-book CD-ROM, 331
self-reference, 190, 201, 324
send event
defining (Statechart), 219–220
transition events (Statechart), 231
Sequence diagram
appointments, querying, 301
basic notation, defining, 169–171
Collaboration diagram versus, 188–189, 327
described, 27, 325
extended notation, defining, 171–173
HTTP (HyperText Transfer Protocol), 280
interactions, mapping to objects, 168–169
inventory control system case study,
applying, 179–185
Model 2 Architecture, 298
purpose, 168, 324
Statechart, deriving, 237–243
server. See Deployment diagram
shareware programs, 331
shipping
inventory control system case study, 36, 242
pack for event, 223
package diagram, 250, 253
Shlaer-Mellor Method, 16–17, 318
signal, 170
signature, 98, 102, 323
slash (/), 96
software
components, mapping to architecture (Deployment
diagram), 266
design patterns, 133–137
litigation of misunderstood requirements, 82
trial, 331
software modules
for inventory control system case study, 258–260
logical design, mapping to physical implementation,
260–261
Model 2 Architecture, 298, 328
modeling, described, 255–256, 318
notation, 256–258