C
call (act)
A call is an invocation of a method during the execution of a procedure.call (dependency)
The term call also refers to a stereotype attached to a dependency within which the source operation invokes the target operation.call action
A call action is an action that invokes behavior and receives one or more return values. This invocation can be either synchronous or asynchronous.
The action places the result values from the invocation on an output pin.
There are two types of call actions: call behavior actions and call operation actions.
A call behavior action is a call action that invokes a specified
call behavior action
call concurrency kind
The term call concurrency kind refers to an enumeration that contains three values:
![]() | |
![]() | |
![]() |
call event
A call event is an event that represents the dispatch of an operation.
A call operation action is a call action that sends a message to a given object to invoke a specific operation.
call operation action
call trigger
A call trigger is a trigger that specifies that a behavior execution may be triggered by the invocation of a given operation.
Within the Unified Process, a candidate architecture is an architecture made up of initial versions of the use case model, the analysis model, the design model, the deployment model, the implementation model, and the test model.
Within the RUP, a capsule is a design pattern that represents an encapsulated thread of control.
Within the RUP, a capsule designer is a person playing the role of focusing on ensuring that the system being modeled will respond to events in a timely manner per the concurrency requirements.
cardinality
The term cardinality refers to the number of elements in a given set.
central buffer node
A central buffer node is an object mode that accepts tokens from upstream object nodes and passes them along to downstream object nodes.
changeability
The term changeability refers to a property whose value indicates whether a given attribute or link can change after being initialized.
The allowable values of the changeability property are as follows:
![]() |
addOnly (for an attribute whose multiplicity is greater than 1, one can add additional values, but one cannot change or delete a value once one has added it; for a link, one can add new links from an object on the opposite side of the given association) |
![]() |
changeable (for an attribute, one can add, change, and delete values without restriction; for a link, one can add, change, and delete links between the objects connected by the given association without restriction) |
![]() |
frozen (for an attribute, one cannot add, change, or delete any values; for a link, one can add new links from an object being created on the opposite side of the given association, but one cannot change or delete a link once one has added it) |
Change and Deliver Configuration Items
Within the RUP, Change and Deliver Configuration Items is an activity within the Configuration and Change Management discipline.
The purpose of this activity is to integrate changes to project artifacts and make them visible to developers for the next round of development.
Within the RUP, a change control manager is a person playing the role of overseeing the change control process.
change event
A change event is an event that represents the satisfaction of a Boolean expression in response to a change to one or more of the values it references.change request
Within the Unified Process, a change request is a formal written request, associated with a particular originator and a specified root cause, to fix a defect, modify a requirement, or otherwise effect a meaningful change to the system being developed.Within the RUP, change requests are part of the Configuration and Change Management artifact set.
A change trigger is a trigger that specifies that a behavior execution may be triggered by a change event.
change trigger
child
The term child refers to the more specific element within a given generalization.
The term choice refers to a pseudostate that makes it possible to perform a branch within which the choice of which outgoing path to take can depend on the results of actions executed before the branch occurs as well as the guards connected with the branch.
choice
class
A class is a named description of a set of objects that share the same attributes, operations, relationships, and semantics. These objects can represent real-world things or conceptual things.
A class may realize one or more interfaces.
A class can be either an active class or a passive class.
class diagram
A class diagram is a structure diagram that shows a set of classes, interfaces, and/or collaborations and the relationships among these elements.The term classification refers to the assignment of an object to a classifier. The UML defines three types of classification:
classification
![]() | dynamic classification |
![]() | multiple classification |
![]() | static classification |
classifier
A classifier is a model element that describes behavioral features and/or structural features of instances that have these things in common.
The UML defines eight kinds of classifiers:
![]() |
actor |
![]() |
artifact |
![]() |
behaviored classifier |
![]() |
class |
![]() |
datatype |
![]() |
interface |
![]() |
signal |
![]() |
structured classifier |
classifier scope
An attribute or association has classifier scope if the values of the attribute, or the target values of the association, are classifiers.
classifier template parameter
A classifier template parameter is a template parameter that exposes a classifier as a formal parameter for a template.
clause
A clause is a combination of a test and a body section such that if execution of the test results in the value True, the body section is executed.
clear association action
A clear association action is an action that destroys all links that are instances of a particular association connected to a given object.
clear structural feature action
A clear structural feature action is a structural feature action that deletes all values from a given structural feature.
clear variable action
A clear variable action is a variable action that deletes all values from a given variable.
client
The term client refers to the element within a dependency that requests one or more services from the supplier. (The client is the dependent element.)
Within the RUP, Close Out Phase is an activity within the Project Management discipline.
The purpose of this activity is to bring a particular phase of the project to a close. This involves tasks such as resolving all major issues from the previous iteration and distributing required artifacts to stakeholders.
Within the RUP, Close Out Project is an activity within the Project Management discipline.
The purpose of this activity is to get the project ready for termination. This involves tasks such as preparing a final status assessment, disposing of remaining assets, and reassigning remaining staff.
code reviewer
Within the RUP, a code reviewer is a person playing the role of planning and conducting source code reviews.collaboration
The term collaboration refers to a description of a structure of collaborating classifiers, instances of which each perform a specialized function (in other words, serve some role), that collectively accomplish some desired functionality.
Connectors define communication paths among participating instances. Each instance within the collaboration is referred to as a connectable element.
collaboration occurrence
A collaboration occurrence is an application of the pattern described by a particular collaboration to a specific situation that involves involving specific classes or instances playing the roles of that collaboration. If a collaboration occurrence represents some behavior offered by a class, the occurrence is connected with the class using a represents dependency.
collect
The term collect refers to an OCL operation that creates a Collection that contains the values that result from evaluating a specified OCL expression for each of the elements in a given Collection.
Collection
Collection is the abstract supertype of Bag, OrderedSet, Sequence, and Set.You can perform any of the following operations on a Collection:
![]() |
collect |
![]() |
collectNested |
![]() |
count |
![]() |
equals |
![]() |
excluding |
![]() |
exists |
![]() |
forAll |
![]() |
includes |
![]() |
includesAll |
![]() |
including |
![]() |
intersection |
![]() |
isEmpty |
![]() |
iterate |
![]() |
notEmpty |
![]() |
reject |
![]() |
select |
![]() |
size |
![]() |
sum |
![]() |
union |
collectNested
The term collectNested refers to an OCL operation that creates a Collection of nested Collections that contains the values that result from evaluating a specified OCL expression for each of the elements in a given Collection.
combined fragment
A combined fragment is an interaction fragment defined by an interaction operator and one or more interaction operands.
comment
A comment is a piece of text that provides arbitrary information associated with one or more model elements.communication association
A communication association is an association that describes a communication relationship between two elements (for instance, an actor and a use case on a use case diagram).communication diagram
A communication diagram is an interaction diagram that focuses on the interactions between lifelines, where the architecture of the internal structure and how this corresponds with the message passing is central. The messages are usually notated with sequence numbers.
Note that communication diagrams and sequence diagrams are semantically equivalent, which means that one can convert one type of diagram to the other without losing any information. A sequence diagram does not have sequence numbers, but it also has a number of features that communication diagrams do not offer.
A communication path is an association between two nodes through which they are able to exchange signals and messages.
complete
The term complete is a constraint attached to a generalization set to signify that all children have been specified for that set and that no more can be specified.A completion event is an event generated by the completion of activities when an object is in a given state. A component may also have ports.
completion event
completion transition
A completion transition is a transition that is triggered by a completion event.
complex transition
A complex transition is a transition that has more than one source state (this is a join) and/or more than one target state (this is a fork).
component
A component is a named physical and replaceable part of a system that represents physical packaging and implementation of otherwise logical elements (such as classes) and that conforms to, and provides the realization of, one or more interfaces.
component diagram
A component diagram is a structure diagram that shows a set of components and the relationships among them.
component engineer
Within the Unified Process, a component engineer is a worker who is responsible for artifacts within several workflows:
A component instance is an instance of a component on a node.
composite aggregation
The term composite aggregation is a synonym of composition.composite class
A composite class is a class that serves as the "whole" within a composition relationship.composite object
A composite object is an instance of a composite class.composite state
A composite state is a state comprised of either concurrent substates or disjoint substates.Given two or more substates at the same level, an object will be in one sequential substate, but each of the concurrent substates.
A composite structure diagram is a structure diagram that shows the internal structure of a classifier and/or the use of a collaboration in a collaboration occurrence.
composite structure diagram
composition
The term composition refers to an aggregation within which the "part"s and the larger "whole" share lifetimes. In other words, if an instance of the "whole" is destroyed, the connected "part"s are also destroyed.
A given model element can be part of only one composition relationship at a time.
compound transition
A compound transition is a path comprised of one or more transitions that originate from one set of states and target a different set of states. Within the RUP, Conceive New Project is an activity within the Project Management discipline. The purpose of this activity is to bring a project from its initial conception to a point at which a reasoned decision can be made to proceed with the project or not. The business case is also developed during this activity.
concrete
A generalizable element is concrete if it can be directly instantiated.
See the entries for concrete class, concrete operation, and concrete use case for more specific information.
concrete class
A concrete class is a class that may have direct instances.
An concrete class cannot have abstract operations, however.
concrete operation
A concrete operation is an operation that has an implementation.
concrete use case
A concrete use case is a use case that is initiated by an actor and that represents a complete sequence of actions to be performed by the system being built.
A concrete use case may reuse the behavior associated with one or more abstract use cases.
concurrency (property)
The term concurrency refers to a property whose value indicates how a given method will respond in the face of more than one concurrent call to it.
The allowable values of the concurrency property are as follows:
![]() |
concurrent (multiple calls may come in simultaneously, and they can all proceed concurrently) |
![]() |
guarded (multiple calls may come in simultaneously, but only one can be addressed at a time) |
![]() |
sequential (only one call may come in at a time) |
concurrency (situation)
The term concurrency also refers to the situation where two or more activities are performing during the same period of time.These activities perform independently unless synchronization points have been explicitly defined.
concurrent substate
A concurrent substate is a substate in which an object can exist simultaneously with other substates at that same level within a composite state.
conditional node
A conditional node is a structured activity node that represents an exclusive choice among some number of alternatives expressed in the form of clauses.
Configuration and Change Management artifact set
Within the RUP, the Configuration and Change Management artifact set is a set of artifacts related to the tracking and maintenance of the integrity of project assets as they evolve.
The Configuration and Change Management artifact set contains the following artifacts:
![]() |
change requests |
![]() |
configuration audit findings |
![]() |
configuration management plan |
![]() |
project repository |
![]() |
workspaces (private development areas and shared areas) |
Configuration and Change Management discipline
Within the RUP, the purpose of the Configuration and Change Management discipline is to track, and maintain the integrity of, project assets as they evolve in the presence of changes.The following activities comprise the Configuration and Change Management discipline:
![]() |
Change and Deliver Configuration Items |
![]() |
Create Project CM Environment |
![]() | Manage Baselines and Releases |
![]() |
Manage Change Requests |
![]() |
Monitor and Report Configuration Status |
![]() |
Plan Project Configuration and Change Control |
configuration audit findings
Within the RUP, configuration audit findings identify a baseline, any missing required artifacts, and incompletely tested or failed requirements.
Configuration audit findings are part of the Configuration and Change Management artifact set.
configuration management plan
Within the RUP, a configuration management plan is an artifact that defines the configuration management policies and practices to be used on the project.
The configuration management plan belongs to the Configuration and Change Management artifact set.
configuration manager
Within the RUP, the configuration manager is a person playing the role of providing the overall configuration management infrastructure and environment for the development team.conflict
A conflict occurs when there is the chance for some kind of contradiction or ambiguity within a given model.For instance, a conflict would arise if a subclass inherits two attributes, both with the same name, from two superclasses, or if an event enables more than one transition.
A connectable element is a set of instances, owned by a classifier instance, that may be joined by attached connectors within the classifier instance. There are four kinds of connectable elements:
connectable element
![]() | parameter |
![]() | port |
![]() | property |
![]() | variable |
A connectable element template parameter is a template parameter that exposes a connectable element as a formal parameter for a template.
connectable element template parameter
connection point reference
A connection point reference is a vertex that represents a usage, as part of a given submachine state, of an entry point or exit point defined in the state machine that the submachine state references.
connector
A connector is a link between two connectable elements that enables those elements to communicate. There are two kinds of connectors: assembly connectors and delegation connectors.
connector end
A connector end is an end point of a connector.
A constant expression is an OCL expression that takes no arguments but produces a value.
There are four types of constant expressions:
![]() | Boolean constant expression |
![]() | enumeration constant expression |
![]() | numeric constant expression |
![]() | string constant expression |
constraint (mechanism)
A constraint is an extensibility mechanism that allows one to create conditions and restrictions, stated as Boolean expressions, that apply to model elements.
One can specify a constraint using free-form text or the more precise Object Constraint Language (OCL).
Note that a constraint represents an assertion, not an executable mechanism.
The following constraints are predefined within the UML:
![]() |
complete |
![]() |
disjoint |
![]() |
incomplete |
![]() |
overlapping |
![]() |
xor |
constraint (OCL)
Within the OCL, a constraint is a restriction on one or more values of part of or all of a model or a system.Construction phase
Within the Unified Process, the Construction phase is the phase of a development project in which the architecture baseline grows to become the full-fledged system.The primary goal of this phase is to produce a product that is ready to put in the hands of its customers. A constructor might have the same name as the class to which it belongs, or it might be named something like "new."
constructor
A constructor is an operation, which has classifier scope, that creates and initializes an instance of a class.
container
A container is an object, designed to contain other objects, that provides operations that one can use to access its contents directly or iterate through them.
Arrays and sets are examples of containers.
A containment hierarchy is a hierarchy within a namespace comprised of a set of model elements and the containment relationships that exist among them.
containment hierarchy
context (OCL)
Within the OCL, the term context refers to the model element with which a given invariant, precondition, or postcondition is associated.
The context of an invariant is always a class, an interface, or a type. The context of a precondition or a postcondition is always an operation or a method.
context (UML)
Within the UML, a context is a piece of a model that provides the environment for a set of related elements of that model.A continuation is an interaction fragment that defines a continuation of one branch of a combined fragment partially defined by the alt interaction operator. A control flow is an activity edge that only passes control tokens.
continuation
control class
Within the Unified Process, the term control class refers to a stereotype attached to a class, contained within the analysis model, to signify that the class defines one or more control objects that embody application logic.
control flow
A control node is an activity node that coordinates the flows between other activity nodes. There are six kinds of control nodes:
control node
![]() |
decision node |
![]() |
final node |
![]() |
fork node |
![]() |
initial node |
![]() |
join node |
![]() |
merge node |
Within the Unified Process, a control object is an instance of a control class.
count
The term count refers to an OCL operation that returns the number of occurrences of a specified element within a given Collection.
course developer
Within the RUP, a course developer is a person playing the role of developing training material with which users are taught how to use the new system.
create (behavioral feature)
The term create refers to a stereotype on a behavioral feature that signifies that the feature creates an instance of the enclosing classifier.
create (dependency)
The term create also refers to a stereotype on a dependency that signifies that the client classifier creates one or more instances of the supplier classifier.
create link action
A A create link object action is a special form of create link action.
create link object action
A create link object action is a create link action that creates a link object.
create object action
A create object action is an action that creates an object belonging to a specified classifier. Within the RUP, Create Project CM Environment is an activity within the Configuration and Change Management discipline. The purpose of this activity is to create a work environment where all project artifacts are available and where the product can be developed, integrated, and archived for subsequent maintenance and reuse.
creation
The term creation refers to the instantiation and initialization of an instance.
current event
The term current event refers to the event that triggered a run-to-completion step within the execution of a given state machine.
Within the Unified Process, a cycle is a period of time within a development project that ends with the release of a version of the system to customers.