Limiting the Scope of the Domain Language to Describe the Application Language

Agile methodologies arise as a way to cope with problems of estimation and planning that occur in traditional software development. Nevertheless, the transition to agile could be hard. The key challenge reported by literature refers to requirements, in particular with the identification and description of User Stories. It is stated that User Stories are often described vaguely by the wrong people at the wrong time. To cope with this problem, there is an already proposed strategy which consists in deriving User Stories from the domain language captured through the Language Extended Lexicon (LEL). This strategy produces an initial set of User Stories with small effort. Since the LEL aims to capture the language of the domain while the User Stories must be limited to a specific application we believe that it is necessary to adjust the LEL. In this paper, we propose a strategy to limit an LEL that describes the language of a domain to describe the vocabulary of a specific application. Consequently, User Stories derived from the limited LEL using the already proposed approach will only describe the functionality of the application. Based on a preliminary evaluation, we state that teams with no experience in writing User Stories obtain better products. Although the results are preliminaries, we think that they are

[1]  H. D. Rombach,et al.  The Goal Question Metric Approach , 1994 .

[2]  Bernd Waldmann There's never enough time: Doing requirements under resource constraints, and what requirements engineering can learn from agile development , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[3]  Nuno Oliveira,et al.  Comparing general-purpose and domain-specific languages: An empirical study , 2010, Comput. Sci. Inf. Syst..

[4]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[5]  Andreia Malucelli,et al.  Scope definition in software product lines: A semi-automatic approach through linguistic annotation , 2012, 2012 XXXVIII Conferencia Latinoamericana En Informatica (CLEI).

[6]  Julio Cesar Sampaio do Prado Leite,et al.  Managing User Stories , 2002 .

[7]  Julio Cesar Sampaio do Prado Leite,et al.  Building Intentional Models Using the ERi*c Method , 2011 .

[8]  Juha Kuusela,et al.  Transition to Agile Development - Rediscovery of Important Requirements Engineering Practices , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[9]  Larry E. Wood,et al.  Semi-structured interviewing for user-centered design , 1997, INTR.

[10]  Sara Jones,et al.  Agile Requirements Can We Have Our Cake and Eat It Too? , 2010, IEEE Software.

[11]  Vijayan Sugumaran,et al.  Integrating Software Product Line Engineering and Agile Development , 2010, IEEE Software.

[12]  Julio Cesar Sampaio do Prado Leite,et al.  Using the Language Extended Lexicon to Support Non-Functional Requirements Elicitation , 2001, WER.

[13]  Leandro Antonelli,et al.  Buenas prácticas en la especificación del dominio de una aplicación , 2013, WER.

[14]  Julio Cesar Sampaio do Prado Leite,et al.  Eliciting Multi-Agent Systems Intentionality: from Language Extended Lexicon to i* Models , 2007, XXVI International Conference of the Chilean Society of Computer Science (SCCC'07).

[15]  Leandro Antonelli,et al.  A Collaborative Approach to Describe the Domain Language through the Language Extended Lexicon , 2016, J. Object Technol..

[16]  Sjaak Brinkkemper,et al.  Forging high-quality User Stories: Towards a discipline for Agile Requirements , 2015, 2015 IEEE 23rd International Requirements Engineering Conference (RE).

[17]  A. A. Issa,et al.  Automated requirements engineering: Use case patterns-driven approach , 2011, IET Softw..

[18]  Robert Feldt,et al.  Validity Threats in Empirical Software Engineering Research - An Initial Survey , 2010, SEKE.

[19]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[20]  Benjamin L. Kovitz,et al.  Practical Software Requirements: A Manual of Content and Style , 1998 .

[21]  Yves Lepage,et al.  Ambiguity spotting using wordnet semantic similarity in support to recommended practice for Software Requirements Specifications , 2011, 2011 7th International Conference on Natural Language Processing and Knowledge Engineering.

[22]  William Hudson,et al.  User stories don't help users: introducing persona stories , 2013, INTR.

[23]  Alejandro Oliveros,et al.  Producción del LEL en un Dominio Técnico. Informe de un caso , 2000, WER.

[24]  Neil A. M. Maiden Exactly How Are Requirements Written? , 2012, IEEE Software.

[25]  Julio Cesar Sampaio do Prado Leite,et al.  A Scenario Construction Process , 2000, Requirements Engineering.

[26]  F. P. Brooks,et al.  The mythical man-month" essays on software engineering, addison-wesley , 1974 .

[27]  Leandro Antonelli,et al.  Deriving requirements specifications from the application domain language captured by Language Extended Lexicon , 2012, WER.

[28]  Julio Cesar Sampaio do Prado Leite,et al.  A strategy for conceptual model acquisition , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.