Goals of a system architect in software project

It would be wrong to say that the review of the goal and objectives of the project is carried out only
once, immediately upon receipt of the requirements for participation in the competition from the customer.
Most often, peer review is carried out throughout the preparatory stage, when the level of problem
statement is insufficient during assessments or decision making. Then you have to clarify with the
customer the goal and objectives and adjust or even completely revise the concept of the project.

We usually review the goal and objectives by the same person who is entrusted with the development of
the concept - an experienced system architect. After the review, this person should have sufficient
information about the customer's expectations about how the developed system will affect its business
processes, and about the significant limitations associated with the future product's operating environment.
Restrictions on the timing and budget of the project when developing the concept should not be taken
into account: the concept is a vision of how the system should function, and not how these functions will
be implemented. In the future, when assessing the demand and feasibility of the product, restrictions on
time and budget will be taken into account.