UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Glossary 335 automatic transition A change in state triggered by the completion or termination of a state activity. See also transition and activity. balking event A message type in which the client can pass the message only if the supplier is immediately ready to accept the message. The client abandons the message if the supplier is not ready. base class A class that is further specified by subclasses. Also called a superclass or ancestor class. For more information see Session 11. See also superclass and subclass. bound element A class resulting from the specification of parameters in a template class. See also template class. class An abstraction of a set of related information, behaviors, and relationships that describes a type of entity. A definition used to create objects. For more information see Sessions 1 and 9. See also object. classification The process of finding common information, behaviors, and relationships among objects, in order to create a common definition for the objects. For more information see Session 9. See also class and object. class operation An operation that is specific to a class rather than to objects of the class. As such, it may be invoked without using an object of the class. For more information see Session 9. class variable An attribute that is specific to a class rather than to objects of the class. As such, it may be referenced within the class without using an object of the class. For more information see Session 9. client An object that initiates a request. collaboration An interaction between objects. The term is also used to describe a pattern, a standardized concept for configuring classes to fulfill a specific function. For more information see Session 12. See also pattern.
336 Glossary component A physical unit of software that may reside in memory on a processor and realizes (implements) a set of interfaces. For more information see Session 25. component view A UML presentation dedicated to the description of software implementation units (components); may be used in combination with the deployment view. For more information see Sessions 25 and 26. See also component and deployment view. composite state See superstate. composition A type of aggregation relationship in which the part object cannot exist separate from the whole object. The whole object is responsible for the creation and destruction of the part object. For more information see Session 11. concrete class A class that may be instantiated because a method (an implementation) has been specified for every operation that is inherited or owned by the class. See also abstract class. concurrency The simultaneous execution of multiple activities by executing multiple threads or multiple processes. For more information see Session 14. constraint The UML extension of the definition of a model element that allows you to impose restrictions on the use of the element (for example, edit rules on an attribute value or limits on the participation in an association). For more information see Sessions 9 and 10. context The set of model elements that defines the frame of reference for the interpretation and implementation of a particular model element. contract An agreement between classes regarding the handling of responsibilities and implementations in the class definitions. For more information see Session 7. coupling A measure of the degree of dependency between model elements. A quantitative assessment of the communication volume, number of relationships, and the complexity of the communication that define the relationship. For more information see the Supplements on the CD. See also dependency. data type The format of information allowed for an attribute (for example, integer, address, or character data). For more information see Session 9.
- Page 307 and 308: 284 Sunday Afternoon and time. A JS
- Page 310 and 311: SESSION 28 Analysis and Architectur
- Page 312 and 313: Session 28—Analysis and Architect
- 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 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 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
336<br />
Glossary<br />
component<br />
A physical unit of software that may reside in memory on a processor and realizes (implements)<br />
a set of interfaces. For more information see Session 25.<br />
component view<br />
A <strong>UML</strong> presentation dedicated to the description of software implementation units (components);<br />
may be used in combination with the deployment view. For more information see<br />
Sessions 25 and 26. See also component and deployment view.<br />
composite state<br />
See superstate.<br />
composition<br />
A type of aggregation relationship in which the part object cannot exist separate from the<br />
whole object. The whole object is responsible for the creation and destruction of the part<br />
object. For more information see Session 11.<br />
concrete class<br />
A class that may be instantiated because a method (an implementation) has been specified<br />
for every operation that is inherited or owned by the class. See also abstract class.<br />
concurrency<br />
The simultaneous execution of multiple activities by executing multiple threads or multiple<br />
processes. For more information see Session 14.<br />
constraint<br />
The <strong>UML</strong> extension of the definition of a model element that allows you to impose restrictions<br />
on the use of the element (for example, edit rules on an attribute value or limits on<br />
the participation in an association). For more information see Sessions 9 and 10.<br />
context<br />
The set of model elements that defines the frame of reference for the interpretation and<br />
implementation of a particular model element.<br />
contract<br />
An agreement between classes regarding the handling of responsibilities and implementations<br />
in the class definitions. For more information see Session 7.<br />
coupling<br />
A measure of the degree of dependency between model elements. A quantitative assessment<br />
of the communication volume, number of relationships, and the complexity of the communication<br />
that define the relationship. For more information see the Supplements on the CD.<br />
See also dependency.<br />
<br />
data type<br />
The format of information allowed for an attribute (for example, integer, address, or character<br />
data). For more information see Session 9.
Change language