%0 Journal Article %1 liu_07_detecting %A Liu, H. %A Shao, W. Z. %A Zhang, L. %A Ma, Z. Y. %B Software, IET %D 2007 %J Software, IET %K 2007 statecharts requirements %N 1 %P 29--36 %R 10.1049/iet-sen:20060023 %T Detecting overlapping use cases %U http://dx.doi.org/10.1049/iet-sen:20060023 %V 1 %X To deal with the complexity of large information systems, the divide-and-conquer policy is usually adopted to capture requirements from a large number of stakeholders: obtain requirements from different stakeholders, respectively, and then put them together to form a full requirement specification. One of the problems induced by the policy is overlapping requirements. A use case driven approach could not avoid overlapping requirements either: it produces overlapping use cases, which are even more harmful, because a use case describes not only inputs and outputs as traditional requirements do, but also the scenarios. Each of the overlapping use cases provides a message sequence to implement the common subgoal. Overlapping use cases not only decrease the maintainability of the requirement specification, but also result in a complicated, confusing and expensive system. To be worse, it is difficult to detect overlapping use cases with existing methods for requirement management. To find out overlapping use cases, a detection approach using sequence diagrams and statecharts is proposed. Evaluation results suggest that practical requirement models do contain overlapping use cases, and the proposed approach is effective in detecting them

@article{liu_07_detecting, abstract = {To deal with the complexity of large information systems, the divide-and-conquer policy is usually adopted to capture requirements from a large number of stakeholders: obtain requirements from different stakeholders, respectively, and then put them together to form a full requirement specification. One of the problems induced by the policy is overlapping requirements. A use case driven approach could not avoid overlapping requirements either: it produces overlapping use cases, which are even more harmful, because a use case describes not only inputs and outputs as traditional requirements do, but also the scenarios. Each of the overlapping use cases provides a message sequence to implement the common subgoal. Overlapping use cases not only decrease the maintainability of the requirement specification, but also result in a complicated, confusing and expensive system. To be worse, it is difficult to detect overlapping use cases with existing methods for requirement management. To find out overlapping use cases, a detection approach using sequence diagrams and statecharts is proposed. Evaluation results suggest that practical requirement models do contain overlapping use cases, and the proposed approach is effective in detecting them}, added-at = {2009-02-11T20:52:40.000+0100}, author = {Liu, H. and Shao, W. Z. and Zhang, L. and Ma, Z. Y.}, biburl = {https://www.bibsonomy.org/bibtex/20300a88904ebab938c234a1865c2d4bc/leonardo}, booktitle = {Software, IET}, citeulike-article-id = {1570956}, doi = {10.1049/iet-sen:20060023}, interhash = {bd793c2dbf400b0ea4c8113798474d76}, intrahash = {0300a88904ebab938c234a1865c2d4bc}, journal = {Software, IET}, keywords = {2007 statecharts requirements}, number = 1, pages = {29--36}, posted-at = {2007-08-17 00:29:05}, priority = {3}, timestamp = {2009-02-11T20:52:40.000+0100}, title = {Detecting overlapping use cases}, url = {http://dx.doi.org/10.1049/iet-sen:20060023}, volume = 1, year = 2007 }