Issue 14435: Meta class BehaviorScenario not synchronized with its representation (marte-rtf)
Source: Commissariat a l Energie Atomique-CEA (Dr. Sebastien Gerard, sebastien.gerard(at)cea.fr)
Nature: Clarification
Severity: Minor
Summary: The description of the Meta class BehaviorScenario is not synchronized with its representation in diagramm shown in FIgure 15.3. As for example, associations called steps in the diagram and called Actions in section F.10.13 (idem issue with assoc labelled inputstream in the section F.10.3 and called cause in diagram 15.3).
Resolution: 
Revised Text: 
Actions taken:
September 28, 2009: received issue
January 14, 2011: closed issue
Discussion: 
This issue ovelaps with 15073 which also revises the BehaviourScenario
definition, so the changes were combined there.
The changes in that resolution, prompted by this issue, are:
In Section F10.3:
• association Actions renamed steps (consistent with Fig 15.3)
• association usedResources dropped (not in Fig. 15.3)
• association inputStream renamed cause (consisten with fig 15.3)
• association connectors added (consistent with Fig 15.3)
• attribute priority dropped (it occurs on Step)(consistent with chapter 15)
Disposition: See issue {15073} for disposition
End of Annotations:=====

m: webmaster@omg.org
Date: 28 Sep 2009 06:02:56 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          Sebastien Gerard
Company:       CEA LIST
mailFrom:      sebastien.gerard@cea.fr
Notification:  Yes
Specification: MARTE Beta 3
Section:       section F.10.13
FormalNumber:  ptc/2009-05-13
Version:       Beta 3
RevisionDate:  June 2009
Page:          709
Title:         Meta class BehaviorScenario not synchronized with its representation
Nature:        Clarification
Severity:      Minor
test:          3qw8
B1:            Report Issue


Description:

The description of the Meta class BehaviorScenario is not synchronized with its representation in diagramm shown in FIgure 15.3. As for example, associations called steps in the diagram and called Actions in section F.10.13 (idem issue with assoc labelled inputstream in the section F.10.3 and called cause in diagram 15.3).