Automation of requirements: user stories generated from an objective-oriented model based on the notation i*
DOI:
https://doi.org/10.26439/interfases2018.n011.2953Keywords:
requirements, user history, agile methodologies, objective-oriented modelingAbstract
This paper describes the implementation of a tool for automated generation of user stories from a graphical model. The objective-oriented modeling approach is applied, which uses the notation i*. The main rationale is that the business objective is not the one that changes, but the ways in which it can be achieved. Once the requirements are compiled through this model, user stories are generated automatically for later traceability. These comply with the basic standard proposed in agile methodologies ensuring that, when arriving at the hands of the developer, there are no ambiguities in either of the two perspectives: graphical and narrative. The results of the tests with developers and analysts, as well as the application of a questionnaire, showed that the proposed tool contributes directly to the establishment of precise, complete and consistent requirements, optimizing the time used by the team members.
Downloads
References
Álvarez, C. (2014), Go JS interactive diagrams for the web. Genbeta. Recuperado de https://www.genbeta.com/desarrollo/go-js-una-libreria-para-html5-canvas.
Bourque, P. y Fairley, R. E. (eds.) (2014). Guide to the software engineering body of knowledge (SWEBOK(R)): Version 3.0. Piscataway, N. J.: IEEE Computer Society Press.
Cohn, M. (2009). User stories applied: For agile software development. Boston: Pearson Education.
González-Baixauli, B., Laguna, M. A. y Leite, J. C. S. (2004). Análisis de variabilidad con modelos de objetivos. En M. Ridao y L. Marcio Cysneiros (eds.). Workshop em Engenharia de Requisitos (WER). Tandil, Argentina, (pp. 77-87).
Microsoft (2018). Información general sobre ASP.NET MVC. Developer Network. Recuperado de
https://msdn.microsoft.com/es-es/library/dd381412(v=vs.108).aspx.
Moccia, J. (2013). Agile requirements, definition and management (RDM). OneSpring. Recuperado de http://community.protoshare.com/wp-content/uploads/2014/03/Agile_RDM.pdf.
Sommerville, I. y Sawyer, P. (1997). Requirements engineering: a good practice guide. John Wiley & Sons, Inc.
Yu, E. S. (1997). Towards modelling and reasoning support for early-phase requirements engineering. En Proceedings of the Third 1997 IEEE International Symposium, Requirements Engineering (pp. 226-235). Annapolis, MD, USA: Institute of Electrical and Electronicals Enginers.
Downloads
Published
Issue
Section
License
Authors who publish with this journal agree to the following terms:
Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under an Attribution 4.0 International (CC BY 4.0) License. that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access).
Last updated 03/05/21
