Non-Functional Requirements Elicitation Guideline for Agile Methods

Authors

  • M. Younas Faculty of Computing, Universiti Teknologi Malaysia, 81310 Johor Bahru, Johor, Malaysia. Government College University Faisalabad, Pakistan.
  • D. N. A. Jawawi Faculty of Computing, Universiti Teknologi Malaysia, 81310 Johor Bahru, Johor, Malaysia.
  • I. Ghani Monash University Malaysia Campus, Subang Jaya, Selangor, Malaysia.
  • R. Kazmi Faculty of Computing, Universiti Teknologi Malaysia, 81310 Johor Bahru, Johor, Malaysia.

Keywords:

Agile, Cloud Computing, Elicitation, Guideline, Non-Functional Requirement,

Abstract

One of the essential activities in software development is elicitation of requirement. Majority of the studies has pointed out that less attention is given to the NonFunctional Requirement (NFR). The negligence of NFR elicitation is due to lack of knowledge of the user and developer about NFR. Our study presents elicitation guidelines for NFRs in agile methods. This guideline will helps developers as well as users in agile methods. A case study is conducted on the group of master students for eliciting NFR with the help of elicitation guidelines. In addition, the initial results were obtained by extracting NFRs from eProcurement document that carries requirements of major European Union projects. The result of the case study is positive and encouraging for the new developers and users having less awareness about NFRs. Furthermore, the study describes the role of cloud computing in agile methods, especially in elicitation activity.

References

S. Franken, S. Kolvenbach, W. Prinz, I. Alvertis, “CloudTeams: Bridging the gap between developers and customers during software development processes,” Procedia Computer Science, vol. 68, pp. 188- 195, 2015.

L. Williams, “Agile requirements elicitation,” 2004. Available at http://agile.csc.ncsu.edu/SEMaterials/AgileRE.pdf

D. Domah, and F. J. Mitropoulos, “The NERV methodology: A lightweight process for addressing non-functional requirements in agile software development,” in SoutheastCon 2015. 2015, pp. 1-7.

D. D. Gregorio, “How the business analyst supports and encourages collaboration on agile projects,” in 2012 IEEE International Systems Conference SysCon 2012. 2012, pp. 1-4.

M. Galster, and E. Bucherer, “A taxonomy for identifying and specifying non-functional requirements in service-oriented development,” in I 2008 IEEE Congress on Services - Part I, 2008, pp. 345-352.

M. Rahman, and S. Ripon, “Elicitation and modeling non-functional requirements-A pos case study,” International Journal of Future Computer and Communication, vol. 2, no. 5, pp. 485-489, 2014.

S. Jeon, M. Han, E. Lee, and K. Lee, “Quality attribute driven agile development,” in 2011 9th International Conference on Software Engineering Research, Management and Applications (SERA), 2011. pp. 203-210.

F. Paetsch, A. Eberlein, and F. Maurer, “Requirements engineering and agile software development,” in Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, WET ICE 2003, 2003, pp. 308.

S. Ullah, M. Iqbal, and A. M. Khan, “A survey on issues in nonfunctional requirements elicitation,” in 2011 International Conference on Computer Networks and Information Technology (ICCNIT), 2011, pp. 333-340.

B. Boehm, and H. In, “Identifying quality-requirement conflicts,” IEEE Software, vol. 13, no. 2, pp. 25-35, 1996.

A. Silva, P.R. Pinheiro, A. Albuquerque, J. Barroso, “Approach to Define a Non-Functional Requirements Elicitation Guide Using a Customer Language,” 2016.

A. Silva, P. Pinheiro, A. Albuquerque, and J. Barroso, “A process for creating the elicitation guide of non-functional requirements,” in Software Engineering Perspectives and Application in Intelligent Systems, 2016, pp. 293-302.

W. Helmy, and A. K. O. Hegazy, “An evaluation framework for requirements elicitation in agile methods,” in The Seventh International Conference on Software Engineering Advances, Lispon, Portugal, 2012, pp. 588-593.

S. D. V. Rojo, and R. Oliveros, “Elicitation and Specification Processes of NFR for Web Applications,” in Joint Proceedings of Workshops, Doctoral Symposium, Empirical Track, and Posters, co-located with the 20th International Conference on Requirements Engineering: Foundation for Software Quality (REFSQ) 2014, 2014, pp. 141-142.

L. Chung, B. A. Nixon, E. Yu, and J. Mylopoulos, Non-Functional Requirements in Software Engineering. Springer US, 2000.

I. Sommerville, Software Engineering. Pearson, 2011.

ISO-IEC 25010: 2011 Systems and Software Engineering-Systems and Software Quality Requirements and Evaluation (SQuaRE)-System and Software Quality Models, International Organization for Standardization 2011

D. Zowghi, and C. Coulin, “Requirements elicitation: A survey of techniques, approaches, and tools, in Engineering and managing software requirements,” in Engineering and Managing Software Requirements, A. Aurum, and C. Wohlin, Eds. Berlin, Heidelberg: Springer, 2005, pp. 19-46.

X. Franch, and J. P. Carvallo, “Using quality models in software package selection,” IEEE Software, vol. 20, no. 1, pp. 34-41, 2003.

L. Chung, and J. do Prado Leite, “On non-functional requirements in software engineering,” in Conceptual modeling: Foundations and applications, A. T. Borgida, V. K. Chaudhri, P. Giorgini, and E. S. Yu, Eds. Berlin Heidelberg: Springer, 2009: pp. 363-379.

R. R. Maiti, and F. J. Mitropoulos, “Capturing, eliciting, predicting and prioritizing (CEPP) non-functional requirements metadata during the early stages of agile software development,” in SoutheastCon 2015. 2015, pp. 1-8.

R. Ankori, “Automatic requirements elicitation in agile processes,” in 2005 Proceedings. IEEE International Conference on SoftwareScience, Technology and Engineering, 2005, pp. 101-109.

T. H. Al Balushi, P. R. F. Sampaio, D. Dabhi, and P. Loucopoulos, “ElicitO: A quality ontology-guided NFR elicitation tool,” in International Working Conference on Requirements Engineering: Foundation for Software Quality, 2007, pp. 306-319.

X. Song, Z. Duan, and C. Tian, “Non-functional requirements elicitation and incorporation into class diagrams,” in International Conference on Intelligent Information Processing, 2010, pp. 72-81.

L. M. Cysneiros, and E. Yu, “Non-functional requirements elicitation, in Perspectives on software requirements,” in Perspectives on Software Requirements, J. C. S. do Prado Leite, and J. H. Doorn, Berlin, Heidelberg: Springer, 2004, pp. 115-138.

L. M. Cysneiros, and J. C. S. do Prado Leite, “Nonfunctional requirements: From elicitation to conceptual models,” IEEE Transactions on Software Engineering, vol. 30, no. 5, pp. 328-350, 2004.

G. Kotonya, and I. Sommerville, Requirements Engineering: Processes and Techniques. Wiley Publishing, 1998.

S. Singh, and I. Chana, “Introducing agility in cloud based software development through ASD,” Int. J. u-and e-Service, Sci. Technol, vol. 6, no. 5, pp. 191-202, 2013.

S. Kalem, D. Donko, and D. Boskovic, “Agile methods for cloud computing,” in 2013 36th International Convention on Information & Communication Technology Electronics & Microelectronics (MIPRO), 2013, pp. 1079-1083.

I. I. S. S. S. Zarinah, and M. Kasirun, “Agile-based software product development using cloud computing services: Findings from a case study,” Sci. Int. (Lahore),pp. 1045-1052, 2013.

M. R. J. Qureshi, and I. Sayid, “Scheme of global scrum management software,” International Journal of Information Engineering and Electronic Business(IJIEEB), vol. 7, no. 2, pp. 1-7, 2015.

M. Manuja, and Manisha, “Moving agile based projects on cloud,” in 2014 IEEE International Advance Computing Conference (IACC), 2014, pp. 1392-1397.

R. R. Maiti, Capturing, Eliciting, and Prioritizing (CEP) NonFunctional Requirements Metadata During the Early Stages of Agile Software Development, College of Engineering and Computing, Nova Southeastern University, 2016.

S. Kopczyńska, and J. Nawrocki, “Using non-functional requirements templates for elicitation: A case study,” in 2014 IEEE 4th International Workshop on Requirements Patterns (RePa), 2014, pp. 47-54.

S. Kopczyńska, S. Maćkowiak, and J. Nawrocki, “Structured meetings for non-functional requirements elicitation,” Foundations of Computing and Decision Sciences, vol. 36, pp. 35-56, 2011.

C. W. Too, S. Hassan, J. Din, A. A. Ghani, and A. Azim, “Towards improving NFR elicitation in software development,” International Journal of Information Technology and Computer Science, vol. 7, no. 1, pp. 33-44, 2013.

J. A. Zachman, “A framework for information systems architecture,” IBM Syst. J., vol. 38, no. 2-3, pp. 454-470, 1999.

D. Mairiza, D. Zowghi, and N. Nurmuliani, “An investigation into the notion of non-functional requirements,” in SAC '10 Proceedings of the 2010 ACM Symposium on Applied Computing, 2010, pp. 311-317.

M. Pierdin, and G. Bulder, “Dimensions and Types of Non-Functional Requirements NFR Dimensiones y tipos de Requisitos No-Funcionales RNF,” RACCIS, vol. 2, no. 1, pp. 11-17, 2012.

Functional Requirements For Conducting Electronic Public Procurement Under The Eu Framework, Volume I, European Communities, 2005, Retrieved: Oct 08 2016, Available at http://ec.europa.eu/idabc/servlets/Doc1ad3.pdf?id=22191.

Downloads

Published

2017-10-20

How to Cite

Younas, M., Jawawi, D. N. A., Ghani, I., & Kazmi, R. (2017). Non-Functional Requirements Elicitation Guideline for Agile Methods. Journal of Telecommunication, Electronic and Computer Engineering (JTEC), 9(3-4), 137–142. Retrieved from https://jtec.utem.edu.my/jtec/article/view/2933

Issue

Vol. 9 No. 3-4: Special Issue on Software Engineering II

Section

Articles

License

TRANSFER OF COPYRIGHT AGREEMENT

The manuscript is herewith submitted for publication in the Journal of Telecommunication, Electronic and Computer Engineering (JTEC). It has not been published before, and it is not under consideration for publication in any other journals. It contains no material that is scandalous, obscene, libelous or otherwise contrary to law. When the manuscript is accepted for publication, I, as the author, hereby agree to transfer to JTEC, all rights including those pertaining to electronic forms and transmissions, under existing copyright laws, except for the following, which the author(s) specifically retain(s):

  1. All proprietary right other than copyright, such as patent rights
  2. The right to make further copies of all or part of the published article for my use in classroom teaching
  3. The right to reuse all or part of this manuscript in a compilation of my own works or in a textbook of which I am the author; and
  4. The right to make copies of the published work for internal distribution within the institution that employs me

I agree that copies made under these circumstances will continue to carry the copyright notice that appears in the original published work. I agree to inform my co-authors, if any, of the above terms. I certify that I have obtained written permission for the use of text, tables, and/or illustrations from any copyrighted source(s), and I agree to supply such written permission(s) to JTEC upon request.