WebREd-Tool

General Information

WebREd-Tool is a Model-Driven Tool conformed by a set of Eclipse plugins that have been developed to assist the designer in the early phases of a Web application development process. With the WebREd-Tool, the designer can specify the Web application requirements by using the i* goal-oriented framework. The WebREd-Tool assists the designer to compare different configurations of functional requirements, while balancing and optimizing non-functional requirements. The underlying algorithm to support this is based on the Pareto efficiency, but to help the designer to better assess and compare each configuration, the WebREd-Tool is also able to visualize each configurations using a radar-chart.

Tool Name

WebREd-Tool

Version

1.0

Group

Cuerpo Académico Señales y Sistemas, Universidad Autónoma de Sinaloa and WaKe Research group , University of Alicante.

Date Tool Template Last Updated

14-Jan-2014

Web page (if available)

http://webred.maz.uasnet.mx

Main Purpose of the Tool

to assist the designer in the early phases of a Web application development process.

i* framework supported

Yu'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/Linux/Mac

Other technology needed

Current state of the tool

Ready for Web Requirements Specification

Ongoing work

Transformations by using Acceleo in order to obtain Web application code from the i* models

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

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

Yes, dragging and dropping the elements into a drawing page

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

Users can change the name, size and type of an element. The element can also be moved, reordered, deleted, copied, pasted, highlighted, and labelled with 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).

Dependency links can be drawn from the palette. The link can also be moved, reordered, deleted, copied, pasted, and highlighted. 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?

Yes

9. Other modelling facilities provided by the tool:

Can push an element into or move it from an expandable element

10. Does the tool check SD models?

No

11. Does the tool check SR models?

No

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?

Yes. Since the tool can be operated as a plug-in of Eclipse, Eclipse allows WebREd-Tool open multiple models at the same time.

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

Yes, Eclipse navigator allows classifying models into different physical folders.

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

Yes, Eclipse navigator allows working with two or more projects at the same time

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

- Change Impact Analysis Report (analyzing the i* requirements model)
- The generation of the domain and navigational model from the requirements model (i* model) by means of ATL (Atlas Transformation Language).
- Softgoals Optimziation by means of the Pareto Efficiency Algorithm.

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

18. Rate the quality of the user manual

• ( ) Inexistent
• ( ) Internal use
• ( ) Ready for public use
• (X) Has been used publicly (only videos)

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

• ( ) incomplete
• ( ) obsolete
• ( ) not in English
• ( ) writing not polished
• () others: please specify (only videos)

Expected date for public use (if any): available

19. Does the tool provides i* learning facilities?

Yes, by means of a methodological guidance to develop Web applications based on the A-OOH method.

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

Yes

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:

• ( ) incomplete
• (X) 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, as a proff of concept, not in real-world applications

24. Has the tool been tested in large models?

Yes

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?

10 Actors

Extensibility and Interoperability

27. Does the tool allow importing files?

Yes, XML, text file, pictures of the graphical representation

28. Does the tool allow exporting files?

Yes, XML, text file, pictures of the graphical representation

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

No

30. Is the architecture of the tool published?

No

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
• (X) Open-Source code
• ( ) 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
• (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?

Yes

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