Domain independent regularities in scenarios

Abstract

Scenario is a description technique which has attracted much attention not only from practitioners but also from researchers. Literature on this topic shows the possibilities that this description technique provides to enhance the understanding of task-related descriptions and the communication among stakeholders. On the other hand, the idea of pattern, as a description of a problem which occurs over and over again in our environment and its solution, has also attracted lots of attention, specially in software design. This paper describes an initial taxonomy of domain-independent-scenario patterns and proposes a preliminary process to use this taxonomy for scenario construction.

Improvement of the Correctness of Scenarios with Rules

“…We can also consider the generic pattern reported, similar to generic patterns and categories of problem domain reported in the CREWS project [10]- [12] and scenario patterns by Ridao et al [18]. Such patterns will make rules cost-effective and reveal interesting insights about the use of scenarios for requirements specification.…”

Towards a framework for pattern experimentation: Understanding empirical validity in requirements engineering patterns

“…Elicitation, which consists of soliciting requirements from stakeholders, is supported by improving communication among requirements engineers [27,28], between requirements engineers and stakeholders [10,31,32], or between requirements engineers and other developers (testing, design, implementation, etc.) [24].…”

“…Language [21] Conditional statement [16,24,25] Template [21] Tabular Format [15,32] Syntactical Template [20,22] SABRE-TM Scenario [9] Graph Goal Oriented Graph [5] KAOS [24,29] Social Network Diagram [10,28] UML [2,11,17,20,21] State Machine [21] Sequence Diagram [9] First-order Logic Pseudocode [31] Transactional Diagram [31] Secure Tropos [16] Questionnaires [10,15,28] Interviews [10,28] Meetings [24] Technical Artifacts…”