23.02.2015 Views

D.3.3 ALGORITHMS FOR INCREMENTAL ... - SecureChange

D.3.3 ALGORITHMS FOR INCREMENTAL ... - SecureChange

D.3.3 ALGORITHMS FOR INCREMENTAL ... - SecureChange

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

models are too complex. The intuitiveness depends on the requirement language used<br />

to represent before and after evolution models.<br />

The Probability Estimation and the Reasoning phase are instead the key phases of<br />

the approach to requirements evolution. The Probability Estimation gives the ability to<br />

“translate” qualitative metrics that are typically used by stakeholders to classify evolution<br />

into quantitative metrics that enable the Reasoning phase. The Reasoning phase has<br />

turned out to be a powerful decision-support tool since it allows to select the optimal<br />

design which is resilient to changes in the requirements model.<br />

6.2 Experiences from Using a Qualitative Research Approach<br />

During the execution of the user study, we have understood that several aspect can influence<br />

the feedback collection from domain experts. The selection of domain experts<br />

strongly influence the relevance of feedbacks collected and the satisfaction of the success<br />

criteria chosen for the user study. In the user study, the domain experts selected had<br />

a different background and so we were able to collect feedbacks about the approach to<br />

requirement evolution from different perspectives.<br />

Another important aspect to take into account is the potential communication gap<br />

between the research team and the domain experts. Research team and domain experts<br />

might use same terms with different meanings that can lead to misunderstandings and<br />

to provide wrong or unrelated feedbacks. Thus, it is required to establish a common<br />

language between the research team and the domain experts before the user study execution,<br />

or to have a “mediator” who reformulates the questions of the research team for<br />

the domain experts and who reformulates the domain experts’ feedback for the research<br />

team. Moreover, the level of engagement of the domain experts depends by two main<br />

factors: the means to provide feedbacks and the language in which such feedbacks need<br />

to be provided. Different ways to collect feedbacks not only verbal one need to be supported.<br />

The most effective one must be the one in which the domain experts can discuss<br />

in their mother tongue language and then provide written feedback in English.<br />

To collect more insightful feedbacks, hands-on sessions where the domain experts<br />

apply/ use the artefacts under validation should be included in the validation session<br />

execution.<br />

Acknowledgement<br />

We would like also to thank DeepBlue and ATM experts for participating in this study.<br />

We would like to thank Professor John Mylopoulos, and colleagues in the ATHENA<br />

research group at University of Trento (UNITN) for their scientific contribution, and<br />

Dr. Alberto Battocchi (UNITN) for acting as an observer.<br />

References<br />

1. EUROCONTROL ATM Strategy for the Years 2000+ Executive Summary, 2003.<br />

2. A. Bertolino, G. D. Angelis, A. D. Sandro, and A. Sabetta. Is my model right? let me ask the<br />

expert. Journal of Systems and Software, 2011.<br />

14

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!