A Scenario Construction Process

Abstract

Scenario is a description

Requirements engineering within a large-scale security-oriented research project: lessons learned

“…Different techniques have been proposed in literature for eliciting requirements from stakeholders [11,16,25,62]: interviews, questionnaires, user observation, workshops, brain storming, use cases and prototyping. Our approach in TAS 3 is mainly based on interviews and use cases.…”

A systematic literature review of use case specifications research

“…Figure 10 shows the statistics for the use case templates where we found that no such evidences about their practical implications (i.e., no study falls under Evaluation Research Category). The five use case templates namely Insfrán et al [71], Somé [131], Leite et al [39], Yue et al [151] and El-Attar et al [47] were evaluated by conducting some small experiments/case studies; six use case templates namely, Liu et al [98], Mushabiddin et al [102], Fleisch [52], Tiwari et al [141], Toro et al [143], and Mattingly et al [99] were proposed to provide the solutions to the problem, and rests were based on the experiences of the researchers gained from the industries or academia. Among all, two [86,64] use case templates were commonly used in the industrial context, but their practical implications, i.e., understandability, learnability and operability aspects are not evaluated.…”

“…With reference to a purely informative perspective the use case specification were documented in a tabular or a paragraph style format with minimal degree of formalism (e.g., [32,39,64,74,86,143] etc). The rationale behind this was to elicit, analyze and validate the problem specifications with the viewpoint of stakeholders and developers.…”

“…Use cases have gradually become a widely accepted requirement specification technique both in research domain [2,10,13,32,33,74,103,151] as well as, to some extent, in industrial practice [8,9,39,59,109]. Nevertheless, their inherent utilization of natural language and a behavior of requirement documentation in a semi-conventional way, mean that they are affected by issues such as ambiguity, redundancy, inconsistency, and incompleteness [2,32,146].…”

Generating relevant scenarios for intelligent transportation service

“…This comes besides with no guarantee on the quality of the requirements. To improve the quality of the requirements, one can consider scenarios with important advantages already addressed in the literature [2,3]. For instance, scenarios tend to adopt the user's viewpoint, which is a key feature to validate the adequacy between the requirements and the user's needs.…”