bongsoo/moco_eval · Datasets at Hugging Face

text stringlengths 16 313
A speciﬁcation of the range of allowable cardinality values—the size—that a setmay assume.
Multiplicity speciﬁcations may be given for association ends, partswithin composite classes, repetitions of messages, and other purposes.
See also multiplicity (of association), multiplicity (of class).
Multiplicity is a constraint on the cardinality (size) of a set.
In principle, it is a sub-set of the nonnegative integers.
In practice, it is usually a ﬁnite set of integer inter-vals, most often a single interval with a minimum and a maximum value.
Any setmust be ﬁnite, but the upper bound can be ﬁnite or unbounded (an unboundedmultiplicity is called “many”).
The upper bound must be greater than zero; or, atany rate, a multiplicity comprising only zero is not very useful, as it permits onlythe empty set.
Multiplicity is coded as a string.
In most cases, a multiplicity may be speciﬁed as an integer range—a minimumand a maximum cardinality—but in general, it may be a discontinuous subset ofthe nonnegative integers.
The set of integers may be inﬁnite—that is, the upperbound may be unlimited (but note that any particular cardinality in the set is ﬁ-nite).
For most practical purposes, this set of integers can be speciﬁed as a ﬁnite list ofdisjoint, disconnected integer intervals.
An interval is a set of contiguous integerscharacterized by its minimum and maximum values.
Some inﬁnite sets cannot bespeciﬁed this way—for example, the set of even integers—but usually little is lostby simply including the gaps.
See multiplicity (of association) and multiplicity (of class) for speciﬁc details ofusing multiplicity with these elements.
where number is an integer representing an interval of a single size.
The multiplicity expression consisting of a single star*is equivalent to the expression 0..
This frequently encountered multiplicityis read “many.
Two contiguous intervals should be combined into a single interval.
A multiplicity expression can include variables, but they must resolve to integervalues when the model is complete—that is, they must be parameters or con-stants.
Multiplicity is not meant to be dynamically evaluated within a run-timescope like a dynamic array bound.
It is meant to specify the possible range of val-ues (worst case) a set might assume and the application must therefore accommo-date in its data structures and operations.
The multiplicity may be suppressed on a diagram, but it exists in the underlyingmodel.
In a ﬁnished model, there is no meaning to an “unspeciﬁed” multiplicity.
The list must be a comma-separated list of names of states that can legally occurconcurrently.
To show a change of class (dynamic classiﬁcation), the object must be displayedtwice, once with each class.
The two symbols are connected by a become relation-ship to show that they represent the same object.
The second compartment shows the attributes for the object and their values as
The type is redundant with the attribute declaration in the class and may be omit-ted.
The value is speciﬁed as a string that represents the value.
The name of the object may be omitted.
In this case, the colon should be keptwith the class name.
Each symbol that contains an anonymous object denotes adistinct object distinguished by its relationships to other objects.
The class of the object may be suppressed (together with the colon), but itshould be shown when possible to avoid confusion.
The attribute value compartment as a whole may be suppressed.
Attributes whose values are not of interest may be suppressed.
To show the changes in value of attributes during a computation, show two ver-sions of the same object with a become relationship between them.
A diagram that shows objects and their relationships at a point in time.
Also related is a collaboration diagram, whichshows prototypical objects (classiﬁer roles) within a context.
Tools need not support a separate format for object diagrams.
” The phrase is useful, however, to characterize a particular usage achievablein various ways.
An object diagram shows a set of objects and links that represent the state of a sys-tem at a particular moment in time.
It contains objects with values, not descrip-tors, although they can, of course, be prototypical in many cases.
To show a generalpattern of objects and relationships that can be instantiated many times, use a col-laboration diagram, which contains descriptors (classiﬁer roles and associationroles) for objects and links.
If a collaboration diagram is instantiated, it yields anobject diagram.
An object diagram does not show the evolution of the system over time.
For thatpurpose, use a collaboration diagram with messages, or a sequence diagram torepresent an interaction.
An object ﬂow is a kind of control ﬂow with an object ﬂow state as an input or anoutput.
An object ﬂow is shown as a dashed line from the source entity to the target entity.
One or both entities may be object ﬂow states, displayed as object symbols.
If there is no label on the arrow, it is a become relationship.
See object ﬂow state, become, and copy for examples.
A state that represents the existence of an object of a particular class at a pointwithin a computation, such as an interaction view or an activity graph.
Both activity graphs and interaction views represent the ﬂow of control amongoperations in target objects by messages, but messages do not show the ﬂow of theobjects that are arguments to operations.
This kind of information ﬂow can berepresented in behavioral models using object ﬂow states.
An object ﬂow state represents an object of a class that exists at a point within acomputation, such as an activity graph or an interaction view.
The object may bethe output of one activity and the input of many other activities.
In an activitygraph, it may be the target of a transition (often a fork, the other branch being themain control path), and it may be the source of a completion transition to an ac-tivity.
When the preceding transition ﬁres, the object ﬂow state becomes active.
This represents the creation of on object of the class.
To show the passage of an ob-ject into a state, rather than the creation of a new object, an object ﬂow state can bedeclared as a class in a state, a class-in-state.
An object ﬂow state must match the type of the result or parameter that it repre-sents.
If it is the output of an operation, it must match the type of the result.
If it isthe input of an operation, it must match the type of a parameter.
In other words, the creation of data in the right form isthe trigger for performing the activity.
Multiple paths to a transition indicate synchronization.
Object ﬂow states are usually useful to document input-output relationships forhuman understanding rather than to specify a computation precisely.
The infor-mation shown by object ﬂow states is already available.
The production of an event by an activity in an activity graph can be modeled as
The object ﬂow state is an output of the activity.
If the activity produces mul-tiple events, the object ﬂow states are targets of a fork.
An object ﬂow symbol represents the existence of the object in a state of the proce-dure itself and not simply the object itself, as data.
The object ﬂow symbol (whichrepresents a state) may appear as the target of one transition arrow and as thesource of multiple transition arrows.
To distinguish these from ordinary transi-tions in an activity diagram, they are drawn as dashed arrows rather than solid ar-rows.
Figure 13-135 shows object ﬂow states in an activity diagram.
An object ﬂow stateis created by the completion of an operation.
For example, Order[Placed] is cre-ated by the completion of Request Service.
Because that activity is followed by an-other activity, the object ﬂow state Order[Placed] is an output of a fork symbol.
State Order[Entered], on the other hand, is the result of completing activity TakeOrder, which has no other successor activities.
Figure 13-136 shows a portion of an activity diagram concerned with building ahouse.
When the frame has been built, the carpenter is free to work on the roofand the house is ready for the plumbing to be installed.
These events are modeledas object ﬂow states of signals—Carpenter free and Frame ready.
As a result ofthese events, the roof can be built and the plumbing can be installed.
Therefore theobject ﬂow states are shown as inputs of the activities.
In the model, the produc-tion of an event by the completion of one activity and its use to trigger the next ac-tivity are implicit in the connection of the activities.
The need for a manifest eventhas been elided.
An object ﬂow state represents the data ﬂow view of a computation.
Unlike tradi-tional data ﬂow, however, it exists at a deﬁnite point within a control ﬂow model (astate machine or an activity graph), rather than within a data ﬂow model.
Thisplaces it squarely into an object-oriented framework.
Object orientation unites thedata structure, control ﬂow, and data ﬂow viewpoints into a single model.
A line in a sequence diagram that represents the existence of an object over a pe-riod of time.
An expression that yields a set of objects when evaluated at run time.
The target of a send action is an object set expression.
When such an expression isevaluated at run time, it yields a set of objects to which a designated signal is sentin parallel.
An object set expression may yield a single element, in which case thesend action is an ordinary sequential action.
It may even yield no element (that is,an empty set) in which case no send occurs.
Object Constraint Language, a text language for specifying constraints and que-ries.
For a fulldeﬁnition, see the book [Warmer-99].
The Object Constrain Language (OCL) is a text language for writing navigationexpressions, Boolean expressions, and other queries.
It may be used to constructexpressions for constraints, guard conditions, actions, preconditions and postcon-ditions, assertions, and other kinds of UML expressions.

A speciﬁcation of the range of allowable cardinality values—the size—that a setmay assume.

Multiplicity speciﬁcations may be given for association ends, partswithin composite classes, repetitions of messages, and other purposes.

See also multiplicity (of association), multiplicity (of class).

Multiplicity is a constraint on the cardinality (size) of a set.

In principle, it is a sub-set of the nonnegative integers.

In practice, it is usually a ﬁnite set of integer inter-vals, most often a single interval with a minimum and a maximum value.

Any setmust be ﬁnite, but the upper bound can be ﬁnite or unbounded (an unboundedmultiplicity is called “many”).

The upper bound must be greater than zero; or, atany rate, a multiplicity comprising only zero is not very useful, as it permits onlythe empty set.

Multiplicity is coded as a string.

In most cases, a multiplicity may be speciﬁed as an integer range—a minimumand a maximum cardinality—but in general, it may be a discontinuous subset ofthe nonnegative integers.

The set of integers may be inﬁnite—that is, the upperbound may be unlimited (but note that any particular cardinality in the set is ﬁ-nite).

For most practical purposes, this set of integers can be speciﬁed as a ﬁnite list ofdisjoint, disconnected integer intervals.

An interval is a set of contiguous integerscharacterized by its minimum and maximum values.

Some inﬁnite sets cannot bespeciﬁed this way—for example, the set of even integers—but usually little is lostby simply including the gaps.

See multiplicity (of association) and multiplicity (of class) for speciﬁc details ofusing multiplicity with these elements.

where number is an integer representing an interval of a single size.

The multiplicity expression consisting of a single star*is equivalent to the expression 0..

This frequently encountered multiplicityis read “many.

Two contiguous intervals should be combined into a single interval.

A multiplicity expression can include variables, but they must resolve to integervalues when the model is complete—that is, they must be parameters or con-stants.

Multiplicity is not meant to be dynamically evaluated within a run-timescope like a dynamic array bound.

It is meant to specify the possible range of val-ues (worst case) a set might assume and the application must therefore accommo-date in its data structures and operations.

The multiplicity may be suppressed on a diagram, but it exists in the underlyingmodel.

In a ﬁnished model, there is no meaning to an “unspeciﬁed” multiplicity.

The list must be a comma-separated list of names of states that can legally occurconcurrently.

To show a change of class (dynamic classiﬁcation), the object must be displayedtwice, once with each class.

The two symbols are connected by a become relation-ship to show that they represent the same object.

The second compartment shows the attributes for the object and their values as

The type is redundant with the attribute declaration in the class and may be omit-ted.

The value is speciﬁed as a string that represents the value.

The name of the object may be omitted.

In this case, the colon should be keptwith the class name.

Each symbol that contains an anonymous object denotes adistinct object distinguished by its relationships to other objects.

The class of the object may be suppressed (together with the colon), but itshould be shown when possible to avoid confusion.

The attribute value compartment as a whole may be suppressed.

Attributes whose values are not of interest may be suppressed.

To show the changes in value of attributes during a computation, show two ver-sions of the same object with a become relationship between them.

A diagram that shows objects and their relationships at a point in time.

Also related is a collaboration diagram, whichshows prototypical objects (classiﬁer roles) within a context.

Tools need not support a separate format for object diagrams.

” The phrase is useful, however, to characterize a particular usage achievablein various ways.

An object diagram shows a set of objects and links that represent the state of a sys-tem at a particular moment in time.

It contains objects with values, not descrip-tors, although they can, of course, be prototypical in many cases.

To show a generalpattern of objects and relationships that can be instantiated many times, use a col-laboration diagram, which contains descriptors (classiﬁer roles and associationroles) for objects and links.

If a collaboration diagram is instantiated, it yields anobject diagram.

An object diagram does not show the evolution of the system over time.

For thatpurpose, use a collaboration diagram with messages, or a sequence diagram torepresent an interaction.

An object ﬂow is a kind of control ﬂow with an object ﬂow state as an input or anoutput.

An object ﬂow is shown as a dashed line from the source entity to the target entity.

One or both entities may be object ﬂow states, displayed as object symbols.

If there is no label on the arrow, it is a become relationship.

See object ﬂow state, become, and copy for examples.

A state that represents the existence of an object of a particular class at a pointwithin a computation, such as an interaction view or an activity graph.

Both activity graphs and interaction views represent the ﬂow of control amongoperations in target objects by messages, but messages do not show the ﬂow of theobjects that are arguments to operations.

This kind of information ﬂow can berepresented in behavioral models using object ﬂow states.

An object ﬂow state represents an object of a class that exists at a point within acomputation, such as an activity graph or an interaction view.

The object may bethe output of one activity and the input of many other activities.

In an activitygraph, it may be the target of a transition (often a fork, the other branch being themain control path), and it may be the source of a completion transition to an ac-tivity.

When the preceding transition ﬁres, the object ﬂow state becomes active.

This represents the creation of on object of the class.

To show the passage of an ob-ject into a state, rather than the creation of a new object, an object ﬂow state can bedeclared as a class in a state, a class-in-state.

An object ﬂow state must match the type of the result or parameter that it repre-sents.

If it is the output of an operation, it must match the type of the result.

If it isthe input of an operation, it must match the type of a parameter.

In other words, the creation of data in the right form isthe trigger for performing the activity.

Multiple paths to a transition indicate synchronization.

Object ﬂow states are usually useful to document input-output relationships forhuman understanding rather than to specify a computation precisely.

The infor-mation shown by object ﬂow states is already available.

The production of an event by an activity in an activity graph can be modeled as

The object ﬂow state is an output of the activity.

If the activity produces mul-tiple events, the object ﬂow states are targets of a fork.

An object ﬂow symbol represents the existence of the object in a state of the proce-dure itself and not simply the object itself, as data.

The object ﬂow symbol (whichrepresents a state) may appear as the target of one transition arrow and as thesource of multiple transition arrows.

To distinguish these from ordinary transi-tions in an activity diagram, they are drawn as dashed arrows rather than solid ar-rows.

Figure 13-135 shows object ﬂow states in an activity diagram.

An object ﬂow stateis created by the completion of an operation.

For example, Order[Placed] is cre-ated by the completion of Request Service.

Because that activity is followed by an-other activity, the object ﬂow state Order[Placed] is an output of a fork symbol.

State Order[Entered], on the other hand, is the result of completing activity TakeOrder, which has no other successor activities.

Figure 13-136 shows a portion of an activity diagram concerned with building ahouse.

When the frame has been built, the carpenter is free to work on the roofand the house is ready for the plumbing to be installed.

These events are modeledas object ﬂow states of signals—Carpenter free and Frame ready.

As a result ofthese events, the roof can be built and the plumbing can be installed.

Therefore theobject ﬂow states are shown as inputs of the activities.

In the model, the produc-tion of an event by the completion of one activity and its use to trigger the next ac-tivity are implicit in the connection of the activities.

The need for a manifest eventhas been elided.

An object ﬂow state represents the data ﬂow view of a computation.

Unlike tradi-tional data ﬂow, however, it exists at a deﬁnite point within a control ﬂow model (astate machine or an activity graph), rather than within a data ﬂow model.

Thisplaces it squarely into an object-oriented framework.

Object orientation unites thedata structure, control ﬂow, and data ﬂow viewpoints into a single model.

A line in a sequence diagram that represents the existence of an object over a pe-riod of time.

An expression that yields a set of objects when evaluated at run time.

The target of a send action is an object set expression.

When such an expression isevaluated at run time, it yields a set of objects to which a designated signal is sentin parallel.

An object set expression may yield a single element, in which case thesend action is an ordinary sequential action.

It may even yield no element (that is,an empty set) in which case no send occurs.

Object Constraint Language, a text language for specifying constraints and que-ries.

For a fulldeﬁnition, see the book [Warmer-99].

The Object Constrain Language (OCL) is a text language for writing navigationexpressions, Boolean expressions, and other queries.

It may be used to constructexpressions for constraints, guard conditions, actions, preconditions and postcon-ditions, assertions, and other kinds of UML expressions.