Evaluating A Novel Agile Requirements Engineering Method: A Case Study

Tanel Tenso, Alex Norta, Irina Vorontsova

Abstract

The use of agile methods during software development is a standard practice and user stories are an established way of breaking complex system requirements into smaller subsets. However, user stories do not suffice for understanding the bigger picture of system goals. While methods exists that try to solve this problem, they lack visual tool support and are too heavy for smaller projects. This article fills the gap by evaluating a novel agile agent-oriented modelling (AAOM) method for requirements engineering. The AAOM-method comprises a visual approach to agile requirements engineering that links goal-model creation techniques taken from agentoriented modelling and connects goals intuitively to user stories. A case study based evaluation explores the applicability of AAOM for requirements engineering in an agile software development process.

References

  1. Ambler, S. W. and Lines, M. (2012). Disciplined agile delivery: A practitioner's guide to agile software delivery in the enterprise. IBM Press.
  2. Beck, K. (2000). Extreme Programming Explained: Embrace Change. Addison-Wesley.
  3. Beck, K. et al. (2001). The agile manifesto.
  4. Cao, L. and Ramesh, B. (2008). Agile requirements engineering practices: An empirical study. IEEE Software, 25(1):60-67.
  5. Carlson, D. and Matuzic, P. (2010). Practical Agile Requirements Engineering. Technical report.
  6. Cockburn, A. (2006). Agile software development: the cooperative game. Pearson Education.
  7. Cohn, M. (2004). User Stories Applied: For Agile Software Development. Addison-Wesley.
  8. Hull, E. et al. (2010). Requirements engineering. Springer.
  9. Jensen, D. (2008). Confirmability, page 113. Sage.
  10. Kniberg, H. and Skarin, M. (2010). Kanban and Scrummaking the most of both. Lulu.com.
  11. Larman, C. and Vodde, B. (2008). Scaling lean & agile development: thinking and organizational tools for large-scale Scrum. Pearson Education.
  12. Leffingwell, D. (2010). Agile software requirements: lean requirements practices for teams, programs, and the enterprise. Addison-Wesley.
  13. Leffingwell, D. (2016). Scaled agile framework. http://scaledagileframework.com.
  14. Leffingwell, D. and Aalto, J. (2009). A lean and scalable requirements information model for the agile enterprise. https://scalingsoftwareagility.wordpress.com/.
  15. Poppendieck, M. and Poppendieck, T. (2007). Implementing lean software development: from concept to cash. Pearson Education.
  16. Robson, C. (2002). Real word research. Blackwell.
  17. Runeson, P., Host, M., Rainer, A., and Regnell, B. (2012). Case Study Research in Software Engineering: Guidelines and Examples. Wiley.
  18. SaldanĖœa, J. (2015). The coding manual for qualitative researchers. Sage.
  19. Schwaber, K. (2004). Agile project management with Scrum. Microsoft Press.
  20. Shenton, A. K. (2004). Strategies for ensuring trustworthiness in qualitative research projects. Education for Information, 22(2):63-75.
  21. Sterling, L. and Taveter, K. (2009). oriented modeling. MIT Press.
  22. Sutherland, J. et al. (2007). Distributed scrum: Agile project management with outsourced development teams. In System Sciences. IEEE.
  23. Tenso, T. and Taveter, K. (2013). Requirements engineering with agent-oriented models. In Evaluation of Novel Approaches to Software Engineering, pages 254-259.
  24. Van Lamsweerde, A. et al. (2009). Requirements engineering: from system goals to UML models to software specifications. Wiley.
  25. Van Maanen, J. (1979). The fact of fiction in organizational ethnography. Administrative Science Quarterly, pages 539-550.
  26. Version One, I. (2016). 9th annual state of agile survey. http://info.versionone.com/state-of-agiledevelopment-survey-ninth.html.
  27. Yin, R. K. (2013). Case study research: Design and methods. Sage.
  28. Yu, E. S. (2009). Social modeling and i*. In Conceptual Modeling: Foundations and Applications, pages 99- 121. Springer.
Download


Paper Citation


in Harvard Style

Tenso T., Norta A. and Vorontsova I. (2016). Evaluating A Novel Agile Requirements Engineering Method: A Case Study . In Proceedings of the 11th International Conference on Evaluation of Novel Software Approaches to Software Engineering - Volume 1: ENASE, ISBN 978-989-758-189-2, pages 156-163. DOI: 10.5220/0005829701560163


in Bibtex Style

@conference{enase16,
author={Tanel Tenso and Alex Norta and Irina Vorontsova},
title={Evaluating A Novel Agile Requirements Engineering Method: A Case Study},
booktitle={Proceedings of the 11th International Conference on Evaluation of Novel Software Approaches to Software Engineering - Volume 1: ENASE,},
year={2016},
pages={156-163},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0005829701560163},
isbn={978-989-758-189-2},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 11th International Conference on Evaluation of Novel Software Approaches to Software Engineering - Volume 1: ENASE,
TI - Evaluating A Novel Agile Requirements Engineering Method: A Case Study
SN - 978-989-758-189-2
AU - Tenso T.
AU - Norta A.
AU - Vorontsova I.
PY - 2016
SP - 156
EP - 163
DO - 10.5220/0005829701560163