Definition of the requirements architecture for IT solution as a business analytics product
DOI:
https://doi.org/10.30837/ITSSI.2024.27.026Keywords:
business analysis; software requirements; documentation of requirements; requirements view; requirements viewpoint; requirements architecture.Abstract
The subject of research in the article is approaches to understanding and interpreting the concept of the architecture of requirements for an IT solution. The purpose of the work is to define the architecture of software requirements for a better understanding and further implementation of this concept in the practice of software development. The article addresses the following tasks: analyze approaches to the classification of requirements to determine common and distinctive characteristics and their impact on the definition of the architecture of requirements; examine requirements engineering standards to find the definition and any relationship to the requirements architecture; consider approaches to building a set of requirements and using templates to describe them to identify optimal strategies for business analytical processes and their impact on the architecture of requirements. The following methods are used: comparative analysis, including comparison and generalization of different classifications of requirements taking into account their impact on the definition of requirements architecture, review of literature and standards related to requirements engineering, as well as analysis of their impact on the process of formation of requirements architecture, analysis of documentation with the aim identifying optimal strategies for building the requirements architecture, as well as analyzing the use of templates for describing requirements and their importance in defining the requirements architecture. In addition, the requirements quality criteria analysis results were interpolated to identify relationships between the quality of requirements and their architecture, which made it possible to determine the optimal approaches to building the architecture of requirements that meet the requirements of software quality. The following results were obtained: approaches to understanding requirements in software development were investigated, generally accepted classifications of requirements and characteristics of quality requirements were given, and links of the chain "requirements – quality of requirements – approaches to description of requirements – standards – architecture of requirements" were analyzed with further logical interpolation of the studied context on the architecture of requirements, the author's definition of the concept of architecture of requirements is proposed. Conclusions. Requirements architecture can be based on different architectural frameworks and depends on software development methodologies, but at the same time, it can vary depending on industry standards and the needs of a specific project. Also, requirements architecture can use certain document templates, but it is not limited to them.
References
Список літератури
A Guide to the Business Analysis Body of Knowledge® (ВАВОК® Guide). International Institute of Business Analysis, Toronto, Ontario, Canada, 2015. 514 р.
Systems and software engineering – Life cycle processes – Requirements engineering. ISO/IEC/IEEE 29148:2018(en). URL: https://doi.org/10.3403/30295695u (дата звернення: 10.12.2023).
Pohl K. Requirements engineering: fundamentals, principles, and techniques. Springer Publishing Company. 2010. 182 p. DOI: http://dx.doi.org/10.5860/choice.48-3304
Lind E., Gonzalez-Huerta J., Alégroth E. Requirements Quality vs. Process and Stakeholders' Well-Being: A Case of a Nordic Bank. Lecture Notes in Business Information Processing. 2023. № 472. P. 17–37.DOI: https://doi.org/10.1007/978-3-031-31488-9_2
BABOK® Guide v3 Glossary – Ukrainian Translation. URL: https://www.iiba.org/globalassets/standards-and-resources/glossary/files/babok-v3-glossary-ukrainian.pdf (дата звернення: 10.12.2023).
Gobov D., Yanchuk V. 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). IEEE. 2021. P. 1–6. DOI: https://doi.org/10.1109/IISEC54230.2021.9672373
Diev S. Structuring complex requirements. ACM SIGSOFT Software Engineering Notes. 2007. №32(2). P. 1–5. DOI: https://doi.org/10.1145/1234741.1234755
Gobov D., Huchenko I. Modern Requirements Documentation Techniques and the Influence of the Project Context: Ukrainian IT Experience. Lecture Notes on Data Engineering and Communications Technologies. 2022. vol 134. P. 260–270. DOI: https://doi.org/10.1007/978-3-031-04812-8_22
Gobov D. Practical Study on Software Requirements Specification and Modelling Techniques. International Journal of Computing. 2023. №22(1). P. 78-86. DOI: https://doi.org/10.47839/ijc.22.1.2882
Rączkowska-Gzowska K., Walkowiak-Gall A. What Should a Good Software Requirements Specification Include? Results of a Survey. Foundations of Computing and Decision Sciences. 2023. № 48(1). P. 57–81. DOI: 10.2478/fcds-2023-0004
Mucha J., Kaufmann A., Riehle D. A systematic literature review of pre-requirements specification traceability. Requirements Engineering. 2024. №1. P. 1–23. DOI: https://doi.org/10.1007/s00766-023-00412-z
Großer K., Riediger V., Jürjens J. Requirements document relations: A reuse perspective on traceability through standards. Software and Systems Modeling. 2022. №21(6). P. 1–37. DOI: https://doi.org/10.1007/s10270-021-00958-y
Wiegers K., Beatty J. Software Requirements (Developer Best Practices). 3rd Edition, Microsoft Press, 2013, 672 p.
The PMI Guide to Business Analysis. Project Management Institute, Inc, Newtown Square, Pennsylvania, 2018. 444 p.
Gregory S. Requirements for the New Normal: Requirements Engineering in a Pandemic. IEEE Software. 2021. vol. 38, No. 2. P. 15–18. DOI: 10.1109/MS.2020.3044403
Sonbol R., Rebdawi G., Ghneim N. Learning software requirements syntax: An unsupervised approach to recognize templates. Knowledge-Based Systems. 2022. Volume 248. 108933 р. DOI: https://doi.org/10.1016/j.knosys.2022.108933
Frattini K, et.al. Requirements quality research: a harmonized theory, evaluation, and roadmap. Requirements engineering. 2023. Volume 28. P. 507–520. DOI:https://doi.org/10.1007/s00766-023-00405-y
Noreika K., Gudas S. Causal Knowledge Modelling for Agile Development of Enterprise Application Systems. Informatica. 2023. №34(1). P. 121–146. DOI: 10.15388/23-INFOR510
Palomares C., et. al. The state-of-practice in requirements elicitation: an extended interview study at 12 companies. Requirements Engineering. 2021. №26. P. 273–299. DOI: https://doi.org/10.1007/s00766-023-00399-7
Gobov D., Zuieva O. Identifying the dependencies between it project context and business analysis document content. Innovative technologies and scientific solutions for industries. 2023. №2(24). P. 39–53. DOI: 10.30837/ITSSI.2023.24.039
Dellsén E., Westgårdh K., Horkoff J. Invest in Splitting: User Story Splitting Within the Software Industry. Lecture Notes in Computer Science. 2022. Vol 13216. P. 115-130. DOI: https://doi.org/10.1007/978-3-030-98464-9_10
Rasheed A., et. al. Requirement Engineering Challenges in Agile Software Development. Mathematical Problems in Engineering. 2021. Volume 2021. Article ID 6696695. Р. 1–18. DOI: https://doi.org/10.1155/2021/6696695
Atoum I, et.al. Challenges of Software Requirements Quality Assurance and Validation: A Systematic Literature Review. IEEE Access. 2021. Vol. 9. P. 137613–137634. DOI: https://doi.org/10.1109/ACCESS.2021.3117989
Paul D., Cadle J., Yeates D. (editors). Business Analysis. Third edition, British Computer Society, 2014. 401 p.
С. К. Кілессо. Архітектура. Енциклопедія сучасної України. [Електронний ресурс] за ред.: І. М. Дзюба, А. І. Жуковський, М. Г. Железняк [та ін.]; НАН України, НТШ. К.: Інститут енциклопедичних досліджень НАН України, 2001. URL : https://esu.com.ua/article-44834
References
A Guide to the Business Analysis Body of Knowledge® (ВАВОК® Guide). International Institute of Business Analysis, Toronto, Ontario, Canada, 2015. 514 р.
Systems and software engineering – Life cycle processes – Requirements engineering. ISO/IEC/IEEE 29148:2018(en). available at: https://doi.org/10.3403/30295695u (last accessed: 10.12.2023).
Pohl, K. (2010), "Requirements engineering: fundamentals, principles, and techniques". Springer Publishing Company. 182 p. DOI: http://dx.doi.org/10.5860/choice.48-3304
Lind, E., Gonzalez-Huerta, J., & Alégroth, E. (2023),"Requirements Quality vs. Process and Stakeholders' Well-Being: A Case of a Nordic Bank". Proceedings of International Conference on Software Quality, P. 17–37. DOI: https://doi.org/10.1007/978-3-031-31488-9_2
International Institute of Business Analysis. "BABOK® Guide v3 Glossary – Ukrainian Translation", available at: https://www.iiba.org/globalassets/standards-and-resources/glossary/files/babok-v3-glossary-ukrainian.pdf
(last accessed: 10.12.2023).
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), IEEE. P. 1–6. DOI: https://doi.org/10.1109/IISEC54230.2021.9672373
Diev, S. (2007), "Structuring complex requirements", ACM SIGSOFT Software Engineering Notes, №32(2), P. 1–5. DOI: https://doi.org/10.1145/1234741.1234755
Gobov, D., Huchenko, I. (2022), "Modern Requirements Documentation Techniques and the Influence of the Project Context: Ukrainian IT Experience", Lecture Notes on Data Engineering and Communications Technologies, Vol 134, P. 260–270. DOI: https://doi.org/10.1007/978-3-031-04812-8_22
Gobov, D. (2023), "Practical Study on Software Requirements Specification and Modelling Techniques", International Journal of Computing, №22(1), P. 78–86. DOI: https://doi.org/10.47839/ijc.22.1.2882
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, № 48(1), P. 57–81. DOI: 10.2478/fcds-2023-0004
Mucha, J., Kaufmann, A., Riehle, D. (2024), "A systematic literature review of pre-requirements specification traceability", Requirements Engineering, №1, P. 1–23. DOI: https://doi.org/10.1007/s00766-023-00412-z
Großer, K., Riediger, V., Jürjens, J. (2022), "Requirements document relations: A reuse perspective on traceability through standards", Software and Systems Modeling, №21(6), P. 1–37. DOI: https://doi.org/10.1007/s10270-021-00958-y
Wiegers K., Beatty J. (2013), Software Requirements (Developer Best Practices). 3rd Edition. Microsoft Press, 672 p.
Project Management Institute (2018), The PMI Guide to BUSINESS ANALYSIS. PMI, Newtown Square, Pennsylvania, 444 p.
Gregory, S. (2021), "Requirements for the New Normal: Requirements Engineering in a Pandemic", IEEE Software, vol. 38, No. 2, P. 15–18. DOI: 10.1109/MS.2020.3044403
Sonbol, R., Rebdawi, G., Ghneim, N. (2022), "Learning software requirements syntax: An unsupervised approach to recognize templates", Knowledge-Based Systems, Volume 248, 108933 р. DOI: https://doi.org/10.1016/j.knosys.2022.108933
Frattini, K, et.al. (2023), "Requirements quality research: a harmonized theory, evaluation, and roadmap", Requirements engineering, Volume 28. P. 507–520. DOI: https://doi.org/10.1007/s00766-023-00405-y
Noreika, K., Gudas, S. (2023), "Causal Knowledge Modelling for Agile Development of Enterprise Application Systems", Informatica. №34(1). P. 121–146. DOI: 10.15388/23-INFOR510
Palomares, C., et. al. (201), "The state-of-practice in requirements elicitation: an extended interview study at 12 companies", Requirements Engineering. №2. P. 273–299. DOI: https://doi.org/10.1007/s00766-023-00399-7
Gobov, D., Zuieva, O. (2023), "Identifying the dependencies between it project context and business analysis document content", Innovative technologies and scientific solutions for industries, №2 (24), P. 39–53. DOI: 10.30837/ITSSI.2023.24.039
Dellsén, E., Westgårdh, K., Horkoff, J. (2022), "Invest in Splitting: User Story Splitting Within the Software Industry", Lecture Notes in Computer Science, Vol 13216, P. 115–130. https://doi.org/10.1007/978-3-030-98464-9_10
Rasheed, A., et. al. (2021), "Requirement Engineering Challenges in Agile Software Development", Mathematical Problems in Engineering, Volume 2021, Article ID 6696695. Р. 1–18. DOI: https://doi.org/10.1155/2021/6696695
Atoum, I., et.al. (2021), "Challenges of Software Requirements Quality Assurance and Validation: A Systematic Literature Review", IEEE Access, Vol. 9, P. 137613–137634. DOI: https://doi.org/10.1109/ACCESS.2021.3117989
Paul, D., Cadle, J., Yeates, D. (2014), Business Analysis. Third edition, British Computer Society, 401 p.
Kilesso, S.K. (2001), "Architecture. Encyclopedia of Modern Ukraine", edited by: I. M. Dzyuba, A. I. Zhukovsky, M. G. Zheleznyak [and others], National Academy of Sciences of Ukraine, National Academy of Sciences. K.: Institute of Encyclopedic Research of the National Academy of Sciences of Ukraine. available at: https://esu.com.ua/article-44834.
Downloads
Published
How to Cite
Issue
Section
License
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.
