%0 Journal Article %1 sutcliffe98supporting %A Sutcliffe, A.G. %A Maiden, N.A.M. %A Minocha, S. %A Manuel, D. %B Software Engineering, IEEE Transactions on %D 1998 %K cites.pclass research.cs.softeng.req research.conceptual.usecases %P 1072-1088 %R 10.1109/32.738340 %T Supporting scenario-based requirements engineering %U http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=738340 %V 24 %X Scenarios have been advocated as a means of improving requirementsengineering yet few methods or tools exist to support scenario based RE.The paper reports a method and software assistant tool for scenariobased RE that integrates with use case approaches to object orienteddevelopment. The method and operation of the tool are illustrated with afinancial system case study. Scenarios are used to represent paths ofpossible behavior through a use case, and these are investigated toelaborate requirements. The method commences by acquisition and modelingof a use case. The use case is then compared with a library of abstractmodels that represent different application classes. Each model isassociated with a set of generic requirements for its class, hence, byidentifying the class(es) to which the use case belongs, genericrequirements can be reused. Scenario paths are automatically generatedfrom use cases, then exception types are applied to normal eventsequences to suggest possible abnormal events resulting from humanerror. Generic requirements are also attached to exceptions to suggestpossible ways of dealing with human error and other types of systemfailure. Scenarios are validated by rule based frames which detectproblematic event patterns. The tool suggests appropriate genericrequirements to deal with the problems encountered. The paper concludeswith a review of related work and a discussion of the prospects forscenario based RE methods and tools

@article{sutcliffe98supporting, abstract = {Scenarios have been advocated as a means of improving requirementsengineering yet few methods or tools exist to support scenario based RE.The paper reports a method and software assistant tool for scenariobased RE that integrates with use case approaches to object orienteddevelopment. The method and operation of the tool are illustrated with afinancial system case study. Scenarios are used to represent paths ofpossible behavior through a use case, and these are investigated toelaborate requirements. The method commences by acquisition and modelingof a use case. The use case is then compared with a library of abstractmodels that represent different application classes. Each model isassociated with a set of generic requirements for its class, hence, byidentifying the class(es) to which the use case belongs, genericrequirements can be reused. Scenario paths are automatically generatedfrom use cases, then exception types are applied to normal eventsequences to suggest possible abnormal events resulting from humanerror. Generic requirements are also attached to exceptions to suggestpossible ways of dealing with human error and other types of systemfailure. Scenarios are validated by rule based frames which detectproblematic event patterns. The tool suggests appropriate genericrequirements to deal with the problems encountered. The paper concludeswith a review of related work and a discussion of the prospects forscenario based RE methods and tools}, added-at = {2009-06-25T16:49:31.000+0200}, author = {Sutcliffe, A.G. and Maiden, N.A.M. and Minocha, S. and Manuel, D.}, biburl = {https://www.bibsonomy.org/bibtex/247fd38a23cb1bc9a619d0675627358a1/msn}, booktitle = {Software Engineering, IEEE Transactions on}, description = {Welcome to IEEE Xplore 2.0: Supporting scenario-based requirements engineering}, doi = {10.1109/32.738340}, file = {sutcliffe98supporting.pdf:papers\\ieeeTransSe\\sutcliffe98supporting.pdf:PDF}, interhash = {289776845df18728d2a94dbe5e20638b}, intrahash = {47fd38a23cb1bc9a619d0675627358a1}, issn = {0098-5589}, keywords = {cites.pclass research.cs.softeng.req research.conceptual.usecases}, pages = {1072-1088}, timestamp = {2009-06-25T16:49:31.000+0200}, title = {Supporting scenario-based requirements engineering}, url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=738340}, volume = 24, year = 1998 }