TAOM4E: an Eclipse ready tool for Agent-Oriented ... - FBK | SE

More documents

Recommendations

Info

Fig. 9. EMF Architecture, see [23] Fig. 10. An high-level view of the TAOM4E meta-model. meta-model has been divided into two logical area: business model (Core) and view (Diagram). The first should contain only the schema of the data (semantic information) that are related to the Tropos meta-model. It define packages/classes etc. related to the methodology concept without referring the diagram section. The second area is concerned with defining what is called the view model: it contains all the graphical information that define a graphical diagram (a view on the model) with the necessary link to the core model elements. This solution decouple model element from view ones. A third utility area (Project) has been defined in order to better manage the different artifact produced by the activity conducted during the various phases of the methodology supported by the tool.
The three high-level packages composing the meta-model are depicted in Figure 10: 1. The Project package (Figure 11) define the concept of Project as an aggregation of different Diagrams (i.e. actor diagram and goal diagram) that are related to a BusinessModel (namely the Tropos meta-model). This package serves as an aggregator of all the data related to a Tropos Project into a single logical structure that will be saved into an xmi document, avoiding synchronization problem of the different component with the shared model. Fig. 11. Project package of the TAOM4E meta-model. 2. The Diagram package (Figure 12) define the structure and the relationship of the graphical element that will be used in the different diagrams. The GenDiagram package define the generic structure of a diagram supported by the tool (Diagram) as an aggregation of different kind of DiagramObject (namely DiagramConnection and DiagramNode) representing graphical connection and graphical element respectivly. A special kind of node object (ContainerDiagramNode) is created in order to manage containment relationship between graphical element (i.e. the Actor container in the Goal Diagram). Every DiagramObject could be related to the core element/s it is representing (an instance of TroposModelElement). Given that structure in place representing a particular kind of diagram is a matter of creating a new package defining the graphical element as extension of the one already present in GenDiagram. At the moment we support two Tropos diagrams, namely actor and goal diagram. The main objective of this packages (and all its sub-ones) is to create a view on the different element of the model that could be persisted in an xmi file maintaing a clear separation and indipendence beetween the different layer 3. The Core packages (Figure 13) mimic the structure used in the Diagram one in order to define the core model of the tool hosting the Tropos meta-model. The GenCore package define a model (BusinessModel) has an aggregation of different kind of TroposModelElement namely TroposClass and TroposRelation object that map respectively to an element and a relation defined in the Tropos meta-model. The InformalCore package contain the definition of the element representing the Tropos meta-model (i.e. Actor, Goal, Dependency, Contribution). The twin pack-
Page 1 and 2: TAOM4E: an Eclipse ready tool for A
Page 3 and 4: a set of relationships between them
Page 5 and 6: 3 Tool Requirements A core set of r
Page 7 and 8: j) Export the diagrams in the pictu
Page 9 and 10: Fig. 5. Eclipse Plug-in interconnec
Page 11: 1. Model: the framework is model ag
Page 15 and 16: Fig. 13. Core package of the TAOM4E
Page 17 and 18: 23. Ed Merks. The eclipse modeling
Page 24 and 25: Appendix B: TAOM4E meta-model diagr
Page 26 and 27: Fig. 15. The Project package.
Page 28 and 29: Fig. 17. The ActorDiagram package.
Page 30 and 31: Fig. 19. The GenCore package.
Page 32 and 33: Fig. 21. The FormalCore package.

TAOM4E: an Eclipse ready tool for Agent-Oriented ... - FBK | SE

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?