Requirement Elicitation Techniques for Software Projects in Ukrainian IT: An Exploratory Study

• Autorzy: Gobov, Denys , Huchenko, Inna
• Konferencja: Federated Conference on Computer Science and Information Systems (15 ; 06-09.09.2020 ; Sofia, Bulgaria)
• Języki publikacji: EN

Abstrakty

EN

Elicitation is a core business analysis/requirements engineering activity that provides inputs for others like analysis, specification, confirmation, management. There is a significant number of specialized techniques that are used for requirement elicitation. The selection of the appropriate techniques considerably influences a project plan and success of a change as a whole. This paper is intended to analyze the industrial standards and experience of business analysts and requirement engineers in the part of elicitation activities. We conducted a survey study involving 328 specialists from Ukrainian IT companies and a series of interviews with experts to interpret the survey results. Furthermore, this paper provides the guideline in selecting a particular elicitation technique with respect to the type of project and situation.

Słowa kluczowe

PL

specyfikacja formalna; weryfikacja formalna; zarządzanie projektami; zarządzanie oprogramowaniem; analiza systemów

EN

formal specification; formal verification; project management; software management; systems analysis

• Czasopismo: Annals of Computer Science and Information Systems
• Rocznik: 2020
• Tom: Vol. 21
• Strony: 673--681
• Opis fizyczny: Bibliogr. 24 poz., tab., wykr.

Twórcy

autor

Gobov, Denys

• National Technical University of Ukraine “Igor Sikorsky Kyiv Polytechnic Institute”, 37, Prosp. Peremohy, Kyiv, Ukraine,

autor

Huchenko, Inna

• National Aviation University, 1, Liubomyra Huzara ave., Kyiv, Ukraine,

Bibliografia

• 1. International Institute of Business Analysis, “A guide to the business analysis body of knowledge (BABOK Guide)” ver. 3, IIBA, 2015.
• 2. J. Rubenss, “Business analysis and requirements engineering: the same, only different?” Requirements Engineering vol. 12(2), 2007, pp. 121–123, http://dx.doi.org/10.1007/s00766-007-0043-3
• 3. M. Aoyama, “Bridging the requirements engineering and business analysis toward a unified knowledge framework” in International Conference on Conceptual Modeling , Springer, Cham, 2016, pp. 149–160, http://dx.doi.org/10.1007/978-3-030-05719-0
• 4. The Standish Group, “CHAOS Report,” The Standish Group, 2014.
• 5. O. Sanchez, M. Terlizzi, “Cost and time project management success factors for information systems develop-ment projects, International Journal of Project Management vol. 35(8), 2017, pp. 1608-1626
• 6. R. Nelson, “IT project management: Infamous failures, classic mistakes, and best practices, MIS Quarterly executive vol. 6(2), 2007
• 7. International Institute of Business Analysis, “A Core Standard A Companion to A Guide to the Business Analysis Body of Knowledge (BABOK® Guide)" ver. 3, IIBA, 2017.
• 8. ISO/IEC/IEEE, “Systems and software engineering - Life cycle processes - Requirements engineering", ISO/IEC/IEE, Standard 29148-2011, 2011, http://dx.doi.org/10.1109/ieeestd.2011.6146379
• 9. Project Management Institute, “The PMI Guide to BUSINESS ANALYSIS", PMI,Newtown Square, Pennsylvania, 2017.
• 10. K. Pohl, “Requirements engineering: fundamentals, principles, and techniques", Springer Publishing Company, 2010.
• 11. S. Wagner, et al., “Status quo in requirements engineering: A theory and a global family of surveys", ACM Transactions on Software Engineering and Methodology (TOSEM) , vol. 28(2), 2019, pp. 1–48.
• 12. D. Fernandez, S. Wagner, “Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany", Information and Software Technology, vol. 57, 2015, pp. 616–643.
• 13. O. Dieste , N. Juristo, “Systematic review and aggregation of empirical studies on elicitation techniques", IEEE Transactions on Software Engineering , vol. 37(2), 2011, pp. 283–304.
• 14. L. Wong, et al., “A systematic literature review about software requirements elicitation", J Eng Sci Technol, vol. 12(2), 2017, pp. 296–317.
• 15. C. Pacheco, I. Garcia, “A systematic literature review of stakeholder identification methods in requirements elicitation", J Syst Softw, vol. 85(9), 2012, pp. 2171–2181.
• 16. T. Ambreen, et al. , “Empirical research in requirements engineering: trends and opportunities", Requirements Engineering, vol. 23(1), 2018, pp. 63–95.
• 17. H. Dar, et al. , “A systematic study on software requirements elicitation techniques and its challenges in mobile application development", IEEE Access, vol. 6, 2018, pp. 63859–63867.
• 18. T. Lym, et al., “Elicitation Techniques for Internet of Things Applications Requirements: A Systematic Review", Proceedings of the 2018 VII International Conference on Network, Communication and Computing, 2018, pp. 182-188.
• 19. F. Anwar, R. Razali, “A practical guide to requirements elicitation techniques selection-an empirical study", Middle-East Journal of Scientific Research, vol.11(8), 2011, pp. 1059-1067.
• 20. D. Carrizo, et al., “Systematizing requirements elicitation technique selection", Information and Software Technology, vol.56(6), 2014, pp. 644-669.
• 21. L. Wong, D. Mauricio, “New Factors That Affect the Activities of the Requirements Elicitation Process", Journal of Engineering Science and Technology, vol.13(7), 2018, pp. 1992-2015.
• 22. D. Paul, et al., “Business analysis", BCS, The Chartered Institute for IT, 2014.
• 23. F. Yates, et al., “The Practice of Statistics", New York: W.H.Freeman, 1st ed., 1999.
• 24. F. Yates, “Contingency table involving small numbers and the Chi-squared test", Suppl J R Stat Soc, 1:217-35, 1934.

Uwagi

1. Track 5: Software and System Engineering

2. Technical Session: Joint 40th IEEE Software Engineering Workshop and 7th International Workshop on Cyber-Physical Systems

3. Opracowanie rekordu ze środków MNiSW, umowa Nr 461252 w ramach programu "Społeczna odpowiedzialność nauki" - moduł: Popularyzacja nauki i promocja sportu (2021).

Identyfikatory

DOI

10.15439/2020F16