The “usage scenario” concept was proposed by Ivar Jacobson, a Swedish scientist in the computer field. He defines this concept as the interaction scenario between a user and a system for a certain purpose.
In this case, the user acts as an actor who has a certain role. Besides the user himself, an actor role may be represented by the other system. The action itself is carried out in the specific situation (context), which co-factors depend on the peculiarities of the product under test.
A scenario is a set of steps which specify the peculiarities of the user and system interaction. Basically, the usage scenarios are created by the developers for the developers themselves. But they will be also useful for the specialists of the testing sphere.
What Are the Usage Scenarios Advantages?
- The usage scenarios or variants define the functional requirements not from the technical point of view but through the prism of the user’s perception. Besides, they do not depend on the product paradigm
- Such scenarios using gives an opportunity to engage the users in the requirements specification process. Thus, the product will be more simple and easy to use.
- The usage scenarios are the basis for the establishment of the key internal system elements.
- Conducting system testing or acceptance testing, the specialists may create the test cases on the basis of the usage scenarios. It will simplify the task a lot.
Functional testing and performance testing will be also more effective during such approach execution. Software testing company always focuses on the highest quality level achievement, and the usage scenarios application exactly promotes this.