2013
DOI: 10.1016/j.ijhcs.2013.08.001
|View full text |Cite
|
Sign up to set email alerts
|

PLANT: A pattern language for transforming scenarios into requirements models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0

Year Published

2014
2014
2022
2022

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 13 publications
(8 citation statements)
references
References 43 publications
0
8
0
Order By: Relevance
“…Domain experts present their ETK of problem-solving based on the specific problem and context. We construct the representation of ETK in initial state by means of scenarios modelling (Weidenhaupt et al 1998;de Brabandere and Iny 2010;Wang et al 2013). The scenarios model provides information addressing the application context, the problem's goal and subgoals, experts' statement and action in problem-solving.…”
Section: Methodsmentioning
confidence: 99%
See 2 more Smart Citations
“…Domain experts present their ETK of problem-solving based on the specific problem and context. We construct the representation of ETK in initial state by means of scenarios modelling (Weidenhaupt et al 1998;de Brabandere and Iny 2010;Wang et al 2013). The scenarios model provides information addressing the application context, the problem's goal and subgoals, experts' statement and action in problem-solving.…”
Section: Methodsmentioning
confidence: 99%
“…Carroll (2000) points out that scenarios should include: presuppose setting, agents or actors, goals or objectives, sequences of actions and events (Carroll 2000). Wang et al (2013) present a scenarios model containing four patterns: story line, things that change, agents and their interactions, goals and their subgoals.…”
Section: Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…Scenario documents have several patterns in it, namely: setting up the storyline, expounding things that change, recognizing specialists and their associations, and disentangling the objective and its subgoals (Wang et al, 2013). Scenario documents can help the target of the story to understand the reasons why the problems need to be solved by the system, why the system is important to be built, why the system needs to be built right away, and what potential benefits of the target may have.…”
Section: Introductionmentioning
confidence: 99%
“…By adopting a model-driven elicitation process, our approach aims to capture different aspects of e-collaboration systems and guide requirement engineers towards a more complete, accurate and reusable requirements specification. The proposed approach builds on our previous work on a pattern language for transforming scenarios into requirements models [59]. Scenario-based requirements engineering approaches [24] [35] are widely used in requirements elicitation [68].…”
Section: Introductionmentioning
confidence: 99%