Loading...
 
Print

E4J

Replace Title

Table of contents



General Information

Tool Name

E4J: Editor for JGOOSE.

Version

0.4.7

Group

Laboratório de Engenharia de Software (LES) da UNIOESTE, campus Cascavel, PR - Brasil.

Date Tool Template Last Updated

05/28/2014

Web page (if available)

http://inf.unioeste.br/~les/

Main Purpose of the Tool

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

i* framework supported

Yu PhD thesis.

Availability of the tool

  • ( ) For i* modelling only
  • ( ) For development only
  • (X) Both
If not available, please specify expected date of availability:

Programming Language

Java

Platform Requirements

Windows, Linux or Mac.

Other technology needed

Java Runtime Environment 7.

Current state of the tool

Under development.

Ongoing work

  • Improve model validation rules of the tool.
  • Improve draws of the tool.
  • Improve the usability and functionality of the tool.
  • Improve interoperability with iStarML language.

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
By means of expandable elements (as in OME).

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

Yes
__Dragging and dropping the elements into a drawing page. To construct an element, click an element
symbol on the “Elements” palette and drag to the position in the drawing page where the
element should locate. To draw a link element, select a link symbol on the “Connectors”
palette, click in the center of source element and drag to the center of target element at
drawing page.__

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

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

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

Users can drag-and-drop elements from “Elements” palette to the drawing page. Users can change the name and
size of an element. The element can also be moved, deleted, copied, pasted, grouped and
styles can be added. All these actions are done graphically and by commands either on
the menu bar or pop-up command window.

Dependencies are modelled with straight lines that can not be redirected.

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

Yes.
Yes. The tool provides a basic graph layout function.

9. Other modelling facilities provided by the tool:

  • Work separately with expandable elements;
  • Undo/Redo Manager;
  • Can push an element into or move it from an expandable element.

10. Does the tool check SD models?

Yes
Checks for unrecognised connections and checks for invalid connections.

11. Does the tool check SR models?

Yes
Checks for unrecognised connections and checks for invalid connections.

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

none

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

No
But the user can run multiples instances of the tool.

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?

  • Export the i* model to iStarML;
  • Generate Use Cases;
  • Export the Use Case to XMI.

Usability


17. Rate the understandability of the user interface

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

  • (X) Inexistent
  • ( ) Internal use
  • ( ) 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?

Yes
Because the syntax checker alert the user about the common errors by using popup.

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

Yes
In the folder “Samples”.

21. Rate the difficulty of installing the tool

  • ( ) Copy files and initializing paths
  • (X) Copy files
  • ( ) 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?

No
If so, specify which ones.

24. Has the tool been tested in large models?

No

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

Not tested.
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?

Not tested.

Extensibility and Interoperability


27. Does the tool allow importing files?

Yes
Yes. i* model in “.tel” and “.mxe”.

28. Does the tool allow exporting files?

Yes
i* model in “.istarml” and “.mxe”. Use Case model in “.xmi”.

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

No
No. Only export “.istarml” and a new DTD must be provided.

30. Is the architecture of the tool published?

Yes
In this thesis

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

No

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:

  • (X) 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
  • (X) no help provided
  • ( ) non-persistent data
  • (X) 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?

No
If so, enumerate the facilities provided
  • ( ) Requirements specification and design decisions available
  • ( ) Interface conventions
  • ( ) Code conventions
  • ( ) Full commented code
  • ( ) Examples
  • ( ) others: please specify



Created by albsilva. Last Modification: Monday 12 of September, 2016 22:19:19 CEST by albsilva.