Scenario-based requirements analysis Export

@article{citeulike:4028522, abstract = {Abstract\ \ A method for scenario-based requirements engineering is described. The method uses two types of scenario: structure models of the system context and scripts of system usage. A modelling language is reported for describing scenarios, and heuristics are given to cross-check dependencies between scenario models and the requirements specification. Heuristics are grouped into several analytic treatments that investigate correspondences between users' goals and system functions; input events and system processes to deal with them; system output and its destination in the scenario model, and acceptability analysis of system output for different stakeholders. The method is illustrated with a case study taken from the London Ambulance Service report. The prospects for scenario-based requirements engineering and related work are discussed.}, author = {Sutcliffe, Alistair}, citeulike-article-id = {4028522}, citeulike-linkout-0 = {http://dx.doi.org/10.1007/BF02802920}, citeulike-linkout-1 = {http://www.springerlink.com/content/jw76516n334g8241}, day = {16}, doi = {10.1007/BF02802920}, journal = {Requirements Engineering}, keywords = {activities, all-possible-interactions, automatons, behavioral-equations, behavioral-models, behavioral-spaces, behavioral-specifications, configurations, contracts, domain-models, domain-theories, exchange-theory, goals, intentions, interactions, lattice-of-situations, marketing, requirements, scenarios, sequences, situations, software-development, specifications, transformability, use-cases}, month = {March}, number = {1}, pages = {48--65}, posted-at = {2009-07-07 16:32:37}, priority = {2}, title = {Scenario-based requirements analysis}, url = {http://dx.doi.org/10.1007/BF02802920}, volume = {3}, year = {1998} }

TY - JOUR ID - citeulike:4028522 L3 - citeulike-article-id:4028522 N2 - Abstract  A method for scenario-based requirements engineering is described. The method uses two types of scenario: structure models of the system context and scripts of system usage. A modelling language is reported for describing scenarios, and heuristics are given to cross-check dependencies between scenario models and the requirements specification. Heuristics are grouped into several analytic treatments that investigate correspondences between users’ goals and system functions; input events and system processes to deal with them; system output and its destination in the scenario model, and acceptability analysis of system output for different stakeholders. The method is illustrated with a case study taken from the London Ambulance Service report. The prospects for scenario-based requirements engineering and related work are discussed. IS - 1 JF - Requirements Engineering EP - 65 TI - Scenario-based requirements analysis VL - 3 SP - 48 KW - activities KW - all-possible-interactions KW - automatons KW - behavioral-equations KW - behavioral-models KW - behavioral-spaces KW - behavioral-specifications KW - configurations KW - contracts KW - domain-models KW - domain-theories KW - exchange-theory KW - goals KW - intentions KW - interactions KW - lattice-of-situations KW - marketing KW - requirements KW - scenarios KW - sequences KW - situations KW - software-development KW - specifications KW - transformability KW - use-cases AU - Sutcliffe, Alistair PY - 1998/03/16/ UR - http://dx.doi.org/10.1007/BF02802920 ER -