Page 31 - Methodology for inter-operator and cross-border P2P money transfers

Figure 10 – Principal action flow for asynchronous testing

13�3 Dual-function set-up and operation • X is in the A Party role, sending money to device
There is a special situation when intra-operator tests Y which is therefore in the B Party role. Events are
in the same country are made in the same location, recorded using the MSW app on device Y.
and the number of devices used in testing shall be • If synchronous mode is used, device functions
minimized. are swapped now. In asynchronous testing, first a
In the standard case, devices have fixed functions; number to transactions is run, then functions are
the DFS device is used to run the use case while the swapped.
Observer device is used to run the MSW app and • After swapping, MSW and DFS Observer is ended
the background-testing app. In the generic case, this on device Y, and started on device X (1). The DFS
would require a total of 4 devices where each device A-Party role is now performed on device Y with
has a dedicated role. device X in the B-Party role.
The number of devices can be reduced to two if
devices switch functions. In that case, both devic- Remark (1): This is a precaution to exclude cross-ef-
es need MoMo accounts, MSW and ObsTool apps fects from background testing into DFS performance.
installed. Assuming device designations X and Y, the By assessment and decision of the FTL, respective
sequence of testing would be: apps can run continuously on both devices.
The following figure shows the set-up and operation
• X is used as the DFS device; MSW and ObsTool are graphically.
started on device Y.

Methodology for inter-operator and cross-border P2P money transfers 29