UML Weekend Crash Course™ - To Parent Directory

Index 355
source code notation, 256
specialization, 121, 124–126, 321
specification
attribute, 97–98
operation, 99–100
split of control, 232–233
square condition brackets ([ ]), 171, 184, 322
start point
Activity diagram, 154, 322
Use Case narrative, 71, 75
state
assumptions, 70
defined, 29, 324
at end, 72–73, 77–78
modeling, 16–17
object, describing, 325
pre-conditions, 70–71
specific behavior, modeling, 135–137
Statechart diagram
building, 206–209
deriving from sequence diagrams, 237–243
described, 27, 203–204, 327
entry and exit actions, 217–219
fundamental notation, 204–206
improvements planned, 17
internal events and activities, defining, 210
inventory control system case study, applying,
217–224, 237–243
objects communicating with others (send event),
219–220
order of events, 220
problem statement, 221
product object, constructing, 221–224
superstates and substates, modeling, 231–234
transition events, modeling, 227–231
static content, Web, 278–280
Static view
Class diagram, 93–103
Component diagram, 255–261
Deployment diagram, 263–271
described, 25–26, 318
Object diagram, 139–146
step-by-step description (dialog), 71–72, 76
stereotype
dependency notation, 248, 319
Deployment diagram, 266
described, 8–9, 94, 317
notation, component diagram, 256
package, 326
relationships among Use Cases, 56
timed event, 172
stocking requirement, 36
subclass
defined, 123
protected visibility, 122
substate
concurrency in, 233–234
defined, 232, 325
split of control, 232–233
subsystem, package, 246, 326
Sun Microsystems, 297
superclass, 122
superstate
concurrency, 233–234
defined, 231
supplements, back-of-the-book CD-ROM, 330
synchronous event, 190, 197, 323, 324
system
behavior, describing, 24–25, 149–155
Class diagram, 93–103
Component diagram, 255–261
Deployment diagram, 263–271
described, 25–26, 318
icon, Use Case diagram, 53
Object diagram, 139–146
requirements for back-of-the-book CD-ROM, 329
trading information (users), 53–54, 320
Use Case diagram, 52, 53
System Architect (Popkin Software), 331
, 256
tagged value, 9
target system, 62
team development
design patterns, 137
modeling tools, 313, 328
XP (extreme programming), 20–21
template
HTML (HyperText Markup Language), 283
JSPs (Java Server Pages), 283–284
termination
Activity diagram, 160
Sequence diagram, 171–172
Use Case narrative, 72, 77, 320
testing
Class diagrams, 142–146
software, 82
transition events for change, 229–230
thermostat example
concurrency, 233–234
split of control, 232–233
substates, 232