Top

Software Quality Journal

Published in:

15-09-2016

A systematic literature review on quality criteria for agile requirements specifications

Authors: Petra Heck, Andy Zaidman

Published in: Software Quality Journal | Issue 1/2018

Activate our intelligent search to find suitable subject content or patents.

search-config

AI-assisted search

Off

Abstract

The quality of requirements is typically considered as an important factor for the quality of the end product. For traditional up-front requirements specifications, a number of standards have been defined on what constitutes good quality : Requirements should be complete, unambiguous, specific, time-bounded, consistent, etc. For agile requirements specifications, no new standards have been defined yet, and it is not clear yet whether traditional quality criteria still apply. To investigate what quality criteria for assessing the correctness of written agile requirements exist, we have conducted a systematic literature review. The review resulted in a list of 16 selected papers on this topic. These selected papers describe 28 different quality criteria for agile requirements specifications. We categorize and analyze these criteria and compare them with those from traditional requirements engineering. We discuss findings from the 16 papers in the form of recommendations for practitioners on quality assessment of agile requirements. At the same time, we indicate the open points in the form of a research agenda for researchers working on this topic .

previous article Tackling class overlap and imbalance problems in software defect prediction

next article How do developers react to API evolution? A large-scale empirical study

Dont have a licence yet? Then find out more about our products and how to get one now:

Springer Professional "Wirtschaft"

Online-Abonnement

Mit Springer Professional "Wirtschaft" erhalten Sie Zugriff auf:

über 67.000 Bücher
über 340 Zeitschriften

aus folgenden Fachgebieten:

Bauwesen + Immobilien
Business IT + Informatik
Finance + Banking
Management + Führung
Marketing + Vertrieb
Versicherung + Risiko

Jetzt Wissensvorsprung sichern!

inform now

Springer Professional "Wirtschaft+Technik"

Online-Abonnement

Mit Springer Professional "Wirtschaft+Technik" erhalten Sie Zugriff auf:

über 102.000 Bücher
über 537 Zeitschriften

aus folgenden Fachgebieten:

Automobil + Motoren
Bauwesen + Immobilien
Business IT + Informatik
Elektrotechnik + Elektronik
Energie + Nachhaltigkeit
Finance + Banking
Management + Führung
Marketing + Vertrieb
Maschinenbau + Werkstoffe
Versicherung + Risiko

Jetzt Wissensvorsprung sichern!

inform now

Springer Professional "Technik"

Online-Abonnement

Mit Springer Professional "Technik" erhalten Sie Zugriff auf:

über 67.000 Bücher
über 390 Zeitschriften

aus folgenden Fachgebieten:

Automobil + Motoren
Bauwesen + Immobilien
Business IT + Informatik
Elektrotechnik + Elektronik
Energie + Nachhaltigkeit
Maschinenbau + Werkstoffe

Jetzt Wissensvorsprung sichern!

inform now

Available only for authorised users

https://jitre.wordpress.com/.

http://www.xp2015.org/1st-international-workshop-on-requirements-engineering-in-agile-development/.

http://scholar.google.com, last visited July 18th, 2015.

Auger, C. P. (1994) Information sources in grey literature. Bowker-Saur.

Beck, K. (2002). Test driven development: By example. Boston, MA: Addison-Wesley Longman Publishing Co. Inc.

Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M. et al. (2001). Manifesto for agile software development. http://agilemanifesto.org. Last visited April 16, 2015.

Belsis, P., Koutoumanos, A., & Sgouropoulou, C. (2014). PBURC: A patterns-based, unsupervised requirements clustering framework for distributed agile software development. Requirements Engineering, 19(2), 213–225.CrossRef

Bhasin, S. (2012). Quality assurance in agile: A study towards achieving excellence. In AGILE India (AGILE INDIA) (pp 64–67).

Bjarnason, E., Unterkalmsteiner, M., Engstrm, E., & Borg, M. (2015). An industrial case study on test cases as requirements. In C. Lassenius, T. Dingsyr, & M. Paasivaara (Eds.) Agile Processes, in Software Engineering, and Extreme Programming, Lecture Notes in Business Information Processing (Vol. 212, pp. 27–39) Springer International Publishing. doi:10.1007/978-3-319-18612-2_3.

Brereton, P., Kitchenham, B. A., Budgen, D., Turner, M., & Khalil, M. (2007). Lessons from applying the systematic literature review process within the software engineering domain. Journal of Systems and Software, 80(4), 571–583.CrossRef

Cornelissen, B., Zaidman, A., van Deursen, A., Moonen, L., & Koschke, R. (2009). A systematic survey of program comprehension through dynamic analysis. IEEE Transactions on Software Engineering, 35(5), 684–702.CrossRef

Davis, A., & Hickey, A. (2009). A quantitative assessment of requirements engineering publications 1963–2008. In M. Glinz & P. Heymans (Eds.), Requirements engineering:Foundation for software quality (Vol. 5512, pp. 175–189). Lecture Notes in Computer Science, Berlin Heidelberg: Springer.

Davis, A., Overmyer, S., Jordan, K., Caruso, J., Dandashi, F., Dinh, A. et al. (1993). Identifying and measuring quality in a software requirements specification. In Int’l Software Metrics Symposium (pp. 141–152). Baltimore (MD).

De Lucia, A., & Qusef, A. (2010). Requirements engineering in agile software development. Journal of Emerging Technologies in Web Intelligence, 2(3), 309–326.CrossRef

Desharnais, J. M., Kocaturk, B., & Abran, A. (2011). Using the cosmic method to evaluate the quality of the documentation of agile user stories. In Joint Conference of the 21st Int’l Workshop on Software Measurement and 6th Int’l Conference on Software Process and Product Measurement (IWSM-MENSURA), Nara, Japan (pp. 269–272).

Dingsøyr, T., Dyba, T., & Abrahamsson, P. (2008). A preliminary roadmap for empirical research on agile software development. In AGILE Conference, Toronto (ON) (pp. 83–94).

Dumas-Monette, JF., & Trudel, S. (2014). Requirements engineering quality revealed through functional size measurement: An empirical study in an agile context. In Joint Conference of the International Workshop on Software Measurement and the International Conference on Software Process and Product Measurement (IWSM-MENSURA), Rotterdam, The Netherlands (pp. 222–232).

Duncan, R. (2001). The quality of requirements in extreme programming. CrossTalk, June 19, pp. 22–31.

Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9–10), 833–859.CrossRef

Eberlein, A., & Leite, J. (2002). Agile requirements definition: A view from requirements engineering. In Proceedings of the International Workshop on Time-Constrained Requirements Engineering (TCRE02), Essen, Germany (pp. 4–8).

Ernst, N. A., & Murphy, G. (2012). Case studies in just-in-time requirements analysis. Int’l Workshop on Empirical Requirements Engineering (pp. 25–32). Chicago (IL): IEEE.

Farid, W., & Mitropoulos, F. (2013). Norplan: Non-functional requirements planning for agile processes. In Proceedings of IEEE Southeastcon, Jacksonville, FL (pp. 1–8).

Firesmith, D. (2004). Generating complete, unambiguous, and verifiable requirements from stories, scenarios, and use cases. Journal of Object Technology, 3(10), 27–40.CrossRef

Gottesdiener, E., & Gorman, M. (2010). Slicing requirements for agile success. Better Software, 2010(04), 16–21.

Grau, R., Lauenroth, K., Bereza, B., van Veenendaal, E., & van der Zee, S. (2014). Requirements engineering and agile development - collaborative, just enough, just in time, sustainable. IREB.

Heck, P., & Zaidman, A. (2014). A quality framework for agile requirements: A practitioner’s perspective. Technical Report TUD-SERG-2014-006, Software Engineering Research Group, Delft University of Technology.

Heck, P., & Zaidman, A. (2016). A framework for quality assessment of just-in-time requirements: The case of open source feature requests. Requirements Engineering (pp. 1–21).

Huo, M., Verner, J., Zhu, L., & Babar, M. (2004). Software quality and agile methods. In Int’l Computer Software and Applications Conference (Vol.1, pp. 520–525). doi:10.1109/CMPSAC.2004.1342889.

IEEE. (1998). IEEE recommended practice for software requirements specifications. IEEE Std 830-1998.

Inayat, I., Salim, S. S., Marczak, S., Daneva, M., & Shamshirband, S. (2014). A systematic literature review on agile requirements engineering practices and challenges. Computers in Human Behavior, 51, 915–929.CrossRef

Kabbedijk, J., Bezemer, C. P., Jansen, S., & Zaidman, A. (2015). Defining multi-tenancy: A systematic mapping study on the academic and the industrial perspective. Journal of Systems and Software, 100, 139–148.CrossRef

Kassab, M. (2014). An empirical study on the requirements engineering practices for agile software development. In 40th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), Verona, Italy (pp. 254–261).

Kitchenham, B., & Charters, S. (2007). Guidelines for performing systematic literature reviews in software engineering. Techical Report, EBSE-2007-01.

Kitchenham, B. A. (2004). Procedures for performing systematic reviews. Technical Report.

Lee, C., Guadagno, L., & Jia, X. (2003). An agile approach to capturing requirements and traceability. In Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering, Montreal, Canada (pp. 17–23).

Leffingwell, D. (2011). Agile software requirements: Lean requirements practices for teams, programs, and the enterprise (1st ed.). Boston: Addison-Wesley Professional.

Liskin, O., Pham, R., Kiesling, S., & Schneider, K. (2014a). Why we need a granularity concept for user stories. In G. Cantone & M. Marchesi (Eds.) Agile Processes in Software Engineering and Extreme Programming, Lecture Notes in Business Information Processing (Vol. 179, pp. 110–125). Berlin: Springer International Publishing.

Liskin, O., Schneider, K., Fagerholm, F., & Münch, J. (2014b). Understanding the role of requirements artifacts in kanban. In Proceedings of the 7th International Workshop on Cooperative and Human Aspects of Software Engineering, Hyderabad, India, CHASE 2014 (pp. 56–63).

Melnik, G., Maurer, F., & Chiasson, M. (2006). Executable acceptance tests for communicating business requirements: Customer perspective. In Agile Conference, 2006 (pp. 12–46). doi:10.1109/AGILE.2006.26.

North, D. (2006). Behavior modification. Better Software, 2006, 4–12.

Paetsch, F., Eberlein, A., & Maurer, F. (2003). Requirements engineering and agile software development. In Int’l Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises, Linz, Austria (pp. 308–308).

Patel, C., & Ramachandran, M. (2009). Story card maturity model (smm): A process improvement framework for agile requirements engineering practices. JSW, 4(5), 422–435.CrossRef

Power, K. (2014). Definition of ready: An experience report from teams at cisco. In G. Cantone, M. Marchesi (Eds.) Agile processes in software engineering and extreme programming. Lecture Notes in Business Information Processing (Vol. 179, pp. 312–319). Berlin: Springer International Publishing.

Ramesh, B., Cao, L., & Baskerville, R. (2010). Agile requirements engineering practices and challenges: An empirical study. Information Systems Journal, 20(5), 449–480.CrossRef

Runeson, P., Host, M., Rainer, A., & Regnell, B. (2012). Case study research in software engineering: Guidelines and examples. New York: Wiley.CrossRef

Sfetsos, P., & Stamelos, I. (2010). Empirical studies on quality in agile practices: A systematic literature review. In Seventh International Conference on the Quality of Information and Communications Technology (QUATIC), Porto, Portugal (pp. 44–53).

Sillitti, A., & Succi, G. (2005). Engineering and managing software requirements, Chapter 14. In A. Aurum & C. Wohlin (Eds.), Requirements engineering for agile methods (pp. 309–326). Berlin: Springer.

Srinivasan, J., & Lundqvist, K. (2009). Using agile methods in software product development: A case study. In Sixth International Conference on Information Technology: New Generations. ITNG ’09, Las Vegas, NV (pp. 1415–1420).

Staples, M., & Niazi, M. (2007). Experiences using systematic review guidelines. Journal of Systems and Software, 80(9), 1425–1437.CrossRef

Wake, B. (2003). INVEST in good stories, and SMART tasks. http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/. Accessed December, 2015.

Wieringa, R., Maiden, N., Mead, N., & Rolland, C. (2005). Requirements engineering paper classification and evaluation criteria: A proposal and a discussion. Requirements Engineering, 11(1), 102–107.CrossRef

Wohlin, C. (2014). Guidelines for snowballing in systematic literature studies and a replication in software engineering. In Proceedings of the International Conference on Evaluation and Assessment in Software Engineering (EASE), London, UK (pp. 38:1–38:10).

Title: A systematic literature review on quality criteria for agile requirements specifications
Authors: Petra Heck
Andy Zaidman
Publication date: 15-09-2016
Publisher: Springer US
Published in: Software Quality Journal / Issue 1/2018
Print ISSN: 0963-9314
Electronic ISSN: 1573-1367
DOI: https://doi.org/10.1007/s11219-016-9336-4

Springer Professional

Abstract

Please log in to get access to your license.

Dont have a licence yet? Then find out more about our products and how to get one now:

Springer Professional "Wirtschaft"

Springer Professional "Wirtschaft+Technik"

Springer Professional "Technik"

Other articles of this Issue 1/2018

In this issue

How do developers react to API evolution? A large-scale empirical study

Towards automation of IT systems repairs

Fail-safe testing of safety-critical systems: a case study and efficiency analysis

Tackling class overlap and imbalance problems in software defect prediction

Predicting failures in agile software development through data analytics

Premium Partner