UTP11 — Continuation information of DefaultApplication should be formalized as model concepts

UTP specification, section 6.4.2 Test Behavior, subsection DefaultApplication (p.19) say the following:
"A default application is a dependency used to apply a default behavior to a unit of testing on a test component. That unit of test behavior must be one of the following: Package, Classifier, Behavior, InteractionFragment, State, Region, or Activity."

Additionally, subsubsection Notation says the following:
"The notation for a default is identical to a Comment (i.e., a rectangle with a bent corner). The text in the comment symbol has the following syntax:
default default-identifier [continue | repeat [repetition-count] ]
If nothing is given following the default identifier, continue is assumed. If no repetition-count is given, infinity is assumed."

Description
##########################################
The information, given in the notation section, determine how to proceed if a applied default is executed. Continue means that the process flow will continue after the behavior of the default was executed once. In contrast, repeat indicates the number of re-invocations of the default, in a case, when a previous execution has not matched.
Those information are crucial parts of «DefaultApplication», hence, introducing them just as a remark in the notation section is not enough. Since the continuation information are currently just defined as “textual syntax”, meaning, there are no metamodel concepts for expressing the continuation behavior, it is not clear where (to what property of the extended metaclass “Dependency”) to add these information. Additionally, a parser is required to obtain the information from the text.
To easy both the applicability and understandability those information should be part of «DefaultApplication» as property. By doing so, access to the information is easy to get and to evaluate.

Introduce a repetition attribute that determines the number of repetitions of the default behavior. The default value is unlimited .
For further formalization a new constraint will be introduced, stating the target of the default application must be a behavior marked as <<Default>>.