Motivated

What do you mean by Motivated?

The quality of an application corresponds to the satisfaction of the customer's expectations. It means that in the preparation work, in addition to observing the canonical qualities of design and realization, it is necessary to understand the reasons why the request was made. Whereas these reasons are clearly expressed or simply interpreted must also be evaluated according to their order of importance. To avoid designing and developing something lacking, it would be good to consider in the feasibility study the "why" a specific application is required. This question certainly leads to formulating the project correctly in its right meanings and for the use that it wants to do. So much so that we are fully aware that the recognition of intentionality is an important qualitative assumption not to be neglected. Design intentions depend directly on the request both in its explicit formulation and in the awareness of the motivations that have desired it. To get the best application solution it is necessary to be as consistent as possible with what the user really wants. It is important that in the design approach are the requests to act as a basis for evaluating the realization and not to move immediately from the requirements of feasibility, which as often happens, take more into account the needs of the system than the applicant's reasons. The learning of the request maintains its own autonomy with respect to the consequential study of the requirements. It is in the first phase that the applicant's intentions should be understood, taking into account the context, the assumptions and the aims. In the subsequent design and realization moments the request will maintain as much as possible its integrity and will not be altered with the use of arbitrary techniques that, even if available at the moment, may be unsuitable for their treatment.

Motivated and Esedra app

Of course, the solution is more satisfying as it approaches man's thinking and is at least conditioned by the technical limits of the machine. This is achieved only if the application keeps a close adherence to the user's requests, so as to become the cornerstone of the entire project. A prerogative to ensure that an application is in full conformity with the applicant's intentions and not to the only formal requirements it is necessary for the application to represent in a faithful way the reality in which these terms are found.

In practice, it is about setting a different design approach, especially considering the requirements. We must not begin to reason from the "what" was asked and from the "how" we want the system to work, but rather we must consider the reasons for the request, even if sometimes the awareness of those who have expressed them is lacking. This still leads to asking pertinent questions and having satisfactory answers, to choose the solution and the most suitable application modalities. It is because it starts to give light to the measures that guarantee the good quality of the results. In every activity the man needs to know and for this reason he makes use of the formulation of why. Since knowledge and meaning are all one, to have the awareness of what should be done, it is good to use knowledge whose meaning is the motivation of the action. We dedicate particular attention to the acquisition of intent to grasp what the interlocutor wants and the relative motivations. It is a work of investigation and stimulus to focus and discover the real needs and priorities of the project, which often the commissioner has only in vague form.