Noraini Ibrahim, Wan M. N. Wan Kadir, Safaai Deris, Shahliza Abd Halim


Natural language is frequently applied to document the stakeholders’ statements during requirement elicitation activities. Nevertheless, the use of generic natural language has potential for the issues of unclear and inconsistent requirements. These issues may result from the diverse interpretations by the stakeholders or other various sources of documents and artefacts. The main objective of this paper was to discuss the definition and application of predefined boilerplates to specify the requirements in the form of natural language statements. The proposed boilerplates were defined and classified based on two main types of requirements, namely functional and non-functional (performance, constraints, and specific quality). Two methods have been applied to evaluate the research results; the applicability of the predefined boilerplates was demonstrated using two different case studies, and the usability aspect is evaluated through synthetic environment experimentation using human respondents.  As a summary, the predefined boilerplates were found helpful, especially among novice requirement engineers to express and specify their requirements in a consistent manner and a standardized way, relatively able to improve the quality of the natural language statements. 


Natural language, requirements boilerplates, applicability, usability

Full Text:



Pohl, K. and Rupp, C. 2011. Requirements Engineering Fundamentals A Study Guide for the Certified Professional for Requirements Engineering Exam. 1 edition. CA, USA: Rocky Nook.

Ibrahim, N., Wan Kadir, W. M. N., and Deris, S. 2009. Propagating Requirement Change into Software Designs to Resilient Software Evolution in The 16th IEEE Asia Pacific Software Engineering Conference (APSEC’09).

Arora, C., Sabetzadeh, M., Briand, L., Zimmer, F., Gnaga, R. 2013. RUBRIC: A Flexible Tool for Automated Checking of Conformance to Requirement Boilerplates. In: 2013 9th Joint Meeting European Software Engineering Conference ACM SIGSOFT Symposium Foundation Software Engineering. ESEC/FSE 2013- Proc. 599-602.

Carrillo de Gea, J. M., Nicolás, J., Fernández Alemán, J. L., Toval, A., Ebert, C., Vizcaíno, A. 2012. Requirements Engineering Tools: Capabilities, Survey and Assessment. Information Software Technology. 54(2012): 1142-1157.

Farfeleder, S., Moser, T., Krall, A., Stalhane, T., Zojer, H., Panis, C. 2011. DODT: Increasing Requirements Formalism Using Domain Ontologies for Improved Embedded Systems Development. 14th IEEE International Symposium on Design and Diagnostics of Electronic Circuits and Systems. 271-274.

Hull, E., Jackson, K., Dick, J. 2005. Requirements Engineering. Springer, London,

Neill, C. J., Laplante, P. A. 2003. Requirements Engineering: The State of the Practice. IEEE Software. 20(2003): 40-45.

Zowghi, D. and Coulin, C. 2005. Requirements Elicitation: A Survey of Techniques, Approaches, and Tools. In Engineering and Managing Software requirements. Springer. 19-46.

Mavin, A. 2012. Listen, Then Use EARS. IEEE Softw. 29(2): 17-18, Mar.

Mavin, A. and Wilkinson, P. 2010. Big Ears (The Return of ‘Easy Approach to Requirements Engineering’). 18th IEEE International Requirements Engineering Conference. 6: 277-282.

Mavin, A., Wilkinson, P., Harwood, A. and Novak, M. 2009. Easy Approach to Requirements Syntax (EARS). 17th IEEE International Requirements Engineering Conference. 317-322.

Ortel, M., Malot, M., Baumgart, A., Becker, J. S., Bogusch, R., Farfeleder, S. et al. 2013. Requirements Engineering. In: A. Rajan, T. Wahl (Eds.). CESAR-Cost-efficient Methods and Processes for Safety-relevant Embedded Systems. Springer, Vienna,

Loucopoulos, P., Wan Kadir, W. M. N. 2008. BROOD: Business Rules- Driven Object Oriented Design. Journal of Database Management. 19(2008): 41-73.

Glinz, M. 2007. On Non-Functional Requirements. 15th IEEE International Requirement Engineering Conference.

Zelkowitz, M.V. and Wallace, D. 1997. Experimental Validation in Software Engineering. Information and Software Technology. 39: 735-743.

Runeson, P. and Höst, M. 2009. Guidelines for Conducting and Reporting Case Study Research in Software Engineering. Empirical Software Engineering. 14(2009): 131-164.

Wohlin, P. R., Höst, M., Ohlsson, M. C., Regnell, B., and Wesslén, A. 2012. Experimentation in Software Engineering. Springer, Berlin Heidelberg,

Robson, C. 2002. Real World Research. Second. Oxford, UK: Blackwell Publishing,

Kirakowski, J. 1994. SUMI Questionnaire Homepage, [Online]. Available:



  • There are currently no refbacks.


Copyright © 2012 Penerbit UTM Press, Universiti Teknologi Malaysia.
Disclaimer : This website has been updated to the best of our knowledge to be accurate. However, Universiti Teknologi Malaysia shall not be liable for any loss or damage caused by the usage of any information obtained from this web site.
Best viewed: Mozilla Firefox 4.0 & Google Chrome at 1024 × 768 resolution.