A relational table (composed of columns).
The explicit definition of a property as a name-value pair. In a Tagged Value, the name is referred to as the tag. Certain tags are predefined in the UML; others can be user defined. Tagged values are one of three extensibility mechanisms in UML.
See also: constraint, stereotype
Synonym: parameterized element
A pseudostate indicating that upon entry of its pseudostate, the state machine's execution ends.
thread [of control]
A single path of execution through a program, a dynamic model, or some other representation of control flow. Also, a stereotype for the implementation of an active object as lightweight process.
See also: process
An event that denotes the time elapsed since the current state was entered.
See also: event
An expression that resolves to an absolute or relative value of time.
A diagram that defines the behavior of different objects within a time-scale, with visual depictions of those objects changing state and interacting over time.
The main toolbar running down the center of Enterprise Architect, from which you can select model elements to insert into diagrams. This is also known as the Enterprise Architect UML Toolbox and the Object Toolbar.
A stereotype of package denoting the top-most package in a containment hierarchy. The topLevel stereotype defines the outer limit for looking up names, as namespaces 'see' outwards. For example, opTopLevelubsystem represents the top of the subsystem containment hierarchy.
A dependency that indicates a historical or process relationship between two elements that represent the same concept without specific rules for deriving one from the other.
An object that exists only during the execution of the process or thread that created it.
A relationship between two states indicating that an object in the first state performs certain specified actions and entesr the second state when a specified event occurs and specified conditions are satisfied. On such a change of state, the transition is said to fire.
A stereotyped class that specifies a domain of objects together with the operations applicable to the objects, without defining the physical implementation of those objects. A type can not contain any methods, maintain its own thread of control, or be nested. However, it can have attributes and associations. Although an object can have at most one implementation class, it can conform to multiple different types.
See also: implementation class
An expression that evaluates to a reference to one or more types.