**** Experience-based Analysis Method - evaluation data ****
Author: Anu Piirisild, Ana Perandrés Gómez
Corresponding author: Anu Piirisild
Contact information: anu.piirisild@ut.ee

University of Tartu Institute of computer Science
Narva mnt 18
Tartu
ESTONIA

*****



*** General Introduction ***

The dataset contains the data that were created to evaluate the Experience-based Analysis (EbA) method. The EbA method has been evaluated by the industry-oriented research and development project Pharaon. The aim of the Pharaon is to develop an ecosystem of technological solutions to improve the quality of life of older adults and their caregivers. The Pharaon project consists of five large-scale case studies or pilots. For the evaluation, the pilot from Andalusia in Spain was chosen as a case study.


Dataset contains two files:

 Case Study Features_Preconditions_Value.xlsx 	Usability analysis by EbA: partly hidden data
 Feature_example.xlsx 				Usability analysis by EbA: one feature complete analysis		

 

*** Method ***

The analysis is made by the EbA method. The preliminary tool and tutorial on how to use the EbA method can be found here: https://datadoi.ee/handle/33/594


*** Usage ***

The data is being made public to act as supplementary data for the EbA method evaluation.

Seven features were extracted from the case study. The data fail “Case Study Features_Preconditions_Value” presents all the seven features, incl. quality goals and emotional goals. The data file includes 48 preconditions found for these seven features and comparable example situations found for the preconditions. In this data collection, the validation inputs, findings, and suggestions on the action plan are hidden. However, we describe by colors and categorization what type of action was suggested. The file also includes categorizations and value evaluations of the findings and suggestions for the action plan. The ”value” clarifies whether the usability findings obtained by EbA are valuable for the product owner and other stakeholders. The last column shows whether the findings are identified as ”technology-oriented”, ”non technology-oriented” or both.

The data collection contains a second file, “Feature_example” where one of the seven features illustrates the analysis with validation inputs and findings, and suggested actions.