TAGOOn+ Tool

Description

TAGOOn+ is a tool for the generation and integration of organizational ontologies that supports: 1) the automatic generation of organizational ontologies coming from models expressed with i*, Tropos and Service-Oriented i*, and 2) the automatic integration of those organizational ontologies with generic or domain ontologies.

Tool Name

TAGOOn+: Tool for the Automatic Generation of Organizational Ontologies and Integration

Versión

1.0

Group

Date Tool Template Last Updated

04/09/2013

Web page (if available)

http://www.tagoon.semanticbuilder.com/

Main Purpose of the Tool

1) It supports the automatic generation of organizational ontologies coming from organizational models expressed with i*, Tropos and Service-Oriented i* (as part of our proposed methodology for integrating i* variants). In order to carry out the ontology generation, the ontological metamodel for these variants (OntoiStar+) has been developed. Model-Driven Engineering (MDE) ideas have been
applied to perform the transformation from organizational models (described in the iStarML format) to ontologies derived from OntoiStar+.

2) It supports the automatic integration of enriched organizational models with generic or domain ontologies (as part of our proposed methodology for enriching organizational models with semantic annotations). In order to carry out the integration, semantic annotation suggestions have been proposed, which are the guidelines to annotate organizational models with concepts from generic
or domain ontologies. The iStarML format has been extended with the attribute “sannotation” to store semantic annotations for each model element.

i* framework supported

i*, Tropos and Service oriented i*

Availability of the tool

• (x) For i* models to ontology transformation
• (x) For i* models integration with generic or domain ontologies

Programming Language

Java

Platform Requirements

Windows/Linux/Mac

Other technology needed

Current state of the tool

Woking versions are available to download on http://www.tagoon.semanticbuilder.com/, and new versions will be released continuously.

Ongoing work

i* Modelling Suitability

1. Does the tool allow SD modelling?

Yes

2. Does the tool allow SR modelling?

Yes

3. Does the tool allow working with SD & SR models jointly?

Yes, the input is the model in the iStarML format which can describe the SD and Sr models jointly

4. Does the tool allow the construction of the models graphically?

No, but the user can generate the model with tools that allows to export the model in the iStarML format.

5. Does the tool allow the construction of the models textually?

No, the input is the model in the iStarML format

6. Describe how the elements are modelled and their flexibility (i.e., the elements can be moved and reordered).

7. Describe how the dependency links are modelled and their flexibility (i.e., dependencies are modelled with straight lines that can not be redirected).

8. Does the tool allow automatic organization of the elements?

No

9. Other modelling facilities provided by the tool:

• ...

10. Does the tool check SD models?

Yes, with the CCistarML java package provided by the iStarML specification that check the consistency of the model described in the iStarML format.

11. Does the tool check SR models?

Yes, with the CCistarML java package provided by the iStarML specification that check the consistency of the model described in the iStarML format.

12. Other checks provided by the tool (i.e., cross validation between SD and SR models).

• ...

13. Does the tool allow working with two or more models at the same time?

No

14. Does the tool allow to group models in projects?

No

15. Does the tool allow working with two or more projects at the same time?

No

16. What are the other functionalities that the tool provides?

Usability

17. Rate the understandability of the user interface

• ( ) Internal use
• (x) Ready for public use
• ( ) Has been used publicly

If it is not ready for public use, mark one or more of the following:

• ( ) not in English
• ( ) writing not polished
• ( ) poor usability (colours, ...)
• ( ) others: please specify

Expected date for public use (if any):

18. Rate the quality of the user manual

• ( ) Inexistent
• ( ) Internal use
• (x) Ready for public use
• ( ) Has been used publicly

If user manual for internal use, mark one or more of the following:

• ( ) incomplete
• ( ) obsolete
• ( ) not in English
• ( ) writing not polished
• ( ) others: please specify

Expected date for public use (if any):

19. Does the tool provides i* learning facilities?

No

20. Does the tool provide any examples for the users?

Yes, examples and case studies

21. Rate the difficulty of installing the tool

• ( ) Copy files and initializing paths
• ( ) Copy files
• (x) Executable installation file provided

Maturity of the Tool

22. Rate the maturity of the tool from the user point of view:

• ( ) Under Development
• ( ) Prototype
• (x) Ready for public use
• ( ) Has been used publicly

If not for public use, mark one or more of the following:

• ( ) incomplete
• ( ) occasional testing
• ( ) non-exhaustive testing
• ( ) non-persistent data
• ( ) poor efficiency
• ( ) not portable
• ( ) others: please specify

Expected date for public use (if any):

23. Has the tool been used for any case study?

Yes
If so, specify which ones.

24. Has the tool been tested in large models?

Yes

25. Has the tool any drawback when working with very large models?

No
If so, which ones?

26. Which is approximately the maximum size of the model (in terms of actors and dependencies) the tool has been used for?

14 actors
45 dependencies
117 Internal elements

Extensibility and Interoperability

27. Does the tool allow importing files?

No, the input is an i* model described in the iStarML format.

28. Does the tool allow exporting files?

No, the output is an OWL file with the ontological representation of the i* model.

29. Does the tool allow importing/exporting the data through an XML format?

No

30. Is the architecture of the tool published?

Yes on http://www.tagoon.semanticbuilder.com/

31. Does the tool allow the addition of other elements outside the i* framework of the tool?

Yes, elements from Tropos and Service oriented i*.

32. New functionalities can be added to the tool by means of:

• ( ) PLUG-IN
• (x) Open-Source code
• ( ) import & export XML
• ( ) NONE

33. Rate the maturity of the tool from for open development:

• ( ) Under Development
• ( ) Prototype
• ( ) Ready for public development use
• ( ) Has been used for public development

If not for public development use, mark one or more of the following:

• ( ) incomplete code
• ( ) no help provided
• ( ) non-persistent data
• ( ) non-exhaustive testing
• ( ) poor efficiency
• ( ) not portable
• ( ) no development installation facilities provided
• ( ) others: please specify

Expected date for public development use (if any):

34. Is there any internal documentation for programmers?

Yes / No
If so, enumerate the facilities provided

• ( ) Requirements specification and design decisions available
• ( ) Interface conventions
• ( ) Code conventions
• ( ) Full commented code
• ( ) Examples
• ( ) others: please specify