OpenOME
Table of contents
- OpenOME
- General Information
- i* Modelling Suitability
- 1. Does the tool allow SD modelling?
- 2. Does the tool allow SR modelling?
- 3. Does the tool allow working with SD & SR models jointly?
- 4. Does the tool allow the construction of the models graphically?
- 5. Does the tool allow the construction of the models textually?
- 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?
- 9. Other modelling facilities provided by the tool:
- 10. Does the tool check SD models?
- 11. Does the tool check SR models?
- 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?
- 14. Does the tool allow to group models in projects?
- 15. Does the tool allow working with two or more projects at the same time?
- 16. What are the other functionalities that the tool provides?
- Usability
- Maturity of the Tool
- 22. Rate the maturity of the tool from the user point of view:
- 23. Has the tool been used for any case study?
- 24. Has the tool been tested in large models?
- 25. Has the tool any drawback when working with very large models?
- 26. Which is approximately the maximum size of the model (in terms of actors and dependencies) the tool has been used for?
- Extensibility and Interoperability
- 27. Does the tool allow importing files?
- 28. Does the tool allow exporting files?
- 29. Does the tool allow importing/exporting the data through an XML format?
- 30. Is the architecture of the tool published?
- 31. Does the tool allow the addition of other elements outside the i* framework of the tool?
- 32. New functionalities can be added to the tool by means of:
- 33. Rate the maturity of the tool from for open development:
- 34. Is there any internal documentation for programmers?
General Information
Tool Name
OpenOMEVersion
TBDGroup
The University of TorontoWeb page (if available)
https://se.cs.toronto.edu/trac/ome/Main Purpose of the Tool
OpenOME is an Eclipse-based tool designed to be a goal-oriented and/or agent-oriented modeling and analysis tool.The Open in OpenOME represents its open source nature. Various researchers are expanding the basic functionality of OpenOME. Researchers are welcome to propose further branches and extensions to the tool.
i* framework supported
Yu'97Availability of the tool
- ( ) For i* modelling only
- ( ) For development only
- (X) Both
Programming Language
JavaPlatform Requirements
Windows/Linux/MacOther technology needed
Current state of the tool
Woking versions are available to download on sourceforge, and new versions will be released continuously.Ongoing work
- Improve the usability and functionality of the tool.
- Improve analysis functionality
- Improve interoperability with q7 language
i* Modelling Suitability
1. Does the tool allow SD modelling?
Yes2. Does the tool allow SR modelling?
Yes3. Does the tool allow working with SD & SR models jointly?
YesIf so, please specify how (i.e., by means of expandable elements).
By means of expandable elements (as in OME)
4. Does the tool allow the construction of the models graphically?
YesIf so, please specify how (i.e., dragging and dropping the elements into a drawing page)
To construct an element, click an element symbol on the menu bar and click the position in the drawing page where the element should locate. To draw a link element, click a link symbol on the menu bar and click in the drawing page the two end elements which the link is supposed to connect.
5. Does the tool allow the construction of the models textually?
YesIf so, please specify how (i.e., filling a dependency table).
Editing a textual file in the Q7 syntax then load it into the graph editor to construct an initial model; saving a graph into the Q7 syntax is also supported.
6. Describe how the elements are modelled and their flexibility (i.e., the elements can be moved and reordered).
Users can change the name, size and type of an element. The element can also be moved, reordered, deleted, copied, pasted, highlighted, and labelled with a symbolic attribute. All these actions are done graphically and by commands either on the menu bar or pop-up command window.7. Describe how the dependency links are modelled and their flexibility (i.e., dependencies are modelled with straight lines that can not be redirected).
Dependency links can be drawn from the palette. The link can also be moved, reordered, deleted, copied, pasted, and highlighted. The link is modelled with straight line that can be curved and redirected. Curved links can also be straightened.8. Does the tool allow automatic organization of the elements?
Yes. The tool provides a basic graph layout function.9. Other modelling facilities provided by the tool:
- Forward and backward qualitative interactive i* analysis
- Can push an element into or move it from an expandable element
10. Does the tool check SD models?
NoIf so, please specify how (i.e., the tool checks if all the SD dependencies are assigned).
11. Does the tool check SR models?
NoIf so, please specify how (i.e., checks if the SR links are correctly stated).
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?
Yes. Since OpenOME can be operated as a plug-in of Eclipse, Eclipse allows OpenOME to open multiple models at the same time.14. Does the tool allow to group models in projects?
Yes. Since OpenOME can be operated as a plug-in of Eclipse, Eclipse navigator allows classifying models into different physical folders.15. Does the tool allow working with two or more projects at the same time?
Yes. Same as 13, 14.16. What are the other functionalities that the tool provides?
- Support Q7 representation
Usability
17. Rate the understandability of the user interface
- () Internal use
- () Ready for public use
- (X) Has been used publicly with little learning curve
- ( ) not in English
- ( ) writing not polished
- ( ) poor usability (colours, ...)
- ( ) others: please specify
18. Rate the quality of the user manual
- ( ) Inexistent
- ( ) Internal use
- ( ) Ready for public use
- (X) Has been used publicly, but still under improvement
- ( ) incomplete
- ( ) obsolete
- ( ) not in English
- ( ) writing not polished
- ( ) others: please specify
19. Does the tool provides i* learning facilities?
NoIf so, explain which ones (i.e., methodological guidance).
20. Does the tool provide any examples for the users?
Yes. The user's guide on the website provides examples of the major functionalities of the tool. In the tool itself, there are also model examples.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
- ( ) Ready for public use
- (X) Has been used publicly
- ( ) incomplete
- ( ) occasional testing
- ( ) non-exhaustive testing
- ( ) non-persistent data
- ( ) poor efficiency
- ( ) not portable
- ( ) others: please specify
23. Has the tool been used for any case study?
YesIf so, specify which ones.
- Kids Help Phone Project
- Analysis user studies
24. Has the tool been tested in large models?
Yes25. Has the tool any drawback when working with very large models?
YesIf so, which ones?
- Backwards analysis can be slow over large models
26. Which is approximately the maximum size of the model (in terms of actors and dependencies) the tool has been used for?
20 actors, 132 elements, and 217 links.Extensibility and Interoperability
27. Does the tool allow importing files?
YesIf so, specify import data formats (i.e., XML, text file, pictures of the graphical representation...)
- q7 files
28. Does the tool allow exporting files?
YesIf so, specify import data formats (i.e., XML, text file, pictures of the graphical representation...)
- q7 files
- .png (picture of graphical representation)
29. Does the tool allow importing/exporting the data through an XML format?
Yes, the default representation is in and EMF-created XML file.If so, link to the DTD for the XML format if available.
N/A
30. Is the architecture of the tool published?
NoIf so, where?
31. Does the tool allow the addition of other elements outside the i* framework of the tool?
Yes32. New functionalities can be added to the tool by means of:
- (X) PLUG-IN: Add new plugins for Eclipse to create new ways of using the OME plugin
- (X) Open-Source code:Modify Open-Source code of OpenOME
- ( ) import & export XML
- ( ) NONE
33. Rate the maturity of the tool from for open development:
- ( ) Under Development
- ( ) Prototype
- ( ) Ready for public development use
- (X) Has been used for public development
- ( ) incomplete code
- ( ) no help provided
- ( ) non-persistent data
- ( ) non-exhaustive testing
- ( ) poor efficiency
- ( ) not portable
- ( ) no development installation facilities provided
- ( ) others: please specify
34. Is there any internal documentation for programmers?
YesIf so, enumerate the facilities provided
- ( ) Requirements specification and design decisions available
- ( ) Interface conventions
- ( ) Code conventions
- (X) Full commented code
- ( ) Examples
- (X) others: please specify Development tickets available here