UML Weekend Crash Course™ - To Parent Directory

Index 349
encapsulation
association class information, 110–111
implementation, 31–33
interface, 30–31, 32–33
end point, 154, 322
engineering, round-trip, 311–312, 328
entry actions, 217–219, 325
evaluating
criteria for modeling tools, 308–313
modeling tools, 313–314
users, 65–66
event
action, associating, 205
defined, 203
identifying, 206, 210
multiple changing object to same state, 217–219
order of, Statechart diagram, 220
transition, 227–231, 323
executable, resources referenced, 256, 258, 266
exit actions, 219, 325
dependency, 57–58, 66–67, 319
eXtensible Markup Language. See XML
Extension Mechanisms package, 8
Extreme Programming Explained,
Embrace Change, 20–21
features, defining, 54–55
features needed to perform jobs. See relationships
, 256
Fill Order case study
flowchart and scenarios, 194
Sequence diagram, 179–185
Use Case diagram, 74–78
Use Case scenarios, 84–90
finding
interface, 185
Use Case scenarios, 83–90
flowchart
activities notation, 151
benefits of using, 83, 327
concurrency, 154–155
decisions, 152–153
described, 24–25, 318
end point, 154
Fill Order case study, 85
inventory control system case study,
applying, 157–164
merge point, 153
methods, defining, 150
start point, 154
transitions notation, 151–152
Use Cases, modeling, 149–150
folder icon. See package
fork bar, 323
forward engineering, 311–312, 328
Foundation package, 8
Friendly Reminder case study
appointment XML (eXtensible Markup
Language), 303–305
MVC (Model View Controller) design
pattern, 294–295
Web development, 287–288
Functional view
Activity diagram, 149–155
described, 24–25
generalization
described, 121–122
elements, 122–124
illustrated how-to, 124–126
relationships, 58
Use Cases, evaluating, 53, 67
goals, defining, 54–55
guard condition
Activity diagram, 151–152, 160
notation, 322
transition events (Statechart), 230–231, 323
guidelines, 317
guillemets (>), 8–9, 56
handheld devices, 289, 294–295
hardware
architecture, modeling, 263–264, 327
concurrency, allowing, 154–155
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
hierarchies
drawing, 124–126
expressing, 111
HTML (HyperText Markup Language)
Class diagram, 302
described, 278, 328
dynamic pages, 284
Java servlet, generating, 282
Continued