The proposed scenario generation method proceeds in the following five steps.
Step 1 – identifying elementary tasks which a product supports
Elementary tasks usually correspond to functions that a product supports. In this example, the
total number of the elementary tasks was fifteen.
Step 2 – identifying the procedure of operations carried out in each elementary task
An operation is an elementary action by the user, which produces a system response or a state
change. In step 2, the procedure of each task is described as a sequence of operations. Table 2 is
a part of the task-operation contingency that appeared in the example.

Step 4 – grouping the tasks based on their operation sequence patterns
In step 4, the tasks are grouped to have similar operation procedures and controls.

http://koasas.kaist.ac.kr/bitstream/10203/7889/1/2004[Hwansu%20Park,%20Wan%20C%20Yoon]Scenario%20elicitaion%20method%20based%20on%20operation%20sequence%20pattern.pdf

Operations are the actions performed by people interacting with a system or by the system itself,[11] and plans explain the conditions necessary for these operations.[1] Operations describe the smallest individual task steps in the HTA, i.e. those which cannot be broken down into plans and further operations. They are the individual actions, such as 'visually locate control' or 'move hand to control', which the user must perform in a particular combination to achieve the goal of task completion.

https://en.wikipedia.org/wiki/Task_analysis

--------------------------------------------------
Note added at 23 hrs (2017-06-15 00:29:31 GMT)
--------------------------------------------------

Or "elementary operations".