Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

E. Stephen, E. Mit


Software requirement specification (SRS) documented an essential requirement of software and its external interface. Many studies found the quality of SRS, but lack of the informality organizing of document and representation of functional requirement. This paper aims to evaluate the quality properties of the software requirement specification (SRS). There are four quality properties to be assessed, which are completeness, correctness, preciseness, and consistency. Completeness quality is used to evaluate the structure of the SRS document; meanwhile, the other three qualities used to evaluate the functional requirement. The measurement for each quality properties has been proposed in the previous study. The evaluation process involves a few stages. In short, the prototype would extract text through the provided document, do a calculation, and came out with the result in the form of a similarity percentage. The prototype designs in such ways it minimizes the user interference. Those resulted in reducing human error. Corpus contains libraries of term and topic are expected to increase the reliability of detection. The corpus includes topics extracted from IEEE 830 standard, vague word, terms represent Create, Read, Update, and Delete (CRUD) operation, and terms denote possible datatype. The extracted functional requirement would be refined based on the Requirement Boilerplate (RB) template. RB adopted in the study to ensure the consistency of functional refinement requirements. The percentage of similarity is determined based on comparison with IEEE 830 standard. The rate of the result of each quality properties reflects the quality of the software requirement specification.


quality properties; quantitative approach; requirement engineering; software requirement specification.

Full Text:



A. Takoshima, and M. Aoyama, “Assessing the Quality of Software Requirements Specifications for Automotive Software Systems,†in Proc. Asia-Pasific Software Engineering Conference (APSEC), 2015, p. 393-400.

E. Stephen, and E. Mit, “Framework for Measuring the Quality of Software Specification,†Journal of Telecommunication, Electronic and Computer Engineering, vol. 9(2-10), pp. 79-84, 2017.

IEEE Recommended Practice for Software Requirement Specifications, IEEE Std. 830, 1998.

K. Weiger, and J. Beatty, Software Requirement, 3rd ed., Redmond, Washington: Microsoft Press, 2013.

K. Pohl, and C. Rupp, Requirement Engineering Fundamentals, 2nd ed., Santa Barbara, United States: Rocky Nook, 2015.

P. A. Laplante, What Every Engineer Should Know About Software Engineering, 1st ed., Boca Raton, Florida: CRC Press, 2007.

E. Hull, K. Jackson, and J. Dick, Requirement Engineering, 3rd ed., New York: Springer, 2011.

R. Kazmi, D. N. A. Jawawi, R. Mohamad, and I. Ghani, “Effective Regression Test Case Selection: A Systematic Literature Review,†Journal ACM Computing Surveys (CSUR), vol. 50(2), pp. 1-32, June 2017.

S. Maalem, and N. Zarour, “Challenge of validation in requirements engineering,†Journal of Innovation in Digital Ecosystems, vol. 3(1), pp. 15-21, June 2016.

M. P. S. Bhatia, A. Kumar, and R. Beniwal, “Ontologies for Software Engineering: Past, Present and Future,†Indian Journal of Science and Technology, vol. 9(9), pp. 1-16, Mar. 2016.

C. S. Gebizli, and H. Sözer, “Automated refinement of models for model-based testing using exploratory testing,†Software Quality Journal, vol. 25(3), pp. 979-1005, Sep. 2017.

N. A. Moketar, M. Kamalrudin, M. M. Yusof, and S. Sidek, “A study of generating abstract test for requirements validation among requirements engineers,†Journal of Theoretical and Applied Information Technology, vol. 95(7), pp. 1381-1388, Apr. 2017.

S. Ahmad, U. Anuar, and N.A. Emran, “A Tool-based Boilerplate Technique to Improve SRS Quality: An Evaluation,†Journal of Telecommunication, Electronic and Computer Engineering, vol. 10(2-7), pp. 111-114, 2018.

G. Lucassen, F. Dalpiaz, J. M. E. M. v. d. Werf, and S. Brinkkemper, “Improving agile requirements: the Quality User Story framework and tool,†Requirement Engineering, vol. 21(3), pp. 383-403, Sep. 2016.

A. Mustafa, W. M. N. W. Kadir, and N. Ibrahim, “Automated Natural Language Requirements Analysis using General Architecture for Text Engineering (GATE) Framework,†Journal of Telecommunication, Electronic and Computer Engineering, vol. 9(3-4), pp. 97-101, 2017.

E. Stachtiari, A. Mavridou, P. Katsaros, S. Bliudze and J. Sifakis, “Early Validation of System Requirements and Design Through Correctness-by-Construction,†Journal of System and Software, vol. 145, pp. 52-78, Nov. 2018.

A. Nordin, N. H. A. Zaidi, and N. A. Mazlan, “Measuring Software Requirements Specification Quality,†Journal of Telecommunication, Electronic and Computer Engineering, vol. 9(3-5 Special Issue), pp. 123-128, 2017.

A. O. J. A. Sabriye, and W. M. N. W. Zainon, “An approach for detecting syntax and syntactic ambiguity in software requirement specification,†Journal of Theoretical and Applied Information Technology, vol. 96(8), pp. 2275-2284, Apr. 2018.

E. Serna, O. Bachiller, and A. Serna, “Knowledge meaning and management in requirements engineering,†International Journal of Information Management, vol. 37(3), pp. 155-161, June 2017.

H. Ahmed, A. Hussain, and F. Baharom, “Current Challenges of Requirement Change Management,†Journal of Telecommunication, Electronic and Computer Engineering, vol. 8(10), pp. 173-176, 2016.

M. Zhang, T. Yue, S. Ali, B. S. O. Okariz, R. Norgre, and K. Intxausti, “Specifying uncertainty in use case models,†The Journal of Systems and Software, vol. 144, pp. 573-603, Oct. 2018.

J. Medeiros, A. Vasconcelos, C. Silva, and M. Goulão, “Quality of software requirements specification in agile projects: A cross-case analysis of six companies,†The Journal of Systems and Software, vol. 142, pp. 171-194, Aug. 2018.

DOI: http://dx.doi.org/10.18517/ijaseit.10.4.10186


  • There are currently no refbacks.

Published by INSIGHT - Indonesian Society for Knowledge and Human Development