A tag definition is a specification of a new kind of property that can be attached to a model element. This new property provides "metadata" for the model element: This information does not affect the content of the given model.
One or more tagged values contain the actual values associated with a given tag definition.
The following tag definitions have been defined as extensions of the UML for the Unified Process:
 |
flow of events |
|
flow of events-analysis |
|
flow of events-design |
|
implementation requirements |
|
special requirements |
|
survey description |
tagged value
A tagged value is an extensibility mechanism that allows the creation of new information about model elements and presentation elements. (Note that this information applies to an element itself, not its instances.)Each tagged value has a list of values that it can assume. These values must agree with the tag type defined by an associated tag definition.
The term target is a synonym for supplier.
Within the RUP, a target-organization assessment is an artifact that describes the current status of the organization within which the system being modeled will be deployed.
The target-organization assessment is part of the Business Modeling artifact set.
target scope
The target scope of an attribute or an association indicates whether the values of that attribute, or the target values of that association, are instances (this is called instance scope) or classifiers (this is class scope).target state
A target state is a state within a state machine that results from the completion of a transition.
A target state may be a simple state, a substate or a composite state as a whole.
technical writer
Within the RUP, a technical writer is a person playing the role of producing end-user support material, such as user guides, help text, and release notes.
template (RUP)
Within the RUP, a template is a model or a prototype of part or all of an artifact.
template (UML)
A template is also a descriptor for a model element that has one or more formal parameters.
One can create a usable element, such as a class, by doing an explicit or implicit a binding of actual parameters to the template's formal parameters.
|
An explicit binding involves the bind stereotype. |
|
An implicit binding involves declaring a class whose name provides the binding. |
A templateable element is an element that can optionally be defined as a template and bound to other templates.
A templateable element may contain a template signature that specifies the formal arguments for the template.
A template argument is a connection between a binding and a parameter.
A template binding is a directed relationship between a templateable element and a template.
A template binding owns a set of template parameter substitutions, which specify the substitutions of actual parameters for the formal parameters of the template.
A template parameter is an element that exposes a parameterable element as a formal parameter of a template.
template parameter substitution
A template parameter substitution is an element that relates one or more actual parameters to formal parameters as part of a template binding.
A template signature is an element that bundles the set of formal template parameters for a templateable element.
The term terminate refers to a pseudostate that represents the termination of the execution of a state machine.
test analyst
Within the RUP, a test analyst is a person playing the role of identifying and defining the required tests, monitoring the details of testing progress and results during each test cycle, and evaluating overall quality experienced as a result of testing activities.
Within the RUP, the Test artifact set is a set of artifacts related to the testing of a system.
The Test artifact set contains the following artifacts:
| |
| test cases |
| test data |
| |
| |
| |
| test interface specifications |
| test log |
| test plan |
| test results |
| test scripts |
| test strategy |
| test suite |
| workload analysis model |
test case
Within the Unified Process, a test case specifies an element of the system to test (for instance, a use case or a use case realization-design), the conditions under which to execute that test, and the expected input(s) and result(s).
Within the RUP, test cases are part of the Test artifact set.
Within the Unified Process, a test class is a class that represents an abstraction of a class within the system’s test model. Within the RUP, the purpose of the Test discipline is to verify that the implemented system does what it is supposed to do. The following activities comprise the Test discipline:
test component
Within the Unified Process, the term test component is a stereotype attached to a component to signify that the component automates part or all of one or more test procedures.
test designer
Within the RUP, a test designer is a person playing the role of generating the test plan and the test model, implementing the test procedures, and evaluating test coverage, results, and effectiveness.
Test discipline
Achieve Acceptable Mission
Define Evaluation Mission
Improve Test Assets
Test and Evaluate
Validate Build Stability
Verify Test Approach
Within the RUP, a tester is a person playing the role of conducting tests and test assessments.
Test and Evaluate
Within the RUP, Test and Evaluate is an activity within the Test discipline.
This activity involves implementing, executing, and evaluating tests and reporting incidents encountered along the way.
test evaluation
Within the Unified Process, a test evaluation is an evaluation of the results of testing efforts.Within the RUP, a test evaluation summary is part of the Test artifact set.
test idea list
Within the RUP, a test idea list is a list of idea that identify potentially useful tests to conduct.
The test idea list is part of the Test artifact set.
Within the RUP, a test log is a set of raw data captured during the execution of a test suite. Test logs are part of the Test artifact set.
test identity action
A
test log
test manager
Within the RUP, a test manager is a person playing the role of having overall responsibility for the success of the testing effort.
test model
The test model is meant to describe how executable components in the implementation model will be tested in the context of integration testing and system testing.
test plan
Within the Unified Process, a test plan is an artifact that identifies the strategies to be used, and the necessary resources, to implement and execute testing of the new system.test procedure
Within the Unified Process, a test procedure specifies how to perform one or more test cases.test script
Within the RUP, a test script is a manual or automated procedure used to execute one or more tests.
Test scripts are part of the Test artifact set.
test strategy
Within the RUP, a test strategy is a collection of techniques that together will drive the planned test effort.
The test strategy is part of the Test artifact set.
Within the Unified Process, the term test subsystem is a stereotype attached to a subsystem to indicate that the subsystem is used to organize test components within a test model.
A test subsystem can also contain other test subsystems.
test suite
Within the RUP, a test suite is a collection of test scripts.
Test suites are part of the Test artifact set.
test system
Within the Unified Process, the term test system is a stereotype that refers to the top-level package within the test model.Test workflow
Within the Unified Process, the purpose of the Test workflow is to verify that the implemented system does what it is supposed to do.The following activities comprise the Test workflow:
|
Design Test |
| Evaluate Test |
|
Implement Test |
|
Perform Integration Test |
|
Perform System Test |
| Plan Test |
time
The term time refers to an absolute or relative moment in time.
time complexity
The term time complexity refers to the minimum, maximum, and/or average time in which an operation is expected to complete.
A time constraint is a constraint on a time interval.
time event
A time event is an event that occurs when a given time expression is satisfied.time expression
A time expression is an expression that resolves to a time value.A time expression generally involves either elapsed time (using the term after) or an absolute time (using the term when).
A time interval is an interval that defines a range between two time expressions.
time interval
time observation action
A time observation action is a write structural feature action that measures the current point in time.
A time trigger is a trigger that specifies that a behavior execution may be triggered by a specific relative or absolute point in time being reached.
timing constraint
A timing constraint is a constraint that involves an absolute or relative value of time.A timing diagram is an interaction diagram that describes the behavior of both individual classifiers and interactions of classifiers, focusing attention on the times of occurrence of events that cause changes in state.
timing mark
A timing mark is a denotation of the specific time at which a given event or message occurs.A token is an object, a piece of data, or a locus of control within an activity.
token
tool specialist
Within the RUP, a tool specialist is a person playing the role of being responsible for the tools that support the development effort.top-level subsystem
Within the Unified Process, the term top-level subsystem is a stereotype attached to a subsystem to signify that the subsystem represents the system itself.A trace is an abstraction that represents a conceptual connection among elements contained within different models (and thus, generally, different levels of abstraction).
One models a trace with the use of the trace stereotype.
trace (event)
The term trace also refers to a sequence of event occurrences.
The term trace also refers to a stereotype that signifies a trace.
transient link
A transient link is a link that exists only for a limited duration (for instance, during the execution of an operation).transient object
A transient object is an object that exists only during the lifetime of the thread that created it.transition
A transition is a directed relationship between a source vertex and a target vertex.
The term transition kind refers to an enumeration whose values specify various types of transitions. These values include the following:
| |
| |
|
|
transition phase
Within the Unified Process, the transition phase is the phase of a development project in which the new system is rolled out into the user community.
The primary goal of this phase is to reach the point at which the system is recognized as matching the criteria specified by the vision. A trigger is a specification that an event may cause the execution of an associated behavior. There are three basic kinds of triggers:
transition time
The term transition time is a synonym of timing mark.
trigger
| change trigger |
| message trigger |
|
triggerless transition
A triggerless transition is a transition that does not have an explicit trigger.
When a triggerless transition is coming from a normal state, it is a completion transition.
A tuple is a group of one or more tuple parts.
tuple
A tuple part is a pairing of a name and a type within a tuple.
type
The term type is a stereotype attached to a class to signify that the class specifies a set of values that serves as a constraint on one or more typed elements.A typed element is a named element of a particular type.
type expression
A type expression is an expression that resolves to a reference to one or more types.
