Abstract^A ^A This paper presents the results of case studies evaluating a method of unifying use cases (UCs) to derive a unified statechart model of the behavior of the domain of a proposed computer-based system. An evaluation of the unification method, the obtained statechart model of the domain, the method^a€™s and model^a€™s feedback on the UCs themselves, and how the method is used in requirements engineering practice was carried out by examining 58 software requirements specifications produced by 189 upper-year undergraduate and graduate students. The results of these studies independently confirm some of the benefits of building a unified SC mentioned in the works of Glinz; Whittle and Schumann; and Harel, Kugler, and Pnueli.
%0 Journal Article
%1 svetinovic_07_unified
%A Svetinovic, Davor
%A Berry, Daniel
%A Day, Nancy
%A Godfrey, Michael
%D 2007
%I Springer London
%J Requirements Engineering
%K 2007 statecharts requirements uml
%N 4
%P 245--264
%R 10.1007/s00766-007-0053-1
%T Unified use case statecharts: case studies
%U http://dx.doi.org/10.1007/s00766-007-0053-1
%V 12
%X Abstract^A ^A This paper presents the results of case studies evaluating a method of unifying use cases (UCs) to derive a unified statechart model of the behavior of the domain of a proposed computer-based system. An evaluation of the unification method, the obtained statechart model of the domain, the method^a€™s and model^a€™s feedback on the UCs themselves, and how the method is used in requirements engineering practice was carried out by examining 58 software requirements specifications produced by 189 upper-year undergraduate and graduate students. The results of these studies independently confirm some of the benefits of building a unified SC mentioned in the works of Glinz; Whittle and Schumann; and Harel, Kugler, and Pnueli.
@article{svetinovic_07_unified,
abstract = {Abstract^{A} ^{A} This paper presents the results of case studies evaluating a method of unifying use cases (UCs) to derive a unified statechart model of the behavior of the domain of a proposed computer-based system. An evaluation of the unification method, the obtained statechart model of the domain, the method^{a}€™s and model^{a}€™s feedback on the UCs themselves, and how the method is used in requirements engineering practice was carried out by examining 58 software requirements specifications produced by 189 upper-year undergraduate and graduate students. The results of these studies independently confirm some of the benefits of building a unified SC mentioned in the works of Glinz; Whittle and Schumann; and Harel, Kugler, and Pnueli.},
added-at = {2009-02-11T20:54:11.000+0100},
author = {Svetinovic, Davor and Berry, Daniel and Day, Nancy and Godfrey, Michael},
biburl = {https://www.bibsonomy.org/bibtex/281fb381f37eb2f15a5d406b50b409829/leonardo},
citeulike-article-id = {1470105},
doi = {10.1007/s00766-007-0053-1},
interhash = {84e29ccb2d6a2f02f75cffaa6a9285ff},
intrahash = {81fb381f37eb2f15a5d406b50b409829},
journal = {Requirements Engineering},
keywords = {2007 statecharts requirements uml},
month = {October},
number = 4,
pages = {245--264},
posted-at = {2007-07-20 19:32:05},
priority = {4},
publisher = {Springer London},
timestamp = {2009-02-11T20:54:11.000+0100},
title = {Unified use case statecharts: case studies},
url = {http://dx.doi.org/10.1007/s00766-007-0053-1},
volume = 12,
year = 2007
}