Loading...
 
Print

GrowingLeaf---BloomingLeaf

GrowingLeaf (BloomingLeaf)

Table of contents



General Information

Tool Name

GrowingLeaf (BloomingLeaf)

Version

1.0

Group

University of Toronto (Grubb & Chechik)

Web page (if available)

http://www.cs.utoronto.ca/~amgrubb/leaf-ui/Tool.html
https://github.com/amgrubb/GrowingLeaf
https://github.com/amgrubb/BloomingLeaf

Main Purpose of the Tool

GrowingLeaf is a web-based goal modeling and analysis tool that allows stakeholders to explicate the dynamic nature of their intentional elements, and ask questions about how this dynamicity affects goal outcomes.
All tools in the Leaf Family of tools (i.e., Leaf2.0, GrowingLeaf, CreativeLeaf, BloomingLeaf) have the same look and feel.
See http://www.cs.toronto.edu/~amgrubb/archive/iStar16.pdf for further information about the tool and http://www.cs.toronto.edu/~amgrubb/archive/RE16.pdf for further information about the technique.

BloomingLeaf has the same goals as GrowingLeaf but uses Tropos syntax and semantics for model relationships.

i* framework supported

i*

Availability of the tool

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

Programming Language

JavaScript

Platform Requirements

Chrome (works in other browsers but less tested)

Other technology needed

none

Current state of the tool

GrowingLeaf is complete, BloomingLeaf is currently in active development.

Ongoing work

  • Analysis and usability of BloomingLeaf

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).
Actor boundaries can be shrunk

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)
Drag and drop interface.

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

No

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

Moved, name change, resized

Dependency links can be drawn from the palette. 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?

No

9. Other modelling facilities provided by the tool:

  • Creation of goal model simulations over time based on three strategies: (1) create a random path given initial states in the model; (2) create a path given desired properties of the intermediate state (with optional properties over the
initial or final state); (3) create a path which is different than the previously seen path over the same constraints.

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


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?

N/A

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): currently available

18. Rate the quality of the user manual

  • ( ) Inexistent
  • ( ) Internal use
  • ( ) Ready for public use
  • (X) Has been used publicly, but still under improvement
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
If so, explain which ones (i.e., methodological guidance).

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

No, but contributions are welcome.

21. Rate the difficulty of installing the tool

Browser-based, no installation.

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
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?

Many examples, no large case study yet

24. Has the tool been tested in large models?

Somewhat large

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

Only the regular drawbacks with large i* models

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

100 nodes.

Extensibility and Interoperability


27. Does the tool allow importing files?

Yes
json files only

28. Does the tool allow exporting files?

Yes
json, svg

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

JSON

30. Is the architecture of the tool published?

No
If so, where?

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

Could be added to the code.

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

acquiring a Rappid license and expanding javascript.

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?

Rappid/JointJS Documentation, Architecture and programming guide.

Created by amgrubb. Last Modification: Monday 10 of July, 2017 15:25:03 CEST by amgrubb.