UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Index 351 languages, programming dynamic Web pages, 281 modeling tools, 310 UML (Unified Modeling Language) independence, 317 Web applications, 278 library component, 259 , 256 lifeline, object, 323 link Collaboration diagram notation, 195 defined, 140, 322 requirement, showing, 189 self-reference, 190, 201, 324 link attribute logging in, 289 logical design, mapping, 260–261, 322–323 lollipop notation, 257, 259–260 look ups prompting, 182 scenario, 199 using attributes, 111–112, 131 loop Activity diagram, 160, 161, 323 Use Case scenarios, 90, 184 mapping interaction to objects in Sequence diagram, 168–169 logical design, mapping to physical implementation in Component diagram, 260–261 Sequence and Collaboration diagram elements to Class diagram, 200–201 software components to architecture in Deployment diagram, 266 merge of control, 204 merge point, 153, 322 message Object diagram, modeling, 187, 190 synchronous, 197 time, modeling over, 170, 172 metametamodel, 7 metamodel described, 6–7, 317 diagrams, 9 organization, 7–8 method, 150 methodology CRC (Class, Responsibilities, and Collaborators), 18–19 defined, 13 Object-Oriented Analysis and Design Task Force, 317 RUP (Rational Unified Process), 14–16 Shlaer-Mellor Method, 16–17 XP (Extreme Programming), 20–21 Meyer, Bertrand, 70 minus sign (-), 96 model, 7, 246 Model 2 Architecture, 297–299 model element, 249 Model Management package, 8 modeling tools code generation, 310 customization, 312 data modeling integration, 311–312 described, 307–308, 328 editor, integrated, 310 evaluating, 313–314 evaluation criteria, 308–313 HTML (HyperText Markup Language) documentation, 309 packages, 249 platform support, 309 printing, 309 repository, 310 round-trip engineering, 311–312 team development, 313 translating through Shlaer-Mellor Method, 16 trial software, back-of-the-book CD-ROM, 331 types and versions of UML (Unified Modeling Language) supported, 309 version control, 310–311 XMI (XML Metadata Interchange), 312–313 multiplicity aggregation, assigning, 118, 321 composition, 119 described, 107–108 limiting, 112 MVC (Model View Controller) design pattern described, 291–292, 327 Friendly Reminder case study, 294–295 Model 2 Architecture, 297–299 name action, 325 associations (Class Diagram), 106–107 attribute, 96 class compartments, modeling, 95, 101, 210, 320 nodes, 327 objects in Collaboration diagram, 190 operation, 98 package namespaces, 246 state, choosing, 240
352 Index node, 263, 264–265, 268, 326 notation Activity diagram, 151–155 Collaboration diagram, 189–191 defined, 317 Deployment diagram, 264–266 hiding, 320 Object diagram, 140–142 packages, 247–249 Statechart diagram, 204–206 notation, Component diagram dependencies, 257–258 interfaces, 257 stereotypes, 256 notation, package constructing for inventory control system case study, 250–253 dependency, 247–248 dependency stereotypes, 248 model elements, 249 pattern, 322 stereotypes, 247 notation, Sequence diagram basic, 169–171 extended, 171–173 number defaulting to zero, 96–97 events, Collaboration diagram, 324 objects, counting, 108 participating objects (multiplicity) in associations on Class Diagram, 107–108, 112 sequence, 171, 190 number sign (#), 96 object aggregation and, 117–118, 321 and aggregation relationships, 120–121 assemblies of, 117–121 defined, 28 elements, 119–120 mapping, Sequence diagram, 168–169 notation, 189–191 Object diagram versus, 323 in same class, relations (reflexive association), 111 Sequence diagram versus, 188–189 Statechart diagram, 221–224 viewing, 27, 187, 193–201, 318 Web pages, moving among, 300, 301 object activation, 171 object combinations aggregation, assigning, 118, 321 composition, 119 described, 107–108 limiting, 112 Object diagram applying to test case diagrams, 142–146 Collaboration diagram versus, 323 described, 25–26, 95, 139, 318 notations, comparing, 140–142 XML (eXtensible Markup Language) schema, 304 object interactions communicating with others (send event) on Statechart diagram, 219–220 connections, 326 Deployment diagram, 263–264 described, 52, 94 Use Case relationships, 56 users, defining, 64–65 object lifeline, 169–170, 171, 173 Object Management Group. See OMG Object Model Class diagram, 94–95 described, 93 Object diagram, 95 object termination, 171 Object-Oriented Analysis and Design Task Force, 6, 317 object-oriented information absence in Web applications, 278 abstraction, 28–29 behavior, 30 encapsulation, 30–33 information, 29 observer design pattern, 134 OMG (Object Management Group), 6, 10, 303, 317 operation behavior, declared, 322 defined, 94 operation, modeling Activity diagram, 150 class compartments, 95, 102 elements, 98–99 specification, creating, 99–100 order fulfillment inventory control system case study, 36 packaging, 252 order of events, Statechart diagram, 220 orders, customer placing Class Diagram, 129–137 problem statement, 35–36 overdrawn, 203–204 package described, 7–8, 245–246 inventory control system case study, 250–253
- 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 368 and 369: Index Symbols and Numerics * (aster
- Page 370 and 371: Index 347 code diagrams, updating,
- Page 372 and 373: Index 349 encapsulation association
- 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
Index 351<br />
<br />
languages, programming<br />
dynamic Web pages, 281<br />
modeling tools, 310<br />
<strong>UML</strong> (Unified Modeling Language)<br />
independence, 317<br />
Web applications, 278<br />
library component, 259<br />
, 256<br />
lifeline, object, 323<br />
link<br />
Collaboration diagram notation, 195<br />
defined, 140, 322<br />
requirement, showing, 189<br />
self-reference, 190, 201, 324<br />
link attribute<br />
logging in, 289<br />
logical design, mapping, 260–261, 322–323<br />
lollipop notation, 257, 259–260<br />
look ups<br />
prompting, 182<br />
scenario, 199<br />
using attributes, 111–112, 131<br />
loop<br />
Activity diagram, 160, 161, 323<br />
Use Case scenarios, 90, 184<br />
<br />
mapping<br />
interaction to objects in Sequence<br />
diagram, 168–169<br />
logical design, mapping to physical implementation<br />
in Component diagram, 260–261<br />
Sequence and Collaboration diagram elements<br />
to Class diagram, 200–201<br />
software components to architecture in Deployment<br />
diagram, 266<br />
merge of control, 204<br />
merge point, 153, 322<br />
message<br />
Object diagram, modeling, 187, 190<br />
synchronous, 197<br />
time, modeling over, 170, 172<br />
metametamodel, 7<br />
metamodel<br />
described, 6–7, 317<br />
diagrams, 9<br />
organization, 7–8<br />
method, 150<br />
methodology<br />
CRC (Class, Responsibilities, and Collaborators), 18–19<br />
defined, 13<br />
Object-Oriented Analysis and Design Task Force, 317<br />
RUP (Rational Unified Process), 14–16<br />
Shlaer-Mellor Method, 16–17<br />
XP (Extreme Programming), 20–21<br />
Meyer, Bertrand, 70<br />
minus sign (-), 96<br />
model, 7, 246<br />
Model 2 Architecture, 297–299<br />
model element, 249<br />
Model Management package, 8<br />
modeling tools<br />
code generation, 310<br />
customization, 312<br />
data modeling integration, 311–312<br />
described, 307–308, 328<br />
editor, integrated, 310<br />
evaluating, 313–314<br />
evaluation criteria, 308–313<br />
HTML (HyperText Markup Language)<br />
documentation, 309<br />
packages, 249<br />
platform support, 309<br />
printing, 309<br />
repository, 310<br />
round-trip engineering, 311–312<br />
team development, 313<br />
translating through Shlaer-Mellor Method, 16<br />
trial software, back-of-the-book CD-ROM, 331<br />
types and versions of <strong>UML</strong> (Unified Modeling<br />
Language) supported, 309<br />
version control, 310–311<br />
XMI (XML Metadata Interchange), 312–313<br />
multiplicity<br />
aggregation, assigning, 118, 321<br />
composition, 119<br />
described, 107–108<br />
limiting, 112<br />
MVC (Model View Controller) design pattern<br />
described, 291–292, 327<br />
Friendly Reminder case study, 294–295<br />
Model 2 Architecture, 297–299<br />
<br />
name<br />
action, 325<br />
associations (Class Diagram), 106–107<br />
attribute, 96<br />
class compartments, modeling, 95, 101, 210, 320<br />
nodes, 327<br />
objects in Collaboration diagram, 190<br />
operation, 98<br />
package namespaces, 246<br />
state, choosing, 240
Change language