Radomir Prodanović, Dejan Rančić, Ivan Vulić, Dušan Bogićević

DOI Number
First page
Last page


The requirement quality affects product development at all lifecycle stages, as well as the end product. Poorly defined requirements bring to extended deadlines, increased financial costs, even to project disruption. Current researches related to the good quality of requirements include characteristics of good requirements and the development of new elicitation techniques. Requirement quality evaluation should be tailored both to the professionals and users who defined requirements according to their needs. Therefore, the model is designed for requirement quality measurement based on the characteristics of good requirements by application of the Generalized Prioritized Fuzzy Constraint Satisfaction Problem. The model enables the participation of selected characteristics of good requirements in quality evaluation, according to priorities. The evaluator obtains information if the requirement satisfies the given quality satisfaction threshold based on the degree of fulfillment of selected characteristics of a good requirement. The model is applied to all types of requirements, as well as to the evaluation of requirements at all software development lifecycle stages.


Quality requirement, GFPCSP, fuzzy logic, elicitation requirement, software product

Full Text:



The Standish Group. Chaos manifesto: Think big, act small. 2013

K. Pohl, Requirements engineering: Fundamentals, principles, and techniques. Berlin, Germany: Springer-Verlag, 2010.

N. Mulla and S. Girase,”A new approach to requirement elicitation based on stakeholder recommendation and collaborative filtering”, International Journal of Software Engineering and Applications (IJSEA), 3(3), 51-60, 2012.

L.R. Wong, and D.S. Mauricio, “New factors that affect the activities of the requirements elicitation process”, Journal of Engineering Science and Technology (JESTEC), 13(7), 1992-2015, 2018.

B. Davey and K. Parker, “Requirements elicitation problems: A literature analysis Issues in informing”, Science and Information Technology, 12, 71-82, 2015.

I. Hadar, P. Soffer and K. Kenzi, “The role of domain knowledge in requirements elicitation via interviews: An exploratory study”, Requirements Engineering, 19(2), 143-159, 2014.

D.C. Derrick, A. Read, C. Nguyen, A. Callens and G.-J. de Vreede, “Automated group facilitation for gathering wide audience end-user requirements”. Proceedings of 46th Hawaii International Conference on System Sciences. Wailea, Maui, Hawaii, pp. 195-204, 2013.

R. Prodanović and I. Vulić, "Classification as an approach to public key infrastructure requirements analysis", IET Software, vol. 13, no. 6, pp. 518-527, 2019, doi: 10.1049/iet-sen.2018.5286.

Ludwig Consulting Services, LLC. Managing requirements. 2009, Retrieved May 7, 2018, from

G. Génova, J. M. Fuentes, J. Llorens, O. Hurtado, V. Moreno, “A Framework to Measure and Improve the Quality of Textual Requirements”, Requirements Engineering 18(1), 2013, DOI: 10.1007/s00766-011-0134-z

B. Heinrich, D. Hristova, M. Klier, A. Schiller, M. Szubartowicz, “Requirements for Data Quality Metrics”, Journal of Data and Information Quality, Volume 9, Issue 2, January 2018,

R. J. Halligan, “Requirements Quality Metrics: The Basis of Informed Requirements Engineering Management”, Presented at the 1993 Complex Systems Engineering Synthesis and Assessment Technology Workshop (CSESAW ’93), Calvados, MD, USA

P. S. Kummler, L. Vernisse, H. Fromm, “How Good are My Requirements?: A New Perspective on the Quality Measurement of Textual Requirements”, 11th International Conference on the Quality of Information and Communications Technology (QUATIC), Coimbra, Portugal, 4-7 Sept. 2018, DOI: 10.1109/QUATIC.2018.00031

L. R. Wong and D. S. Mauricio, “Qualities that the Activities of the Elicitation Process Must Meet to Obtain a Good Requirement”, Journal of Engineering Science and Technology Vol. 14, No. 5, pp. 2883 – 2912, 2019.

B. Boehm, "A view of 20th and 21st century software engineering". ICSE '06 Proceedings of the 28th international conference on Software engineering. University of Southern California, University Park Campus, Los Angeles, CA: Association for Computing Machinery, ACM New York, NY, USA. pp. 12–29. 2006. ISBN 1-59593-375-1.

M.A.Wick, E. Iem, M.A.J Burns, et al.: ‘A guide to the business analysis body of knowledge® (BABOK® Guide)’, v3, IIBA, 2015, p. 16

IEEE SA - 610.12-1990 - IEEE Standard Glossary of Software Engineering Terminology.

A. M. Davis, Software Requirements: Objects, Functions, and States, Second Edition. Prentice Hall. 1993, ISBN 978-0-13-805763-3.

IEEE Computer Society, IEEE Recommended Practice for Software Requirements Specifications. Institute of Electrical and Electronics Engineers, Inc. 1998, ISBN 978-0-7381-0332-7.

G. Koelsch, “Requirements Writing for System Engineering”, Springer Science+Business Media New York, New York, 2016, DOI 10.1007/978-1-4842-2099-3

D. Firesmith, “Specifying Good Requirements”, Journal of Object Technology, Vol. 2, No. 4, 2003

X. Luo, J. Lee, H. Leung and N.Jennings, “Prioritized Fuzzy Constraint Satisfaction Problems: Axioms, Instantiation and Validation”. Fuzzy Sets and Systems, 136(2), pp. 151–188, 2003

G. Panić, The development a dedicated system for the application fuzzy logic in systems for manage of XML documents, Doctoral thesis, Faculty of Sciences, University of Novi Sad, 2013

A. Takači, Trougaone norme prioriteta i njihova primena na modeliranje ispunjenja fazi ograničenja, Doctoral thesis, Faculty of Sciences, University of Novi Sad, 2006

NASA, Appendix C: How to Write a Good Requirement, 2019,



  • There are currently no refbacks.

Print ISSN: 1820-6417
Online ISSN: 1820-6425