International Journal of Information Technology and Computer Science (IJITCS)
IJITCS Vol. 18, No. 3, 8 Jun. 2026
Cover page and Table of Contents: PDF (size: 535KB)
Context-oriented Framework for Determining Requirements Change Documentation Approaches
PDF (535KB), PP.96-108
Views: 0 Downloads: 0
Author(s)
Index Terms
Requirements Change Management, Requirements Specification, Business Analysis
Abstract
Requirements change management is one of the core business analyst's activities, directly affecting change impact analysis, stakeholder communication, and the long-term system maintainability. While research on this topic examines in detail change processes, tracking methods, and change type classification, the problem of systematically documenting requirements changes remains underexplored. Existing research lacks a unified classification of change documentation approaches and context-sensitive recommendations for their selection, which limits their effectiveness in managing requirements.
To address this gap, this study develops a context-oriented framework for selecting approaches to requirements change documentation. The framework integrates three components: a conceptual model based on the Baseline–Delta–Target State triad, a taxonomy of documentation approaches, and a context-driven selection mechanism grounded in empirical evidence. A systematic literature review was combined with an analysis of the survey of 324 practicing business analysts from Ukrainian and international companies. Statistically significant associations between selected project context attributes and documentation practices were identified using the Chi-square test of independence and Cramer's V, while additional dimensions were supported through evidence from the literature.
The framework incorporates six documentation approaches: Full Target State, Delta-only, Target-driven Delta, Delta-driven Target, Parallel Use, and Hybrid Cycle. Four contextual dimensions emerge as key factors: project, environment, resources, and stakeholders. To support context-based selection of the change documentation approach, a matrix was developed that integrates the identified dependencies.
The results position requirements change documentation as a context-sensitive knowledge management mechanism rather than a universal procedural standard.
Cite This Paper
Denys Gobov, Oleksandra Zuieva, Viktoriia Shashko, "Context-oriented Framework for Determining Requirements Change Documentation Approaches", International Journal of Information Technology and Computer Science(IJITCS), Vol.18, No.3, pp.96-108 2026. DOI:10.5815/ijitcs.2026.03.07
Reference
[1]Jayatilleke, S., & Lai, R. (2018). A systematic review of requirements change management. Information and Software Technology, 93, 163-185. DOI: 10.1016/j.infsof.2017.09.004
[2]Jayatilleke, S., Lai, R., & Reed, K. (2018). Managing Software Requirements Changes Through Change Specification and Classification. Computer Science and Information Systems, 15(2), 321-346. DOI: 10.2298/CSIS161130041J.
[3]Madampe, K., Hoda, R., & Grundy, J. (2022). A Faceted Taxonomy of Requirements Changes in Agile Contexts. IEEE Transactions on Software Engineering, 48(10), 3737-3752. DOI: 10.1109/TSE.2021.3104732
[4]Sakhrawi, Z., Sellami, A., & Bouassida, N. (2020). Requirements Change Requests Classification: An Ontology-Based Approach. International Conference on Intelligent Systems Design and Applications, 1181, 487–496. DOI: 10.1007/978-3-030-49342-4_47
[5]Anwer, S., Wen, L., Rout, T., & Wang, Z. (2018). Introducing requirements change management process into ISO/IEC 12207. In Software Process Improvement and Capability Determination (SPICE 2018) (CCIS, Vol. 918, pp. 170–181). Springer. DOI: 10.1007/978-3-030-00623-5_13
[6]Akbar, M. A., Mahmood, S., Huang, Z., Khan, A. A., & Shameem, M. (2020). Readiness model for requirements change management in global software development. Journal of Software: Evolution and Process, 32(10), e2264. DOI: 10.1002/smr.2264
[7]Akbar, M. A., Khan, A. A., Mahmood, S., & Mishra, A. (2023). SRCMIMM: The Software Requirements Change Management and Implementation Maturity Model in the Domain of Global Software Development Industry. Information Technology and Management, 24, 195-219. DOI: 10.1007/s10799-022-00364-w
[8]Krause, J., Kaufmann, A., Riehle, D., & Jung, M. (2022). The Benefits of Pre-Requirements Specification Traceability. IEEE 30th International Requirements Engineering Conference (RE), 166-177. DOI: 10.1109/RE54965.2022.00021
[9]Mucha, J., Kaufmann, A., & Riehle, D. (2024). A Systematic Literature Review of Pre-Requirements Specification Traceability. Requirements Engineering, 29, 119–141. DOI: 10.1007/s00766-023-00412-z
[10]Ilyas, I. et al. (2025). Optimized Change Management Process Through Semantic Requirements and Traceability Analysis Tool. Journal of Engineering, 2296387-2296404. DOI: 10.1155/je/2296387
[11]Franch, X., Palomares, C., Quer, C., Chatzipetrou, P., & Gorschek, T. (2023). The State-of-Practice in Requirements Specification: An Extended Interview Study at 12 Companies. Requirements Engineering, 28, 377-409. DOI: 10.1007/s00766-023-00399-7
[12]Gobov, D., & Sokolovskiy, N. (2025). An Association Rule Mining for Requirement Document Structure in IT Projects. Advances in Computer Science for Engineering and Education VII, 242. DOI: 10.1007/978-3-031-84228-3_27
[13]Gobov, D., & Zuieva, O. (2025). Software Quality Attributes in Requirements Engineering. International Journal of Information Technology and Computer Science (IJITCS), 17(4), 38-48. DOI: 10.5815/ijitcs.2025.04.04
[14]Anwer, S., Wen, L., & Wang, Z. (2019). A systematic approach for identifying requirement change management challenges: Preliminary results. In Proceedings of the 23rd International Conference on Evaluation and Assessment in Software Engineering (EASE 2019) (pp. 245–250). ACM. DOI: 10.1145/3319008.3319031
[15]Akbar, M. A., Khan, A. A., Mahmood, S., & Mishra, A. (2020). Requirement Change Management Challenges in Global Software Development: An Analytical Hierarchy Process Approach. Journal of Software: Evolution and Process, 32, e2246. DOI: 10.1002/smr.2246
[16]Bhatti, S. N. et al. (2020). Optimized Approach in Requirements Change Management in Geographically Dispersed Environment. International Journal of Advanced Computer Science and Applications, 11(3), 520-525. DOI: 10.14569/IJACSA.2020.0110366
[17]Ahmad, J. et al. (2022). Quality Requirement Change Management’s Challenges: An Exploratory Study Using SLR. IEEE Access, 10, 127575-127588. DOI: 10.1109/ACCESS.2022.3224593
[18]Gräßler, I., Pottebaum, J., Oleff, C., & Preuß, D. (2021). Handling of Explicit Uncertainty in Requirements Change Management. Proceedings of the Design Society, 1687–1696. DOI: 10.1017/pds.2021.430
[19]Malcher, P., Viana, D., Antonino, P. O., & dos Santos, R. P. (2025). Towards an Understanding of Requirements Management in Software Ecosystems. Information and Software Technology, 180, 107672. DOI: 10.1016/j.infsof.2025.107672
[20]Chua, B. B., & Verner, J. (2010). Examining Requirements Change Rework Effort: A Study. International Journal of Software Engineering & Applications, 1, 48–64. DOI: 10.5121/ijsea.2010.1304
[21]Khan, H. U. et al. (2021). Empirical Investigation of Critical Requirements Engineering Practices for Global Software Development. IEEE Access, 9. pp. 93593–93613, 2021, DOI: 10.1109/ACCESS.2021.3092679
[22]Gobov, D., & Titlova, O. (2023). Towards identifying challenges in business analysis on IT projects–a practical study. Radioelectronic and Computer Systems, (2), 193-206. DOI: 10.32620/reks.2023.2.16
[23]Neha, K., & Ghimire, B. (2024). Agile Requirement Change Management Model for Global Software Development. arXiv preprint arXiv:2402.14595. DOI: 10.48550/arXiv.2402.14595
[24]Bismal, M., & Sabahat, N. (2024). Requirements Change Management (Rcm) Tool For Pakistan Software Industry. Pakistan Journal of Scientific Research, 3(2), 190-200. DOI: 10.57041/pjosr.v3i2.1018
[25]Wahbeh, N., Admodisastro, N., Hassan, S. et al. (2024). Requirement Change Management in Global Software Development: A Systematic Review. DOI: 10.21203/rs.3.rs-4253959/v1
[26]Ben Charrada, E. (2013). Supporting Requirements Update during Software Evolution. Dissertation, University of Zurich. DOI: 10.5167/uzh-89558
[27]Janes, A., Remencius, T., Sillitti, A., & Succi, G. (2013). Managing changes in requirements: an empirical investigation. Journal of Software: Evolution and Process, 25, 1273-1283. DOI: 10.1002/smr.1602
[28]Spijkman, T., Dalpiaz, F., & Brinkkemper, S. (2022). Back to the Roots: Linking User Stories to Requirements Elicitation Conversations. IEEE 30th International Requirements Engineering Conference (RE), 281-287. DOI: 10.1109/RE54965.2022.00042
[29]Satapathy, B., Sharma, A., Dash, M. et al. (2025). Driving Innovation Through Change: Release Management With a Focus on Nonfunctional Requirements and Emerging Technologies. Cureus Journal of Computer Science, 2. DOI: 10.7759/s44389-025-03354-5
[30]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), 39–53. DOI: 10.30837/itssi.2023.24.039
[31]Conradi, R., & Westfechtel, B. (1998). Version models for software configuration management. ACM Computing Surveys, 30(2), 232–282. DOI: 10.1145/280277.280280
[32] International Institute of Business Analysis. (2015). A Guide to the Business Analysis Body of Knowledge (BABOK® Guide) (Version 3.0).
[33]Badamasi, I. Y., Nordin, A., Salleh, N., & Mustapha, S. W. (2019). Requirement Patterns: An Approach for Streamlining Requirements Engineering in Software Product Families. International Journal of Advanced Trends in Computer Science and Engineering, 8(1.4), 507-514. DOI: 10.30534/ijatcse/2019/7981.42019
[34]Mehmood, W., Khan, A. W., Aslam, W., Ahmad, S., El-Sherbeeny, A. M., & Shafiq, M. (2022). Requirement Design for Software Configuration and System Modeling. Intelligent Automation & Soft Computing, 32(1), 441–454. DOI: 10.326204/iasc.2022.016116
[35]Ernst, N., Borgida, A., Jureta, I. J., & Mylopoulos, J. (2014). An Overview of Requirements Evolution. Evolving Software Systems. DOI: 10.1007/978-3-642-45398-4_1
[36]IEEE. (1984). IEEE Guide for Software Requirements Specifications. IEEE Std 830-1984, 1-26. DOI: 10.1109/IEEESTD.1984.119205
[37]Koegel, M., Herrmannsdoerfer, M., Li, Y., Helming, J., & David, J. (2010). Comparing state- and operation-based change tracking on models. Proceedings of the 14th IEEE International Enterprise Distributed Object Computing Conference (EDOC ’10), 163–172.
[38]Rochkind, M. J. (1975). The Source Code Control System. IEEE Transactions on Software Engineering, SE-1(4), 364–370
[39]Patel, R. (2025). Capturing Delta Requirements: A Guide to Fit-to-Standard Workshops. Medium. [Online]. Available: https://rajenpatel.medium.com/selecting-business-processes-for-improvement-during-sap-s-4hana-upgrade-project-brownfield-sdt-f833de52a87f
[40]Fowler, M., & Highsmith, J. A. (2001). The agile manifesto. Software Development, 9(8), 28-35.
[41]Gobov, D., & Sokolovskiy, N. (2024). An Association Rule Mining for Selection Requirement Elicitation and Analysis Techniques in IT Projects. Software, System, and Service Engineering, 499. DOI: 10.1007/978-3-031-51075-5_4
[42]Aljuhani, A. (2024). Identification of Agile Requirements Change Management Success Factors in Global Software Development Based on the Best-Worst Method. International Journal of Advanced Computer Science and Applications (IJACSA), 15(7). DOI: 10.14569/IJACSA.2024.01507131
[43]Gobov, D., & Sokolovskiy, N. (2023). Association rule mining for requirement elicitation techniques in IT projects. Proceedings of the 18th Conference on Computer Science and Intelligence Systems (FedCSIS), 983–987. DOI: 10.15439/2023F4831
[44]Hakim, H., Sellami, A., & Ben-Abdallah, H. (2024). A Measures-Driven Decision Support System for Managing Requirement Change in Scrum: An Empirical Evaluation. Proceedings of the 19th International Conference on Software Technologies – ICSOFT, 1, 161-168. DOI: 10.5220/0012807700003753
[45]Bantwal, A., & Valilai, O. F. (2026). Integrated engineering change management framework for efficient information flow to product design systems. The International Journal of Advanced Manufacturing Technology. DOI: 10.1007/s00170-025-17175-2
[46]Gonçalves, E., Malcher, P., Antonino, P., & Santos, R. (2025). Investigating requirements change requests. Proceedings of the 21st Brazilian Symposium on Information Systems, 733-742. DOI: 10.5753/sbsi.2025.246624
[47]Gobov, D., & Shevchenko, N. (2024). Definition of the requirements architecture for IT solution as a business analytics product. Innovative Technologies and Scientific Solutions for Industries, 1(27), 26–38. DOI: 10.30837/ITSSI.2024.27.026
[48]Dai, P., Yang, L., Wang, Y., Jin, D., & Gong, Y. (2023). Constructing Traceability Links between Software Requirements and Source Code Based on Neural Networks. Mathematics, 11(2), 315. DOI: 10.3390/math11020315
[49]Rusdianto, D. S., Fabroyir, H., & Yuhana, U. L. (2024). Innovative Approaches to Impact Analysis of Requirement Changes using LLM in Software Projects. IEEE International Symposium on Consumer Technology (ISCT), 604-610. DOI: 10.1109/ISCT62336.2024.10791169
[50]Etezadi, R., Abualhaija, S., Arora, C., & Briand, L. (2025). LLM-driven cost-effective requirements change impact analysis. arXiv. DOI: 10.48550/arXiv.2511.00262