complexType "uml:Behavior"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
|
Used: |
|
XML Representation Summary |
| <... |
| |
|
= |
xsd:ID |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:IDREF |
|
= |
"2.0" |
|
= |
xsd:QName |
|
= |
xsd:string |
|
= |
("public" | "private" | "protected" | "package") |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
("public" | "private" | "protected" | "package") |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
= |
xsd:string |
|
| |
> |
| |
|
| </...> |
Known Direct Subtypes (3):
-
Known Indirect Subtypes (1):
-
All Direct / Indirect Based Elements (24):
-
Annotation
Behavior is a specification of how its context classifier changes state over time. This specification may be either a definition of possible behavior execution or emergent behavior, or a selective illustration of an interesting subset of possible executions. The latter form is typically used for capturing examples, such as a trace of a particular execution. A classifier behavior is always a definition of behavior and not an illustration. It describes the sequence of state changes an instance of a classifier may undergo in the course of its lifetime. Its precise semantics depends on the kind of classifier. For example, the classifier behavior of a collaboration represents emergent behavior of all the parts, whereas the classifier behavior of a class is just the behavior of instances of the class separated from the behaviors of any of its parts. When a behavior is associated as the method of a behavioral feature, it defines the implementation of that feature; i.e., the computation that generates the effects of the behavioral feature. As a classifier, a behavior can be specialized. Instantiating a behavior is referred to as “invocating” the behavior, an instantiated behavior is also called a behavior “execution.” A behavior may be invoked directly or its invocation may be the result of invoking the behavioral feature that specifies this behavior. A behavior can also be instantiated as an object in virtue of it being a class. The specification of a behavior can take a number of forms, as described in the subclasses of Behavior. Behavior is an abstract metaclass factoring out the commonalities of these different specification mechanisms. When a behavior is invoked, its execution receives a set of input values that are used to affect the course of execution and as a result of its execution it produces a set of output values which are returned, as specified by its parameters. The observable effects of a behavior execution may include changes of values of various objects involved in the execution, the creation and destruction of objects, generation of communications between objects, as well as an explicit set of output values.
Type Derivation Tree uml:Behavior |
XML Source (w/o annotations (5); see within schema source)
| <xsd:complexType name="Behavior"> <xsd:complexContent> <xsd:choice maxOccurs="unbounded" minOccurs="0"> </xsd:choice> </xsd:extension> </xsd:complexContent> </xsd:complexType> |
Attribute Detail (all declarations; defined within this component only; 5/25)
isReentrant-
Type: |
xsd:string, predefined |
Use: |
optional |
Tells whether the behavior can be invoked while it is still executing from a previous invocation.
XML Source (w/o annotations (1); see within schema source)
postcondition-
Type: |
xsd:string, predefined |
Use: |
optional |
XML Source (see within schema source)
precondition-
Type: |
xsd:string, predefined |
Use: |
optional |
XML Source (see within schema source)
redefinedBehavior-
Type: |
xsd:string, predefined |
Use: |
optional |
XML Source (see within schema source)
specification-
Type: |
xsd:string, predefined |
Use: |
optional |
Designates a behavioral feature that the behavior implements. The behavioral feature must be owned by the classifier that owns the behavior or be inherited by it. The parameters of the behavioral feature and the implementing behavior must match. If a behavior does not have a specification, it is directly associated with a classifier (i.e., it is the behavior of the classifier as a whole).
XML Source (w/o annotations (1); see within schema source)