Prepare a functional journey

What to measure?

It is important to know that everything doesn’t need to be measured. Focus on the main user journey and critical steps.

For example, if the need is to measure the usual user journey to buy a service on the mobile application, don’t measure the initial steps of application configuration (sign in, etc).

Before coding, it's important to have an overview of the journey and the steps involved.

For that :

Verify the journey manually
Decompose the journey in different steps according to the following documentation.

Steps in GDSL

To decompose a functionality, there are three possible steps: load, action, pause.

Load :

An action leading to the display of a new view
Triggered by clicking on a button or link, by launching an application, or directly by validating an url in the menu bar.
Ends with the arrival of a graphic element in the new view

Action :

An action in the current view that does not lead to the display of a new view (but potentially to a modification of the current view).
Triggered by view scroll, form, or smartphone actions
Ended by the end of the action itself (e.g. end of scroll directly)
Several actions can be grouped together if there is functional coherence

Pause :

A waiting period with no action
To simulate the user between actions

Example

In a Microsoft application, the user must log in and identify himself. The steps involved in authentication are: action (filling in a field, clicking), load, scroll or pause.

Step	Type	Example of step name	State at the beginning of the step	State at the end of the step

Step	Type	Example of step name
Click on Entry to load connection page	Load	CHRGT_connection
Pause on connection page	Pause	PAUSE_connection
Report email	Action	ACTION_connection
Click on “Next”	Load	CHRGT_validationConnection