UML Weekend Crash Course™ - To Parent Directory

Index 347
code
diagrams, updating, 311
maintenance, 328
pre-conditions, 70
code generation
aggregation, 117–121
associations, 105–112
attributes, modeling, 95–98
building, 130–133
compartments, modeling, 100–102
described, 25–26, 93–95, 318
elements, 95
generalization, 121–126
inventory control system case study,
applying, 129–137
modeling tools, 310
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
XP (extreme programming), 20–21
code marker, 310
collaboration, 135
Collaboration diagram
described, 27, 187, 318
inventory control system case study,
applying, 193–201
notation, 189–191
Object diagram versus, 323
Sequence diagram versus, 188–189
Web pages, moving among, 300, 301
commas (,), 108
comments
Collaboration diagram, 191, 199
icon, 9
Sequence diagram, 184
Common Gateway Interface. See CGI scripts
communication
association between nodes, 326–327
inter-object (send event), Statechart
diagram, 219–220
compartments, 100–102
component, 256
Component diagram
described, 255–256, 318
for inventory control system case study, 258–260
logical design, mapping to physical implementation,
260–261
Model 2 Architecture, 298, 328
notation, 256–258
composite state
concurrency, 233–234
defined, 231
composition
aggregation and, 117–118, 321
and aggregation relationships, 120–121
elements, 119–120
computers, diagramming
described, 263–264, 327
dynamic Web content, 281
inventory control system case study,
applying, 266–271
Model 2 Architecture, 299
notation, 264–266
software components, mapping to architecture, 266
static Web page, 279
Visual Basic client, 300
Conallen, Jim, 305
concrete class, 123
concurrency
Activity diagram, 154–155, 163–164
multiple Statecharts, 233–234
conditional (guard condition), 230
conditions
delegate to another Use Case (
dependency notation), 57–58
message, 184
constraint
associations (Class Diagram), 109–110
attributes, 97
defined, 9, 320
inventory control system case study
requirements, 38, 41
notation ({ }), 101
contacts
querying, 300–301
uploading, 299–300
contents, CD-ROM, back-of-the-book, 330–331
context
state design pattern, 136
target system, 62
contract, 38
CORBA standard, 6
Core package, 8
coupling, 71
CRC (Class, Responsibilities, and Collaborators),
18–19, 318
customers
events and activities, defining, 210
performance, changing status, 208–209
customization, modeling tools, 312, 328