Во-первых, заказчик изменил требова

Во-первых, заказчик изменил требования к производительности системы уже на финальной стадии разработки. Это достаточно частое явление. Как правило, доработки проекта в таких случаях существенны. Возможно, такой проблемы можно избежать, если «плотнее» работать с заказчиком и указывать на явные и не явные риски. Во-вторых, стоит учитывать возможное масштабирование системы, рост базы данных. С этим критерием работать сложно, потому что от заказчика сложно получить конкретную информацию о возможном росте нагрузки на систему.

Результаты (английский) 1:

First, the customer has changed the requirements for the performance of the system already in the final stages of development. This is a fairly common occurrence. Typically, completion of the project in such cases, substantial. Perhaps this problem can be avoided by "dense" work with the customer and indicate the obvious and not obvious risks.
Secondly, it is necessary to take into account the ability to scale the system, database growth. With this criterion is difficult to work, because the customer is difficult to obtain specific information about a possible increase in the load on the system.

Результаты (английский) 2:

First, the customer changed the system's performance requirements at the final stage of development. This is quite common. As a rule, the project's improvements in such cases are significant. Perhaps this problem can be avoided if you work more closely with the customer and point out obvious and non-obvious risks.
Secondly, it is worth considering the possible scaling of the system, the growth of the database. It is difficult to work with this criterion, because it is difficult to get specific information from the customer about the possible increase in the load on the system.

Результаты (английский) 3:

First of all, in the final stage of development, customers changed their requirements for system performance. This is quite a common phenomenon. In this case, major changes are usually made to the project. This problem may be avoidable if "closer" cooperation with the orderer is carried out and the obvious and non obvious risks are pointed out.
Second, we should consider the possible scale of the system and the growth of the database. This standard is difficult to operate because it is difficult to obtain specific information from customers about the possible increase in the workload of the system.