UML Weekend Crash Course™ - To Parent Directory

Index 353
namespace, 246
notation, 247–249
visibility, 96, 99
parameter, 98
path. See also scenario
incomplete, revealing, 83
merge point, 153
pattern, 133–137, 322
people. See user
performance
customer, triggering events, 208
inventory control system case study
requirements, 39, 41
system requirements, 289
period (.), 108
phases, project lifecycle, 14–15
physical implementation, 260–261
platform support, modeling tools, 309
plus sign (+), 96
post-condition
Activity diagram, 160
Use Case narrative, 72–73, 77–78
pre-condition, 70–71, 75
primitive data type, 95
printing, 309
private, 96, 99
problem domain, 38
problem statement
Class Diagram, 129–130
inventory control system case study, 35–36
Statechart diagram, 206, 221
procedure call, 190, 324
process, 6, 9
processors, identifying. See Deployment diagram
product object, constructing, 221–224
profile, 9, 328
programmers
assumptions, making, 43
cooperation, XP (extreme programming), 19–21
MVC (Model View Controller) method,
advantages, 292
object-oriented methods, teaching, 18–19
portraying code to other, 137
roadmap, creating, 300
Web development, 283–284
“programming by contract”, 70
properties, shared. See superclass
property, 94, 101
protected, 96, 99, 122
prototypes, 82–83
public, 96, 99
purchase order
initial entry, 221–222
tracking, 222–223
purpose
object encapsulation, 32
Sequence diagram, 168
qualified associations, 111–112
qualifier, 56, 321
quality-assurance, 82
query, database
code, writing, 281–282, 292
interface, 294
Use Case diagram, 289–290
Web application design, 300–301
range, indicating, 108
Rational Software, 305
realization, 257
real-time systems, 16–17
receiving
Deployment diagram, 267
objects, 200
package diagram, 250–251
requirements, analyzing, 36
reflexive association, 111
relational database
accessing, 256, 268–269
integrating, 311–312
Java Web development, 293, 297
object, 310
relationships
aggregation and composition, 120–121
association notation, 56
conditionally delegating to another Use Case
( dependency notation), 57–58
defined, 55–56
delegating to another Use Case (
dependency notation), 56–57
generalization, 58
objects in same class (reflexive association), 111
purpose, displaying, 321
stereotype notation, 56
Use Case diagram, 55–58
relationships, software modules
aggregation, 117–121
associations, 105–112
attributes, modeling, 95–98
building, 130–133
compartments, modeling, 100–102
described, 25–26, 93–95, 255–256, 318
Continued