i-manager Publications

ReQueclass: A Framework for Classifying Requirement Elicitation Questions Based on Kipling's Technique and Zachman's Enterprise Framework - A Guide for Software Requirement Engineers

Salihu Abdulkadir*, Hamzat Olanrewaju Aliyu**

* Department of Computer Science, Federal University of Technology, Minna, Nigeria.

** School of Information and Communication Technology, Federal University of Technology, Minna, Nigeria.

Periodicity:October - December'2018
DOI : https://doi.org/10.26634/jse.13.2.15625

Abstract

At present, interview is still considered one of the pragmatic approaches to gathering software requirements from the different stakeholders in a software project. Despite unrelenting efforts by researchers, requirements gathered using this method still suffer anomalies such as inconsistency and incompleteness; this problem is partly due to communication gaps between Requirement Engineers (RE) and project stakeholders and partly due to the RE directing some questions to the wrong persons. This paper proposes a framework, which mirrors the Zachman's Enterprise Framework to systematically classify requirement interview questions and assign different question categories to appropriate persons in a disciplined way. A working software project is used as an example to illustrate the use of the framework.

Keywords

ReQueClass, Requirement Question Classification, Requirements Elicitation, Kipling Method, Zachman's Enterprise Framework

How to Cite this Article?

Abdulkadir, S., & Aliyu, H. O. (2018). Requeclass: A Framework for Classifying Requirement Elicitation Questions Based on Kipling's Technique and Zachman's Enterprise Framework, i-manager's Journal on Software Engineering, 13(2), 9-17. https://doi.org/10.26634/jse.13.2.15625

References

[1]. Abad, Z. S. H., Shymka, A., Pant, S., Currie, A., & Ruhe, G. (2016, September). What are practitioners asking about Requirements Engineering? An exploratory analysis of social Q&A sites. In Requirements Engineering Conference Workshops (REW), IEEE International (pp. 334-343). IEEE.

[2]. Carmagnola, F. (2008). The five Ws for user model interoperability. In Ubiquitous User Modeling (pp. 30-36).

[3]. Chen, X., & Jin, Z. (2016). Capturing requirements from expected interactions between software and its interactive environment: an ontology based approach. International Journal of Software Engineering and Knowledge Engineering, 26(01), 15-39.

[4]. Chung, S., Won, D., Baeg, S. H., & Park, S. (2009, January). Service-oriented reverse reengineering: 5W1H model-driven re-documentation and candidate services identification. In Service-Oriented Computing and Applications (SOCA), 2009 IEEE International Conference on (pp. 1-6). IEEE.

[5]. Hadar, I., Soffer, P., & Kenzi, K. (2014). The role of domain knowledge in requirements elicitation via inter views: An explorator y study. Requirements Engineering, 19(2), 143-159.

[6]. Hanif, M. K., Talib, M. R., Haq, N. U., Mansoor, A., Sarwar, M. U., & Ayub, N. (2017). A collaborative approach for effective requirement elicitation in oblivious client environment. International Journal of Advanced Computer Science and Applications, 8(6), 179-186.

[7]. Hart, G. (1996). The five W's: An old tool for the new task of task analysis. Technical Communication, 43(2), 139- 145.

[8]. Hickey, A. M., & Davis, A. M. (2003, September). Elicitation technique selection: How do experts do it? In Requirements Engineering Conference, 2003. Proceedings. 11^th IEEE international (pp. 169-178). IEEE.

[9]. Jabar, M. A., Ahmadi, R., Shafazand, M. Y., Ghani, A. A. A., & Sidi, F. (2013, August). An automated method for requirement determination and structuring based on 5W1H elements. In Control and System Graduate Research Colloquium (ICSGRC), 2013 IEEE 4^th (pp. 32-37). IEEE.

[10]. Kipling, R. (1902). Just so Stories. London, UK: Macmillan & Co.

[11]. Lee, Y., & Zhao, W. (2006, June). An ontology-based approach for domain requirements elicitation and analysis. In Computer and Computational Sciences, 2006. IMSCCS'06. First International Multi-Symposiums on (Vol. 2, pp. 364-371). IEEE.

[12]. Mishra, A., Awal, A., & Elijah, J. (2017). Automation of requirement analysis in software engineering. International Journal on Recent and Innovation Trends in Computing and Communication, 5(5), 1173-1188.

[13]. Mohanan, M., & Samuel, P. (2016). Software Requirement Elicitation using natural language processing. In Innovations in Bio-Inspired Computing and Applications (pp. 197-208). Springer, Cham.

[14]. Moon, M., Yeom, K., & Chae, H. S. (2005). An approach to developing domain requirements as a core asset based on commonality and variability analysis in a product line. IEEE Transactions on Software Engineering, 31(7), 551-569.

[15]. Nuseibeh, B., & Easterbrook, S. (2000, May). Requirements engineering: A roadmap. In Proceedings of the Conference on the Future of Software Engineering (pp. 35-46). ACM.

[16]. Oranje, A. P., Al-Mutairi, N., & Shwayder, T. (Eds.). (2016). Practical Pediatric Dermatology: Controversies in Diagnosis and Treatment. Springer.

[17]. Pohl, K. (2016). Requirements engineering fundamentals: A study guide for the certified professional for requirements engineering exam-foundation level. Rocky Nook, Inc.

[18]. Reza, A. Y. (2015). Requirements Engineering practices in global software engineering organizations: A study in the banking industry (Master Thesis, Delft University of Technology).

[19]. Sadiq, M. (2017). A fuzzy set-based approach for the prioritization of stakeholders on the basis of the importance of software requirements. IETE Journal of Research, 63(5), 616-629.

[20]. Shabir, M. (2016). Enhancing students' ability in extending ideas in the narrative writing through the 5W1H concept. English Journal, 17(2), 48-54.

[21]. Sommerville, I. (2005). Integrated requirements engineering: A tutorial. IEEE Software, 22(1), 16-23.

[22]. Sommerville, I., Sawyer, P., & Viller, S. (1998, April). Viewpoints for requirements elicitation: A practical approach. In Requirements Engineering, 1998. Proceedings. 1998 Third International Conference on (pp. 74-81). IEEE.

[23]. Sutcliffe, A., & Sawyer, P. (2013, July). Requirements elicitation: Towards the unknown unknowns. In Requirements Engineering Conference (RE), 2013 21^st IEEE International (pp. 92-104). IEEE.

[24]. Tiwari, S., & Rathore, S. S. (2017). A methodology for the selection of requirement elicitation techniques. arXiv preprint arXiv:1709.08481.

[25]. Wang, M., & Zeng, Y. (2009). Asking the right questions to elicit product requirements. International Journal of Computer Integrated Manufacturing, 22(4), 283-298.

[26]. Wong, L. R., Mauricio, D. S., & Rodriguez, G. D. (2017). A systematic literature review about software requirements elicitation. Journal of Engineering Science and Technology, 12(2), 296-317.

[27]. Zachman, J. A. (2003). The Zachman framework for enterprise architecture: primer for enterprise engineering and manufacturing. Zachman International. Retrieved from http://www3.cis.gsu.edu/dtruex/courses/CIS8090/ Cases-Articles/ZachmanBookRFIextract.pdf

[28]. Zhaoyin, Z., Yanfang, L., & Chao, C. (2009, December). Software requirement analysis research based on event-driven. In Computer Science-Technology and Applications, 2009. IFCSTA'09. International Forum on (Vol. 1, pp. 247-250). IEEE.

ReQueclass: A Framework for Classifying Requirement Elicitation Questions Based on Kipling's Technique and Zachman's Enterprise Framework - A Guide for Software Requirement Engineers

Abstract

Keywords

How to Cite this Article?

References

If you have access to this article please login to view the article or kindly login to purchase the article

Purchase Instant Access

Options for accessing this content:

	North Americas,UK, Middle East,Europe		India	Rest of world
	USD	EUR	INR	USD-ROW
Pdf	35	35	200	20
Online	35	35	200	15
Pdf & Online	35	35	400	25