Abstract
[Context] Failures in management of non-functional requirements (NFRs) (e.g., incomplete or ambiguous NFRs) are frequently identified as one of the root causes of software failures. Recent studies confirm that using a catalog of NFR templates for requirements elicitation positively impacts the quality of requirements. However, practitioners are afraid of templates as the return on investment in this technique is still unknown.
[Aim] Our aim was to investigate how the usefulness of catalog of NFR templates and its maintenance costs change over time.
[Method] Using 41 industrial projects with 2,231 NFRs, we simulated 10,000 different random evolutions of a catalog of NFR templates. It allowed us to examine the distribution of catalog value, maintenance effort, catalog utilization over a sequence of projects (a counterpart of elapsing time).
[Results] From the performed analysis it follows that after considering about 40 projects we can expect catalog value of 75% or more and maintenance effort of 10% or less. Then one could expect about 400 templates in the catalog, but only about 10% of them would be used by a single project (on average).
[Conclusions] Usefulness and maintenance costs of catalog of NFR templates depend on the number of projects used to develop it. A catalog of high usefulness and low maintenance effort need to be developed from about 40 projects. Since high variability of studied projects, this number in practice might be lower. From the perspective of a large or medium software company it seems not a big problem.
This work was partially supported by the Young Staff grant 09/91/SBAD/0683.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsReferences
Website of NoRTs. http://norts.cs.put.poznan.pl
Adolph, S., Bramble, P., Cockburn, A., Pols, A.: Patterns for Effective Use Cases. Addison-Wesley, Boston (2002)
Alsaqaf, W., Daneva, M., Wieringa, R.: Quality requirements challenges in the context of large-scale distributed agile: an empirical study. Inf. Softw. Technol. 110, 39–55 (2019)
Berry, D.M., Kamsties, E., Krieger, M.M.: From Contract Drafting to Software Specification: Linguistic Sources of Ambiguity. A Handbook. Ver 1.0. https://cs.uwaterloo.ca/~dberry/handbook/ambiguityHandbook.pdf. Accessed 07 Sept 2015
Boehm, B., In, H.: Identifying quality-requirement conflicts. IEEE Softw. 13(2), 25–35 (1996)
Breitman, K.K., Leite, J.C.S., Finkelstein, A.: The world sa stage: a survey on requirements engineering using a real-life case study. J. Braz. Comput. Soc. 6(1), 13–37 (1999)
Cleland-Huang, J., Mazrouee, S., Liguo, H., Port, D.: Open-Science teraPROMISE repository. http://openscience.us/repo/requirements/other-requirements/nfr. (2010). Accessed 26 June 2017
Denger, C., Berry, D.M., Kamsties, E.: Higher quality requirements specifications through natural language patterns. In: IEEE International Conference on Software: Science, Technology and Engineering, pp. 80–90 (2003)
Doerr, J., Paech, B., Koehler, M.: Requirements engineering process improvement based on an information model. In: 2004 Proceedings of 12th IEEE International Requirements Engineering Conference, pp. 70–79. IEEE (2004)
Eckhardt, J., Vogelsang, A., Femmer, H., Mager, P.: Challenging incompleteness of performance requirements by sentence patterns. In: International Requirements Engineering Conference (RE), pp. 46–55. IEEE (2016)
Gilb, T.: Competitive Engineering: A Handbook for Systems and Software Engineering Management Using Planguage. Butterworth-Heinemann, Oxford (2005)
Hull, E., Jackson, K., Dick, J.: Requirements Engineering (2005)
ISO/IEC: ISO/IEC 25010 - Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models. Technical report, ISO/IEC (2010)
Kopczynska, S., Nawrocki, J.: Using non-functional requirements templates for elicitation: a case study. In: IEEE International Workshop Requirements Patterns (2014)
Kopczynska, S., Nawrocki, J., Ochodek, M.: An empirical study on catalog of non-functional requirement templates: Usefulness Maintenance Issues. Inf. Softw. Technol. 103, 75–91 (2018)
Kopczyńska, S., Ochodek, M., Nawrocki, J.: On importance of non-functional requirements in agile software projects—a survey. In: Jarzabek, S., Poniszewska-Marańda, A., Madeyski, L. (eds.) Integrating Research and Practice in Software Engineering. SCI, vol. 851, pp. 145–158. Springer, Cham (2020). https://doi.org/10.1007/978-3-030-26574-8_11
Lam, W., McDermid, T., Vickers, A.: Ten steps towards systematic requirements reuse. In: Intenational Symposium on Requirements Engineering, pp. 6–15. IEEE (1997)
Lindstrom, D.R.: Five ways to destroy a development project. IEEE Softw. 10(5), 55–58 (1993)
Mavin, A., Wilkinson, P.: Big Ears (The Return of “Easy Approach to Requirements Engineering”). In: Requirements Engineering Conference, pp. 277–282 (2010)
Nuseibeh, B.: Ariane 5: who dunnit? IEEE Softw. 14(3), 15–16 (1997)
Palomares, C., Quer, C., Franch, X.: Requirements reuse and requirement patterns: a state of the practice survey. Empirical Softw. Eng. 22, 1–44 (2015)
Pohl, K.: Requirements Engineering: Fundamentals, Principles, and Techniques. Springer, Heidelberg (2010)
Pohl, K., Rupp, C.: Requirements Engineering Fundamentals. Rocky Nook, San Rafael (2011)
R Documentation: Box Plots. www.rdocumentation.org/packages/graphics/versions/3.5.1/topics/boxplot. Accessed 28th Sept 2018
Regnell, B., Svensson, R.B., Olsson, T.: Supporting roadmapping of quality requirements. IEEE Softw. 25(2), 42–47 (2008)
Renault, S., Méndez Bonilla, Ó., Franch Gutiérrez, J., Quer Bosor, M.C., et al.: A pattern-based method for building requirements documents in call-for-tender processes. IJCSA 6(5), 175–202 (2009)
Riaz, M., et al.: Identifying the implied: findings from three differentiated replications on the use of security requirements templates. Empirical Softw. Eng. 22, 2127–2178 (2016)
Robertson, S., Robertson, J.: Mastering the Requirements Process: Getting Requirements Right, 3rd edn. Addison-Wesley, Boston (2012)
Sommerville, I., Sawyer, P.: Requirements Engineering: A Good Practice Guide. Wiley, Hoboken (1997)
Withall, S.: Software Requirement Patterns (Developer Best Practices). Microsoft Press, Redmond (2007)
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M.C., Regnell, B., Wesslén, A.: Experimentation in Software Engineering. Springer, Heidelberg (2012). https://doi.org/10.1007/978-3-642-29044-2
Acknowledgments
We would like to thank the companies that shared their data with us especially ATREM S.A., Consdata Sp. z o.o., Currency One S.A., IT Department of Poznan City Hall, Roche Sp. z o.o., TALEX S.A.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2019 Springer Nature Switzerland AG
About this paper
Cite this paper
Kopczyńska, S., Nawrocki, J., Ochodek, M. (2019). When NFR Templates Pay Back? A Study on Evolution of Catalog of NFR Templates. In: Franch, X., Männistö, T., Martínez-Fernández, S. (eds) Product-Focused Software Process Improvement. PROFES 2019. Lecture Notes in Computer Science(), vol 11915. Springer, Cham. https://doi.org/10.1007/978-3-030-35333-9_11
Download citation
DOI: https://doi.org/10.1007/978-3-030-35333-9_11
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-030-35332-2
Online ISBN: 978-3-030-35333-9
eBook Packages: Computer ScienceComputer Science (R0)