Issue 9797: Section: 6.3.2 Test Behavior (uml-testing-profile-rtf) Source: (, ) Nature: Clarification Severity: Significant Summary: 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>>. Resolution: Revised Text: Actions taken: May 29, 2006: received issue May 29, 2006: received issue October 21, 2011: closed issue Discussion: This issue is a subset of the more comprehensive issues 15771. Disposition: See issue 15771 for disposition End of Annotations:===== m: webmaster@omg.org Date: 29 May 2006 09:33:19 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Jolita Mackiene Company: No Magic, Inc. mailFrom: jolita.mackiene@nomagic.com Notification: Yes Specification: UML: Testing Profile Section: 6.3.2 Test Behavior FormalNumber: ptc Version: 2.0 RevisionDate: 04/04/2004 Page: 27 - 29 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; .NET CLR 2.0.50727) Description 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 <> stereotype and for DefaultApplication . dependency with stereotype <>.