[aadl]: The flow implementation in Osate 2.0.8

[Peter Feiler]

The tool just enforces what the standard says.
The standard currently requires the different sections of a component type or implementation to be in a fixed order.
We can consider relaxing this rule in the standard in the next revision or as an errata.

Peter

From: Zhibin Yang [mailto:zhibinyang168 at gmail.com]
Sent: Thursday, December 11, 2014 10:01 AM
To: Lewis, Bruce CIV (US); Peter Feiler; Julien Delange; Jerome.HUGUES at isae.fr; sae-aadl-users at lists.sei.cmu.edu
Subject: The flow implementation in Osate 2.0.8

Dear Profs. Lewis Bruce, Peter Feiler, Julien Delange, and Jerome  HUGUES,

When we define a flow implementation, we find that the "flows" term must be defined before the "properties" term, otherwise, the Osate tool says "Not allowed: flows".

1. the correct one
[Inline image 2]

2: the incorrect one
[Inline image 1]

The tool is Osate 2.0.8. Actually, it is not a problem, but may be (a little) not so friendly.

Thanks a lot.

Zhibin Yang
with Mamoun, and Jean Paul

IRIT


-------------- next part --------------
HTML attachment scrubbed and removed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 65394 bytes
Desc: image001.png
URL: <http://lists.sei.cmu.edu/pipermail/sae-aadl-users/attachments/20141211/3fa70f06/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 62437 bytes
Desc: image002.png
URL: <http://lists.sei.cmu.edu/pipermail/sae-aadl-users/attachments/20141211/3fa70f06/attachment-0003.png>