Divide and demand

rabiakhatun

Interested representatives of the business that we are going to digitize and automate are usually called stakeholders. These can be, for example, heads of production, finance, commerce, logistics and other departments. It happens that shareholders, business owners and clients are also included in the circle of stakeholders due to their interest in the final automation.

People who will use the information system for their work or purposes are users. At the same time, the user can simultaneously be a stakeholder if he is responsible for the implementation of a business task. And if he does not have such responsibility, then his main goals are the convenience and simplicity of digital products.

Often, user requirements are difficult to content writing service separate from business requirements precisely because stakeholders are both users and business owners of tasks.

It is important to understand that the goals of users and stakeholders often do not coincide.

User requirements are how the user ideally imagines working in the AIS. Usually, these requirements include not only answers to questions about what and how the system should allow to do, but also ergonomics and visual display of the user interface.




On the other hand, there are functional requirements - these are requirements for the performance of certain business functions in the AIS, for example, the functions of a treasurer or an accountant. They are usually described in great detail. Also, for greater accuracy, they are also called functional-technical requirements (FTR), but in essence they still remain functional requirements and cannot be classified as purely technical.

Non-functional requirements (technical) are requirements for the system as a technical product and its operation. For example, this includes the availability of the system for the user or the response time to an operation. These are more often numbers than words.

THE IDEAL AUTOMATION MODEL

Now let's move on to a model of how all this should work:

1. Business challenges pose business tasks to stakeholders.

2. Business tasks are closed by implementing business requirements for the new system.

3. Business requirements are closed by fulfilling functional and non-functional requirements for the AIS.

If everything is taken into account and described correctly, then we get a positive result and the fulfillment of the automation goal.

Some of the readers will exclaim: "Where are the user requirements here, have we forgotten about them?!" That's right, we have forgotten about them. Whether this is correct or not, we need to look into this in more detail.

So, from the point of view of a "rabid" business, the convenience of ordinary AIS users, if these are not clients who bring in vital revenue, fades into the background, because the owner of the business ultimately pays for the implementation of these requirements. Moreover, the implementation of such requirements often does not correlate with the achievement of business requirements and business tasks, but rather has an inverse effect on efficiency.