Issues for Mailing list of the UML testing Profile Revision Task Force

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 9797: Section: 6.3.2 Test Behavior
Issue 9798: Section: 6.3.2 Test Behavior, FinishAction
Issue 9799: Section: 6.3.3 Test Data, CodingRule

Issue 9797: Section: 6.3.2 Test Behavior (uml-testing-profile-rtf)

Default chapter, Notation section (p.28): “a default is behavior and has no special notation”. DefaultApplication chapter, Description section (p.28): “a default application is a dependency used to apply a default behavior to a unit of test component”. However, in Notation section of DefaultApplication chapter there is written that default should be represented as comment. The same notation is used in examples on Figures 29 and 31. Since information in Default and DefaultApplication chapters contradicts each other we need clarification what notation should be used for Default and DefaultApplication. Also it is unclear how repeat and continue parameters should be represented. According to UML specification the detailed semantics of behavior is determined by it subtypes. Each subtype (Interaction, Activity, StateMachine) has it own notation. Since Default can also be described on Interaction, Activity or StateMachine the most convenient notation for Default would be behavior subtype notation with <<Default>> stereotype and for DefaultApplication – dependency with stereotype <<DefaultApplication>>. 

<<FinishAction>> stereotype extends Action metaclass. However FinishAction chapter, Notation section specifies how FinishAction should be represented on Activity, Interaction and StateMachine diagrams. In that case we have conflict with UML 2.0 specification: according to UML specification actions cannot be used on Interaction and StateMachine diagrams. Actually for interactions UML 2.0 defines ActionExecutionSpecification that specifies execution of action within the Lifeline. However, then <<FinishAction>> stereotype should extend ActionExecutionSpecification metaclass. 

UML Testing Profile defines that “the notation for coding rule is identical to a comment in UML”. Can coding rule be displayed as stereotype attribute (tagged value) using notation given by UML 2.0 specification?