i* Modules
i* Modules
Version
Prototype v1
Group
Group of Software Engeneering for Information Systems (GESSI) - UPC Barcelona
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*.
- (X) For iStar modelling only
- ( ) For development only
- ( ) Both
Programming Language
Java 1.5 for development
- 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)
Prototype v1 supports:
- iStar module creation
- iStar module constraints cheking
- iStar module operations
Ongoing work
- Graphic expansion/collapse feature
i* Modelling Suitability
Yes, but actors need to contain at least one intentional element.
Yes
Yes.
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
7. Describe how the dependency links are modelled and their flexibility (i.e., dependencies are modelled with straight lines that can not be redirected).
Links are multiple-point lines. They can be defined once and referenced/reused in many diagrams. They cannot be redirected.
Yes
This extension allows the user to define and manage modules of different types and combine them.
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.
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.
- Particular and general constraints over Specific module type: SRModules, SDModules, ...
Yes, multiple files can be opened but module related features only support single diagram files.
Yes
Yes
- 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
No
No
- ( ) Copy files and initializing paths
- (X) Copy files
- ( ) Executable installation file provided
- ( ) 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
No
No
No
5 actors, 10 dependencies
Extensibility and Interoperability
Yes
Yes
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
- 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
Yes, based on the NFR framework, the UCM notation, and GRL extensions for Key Performance Indicators.
- (X) PLUG-IN
- (X) Open-Source code
- (X) import & export XML
- ( ) NONE
- ( ) 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
