Jesteś w: Start > Publikacje > HAZOP-based identification of events in use cases
 
Newsletter
Newsletter
(Required)
Zaloguj


Zapomniałeś hasła?
 

HAZOP-based identification of events in use cases

Jakub Jurkiewicz, Jerzy Nawrocki, Mirosław Ochodek, and Tomasz Głowacki (2013)

Empirical Software Engineering, 20(1):82-109.

 Completeness is one of the main quality attributes of requirements specifications. If functional requirements are expressed as use cases, one can be interested in event completeness. A use case is event complete if it contains description of all the events that can happen when executing the use case. Missing events in any use case can lead to higher project costs. Thus, the question arises of what is a good method of identification of events in use cases and what accuracy and review speed one can expect from it. The goal of this study was to check if (1) HAZOP-based event identification is more effective than  ad hoc  review and (2) what is the review speed of these two approaches. Two controlled experiments were conducted in order to evaluate  ad hoc  approach and H4U method to event identification. The first experiment included 18 students, while the second experiment was conducted with the help of 82 professionals. In both cases, accuracy and review speed of the investigated methods were measured and analyzed. Moreover, the usage of HAZOP keywords was analyzed. In both experiments, a benchmark specification based on use cases was used. The first experiment with students showed that a HAZOP-based review is more effective in event identification than  ad hoc  review and this result is statistically significant. However, the reviewing speed of HAZOP-based reviews is lower. The second experiment with professionals confirmed these results. These experiments showed also that event completeness is hard to achieve. It on average ranged from 0.15 to 0.26. HAZOP-based identification of events in use cases is an useful alternative to  ad hoc  reviews. It can achieve higher event completeness at the cost of an increase in effort.

requirements engineering, software quality, controlled experiment, use cases
Wspierać najlepszych, aby mogli stać się jeszcze lepsi