01.01.2015 Views

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Glossary 335<br />

automatic transition<br />

A change in state triggered by the completion or termination of a state activity. See also<br />

transition and activity.<br />

<br />

balking event<br />

A message type in which the client can pass the message only if the supplier is immediately<br />

ready to accept the message. The client abandons the message if the supplier is not ready.<br />

base class<br />

A class that is further specified by subclasses. Also called a superclass or ancestor class. For<br />

more information see Session 11. See also superclass and subclass.<br />

bound element<br />

A class resulting from the specification of parameters in a template class. See also template<br />

class.<br />

<br />

class<br />

An abstraction of a set of related information, behaviors, and relationships that describes a<br />

type of entity. A definition used to create objects. For more information see Sessions 1<br />

and 9. See also object.<br />

classification<br />

The process of finding common information, behaviors, and relationships among objects, in<br />

order to create a common definition for the objects. For more information see Session 9. See<br />

also class and object.<br />

class operation<br />

An operation that is specific to a class rather than to objects of the class. As such, it may be<br />

invoked without using an object of the class. For more information see Session 9.<br />

class variable<br />

An attribute that is specific to a class rather than to objects of the class. As such, it may be<br />

referenced within the class without using an object of the class. For more information see<br />

Session 9.<br />

client<br />

An object that initiates a request.<br />

collaboration<br />

An interaction between objects. The term is also used to describe a pattern, a standardized<br />

concept for configuring classes to fulfill a specific function. For more information see<br />

Session 12. See also pattern.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!