1 Scope
2 References
3 Definitions
3.1 Terms defined elsewhere
3.2 Terms defined in this Recommendation
4 Abbreviations and acronyms
5 Conventions
6 Test scenario under consideration
6.1 Roles, entities and action or /event flow
6.2 Test parameterization and neutral starting state
6.3 Re-initialization after unsuccessful transactions
6.4 Disappearing money
6.5 Automation of tests
7 Transaction model and digital financial service key performance
indicators
8 Creating the use case model from actual use case examples
9 Data sources
10 Special procedures in the field
10.1 Operational protocol if party A and B do not communicate
directly
11 Testing modes
11.1 Basics
11.2 Synchronized and asynchronous testing mode
11.3 Dual-function set-up and operation
12 Recording events of DFS test cases
12.1 Basic functionality
12.2 Practical application
13 Measurements in the background
14 General considerations about errors in measurements
15 Data validation and processing
15.1 Overview
15.2 Plausibility and validity checks
15.3 Data processing
15.4 Time profile
16 Background testing of mobile networks
Appendix I – Working example for creation of a use case model from actual
implementations
Appendix II – Best-practice example of data structures and procedures used in
DFS testing campaigns
II.1 Basic considerations for data collection and processing
II.2 Additional considerations for cross-border and inter-network
testing
II.3 Data structure overview
II.4 Naming and formatting conventions
II.5 Naming and formatting conventions for data objects
II.6 Local log sheets
II.7 Team assignment list
II.8 Device assignment list
Appendix III – Best-practice examples for background testing of mobile
networks
Bibliography