The bracketed numbers following each definition indicate the page number on which the term is defined or first used. A - abstract class
-
An abstract class is a class that cannot be directly instantiated. An instance can be created only in conjunction with an instance of one of its descendant subclasses. [98]
- action
-
An action is an individual operation that performs a single task on an element of a model. [111]
- activation
-
An activation is the execution of a single procedure in a state machine instance at some time. [184]
- actor
-
An actor is a role played by an external entity that requires something from the system in one or more interactions with the system. [42]
- archetype
-
An archetype is a fragment of data access and text manipulation logic that states formally how to embed an Executable UML model into text. [294]
- assigner
-
An assigner is a state machine that serves as a single point of control for creating links on competitive associations. [219]
- association
-
An association is the abstraction of a set of domain relationships that hold systematically between different kinds of conceptual entities, abstracted as classes, in the domain. [81]
- association class
-
An association class is an abstraction, as a class, of an association that may have its own attributes, other associations, and behavior. [93]
- association loop
-
An association loop is a set of associations that together make up a path from one class, through other classes, back to the same class. [138]
- attribute
-
An attribute is the abstraction of a single characteristic possessed by all the entities that were, themselves, abstracted as a class. [64]
B - bridge
-
A bridge is a layering dependency between domains. One domain makes assumptions, and other domains take those assumptions as requirements. [35]
- bridge operation
-
A bridge operation is an operation defined on an external entity and implemented in another domain. [284]
C - class
-
A class is an abstraction from a set of conceptual entities in a domain so that all the conceptual entities in the set have the same characteristics, and they all are subject to and behave according to the same rules and policies. [58]
- constraint
-
A constraint is a rule, expressed as a calculation in terms of other classes, attributes, and associations, that restricts the values of attributes and/or associations in a model. [125]
- constraint idiom
-
A constraint idiom is a general pattern for a commonly occurring type of constraint that can be represented by a predefined tag. [128]
- core data type
-
A core data type is a fundamental datatype from which other domain-specific datatypes can be defined. [65]
D - data access set
-
The data access set is the set of all data items read, written, or referenced by a single activation. [192]
- derived attribute
-
A derived attribute is an attribute whose value can be computed from other attributes already in the model. [132]
- derived identifier
-
A derived identifier is an identifier that is the derived concatenation of several identifying attributes. [137]
- domain
-
A domain is an autonomous, real, hypothetical, or abstract world inhabited by a set of conceptual entities that behave according to characteristic rules and policies. [30]
- domain-specific data type
-
A domain-specific data type is a definition of the set of legal values that can be assigned to attributes in a domain model. [65]
E - event
-
An event is the abstraction of an incident in the domain that tells us that something has happened. [152]
- event parameter
-
An event parameter is a data item passed along with an event. [170]
- Executable UML model compiler
-
An Executable UML model compiler compiles an Executable UML model into a runnable implementation. [292]
- execution trace
-
An execution trace is a sequence of procedures and signals that occurs in response to the arrival of a particular signal when the objects are in specific states and their attributes have specific values. [180]
F - final pseudostate
-
A final pseudostate is the state in which an object is deleted. [163]
I - identifier
-
An identifier is a set of one or more attributes that uniquely distinguishes each instance of a class. [126]
- identifying attribute
-
An identifying attribute is an attribute that forms part of at least one identifier. [129]
- initial pseudostate
-
An initial pseudostate is the state in which the state machine for an object is started. [162]
J - join point
-
A join point is a correspondence between domains that are created and maintained separately from the models of the two domains involved. [286]
L - leaf subclass
-
A leaf subclass is a subclass that is not the superclass of any other class. [97]
- link object
-
A link object is an instance of an association class. [94]
M - metamodel
-
A metamodel is a model of a language expressed using a modeling language. [294]
O - object
-
An object is an instance of a class, or an instance of several classes in a generalization-specialization hierarchy. [98]
- object reference
-
An object reference is a value that refers to an object. [111]
- object reference set
-
An object reference set holds a set of object references. [112]
P - polymorphic event
-
A polymorphic event is an event that has many potential receiving state machines in a generalization hierarchy. [227]
- polymorphic signal
-
A polymorphic signal is a signal delivered at run time to a specific state machine for a class in a generalization hierarchy. [227]
- procedure
-
A state procedure is an operation that is executed by an object on entry to a state. [154]
R - realized domain
-
A realized domain is a domain supplied as code. [280]
- reclassification
-
Reclassification is the act of moving an object from one leaf subclass in a generalization-specialization hierarchy to another. [118]
- referential attribute
-
A referential attribute is an attribute whose value is the value of an identifying attribute in one or more associated classes. [134]
- reflexive association
-
A reflexive association is an association between instances of the same class. [103]
S - scenario
-
A scenario is the planned execution of a use case with ranges of values for signal parameters, initial states for state machine instances, and ranges of values for attributes of objects, so that there is only path through the model. [254]
- signal
-
A signal sequences state machine instances. A signal may carry data used by the actions in the recipient's procedure. [170]
- state
-
A state represents a condition of an object in which a defined set of rules, policies, regulations, and physical laws applies. [151]
- subclass
-
A subclass is a class that specializes classes in a generalization-specialization hierarchy. [97]
- subsystem
-
A subsystem is a part of a domain containing classes, relationships, state machines, and their procedures. [269]
- superclass
-
A superclass is a class that generalizes classes in a generalization-specialization hierarchy. [97]
T - transition
-
A transition abstracts the progression from state to state as caused by an event. [153]
U - use case
-
A use case specifies an interaction between the system and one or more actors together with the activities performed by the system. [43]
- use case postcondition
-
A use case postcondition represents what must be true when the use case has completed. [54]
- use case precondition
-
A use case precondition denotes a relevant, verifiable property of the system that is required to be true before the use case is performed. [53]
|
