Adornaments of UML things.

Adornaments of UML things:
Class:

• Class is a description of a set of objects that share the same attributes, operations, relationships, and semantics.
• A class implements one or more interfaces. 
• Graphically, a class is rendered as a rectangle, usually including its name, attributes, and operations.

Interface :

• Interface is a collection of operations that specify a service of a class or component. 
• An interface is rendered as a circle together with its name. 
• An interface rarely stands alone. 
• Rather, it is typically attached to the class or component that realizes the interface.

Collaboration:

• Collaboration defines an interaction and is a society of roles and other elements that work together to provide some cooperative behavior that's bigger than the sum of all the elements. 
• Graphically, a collaboration is rendered as an ellipse with dashed lines, usually including only its name.

Use Case:

• Use case is a description of set of sequence of actions that a system performs that yields an observable result of value to a particular actor.A use case is realized by a collaboration. 
• Graphically, a use case is rendered as an ellipse with solid lines, usually including only its name.

Active Classes:

• Active class is just like a class except that its objects represent elements whose behavior is concurrent with other elements. 
• Graphically, an active class is rendered just like a class, but with heavy lines, usually including its name, attributes, and operations.

COMPONENTS:

• Component is a physical and replaceable part of a system that conforms to and provides the realization of a set of interfaces. 
• Graphically, a component is rendered as a rectangle with tabs.

Node:

• Node is a physical element that exists at run time and represents a computational resource, generally having at least some memory and, often, processing capability. 
• Graphically, a node is rendered as a cube, usually including only its name.

Interaction:

• Interaction is a behavior that comprises a set of messages exchanged among a set of objects within a particular context to accomplish a specific purpose.
• Graphically a message is rendered as a directed line, almost always including the name of its operation.

State Machine:

• State machine is a behavior that specifies the sequences of states an object or an interaction goes through during its lifetime in response to events, together with its responses to those events. 
• Graphically, a state is rendered as a rounded rectangle, usually including its name and its substates.

Packages:

• Grouping things are the organizational parts of UML models. 
• These are the boxes into which a model can be decomposed. 
• In all, there is one primary kind of grouping thing, namely, Packages.

Notes:

• Annotational things are the explanatory parts of UML Models. 
• These are the comments you may apply to describe and illuminate about any element in a model. 

Dependency:

• Dependency is a semantic relationship between two things in which a change to one thing  may affect the semantics of the other thing.
• Graphically a dependency is rendered as a dashed line, possibly directed, and occasionally including a label.

Association: 

• It is a structural relationship that describes a set of links, a link being a connection among objects.
• Graphically an association is rendered as a solid line, possibly directed, occasionally including a label, and often containing other adornments, such as multiplicity and role names.

Generalization:      

• It is a structural relationship between a whole and its parts. 
• Graphically, a generalization relationship is rendered as a solid line with a hollow arrowhead pointing to the parent. 

Realization:

• It is a semantic relationship between classifiers, wherein one classifier specifies a contract that another classifier guarantees to carry out. 
• Graphically a realization relationship is rendered as a cross between a generalization and a dependency relationship.