A Methodology for Scenario-Based Requirements Capture Export

@inproceedings{WhKr04, abstract = {Scenarios are an intuitive way for software project stakeholders to capture requirements, describe test cases and evaluate software architectures. Typically, however, coming up with a complete scenario specification is difficult. Basic (or nominal) scenarios are easy to write down, but more complex or less common (non-nominal) scenarios are harder to elicit. In particular, there is currently no good way of knowing when enough scenarios have been developed and scenario writing should stop. What is needed is a methodology for developing a scenario specification from an initial set of nominal scenarios, accompanied by metrics for deciding when the specification is complete. We sketch out a preliminary form of such a methodology in this paper.}, author = {Whittle, Jon and Kr\"{u}ger, Ingolf H.}, booktitle = {Proceedings of the ICSE 2004 Workshop on Scenarios and State Machines (SCESM)}, citeulike-article-id = {1075328}, citeulike-linkout-0 = {http://www-cse.ucsd.edu/~ikrueger/publications.htm}, keywords = {bibtex-import, requirement-engineering, scenario}, posted-at = {2007-01-30 00:19:30}, priority = {2}, title = {A Methodology for Scenario-Based Requirements Capture}, url = {http://www-cse.ucsd.edu/~ikrueger/publications.htm}, year = {2004} }

TY - CONF ID - WhKr04 L3 - citeulike-article-id:1075328 N2 - Scenarios are an intuitive way for software project stakeholders to capture requirements, describe test cases and evaluate software architectures. Typically, however, coming up with a complete scenario specification is difficult. Basic (or nominal) scenarios are easy to write down, but more complex or less common (non-nominal) scenarios are harder to elicit. In particular, there is currently no good way of knowing when enough scenarios have been developed and scenario writing should stop. What is needed is a methodology for developing a scenario specification from an initial set of nominal scenarios, accompanied by metrics for deciding when the specification is complete. We sketch out a preliminary form of such a methodology in this paper. TI - A Methodology for Scenario-Based Requirements Capture T2 - Proceedings of the ICSE 2004 Workshop on Scenarios and State Machines (SCESM) KW - bibtex-import KW - requirement-engineering KW - scenario AU - Whittle, Jon AU - Krüger, Ingolf PY - 2004/// UR - http://www-cse.ucsd.edu/~ikrueger/publications.htm ER -