Loading...
 

i* Modules

i* Modules

Table of contents



General Information

Tool Name

i* Modules

Version

Prototype v1

Group

Group of Software Engeneering for Information Systems (GESSI) - UPC Barcelona

Date Tool Template Last Updated

17/06/2011

Web page (if available)

http://www.essi.upc.edu/~gessi/mod_extension/index.html

Main Purpose of the Tool

This tool is an extension of the jUCMNav 4.2.1 Eclipse plug-in that introduces support to i* module creation and operation.

i* framework supported

Goal-oriented Requirement Language (GRL, ITU-T Recommendation Z.151, November 2008), which is based in part on i*.

Availability of the tool

  • (X) For iStar modelling only
  • ( ) For development only
  • ( ) Both

Programming Language

Java 1.5 for development

Platform Requirements

  • Java 1.5 JRE. Eclipse 3.5 and above, with GEF and EMF, and MDT OCL
  • Eclipse's Web services tools optionally required to connect jUCMNav to external data sources for monitoring.

Other technology needed

GraphViz for automatic layout. (optional)

Current state of the tool

Prototype v1 supports:
  • iStar module creation
  • iStar module constraints cheking
  • iStar module operations

Ongoing work

  • Graphic expansion/collapse feature

i* Modelling Suitability


1. Does the tool allow SD modelling?

Yes, but actors need to contain at least one intentional element.

2. Does the tool allow SR modelling?

Yes

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

Yes.

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

Yes, using a palette in an Eclipse-based editor.

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

  • Elements can be defined once in the model and referenced consistently in many diagrams, which helps with model scalability.
  • Single or multiple elements can be moved and deleted easily.
  • An auto-layout feature can be used.
  • Intentional elements bound to actors can be moved/resized with the actor boundary.
  • There is also a multiple undo/redo mechanism for all functionalities.
  • Metadata (and stereotypes) can be attached to any single elements
  • URN typed links can be used to connect any pair of elements
Links are multiple-point lines. They can be defined once and referenced/reused in many diagrams. They cannot be redirected.

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

Yes

9. Other modelling facilities provided by the tool:

This extension allows the user to define and manage modules of different types and combine them.

10. Does the tool check SD models?

Yes, by construction. The tool GUI prevents the creation of syntactically incorrect diagrams. User-defined OCL rules can be created, selected and checked. Many are provided by default.

11. Does the tool check SR models?

Yes, by construction. The tool GUI prevents the creation of syntactically incorrect diagrams. User-defined OCL rules can be created, selected and checked. Many are provided by default.

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

  • Particular and general constraints over Specific module type: SRModules, SDModules, ...

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

Yes, multiple files can be opened but module related features only support single diagram files.

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?

  • iStar module creation
  • iStar module constraints cheking
  • iStar module operations

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

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

19. Does the tool provides i* learning facilities?

No

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

No

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
  • (X) Prototype
  • ( ) Ready for public use
  • ( ) Has been used publicly
If not for public use, mark one or more of the following:
  • (X) incomplete
  • (X) 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?

No

24. Has the tool been tested in large models?

No

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

No

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

5 actors, 10 dependencies

Extensibility and Interoperability


27. Does the tool allow importing files?

Yes

28. Does the tool allow exporting files?

Yes

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

Yes. The XMI format is the serialization of the EMF interpretation of the URN metamodel available at http://cserg0.site.uottawa.ca/twiki/bin/view/ProjetSEG/URNMetaModel. In addition, the Z.151 XML format is supported http://jucmnav.softwareengineering.ca/ucm/bin/view/ProjetSEG/Z151ImportExport

30. Is the architecture of the tool published?

  • Yes, see documentation on-line at http://jucmnav.softwareengineering.ca/twiki/bin/view/ProjetSEG/WebHome
  • The extended metamodel supporting iStar modules can be found at http://www.essi.upc.edu/~gessi/mod_extension/resources.html

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

Yes, based on the NFR framework, the UCM notation, and GRL extensions for Key Performance Indicators.

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

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

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

  • ( ) Under Development
  • (X) 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
  • (X) no development installation facilities provided
  • ( ) others: please specify

34. Is there any internal documentation for programmers?

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


Created by dncolomer. Last Modification: Monday 18 of July, 2011 09:41:53 CEST by admin.