OME

General Information

Tool Name

OME

Version

3.13

Group

The University of Toronto

Web page (if available)

http://www.cs.toronto.edu/km/ome/

Main Purpose of the Tool

A graph editor to support goal-oriented and/or agent-oriented modeling.

i* framework supported

Yu PhD Thesis, Yu RE'97

Availability of the tool

• (X) For i* modelling only
• ( ) For development only
• ( ) Both

If not available, please specify expected date of availability: Already available

Programming Language

Java

Platform Requirements

Windows

Other technology needed

none

Current state of the tool

Working version are available to download on the website, new versions will be released continuously.

Ongoing work

Improving the performance of the tool, improving usability of the tool, bulidng web server for i* model sharing.

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
If so, please specify how (i.e., by means of expandable elements).
By means of expandable elements. The tool allows you to expand/contract an individual expandable node or all expandable nodes at once.

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

Yes
If 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 be located. To draw a link element, click a link symbol on the menu bar and click in the drawing page on the two end element that the link should connect.

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

No
If so, please specify how (i.e., filling a dependency table).
N/A

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 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).

Users can change the size and type of a dependency link. The link can also be moved, reordered, deleted, copied, pasted, and highlighted. The link is modelled with astraight line that can be curved and rediredcted. Curved links can also be straightened.

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

No

9. Other modelling facilities provided by the tool:

• Can hide or unhide an element
• Can push an element into or move it from and expandable element
• Propagation of reasoning labels interactively

10. Does the tool check SD models?

No
If so, please specify how (i.e., the tool checks if all the SD dependencies are assigned).

11. Does the tool check SR models?

No
If 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).

N/A

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

Yes

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

Yes

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

Yes

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

• The tool allows extensions and modifications to the i* framework.
• The tool allows combined use of multiple frameworks, e.g. i* + Annotation, i* + ER, etc.
• The tool allows exporting of graphs as .png files, which may be further edited in a graphic tool iview. For instance, to crop the blank margins off.
• The tool allows the selection and moving of multiple objects.

Usability

17. Rate the understandability of the user interface

• ( ) Internal use
• ( ) Ready for public use
• (X) Has been used publicly with little learning curve

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
• ( ) Ready for public use

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

• ( ) incomplete
• ( ) obsolete
• ( ) not in English
• ( ) writing not polished
• (X) others: Has been used publicly, but still under improvement.

Expected date for public use (if any):

19. Does the tool provides i* learning facilities?

No
If 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
• (*) Has been used for public development

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?

Yes
If so, which ones?
The tool gets slow as the models get big.

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

Approximately 100+ elements (elements being actors, goals, tasks, and resources).

Extensibility and Interoperability

27. Does the tool allow importing files?

Yes
If so, specify import data formats (i.e., XML, text file, pictures of the graphical representation...)
.tel (text)

28. Does the tool allow exporting files?

Yes
If so, specify import data formats (i.e., XML, text file, pictures of the graphical representation...)
.tel, .sml, and.png

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

No
If so, link to the DTD for the XML format if available.

30. Is the architecture of the tool published?

Yes
If so, where?
http://www.cs.utoronto.ca/km/ome/docs/architecture/architecture.html

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

Yes

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

• (X) PLUG-IN: Modify the plugin source code
• ( ) 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
• (X)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
If so, enumerate the facilities provided

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