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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Understanding How to Manage Requirements<br />

Evolution: An Experience in the Air Traffic Domain ⋆<br />

F. Paci 1 , M.S. Tran 1 , F. Massacci 1 , D. Nagaraj 1 , and A. Tedeschi 2<br />

1 DISI - University of Trento,<br />

{paci, tran, massacci,nagaraj}@disi.unitn.it<br />

2 Deep Blue<br />

alessandra.tedeschi@dblue.it<br />

Abstract. [Context/Motivation] Requirements evolution is still a major problem<br />

in practice. Continuously changing requirements make the traceability of<br />

requirements difficult and the monitoring of requirements unreliable.[Question/<br />

Problem] In this paper we tackle the problem of modeling and reasoning about<br />

requirements evolution. Our research objectives are to gain in-depth understanding<br />

of the change management process adopted in a real industrial setting, and<br />

investigate how the approach to model and reason on requirements evolution previously<br />

proposed in [15] can facilitate the industrial change management process.<br />

[Principal Ideas/Results]This paper presents the results of the qualitative<br />

user study we have conducted in the air traffic management (ATM) domain where<br />

change management is still an open issue [13]. The user study has involved eight<br />

ATM domain experts in the assessment of the approach to requirement evolution.<br />

[Contribution] The results from the study demonstrated the usefulness of the<br />

approach to requirements evolution in the ATM industrial setting. Furthermore,<br />

important lessons were learned about the key aspects of the approach to evolution<br />

and about the aspects to be taken into account during research methodology’s<br />

design.<br />

Keywords: requirement engineering, evolution, change management, user study, air<br />

traffic domain<br />

1 Introduction<br />

The requirements for any non-trivial system will inevitably change, not only after the<br />

system has been built, but also during the process of implementing the system. Changes<br />

make the traceability of requirements hard and the monitoring of requirements unreliable:<br />

requirements management is difficult, time-consuming and error-prone when done<br />

manually. Thus, change management is a major problem in practice. However, very few<br />

empirical studies [6, 16, 9, 10, 3] about requirements evolution have been reported.<br />

This paper presents the results of a user study conducted about modeling and reasoning<br />

on requirements evolution. The study has been carried out using a qualitative<br />

research approach. Qualitative research aims to investigate and understand social and<br />

⋆ Work partly supported by the projects EU-FP7-IP-<strong>SecureChange</strong>, EU-FP7-NoE-NESSOS.

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

Saved successfully!

Ooh no, something went wrong!