User Acceptance
In Software Design, the term of “User Acceptance” is always something not very pleasantly thought of, because it often embodies the greatest of all risks: profitability. Clients of a software company are usually users or groups of users, and their willingness to acquire some product or service depends wheather or they accept the offer. But it’s not only a process of haggling, but the product or service itself must be accepted by its prospect users. Obviously this is very hard to foresee if it hasn’t been tested yet in the target environment, turning the whole situation into kind of a deadlock.
Acceptance therefore has to be critically assessed, and it makes sense to always also consider a worst-case scenario. [to be continued]
