Download HAM User Manual

1. Introduction
This document gives an overview of the tool developed to implement the HAM
algorithm (Pimentel, 2009). To collect the NFRs, the HAM tool works in collaboration
with the EA-Miner tool, which mines NFRs from textual (requirements) files. HAM
starts by opening the Requirements Description Language (RDL) file produced by EAMiner. RDL files are XML-style files that contain the NFRs. The HAM Tool filters the
Non-Functional Requirements (NFRs) from the produced RDL file. We can add new
NFRs to the list obtained from the RDL file, or remove NFRs from that list if we
consider that there are NFRs wrongly identified by the EA-Miner. The stakeholders,
architecture styles and products are elicited manually.
2. Installing and running
The installation process for the HAM Tool is very simple. Just copy and paste the
HAM Tool plugin into the Eclipse plugins folder. Notice that the HAM plugin has the
follow
dependencies:
org.eclipse.emf.common,
org.eclipse.emf.ecore,
net.ample.tracing.core, net.ample.tracing.core.query; this is present in the AMPLE
Eclipse bundle ("AMPLE Project," 2006). Start Eclipse. You need to include the RDL
file of the system you are assessing in the current Eclipse project.
To run the HAM Tool just right click on the RDL file and select “HAM TOOl”. A
window with four tabs opens, each one presenting: “Quality Attributes” for raking
NFRs according to the opinion of a set of Stakeholders, “Architectures” for ranking
architectural styles with respect to the one set of NFRs, “Products” for ranking
product configurations with respect to a set of NFRs and “Features” for ranking
features of a software product line configuration with respect to one set of NFRs and
detect possible conflict between NFRs in a feature.
2.1. Working with the HAM Tool
For the example in this user manual, we used the “Quality Attributes” functionality.
The HAM Tool’s main window is displayed in Erro! A origem da referência não foi
encontrada.. Considering the top-half of the window, we can observe, on the lefthand side, a tree-like structure with aiming at assessing the selected criteria and
alternatives. In the top-middle of the window, there is the pair-wise comparison
matrix. This is where the tradeoffs between the criteria will be filled. We just need to
fill the right-upper side of the pair-wise matrix. The lower-left cells will be filled
automatically. On the right-hand side is a matrix that displays the weights of the
criteria. If the criteria weights are inconsistent, one message pop-up will warn the
user. Under the pair-wise matrix we can see a combo box to Assign Value,. This
component is used to assign values to the pair-wise matrix cells. In the bottom-half