IDENTIFYING THE DEPENDENCIES BETWEEN IT PROJECT CONTEXT AND BUSINESS ANALYSIS DOCUMENT CONTENT
DOI:
https://doi.org/10.30837/ITSSI.2023.24.039Keywords:
business analysis document; requirements engineering; project context; Cramer V; empirical studyAbstract
The subject matter of the article is software requirements documentation practices in IT projects. The goal of the work is to identify what information is included in business analysis deliverables and how the project context influences the content of business analysis documents. The following tasks were solved in the article: to examine the industrial standards and experience of business analysts and requirements engineers in requirements specification and modeling activities in software development, to create and conduct a survey on practices in requirement documentation activities in IT projects, to define practitioners’ preferences regarding business analysis documents’ content, and to define how project context influences document content. The following methods are used: three hundred and twenty-four practitioners from Ukrainian companies were surveyed about their current preferences in business analysis document creation, their experience, and project profile attributes in which techniques were used. The Chi-Square test of independence and Cramer’s V effect size measure were applied to define statistically significant dependencies between project context and business analysis document content. The following results were obtained: a list of the most commonly used elements in business analysis documents was defined. Seventy-eight statistically significant associations for pairs "project context – business analysis document content" were found based on the p-value of the Chi-Square test, for eighteen of which the significance of the identified dependencies was confirmed using the Cramer’s V effect size measure. Conclusions: It is concluded that project context influences the content of business analysis documents in IT projects. The most influential factors are the business analyst’s experience, team distribution, company size and type, template usage, and the purpose of using the requirements documents. The found dependencies can guide the selection of business analysis document structure and the creation of project-specific templates during the creation business analysis approach and business analysis information management approach.
References
References
Project Management Institute (2017), The PMI Guide to BUSINESS ANALYSIS. PMI, Newtown Square, Pennsylvania, 488 p.
Gobov, D., Yanchuk, V. (2021), "Network Analysis Application to Analyze the Activities and Artifacts in the Core Business Analysis Cycle", Proceedings of the 2nd International Informatics and Software Engineering Conference (IISEC), Р. 1–6. DOI: 10.1109/IISEC54230.2021.9672373
International Institute of Business Analysis (2015), A guide to the business analysis body of knowledge (BABOK Guide) ver. 3., IIBA, Toronto, Ontario, Canada, 514 p.
Pohl, K. (2010), "Requirements engineering: fundamentals, principles, and techniques", Springer Publishing Company, 182 p., available at: https://www.bbau.ac.in/dept/dit/TM/requirementsengi.pdf
ISO/IEC/IEEE 29148. (2011), "Systems and Software Engineering−Life Cycle Processes−Requirements Engineering". ISO/IEC/IEE, Standard 29148:2011. 83 р., available at: https://www.iso.org/standard/45171.html
Jacobson, I., Booch, G., Rumbaugh, J. (1999), "Unified Software Development Process", Addison-Wesley Professional, 463 p.
Gobov, D., Huchenko, I. (2022). "Modern Requirements Documentation Techniques and the Influence of the Project Context: Ukrainian IT Experience", Advances in Computer Science for Engineering and Education. ICCSEEA 2022. Lecture Notes on Data Engineering and Communications Technologies, Vol. 134. Springer, Cham. Р.260-270. DOI: https://doi.org/10.1007/978-3-031-04812-8_22
Rączkowska-Gzowska, K., Walkowiak-Gall, A. (2023), "What Should a Good Software Requirements Specification Include? Results of a Survey", Foundations of Computing and Decision Sciences, Vol.48(1), Р. 57–81. DOI: https://doi.org/10.2478/fcds-2023-0004
Franch, X. et al. (2023), "The state-of-practice in requirements specification: an extended interview study at 12 companies", Requirements Engineering, 29 April. Vol. 28(3), Р. 1–33. DOI: https://doi.org/10.1007/s00766-023-00399-7
Wagner, S. et al. (2017), "Requirements Engineering Practice and Problems in Agile Projects: Results from an International Survey", Proc. XX Ibero-American Conference on Software Engineering (CIbSE), Argentina, available at: https://arxiv.org/list/cs/1703?skip=450&show=2000
Wagner, S. et al. (2019), "Status Quo in Requirements Engineering", ACM Transactions on Software Engineering and Methodology, Vol.28 (2), Р. 1–48. DOI: https://doi.org/10.1145/3306607
Abdalazeim, A., Meziane, F. (2021), "A review of the generation of requirements specification in natural language using objects UML models and domain ontology", Procedia Computer Science, Vol.189, P. 328–334. DOI: https://doi.org/10.1016/j.procs.2021.05.102
Medeiros, J. et al. (2017), "An approach based on design practices to specify requirements in agile projects", Proceedings of the Symposium on Applied Computing (SAC 17), Association for Computing Machinery, New York, NY, USA, Р. 1114–1121. DOI: https://doi.org/10.1145/3019612.3019753
Heck, P., Zaidman, A. (2016), "A systematic literature review on quality criteria for agile requirements specifications", Software Quality Journal, Vol. 26 (1), Р. 127–160. DOI: https://doi.org/10.1007/s11219-016-9336-4
Jarzębowicz, A., Połocka, K., (2017) "Selecting requirements documentation techniques for software projects: a survey study", Proceedings of Federated Conference on Computer Science and Information Systems (FedCSIS, 2017), IEEE, Р. 1189–1198. DOI: https://doi.org/10.15439/2017F387
Gobov, D. (2023), "Practical Study on Software Requirements Specification and Modelling Techniques", International Journal of Computing, Р. 78–86. DOI: https://doi.org/10.47839/ijc.22.1.2882
Beedle, M. et al. "Manifesto for Agile Software Development", available at: https://agilemanifesto.org/ (last accessed: 11 May 2023)
Al-Msie’deen, R., Blasi, A., Alsuwaiket, M. (2021), "Constructing a software requirements specification and design for electronic IT news magazine system", International Journal of Advanced and Applied Sciences, Vol. 8(11), Р. 104–118. DOI: https://doi.org/10.21833/ijaas.2021.11.014
Gobov, D. (2022), "Dependencies between requirements elicitation techniques: a survey study in Ukrainian companies", Innovative Technologies and Scientific Solutions for Industries, Vol. 3 (21), Р. 5–15. DOI: https://doi.org/10.30837/ITSSI.2022.21.005
Kassab, M., Neill, C., Laplante, P. (2014), "State of practice in requirements engineering: contemporary data", Innovations in Systems and Software Engineering, 10, Р. 235–241. DOI: https://doi.org/10.1007/s11334-014-0232-4
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2023 Денис Гобов, Олександра Зуєва
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Our journal abides by the Creative Commons copyright rights and permissions for open access journals.
Authors who publish with this journal agree to the following terms:
Authors hold the copyright without restrictions and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License (CC BY-NC-SA 4.0) that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this journal.
Authors are able to enter into separate, additional contractual arrangements for the non-commercial and non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgment of its initial publication in this journal.
Authors are permitted and encouraged to post their published work online (e.g., in institutional repositories or on their website) as it can lead to productive exchanges, as well as earlier and greater citation of published work.
