Bridging the Gap Between Stakeholder and Software Products: A Review of Software Requirement Engineering Techniques


  • Monday Eze Babcock University
  • Shade Kuyoro
  • Folasaded Ayankoya
  • Nzechukwu Chizaram Otuneme Babcock University


software, Requirement Engineering, Software Products, Stakeholders


Effective software requirement engineering plays a crucial role in bridging the gap between stakeholders and software products. The success of any software project heavily relies on accurately capturing, analyzing, and documenting stakeholders' needs and expectations. This article provides a comprehensive review of various software requirement engineering techniques that facilitate the alignment of stakeholder requirements with software product development. Software requirements are extracted from a variety of stakeholders, but the decision of "what to develop" is a difficult one. Stakeholders' lack of clarity about what they want makes requirement elicitation a difficult and vital task. It explores the significance of understanding stakeholders' perspectives, discusses popular requirement engineering approaches, and highlights their strengths and limitations. The article concludes by emphasizing the importance of selecting appropriate requirement engineering techniques based on the project's context and offers recommendations for future research in this domain.


IEEE Standard, “INTERNATIONAL STANDARD ISO / IEC / IEEE Systems and software engineering - Architecture description,” Ieee Standards, vol. 2018, 2018.

C. W. Ho, M. J. Johnson, L. Williams, and E. M. Maximilien, “On Agile performance requirements specification and testing,” in Proceedings - AGILE Conference, 2006, 2006, pp. 47–52. doi: 10.1109/AGILE.2006.41.

C.-Y. Pang, “Product Backlog and Requirements Engineering for Enterprise Application Development,” in Software Engineering for Agile Application Development, 2020. doi: 10.4018/978-1-7998-2531-9.ch001.

S. Robertson and J. Robertson, Mastering the Requirements Process: Getting Requirements Right, Third. Addison Wesley, 2013.

M. Broy, “Rethinking Nonfunctional Software Requirements,” Computer, vol. 48, no. 6, pp. 72–75, 2015, doi: 10.1109/MC.2015.172.

IEEE, “IEEE 610.12 - Standard Glossary of Software Engineering Terminology | EnIEEE. 1990. IEEE 610.12 - Standard Glossary of Software Engineering Terminology | Engineering360.gineering360,” 1990. Accessed: May 27, 2021. [Online]. Available: 610.12

IEEE Computer Society, IEEE Trial-Use Standard for Software. The Institute of Electrical and Electronics Engineers Standards Assosiation, 2019. doi: 10.1109/IEEESTD.2019.8870263.

COSMIC and IFPUG, “Glossary of terms for Non-Functional Requirements and Project Requirements used in software project performance measurement , benchmarking and estimating,” no. September, 2015.

IFPUG, “COSMIC and IFPUG Glossary of terms ,” international Functions Point Users Group (IFPUG), May 30, 2019. (accessed Aug. 16, 2021).

K. Power, “Stakeholder Identification in Agile Software Product Development Organizations: A Model for Understanding Who and What Really Counts,” in 2010 Agile Conference, IEEE, Aug. 2010, pp. 87–94. doi: 10.1109/AGILE.2010.17.

S. Lewellen, “A comprehensive approach to identifying key stakeholders in complicated software ecosystems,” Proceedings of the IEEE International Conference on Requirements Engineering, pp. 492–497, 2021, doi: 10.1109/RE51729.2021.00074.

H. S. Dar, “Reducing Ambiguity in Requirements Elicitation via Gamification,” Proceedings of the IEEE International Conference on Requirements Engineering, vol. 2020-Augus, pp. 440–444, 2020, doi: 10.1109/RE48521.2020.00065.

S. Alzu’Bi, B. Hawashin, M. Eibes, and M. Al-Ayyoub, “A Novel Recommender System Based on Apriori Algorithm for Requirements Engineering,” 2018 5th International Conference on Social Networks Analysis, Management and Security, SNAMS 2018, pp. 323–327, 2018, doi: 10.1109/SNAMS.2018.8554909.

F. Dwitam and A. Rusli, “User stories collection via interactive chatbot to support requirements gathering,” Telkomnika (Telecommunication Computing Electronics and Control), vol. 18, no. 2, pp. 890–898, 2020, doi: 10.12928/TELKOMNIKA.V18I2.14866.

R. Pressman, Software engineering: a practitioner’s approach. MCGRAW-HILL US HIGHER ED., 2019.

S. L. Buitron, F. J. Pino, B. L. Flores-Rios, J. E. Ibarra-Esquer, and M. A. Astorga-Vargas, “A Model for Enhancing Tacit Knowledge Flow in Non-functional Requirements Elicitation,” Proceedings - 2017 5th International Conference in Software Engineering Research and Innovation, CONISOFT 2017, vol. 2018-Janua, pp. 25–33, 2018, doi: 10.1109/CONISOFT.2017.00011.

R. K. Gnanasekaran, S. Chakraborty, J. Dehlinger, and L. Deng, “Using recurrent neural networks for classification of natural language-based non-functional requirements,” CEUR Workshop Proceedings, vol. 2857, 2021.

F. Khan, S. R. Jan, M. Tahir, S. Khan, and F. Ullah, “Survey: Dealing Non-Functional Requirements at Architecture Level,” VFAST Transactions on Software Engineering, vol. 9, no. 2, p. 7, Apr. 2016, doi: 10.21015/vtse.v9i2.410.

R. K. Surana, Chetan Surana, Shriya, Di. B. Gupta, and S. P. Shankar, “Intelligent Chatbot for Requirements Elicitation and Classification,” 2019 4th IEEE International Conference on Recent Trends on Electronics, Information, Communication and Technology, RTEICT 2019 - Proceedings, pp. 866–870, 2019, doi: 10.1109/RTEICT46194.2019.9016907.

G. A. Alencar, F. V. S. De Oliveira, J. Da Silva Correia-Neto, and M. M. Teixeira, “Non-functional requirements in health information systems: A systematic mapping research,” Iberian Conference on Information Systems and Technologies, CISTI, vol. 2019-June, no. June, pp. 1–5, 2019, doi: 10.23919/CISTI.2019.8760720.

H. Dar, M. I. Lali, H. Ashraf, M. Ramzan, T. Amjad, and B. Shahzad, “A systematic study on software requirements elicitation techniques and its challenges in mobile application development,” IEEE Access, vol. 6, pp. 63859–63867, 2018, doi: 10.1109/ACCESS.2018.2874981.

B. B. Chua, D. V. Bernardo, and J. Verner, “Understanding the use of elicitation approaches for effective requirements gathering,” Proceedings - 5th International Conference on Software Engineering Advances, ICSEA 2010, pp. 325–330, 2010, doi: 10.1109/ICSEA.2010.89.

J. Kontio, L. Lehtola, and J. Bragge, “Using the focus group method in software engineering: Obtaining practitioner and user experiences,” in Proceedings - 2004 International Symposium on Empirical Software Engineering, ISESE 2004, 2004, pp. 271–280. doi: 10.1109/ISESE.2004.1334914.

E. C. Groen et al., “The Crowd in Requirements Engineering: The Landscape and Challenges,” IEEE Software, vol. 34, no. 2, pp. 44–52, Mar. 2017, doi: 10.1109/MS.2017.33.

T. Y. Lim, F. F. Chua, and B. B. Tajuddin, “Elicitation techniques for internet of things applications requirements: A systematic review,” ACM International Conference Proceeding Series, pp. 182–188, 2018, doi: 10.1145/3301326.3301360.

E. C. Groen et al., “The Crowd in Requirements Engineering: The Landscape and Challenges,” IEEE Software, vol. 34, no. 2, pp. 44–52, 2017, doi: 10.1109/MS.2017.33.

O. Adetunji, E. Oyenuga, and N. Otuneme, “Crowd Requirement Rating Technique (CrowdReRaT) Model for Crowd Sourcing,” Int J Comput Appl, vol. 176, no. 22, pp. 9–14, 2020, doi: 10.5120/ijca2020920178.

N. Seyff, I. Todoran, K. Caluser, L. Singer, and M. Glinz, “Using popular social network sites to support requirements elicitation, prioritization and negotiation,” Journal of Internet Services and Applications, vol. 6, no. 1, p. 7, Dec. 2015, doi: 10.1186/s13174-015-0021-9.

P. K. Srivastava and R. Sharma, “Crowdsourcing to elicit requirements for MyERP application,” 1st International Workshop on Crowd-Based Requirements Engineering, CrowdRE 2015 - Proceedings, pp. 31–35, 2015, doi: 10.1109/CrowdRE.2015.7367586.




How to Cite

Eze, M. ., Kuyoro , S., Ayankoya , F., & Otuneme, N. C. (2023). Bridging the Gap Between Stakeholder and Software Products: A Review of Software Requirement Engineering Techniques. American Scientific Research Journal for Engineering, Technology, and Sciences, 93(1), 100–110. Retrieved from