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 339<br />

<br />

link<br />

A relationship between two objects. For more information see Session 13. See also association.<br />

link attribute<br />

A value that helps to describe a relationship between two objects. See also association class<br />

and link.<br />

logical view<br />

A presentation dedicated to the description of conceptual analysis and design work products<br />

for a software project. For more information see Session 3.<br />

<br />

merge of control<br />

<strong>To</strong> synchronize or coordinate the completion of multiple threads or processes and pass<br />

control to a single thread or process. Merge of control does not require the completion of all<br />

threads or processes. Merge may be conditional on the completion of one or more of a set of<br />

threads, time, or other conditions. For more information see Sessions 14 and 20.<br />

message<br />

Communication between objects, typically an event containing information and/or eliciting<br />

a response. For more information see Sessions 16 and 18.<br />

metamodel<br />

The specification of a language for describing the <strong>UML</strong> diagrams. Also, a model that describes<br />

the elements and the relationships between those elements that make up a specified domain<br />

(for example, the Class diagram). For more information see Session 1.<br />

method<br />

The implementation of an operation. For more information see Session 9. See also operation.<br />

model<br />

A representation of a view of a physical system, usually designed to simplify and facilitate<br />

understanding of the system. The representations may focus on the logical rules and relationships<br />

that define the system as well as the physical components used to implement the<br />

system. For more information see Session 3.<br />

model element<br />

The smallest unit of semantic definition in a model. The same model element may appear<br />

in multiple diagrams. For example, an event appears in Sequence diagrams, Collaboration<br />

diagrams, and Statechart diagrams. In all three contexts it provides the same semantic<br />

information. For more information see Session 3.<br />

multiplicity<br />

A constraint on the number of objects that may participate in one end of an association. For<br />

more information see Session 9.

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

Saved successfully!

Ooh no, something went wrong!