UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Glossary 341 overloading Used to describe operations within a class where an operation name is shared but the arguments vary in number and/or type. Contrast this with polymorphism. package A general-purpose mechanism for grouping models and model elements, typically by similar functions or uses within the context of a system. For more information see Session 24. pattern A common solution to a common problem, describing a set of cooperating classes, the rules for their interactions, and consequences of using the pattern. For more information see Session 12. polymorphism Operations where the operation signature is the same but the implementation (method) is different. See also overloading. post-condition A statement that must test true at the completion of the responsible task or Use Case. For more information see Session 7. See also pre-condition. pre-condition A statement that must test true before execution of the responsible task or Use Case. For more information see Session 7. See also post-condition. primitive data type The smallest unit of data definition provided by the implementation environment (for example, integer, float, or char). For more information see Session 9. See also abstract data type. private A form of visibility constraint that prevents access to a model element from outside of the owning class. For more information see Session 9. See also public. process A “heavyweight” flow of control that can execute concurrently with other processes. property A named value describing a characteristic of an element. protected A type of model element visibility that allows only subclasses to have access to the protected model element (for example, an operation or attribute). In some languages, like Java, protected may also allow access from within the same package. For more information see Session 9. public A form of visibility constraint that allows access to a model element by any object outside the owning class. For more information see Session 9. See also private.
342 Glossary qualifier A modeling element, used on associations, that identifies an attribute or attributes used to navigate an association. Synonymous in function with keys or indexes in a database or the data modeling domain. For more information see Session 10. realization When a class implements an interface specified by another class (or interface class as in Java). reflexive association An association that relates objects within the same class to one another. For more information see Session 10. See also association. reverse engineering The process of translating code into modeling elements. This typically results in a Class diagram. But new tools are providing Sequence and Statechart diagrams as well. For more information see Session 30. role Describes how an object participates in an association. For more information see Session 10. scenario A single logical path through a Use Case, often used as a test case. For more information see Session 8. See also Use Case view. send event A message or signal sent to another object from within a Statechart diagram. For more information see Session 22. server An object that acts only as a respondent in an interaction. Note that the same object may act as a client in another interaction. signal An asynchronous stimulus sent from one object to another. signature Synonym for operation and described as the name, the number, type, and order of arguments, and sometimes the return data type (implementation languages vary on their interpretation). For more information see Session 9. See also polymorphism, overloading, and interface.
- Page 314 and 315: Session 28—Analysis and Architect
- Page 316 and 317: Session 28—Analysis and Architect
- 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 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 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
342<br />
Glossary<br />
<br />
qualifier<br />
A modeling element, used on associations, that identifies an attribute or attributes used to<br />
navigate an association. Synonymous in function with keys or indexes in a database or the<br />
data modeling domain. For more information see Session 10.<br />
<br />
realization<br />
When a class implements an interface specified by another class (or interface class as in<br />
Java).<br />
reflexive association<br />
An association that relates objects within the same class to one another. For more information<br />
see Session 10. See also association.<br />
reverse engineering<br />
The process of translating code into modeling elements. This typically results in a Class<br />
diagram. But new tools are providing Sequence and Statechart diagrams as well. For more<br />
information see Session 30.<br />
role<br />
Describes how an object participates in an association. For more information see Session 10.<br />
<br />
scenario<br />
A single logical path through a Use Case, often used as a test case. For more information see<br />
Session 8. See also Use Case view.<br />
send event<br />
A message or signal sent to another object from within a Statechart diagram. For more<br />
information see Session 22.<br />
server<br />
An object that acts only as a respondent in an interaction. Note that the same object may<br />
act as a client in another interaction.<br />
signal<br />
An asynchronous stimulus sent from one object to another.<br />
signature<br />
Synonym for operation and described as the name, the number, type, and order of arguments,<br />
and sometimes the return data type (implementation languages vary on their interpretation).<br />
For more information see Session 9. See also polymorphism, overloading, and<br />
interface.
Change language