UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Index Symbols and Numerics * (asterisk), 108 { } (braces), 9, 101, 110 , (commas), 108 > (guillemets), 8–9, 56 - (minus sign), 96 # (number sign), 96 . (period), 108 + (plus sign), 96 / (slash), 96 [ ] (square condition brackets), 171, 184, 322 ~ (tilde), 96 abstract class, 123 abstract data type, 96, 100 abstraction, 28–29 stereotype, 248, 251–252, 253 action, 205 Action Semantics, 17 action state, 151 activation, 171–172, 183, 323 activities, internal, 210 Activity diagram 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 guard condition, 151–152 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 actor, 52 aggregation composition and, 117–118 elements, 118–119 relationships, 120–121 analysis constraints, 38 performance, 39 rules, 39 Web development, 290–291 appointments querying, 300–301 uploading, 299–300 XML (eXtensible Markup Language), 303–305 archive, 206 argument, 98–99 arrows. See also transition dashed dependency, 247 message, 170, 173 returns, 323 Statechart diagram, 204–209 artifact, 14 assignment operator, 96 association connections, 326 Deployment diagram, 263–264 described, 52, 94 Use Case relationships, 56 users, defining, 64–65
346 Index association class constraints, 109–110 described, 105 information, encapsulating (association class), 110–111 name, 106–107 number of participating objects (multiplicity), 107–108 objects in same class, relations (reflexive association), 111 qualified, 111–112 roles, 109 assumptions pitfalls of making, 43, 318 Use Case narrative, 70, 75 asterisk (*), 108 asynchronous event or action, 172, 173, 198 asynchronous message, 191–192 attribute class compartments, modeling, 101 defined, 94, 95 specification, 97–98 subclasses, identifying, 123 visibility, 96–97 XML (eXtensible Markup Language) document, 304 Auxiliary elements package, 8 availability, 288 Beck, Kent (Extreme Programming Explained, Embrace Change), 20–21 , 257, 266 behavior, 30 Behavioral Elements package, 8 Booch, Grady, 6, 317 braces ({ }), 9, 101, 110 BridgePoint, 16 bull’s-eye, 154 call Object diagram, modeling, 187, 190 synchronous, 197 time, modeling over, 170, 172 call event, 228–229 cancel events, 77 card, CRC (Class, Responsibilities, and Collaborators), 18–19, 318 CD-ROM, back-of-the-book contents, 330–331 system requirements, 329 troubleshooting, 331–332 Windows, using with, 329–330 cellular telephones, 289, 294–295 CGI (Common Gateway Interface) scripts, 281 changing customer performance status, 208–209 multiple objects to same state, 217–219 transition events, testing in Statechart, 229–230 class association, 106 attribute, 97 CRC (Class, Responsibilities, and Collaborators) method, 18–19, 318 generalization relationship, 122 objects in same class, relations (reflexive association), 111 class compartments, modeling attribute, 101 described, 100–101 name, 101 operation, 102 class definition described, 121–122 elements, 122–124 illustrated how-to, 124–126 relationships, 58 Use Cases, evaluating, 53, 67 Class diagram 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 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 class operation, 142 classification, 142 classifiers, 56 client assumptions, fair, 319 XP (extreme programming), 20–21
- Page 318 and 319: Session 28—Analysis and Architect
- Page 320 and 321: SESSION 29 Design of a Web Applicat
- Page 322 and 323: Session 29—Design of a Web Applic
- Page 324 and 325: Session 29—Design of a Web Applic
- Page 326 and 327: Session 29—Design of a Web Applic
- Page 328 and 329: Session 29—Design of a Web Applic
- Page 330 and 331: SESSION 30 UML Modeling Tools Sessi
- Page 332 and 333: Session 30—UML Modeling Tools 309
- Page 334 and 335: Session 30—UML Modeling Tools 311
- Page 336 and 337: Session 30—UML Modeling Tools 313
- Page 338 and 339: PART VI # Sunday Afternoon Part Rev
- Page 340 and 341: APPENDIX A Answers to Part Reviews
- Page 342 and 343: Answers to Part Reviews 319 20. I a
- Page 344 and 345: Answers to Part Reviews 321 26. It
- Page 346 and 347: Answers to Part Reviews 323 22. Dra
- Page 348 and 349: Answers to Part Reviews 325 Sunday
- Page 350 and 351: Answers to Part Reviews 327 It maps
- Page 352 and 353: APPENDIX B What’s on the CD-ROM T
- Page 354 and 355: What’s on the CD-ROM 331 Trial So
- Page 356 and 357: Glossary abstract class A class th
- Page 358 and 359: Glossary 335 automatic transition A
- Page 360 and 361: Glossary 337 decomposition Separati
- Page 362 and 363: Glossary 339 link A relationship b
- Page 364 and 365: Glossary 341 overloading Used to de
- Page 366 and 367: Glossary 343 specialization The ide
- Page 370 and 371: Index 347 code diagrams, updating,
- Page 372 and 373: Index 349 encapsulation association
- Page 374 and 375: Index 351 languages, programming d
- Page 376 and 377: Index 353 namespace, 246 notation,
- Page 378 and 379: Index 355 source code notation, 256
- Page 380 and 381: Index 357 resources, 50, 51-52 Use
- Page 382 and 383: Wiley Publishing, Inc. End-User Lic
346<br />
Index<br />
association class<br />
constraints, 109–110<br />
described, 105<br />
information, encapsulating (association<br />
class), 110–111<br />
name, 106–107<br />
number of participating objects<br />
(multiplicity), 107–108<br />
objects in same class, relations (reflexive<br />
association), 111<br />
qualified, 111–112<br />
roles, 109<br />
assumptions<br />
pitfalls of making, 43, 318<br />
Use Case narrative, 70, 75<br />
asterisk (*), 108<br />
asynchronous event or action, 172, 173, 198<br />
asynchronous message, 191–192<br />
attribute<br />
class compartments, modeling, 101<br />
defined, 94, 95<br />
specification, 97–98<br />
subclasses, identifying, 123<br />
visibility, 96–97<br />
XML (eXtensible Markup Language) document, 304<br />
Auxiliary elements package, 8<br />
availability, 288<br />
<br />
Beck, Kent (Extreme Programming Explained,<br />
Embrace Change), 20–21<br />
, 257, 266<br />
behavior, 30<br />
Behavioral Elements package, 8<br />
Booch, Grady, 6, 317<br />
braces ({ }), 9, 101, 110<br />
BridgePoint, 16<br />
bull’s-eye, 154<br />
<br />
call<br />
Object diagram, modeling, 187, 190<br />
synchronous, 197<br />
time, modeling over, 170, 172<br />
call event, 228–229<br />
cancel events, 77<br />
card, CRC (Class, Responsibilities, and<br />
Collaborators), 18–19, 318<br />
CD-ROM, back-of-the-book<br />
contents, 330–331<br />
system requirements, 329<br />
troubleshooting, 331–332<br />
Windows, using with, 329–330<br />
cellular telephones, 289, 294–295<br />
CGI (Common Gateway Interface) scripts, 281<br />
changing<br />
customer performance status, 208–209<br />
multiple objects to same state, 217–219<br />
transition events, testing in Statechart, 229–230<br />
class<br />
association, 106<br />
attribute, 97<br />
CRC (Class, Responsibilities, and Collaborators)<br />
method, 18–19, 318<br />
generalization relationship, 122<br />
objects in same class, relations<br />
(reflexive association), 111<br />
class compartments, modeling<br />
attribute, 101<br />
described, 100–101<br />
name, 101<br />
operation, 102<br />
class definition<br />
described, 121–122<br />
elements, 122–124<br />
illustrated how-to, 124–126<br />
relationships, 58<br />
Use Cases, evaluating, 53, 67<br />
Class diagram<br />
aggregation, 117–121<br />
associations, 105–112<br />
attributes, modeling, 95–98<br />
building, 130–133<br />
compartments, modeling, 100–102<br />
described, 25–26, 93–95, 318<br />
elements, 95<br />
generalization, 121–126<br />
inventory control system case study,<br />
applying, 129–137<br />
operation, modeling, 98–100<br />
patterns, 133–137<br />
problem statement, 129–130<br />
round-trip engineering, 311–312<br />
Sequence and Collaboration diagram elements,<br />
mapping, 200–201<br />
views, creating different, 102<br />
Web development, 290–291, 302<br />
XML (eXtensible Markup Language) modeling, 303<br />
class operation, 142<br />
classification, 142<br />
classifiers, 56<br />
client<br />
assumptions, fair, 319<br />
XP (extreme programming), 20–21
Change language