A4WSN is a solution that combines multiple metamodels (SAML, NODEML, ENVML, and weaving metamodels) into a single A4WSN metamodel. This allows models that conform to the individual metamodels to be integrated into a single model representing the entire architecture. Previously, managing different conforming models separately did not provide a unified view. The A4WSN transformation defines rules to integrate the five artifact models into a single model under the A4WSN metamodel. This transformation was generated using a higher-order transformation to solve the problems of manually defining the rules and dealing with model (co)evolution issues.

1. A4WSN - HOT
1° Part

2. What ‘s A4WSN ?
As you know, me4awsn is composed of
several meta-models:
O SAML
O NODEML
O ENVML
O WEAVING MetaModels
MAPPING between
SA and NODE
DEPLOYMENT between
Node and Env

3. ME4AWSN MetaModels

4. ME4AWSN Weaving MetaModels

5. What ‘s A4WSN ?
What if i want to manage differents models
together, in order to have a unique model
rapresenting the whole architecture ?
I have different models conform to each related
metamodels (e.g. a SA model is conform SAML
MetaModel) …
… In this case, i haven’t a cleanly unique view
of the whole architecture

6. What’s A4WSN ? Solution
Our solution is to combine all the
metamodels previously seen, by defining a
new metamodel:
The A4WSN MetaModel

7. A4WSN: Metamodel
O The 3 metamodels remain the same (are
simply included as sub packages)

8. A4WSN: Metamodel
O The weaving models are modified: they
don’t include the Weaving Model part

9. A4WSN: Metamodel
O The specification parts allows to refer to
the various subpackages, giving an
organization of the whole architecture

10. A4WSN Metamodel
O Ok, but now how can i use it ?
O Have i to rewrite a new model, conformant
to the A4WSN metamodel?
.. Obviously not!
O We have defined an ATL
transformation, that aims to integrate the 5
artifacts

11. A4WSN Transformation
wsnmeTOa4wsn.atl

12. A4WSN - HOT
O How to write this transformation?
By hands .. No
O How to solve it? A solution can be an
Higher Order Transformation
To big !
(Co)Evolution Problem !

13. A4WSN-Hot.atl
SAML
ENVML
NODEML
MAPPING
DEPLOYMENT
Transformation.ecore
output

14. Using the AMMA platform
Extracting Model
On the Transformation.ecore we select

15. A4WSN - InAction
O Now we can play the video showing how
to interact with the tool
VIDEO

16. A4WSN HOT – In Detail
O For the first three metamodels, we have
generated rules the simply map elements form
the source metamodel toward the A4WSN
metamodels
Figure : The ComponentRule of Component in SAML

17. A4WSN HOT – In Detail
O In case of weaving models, we’ve some
problems

18. A4WSN HOT – In Detail
O In the weaving models we don’t have the
type of referred element
 Annotation

19. A4WSN HOT – In Detail
O In this case, we’ve to resolve weaving
reference with ‘real’ pointer
O You can find a different solution for the
collection case

20. The End
Thanks for your
attention
