Issue 10962: Variability in notation (voice-ftf)
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: 
Summary: Allow usage of activity diagrams as alternative to state machine 
when not available
Resolution: After section 9.2 Stereotypes of the UML Voice Profile, add a section: "Using Activity diagrams to represent dialog behavior" with the following content.

For more flexibility in the implementation, the dialog behavior which, from a semantic point of view is defined by a state machine, can however be rendered by an activity diagram following some conventions.
 
When this variation in notation is used the following mappings should apply:

-	An ActivityGraph replaces a StateMachine.
-	A InitialNode replaces a Pseudostate with kind=initial
-	A DecisionNode replaces a Pseudostate with kind=choice
-	A  MergeNode replaces  a Pseudostate with kind=junction
-	An ActivityFinalNode replaces a FinalState
-	An Action replaces a State


 The base classes for the stereotypes are changed according to these mappings.

Revised Text: 
Actions taken:
April 20, 2007: received issue
November 7, 2007: closed issue
Discussion: 
The UML2 transition-oriented notation for state-machines which is appropriate to render voice dialogs is not yet widely implemented by UML tools. The activity diagram notation, which renders closely like the transition-oriented notation, is in constrast widely supported.
End of Annotations:=====
s is issue # 10962

Variability in notation

Allow usage of activity diagrams as alternative to state machine 
when not available