What is the main problem of this analytical model - Low logging efficiency - Lack of tools for decision recording - Lack of transparency in communications - No process for controlling and recording requirement changes, leading to inconsistency in functionality - No approach to archiving discussions - No requirements management tools

The main problem of this analytical model is the lack of a systematic approach to requirements management and communications. This manifests in:

• The absence of tools for recording decisions and controlling changes, leading to inconsistency in functionality.
• Lack of transparency in communications and the absence of a discussion archiving process, which complicates tracking history and decision-making.
• Low efficiency of protocol logging, which may result in important information being lost.

As a result, the model does not provide comprehensive requirements and communication management, which is critical for the successful implementation of the project.