|
DEAL was originally created with the goal of analyzing existing user interfaces for [domain usability](https://link.springer.com/chapter/10.1007/978-3-319-08491-6_2) in an automated manner. This can be achieved using the [ADUE (Automated Domain Usability Analysis) Tool](https://ieeexplore.ieee.org/document/7377805) of DEAL.
|
|
DEAL was originally created with the goal of analyzing existing user interfaces for [domain usability](https://link.springer.com/chapter/10.1007/978-3-319-08491-6_2) in an automated manner. This can be achieved using the [ADUE (Automated Domain Usability Analysis) Tool](https://ieeexplore.ieee.org/document/7377805) of DEAL. ADUE is a proof of concept tool, thus its abilities on Windows and web applications is limited. Its full potential can be leveraged when analyzing Java application.
|
|
|
|
|
|
ADUE has multiple possibilities for analysis.
|
|
ADUE has multiple possibilities for analysis.
|
|
|
|
|
|
## Evaluation of labels
|
|
## Evaluation of labels
|
|
|
|
|
|
DEAL checks, whether each label is connected to a component using the Java `labelFor` relation. If any component needs a label, DEAL lets you know with a red (Usability issues) or orange (Recomendation) color in the Tree view, and an explanatory tooltip with with an advice on how to fix the issue. Below is an example with a few Usability issues found in the OpenRocket app (version 12.03). |
|
DEAL checks, whether each label is connected to a component using the Java `labelFor` relation. If any component needs a label, DEAL lets you know with a red (Usability issues) or orange (Recomendation) color in the Tree view, and an explanatory tooltip with with an advice on how to fix the issue.
|
|
\ No newline at end of file |
|
|
|
|
|
Below is an example with a few Usability issues found in the OpenRocket app (version 12.03). In the front there is the DEAL window with issues found, in the background is the OpenRocket user interface with the specified component being higlighted.
|
|
|
|

|
|
|
|
|
|
|
|
To perform the evaluation of labels, click on **File** in the menu and then select **Show labelFor evaluation**.
|
|
|
|

|
|
|
|
|
|
|
|
## Evaluation of tooltips
|
|
|
|
|
|
|
|
DEAL checks each functional component, whether it has a textual description. If not, it checks for the presence of its tooltip.
|
|
|
|
|
|
|
|
* If there is no description nor a tooltip present, it is considered a usability issue.
|
|
|
|
* If there is a description, but there is no tooltip, it is recommended to add a tooltip.
|
|
|
|
|
|
|
|
Below is an example of a few Usability issues found in the OpenRocket app (version 12.03). In the front there is the DEAL window with issues found, in the background is the OpenRocket user interface with the specified button component being highlighted. In this case, the button has only an icon, but no textual description nor a tooltip.
|
|
|
|

|
|
|
|
|
|
|
|
To perform the tooltip evaluation, click on **File** in the menu and then select **Show tooltip evaluation**.
|
|
|
|
 |