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.

As software systems continue to grow more complex, evaluating software quality becomes increasingly critical. This study analyzes existing software quality models, including McCall, Boehm, FURPS, and ISO Systems and Software Engineering – Systems and Software Quality Requirements and Evaluation (SQuaRE), with a specific focus on the ISO/IEC 25010:2023 standard. The research aims to assess the completeness of these models and explore interdependencies among key quality attributes relevant to software requirements engineering. The paper identifies key characteristics and associated metrics based on ISO/IEC standards using comparative analysis and a literature review. Findings show that ISO/IEC 25010:2023 provides the most comprehensive structure, with Functional Suitability and Compatibility identified as essential due to their universally recommended metrics. Survey data from 328 practicing analysts in Ukraine and internationally demonstrate a gap between theoretical models and real-world requirements documentation practices, particularly for non-functional requirements. The identified dependencies between quality attributes enable a more integrated and structured approach to identifying and analyzing non-functional requirements in IT projects. The study emphasizes that software quality models must be tailored to project-specific goals and constraints, with attention to trade-offs and stakeholder needs during the requirements specification, prioritization, and validation processes. The findings support the adaptation of quality models to specific project constraints and emphasize the business analyst’s role in tailoring quality criteria for practical use in software development.