[aadl-modeling]: Delcarative AADL-Model according to Annex C

[Peter Feiler]

In OSATE2 we use XText, which converts the textual declarative AADL file into the in-core XMI representation, i.e., according to the Ecore Meta model specification for AADL. You can operate on it the same way you would after an XMI-based file is read in. If you need to process the XMI representation from a file you can save the in-core representation as XMI by creating an XMI resource object with an extension other than aadl and moving the in-memory content from the original resource into it.

From: aadl-modeling-bounces+phf=sei.cmu.edu at lists.sei.cmu.edu [mailto:aadl-modeling-bounces+phf=sei.cmu.edu at lists.sei.cmu.edu] On Behalf Of Daniel Tigges
Sent: Tuesday, August 21, 2018 5:14 AM
To: aadl-modeling at lists.sei.cmu.edu
Subject: [aadl-modeling]: Delcarative AADL-Model according to Annex C

Hello,

according to AS5506/1 - Annex C "AADL Meta Model and Interchange Formats" there exist three model representations and persistent XML formats of AADL (see page 24 of Annex C). The connections between these models is shown in the figure below (also from Annex C).[image.png]

In OSATE2, I can instantiate the "AADL Instance Model" from an existing "Textual AADL". That creates an *.aaxl2 xml-File which I can process further. The problem is however, that I can't get the "Declarative AADL Model" generated with OSATE2. The only thing is can use is the "Textual AADL" which in my case is insufficient. I need an XML representation of the "Declarative AADL Model". Is it possible to get a XML representation of the "Declarative AADL Model"?


Thanks in advance,
Daniel
-------------- next part --------------
HTML attachment scrubbed and removed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 87228 bytes
Desc: image002.jpg
URL: <http://lists.sei.cmu.edu/pipermail/aadl-modeling/attachments/20180821/7929c2d2/attachment.jpg>