Issue 14865: FLOW : MARTE and AADL alignment (marte-rtf) Source: THALES (Dr. Madeleine Faugere, madeleine.faugere(at)thalesgroup.com) Nature: Clarification Severity: Significant Summary: The AADL flow path implementation semantics is not in line with MARTE mapping proposition. The AADL flow path declaration and implementation mapping need to be rethink Resolution: AADL flow semantics has been introduced to specify information transmission (data/event) over connection and subcomponent, covering the whole component and subcomponent hierarchy. This aspect is complementary to the structural one. Declaration flow paths links flow sources to flow sinks of components in a black boxes approach. Implementation flow paths specify the way this information is convey over connections and flow paths. End-to-end flows represent a logical flow of data and control from a source to a destination through the system instance, meaning a sequence of threads that process and possibly transform the data. The corresponding end-to-end flow instance is determined by expanding the flow specifications through their flow implementations. As UML/MARTE concepts makes a full distinction between logical and structural aspects, and while AADL manipulates them jointly, different and not full satisfying solutions can be provided to represent AADL flows and end-to-end-flows. • UML sequence diagrams, using message exchanges between instances and associated ports • UML activity diagrams, more focusing on actions and their associated control flow. Flow path declaration representation will stay unmodified, using the UML “InformationFlow” concept. Flow path implementation will be represented in a sequence diagram, using UML “GeneralOrdering” elements to keep order preservation between messages received and sent over the ports, UML “Messages” will be used to represent communication between instances. The Name of the GeneralOrdering element will make reference to the FlowPath declaration; the name of the message will make reference to the connection conveying it. To provide a representative distinction and to avoid code generation ambiguity between end-to-end flow and flow implementation representations, both represented as sequence diagrams, the first one will be stereotyped “end-to-end flow”, the second one, will have the suffix: Flowname_flow_impl. AADL flow sinks and flow sources can’t be represented in UML/MARTE. Revised Text: Section A.2.8 Flow specification declaration paragraph: The following sentence will be added after the figure “AADL flow sinks and flow sources can’t be explicitly modelized in UML/MARTE” Flow specification implementation paragraph: Flow entire specification implementation paragraph will be replaced by the following: A flow-implementation declaration in a component implementation specifies how a flow specification is realized in this implementation: as a sequence of flows through subsystems (i.e., subcomponents) along connections from the flowspecification inport to the flow specification outport. Since flows are realized when code is executed, processes and threads must be considered. An UML interaction diagram will be used to represent the flow path implementation. The name of the Interaction diagram will make reference to the flow path name completed with the suffixe “flow.impl”. Instances will be represented with input and output ports, UML “GeneralOrdering” elements keeping order preservation in mind will be used to represent flow path declarations inside components, UML “Messages” will be used to represent communication between instances. To be in line with the structural AADL semantics, the name of the GeneralOrdering element will make reference to the flow path declaration; the name of the message will make reference to the connection conveying it. <<<see page 46 of ptc/2010-08-30 for graphic>>> Actions taken: December 15, 2009: received issue January 14, 2011: closed issue Discussion: End of Annotations:===== te: Tue, 15 Dec 2009 16:20:11 +0100 From: Madeleine FAUGERE User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) To: issues@omg.org Subject: MARTE AADL mapping issue FLOW : MARTE and AADL alignment The AADL flow path implementation semantics is not in line with MARTE mapping proposition. The AADL flow path declaration and implementation mapping need to be rethink Madeleine -- Madeleine Faugere Embedded Systems Lab THALES Research and Technology Software Research Group 1, avenue Augustin Fresnel 91767 Palaiseau Cedex 91767 Palaiseau Cedex - France Tel: +33 (0)1 69 41 60 43 email : madeleine.faugere@thalesgroup.com The information contained in this e-mail/fax and any attachments are the property of THALES and may be confidential. If you are not the intended recipient, please notify us immediately, send this message back to us and destroy it. You are hereby notified that any review, dissemination, distribution, copying or otherwise use of this e-mail/fax is strictly prohibited