TY - GEN
T1 - Conceptualizing Requirements Using User Stories and Use Cases
T2 - 26th International Working Conference on Requirements Engineering: Foundation for Software Quality, REFSQ 2020
AU - Dalpiaz, Fabiano
AU - Sturm, Arnon
N1 - Publisher Copyright:
© 2020, Springer Nature Switzerland AG.
PY - 2020/1/1
Y1 - 2020/1/1
N2 - [Context and motivation] Notations for expressing requirements are often proposed without explicit consideration of their suitability for specific tasks. Consequently, practitioners may choose a sub-optimal notation, thereby affecting task performance. [Question/problem] We investigate the adequacy of two well-known notations: use cases and user stories, as a starting point for the manual derivation of a static conceptual model. In particular, we examine the completeness and correctness of the derived conceptual model. [Principal ideas/results] We conducted a two-factor, two-treatment controlled experiment with 118 subjects. The results indicate that for deriving conceptual models, user stories fit better than use cases. It seems that the repetitions in user stories and their conciseness contribute to these results. [Contribution] The paper calls for evaluating requirements notations in the context of various requirements engineering tasks and for providing evidence regarding the aspects that need to be taken into account when selecting a requirement notation.
AB - [Context and motivation] Notations for expressing requirements are often proposed without explicit consideration of their suitability for specific tasks. Consequently, practitioners may choose a sub-optimal notation, thereby affecting task performance. [Question/problem] We investigate the adequacy of two well-known notations: use cases and user stories, as a starting point for the manual derivation of a static conceptual model. In particular, we examine the completeness and correctness of the derived conceptual model. [Principal ideas/results] We conducted a two-factor, two-treatment controlled experiment with 118 subjects. The results indicate that for deriving conceptual models, user stories fit better than use cases. It seems that the repetitions in user stories and their conciseness contribute to these results. [Contribution] The paper calls for evaluating requirements notations in the context of various requirements engineering tasks and for providing evidence regarding the aspects that need to be taken into account when selecting a requirement notation.
KW - Conceptual modeling
KW - Controlled experiment
KW - Requirements engineering
KW - Use cases
KW - User stories
UR - http://www.scopus.com/inward/record.url?scp=85083977789&partnerID=8YFLogxK
U2 - 10.1007/978-3-030-44429-7_16
DO - 10.1007/978-3-030-44429-7_16
M3 - Conference contribution
AN - SCOPUS:85083977789
SN - 9783030444280
T3 - Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
SP - 221
EP - 238
BT - Requirements Engineering
A2 - Madhavji, Nazim
A2 - Pasquale, Liliana
PB - Springer
Y2 - 24 March 2020 through 27 March 2020
ER -