# A Modular Experimentation Methodology for 5G Deployments: The 5 GENESIS Approach
## 4 Formalization of the Experimentation Methodology
### Test Case

Table 2: Test case for assessing the maximum throughput available at the application level. and understanding the obtained values. More precisely, the following information is provided in the test case template:  
**Target KPI**: this field includes the definition of the target KPI. Each test case targets only one KPI (main KPI). However, secondary measurements from complementary KPIs can also be added (see \"Complementary measurements\" field of this template). The definition of the main KPI specifies the related target metric, the ID of which is declared in the first row of the template. More precisely, the definition of the main KPI declares at least the reference points from which the measurement(s) are performed, the underlying system, the reference protocol stack level, and so on. Within the 5 GENESIS experimentation methodology, the term \"metric\" refers to a generic high-level definition of a target quality factor (attribute) to be evaluated, i.e., a definition that is independent of the underlying system, the reference protocol layer, or the tool used for the measurement. The initial set of identified metrics is specified in [25], based on an abstraction of the set of 5G KPIs defined by 5G-PP in [45]. **Methodology**: this field declares the procedure and configurations relevant for defining the experiment execution, including the acceptable values for the experiment duration, the iterations required to obtain statistically significant results, and the measurement interval, to mention a few. **Calculation process and output**: this field describes the processing performed on the KPI samples that allows to derive the statistical indicators for the executed test case, ultimately enabling the KPI validation. As reported in the \"Methodology\" field, the experiment should be executed for a statistically significant number of iterations, e.g., \(I\), in order to obtain an accurate picture of the KPI. An example of calculation process and corresponding output is given in the test case template that is presented in Table 2.  
**Complementary measurements**: this field defines a list of secondary parameters useful to interpret the values of the target KPI. On the one hand, getting these measurements is not mandatory for the test case itself; on the other hand, the M&A framework can exploit them in order to provide more insights on the experiment execution. As a first step, an overview of the complementary measurements (e.g., in terms of per-iteration and test case statistical indicators) can be provided to the experimenter along with the results that are related to the target KPI. Moreover, such measurements can help to pinpoint anomalous and unexpected behaviors, provide correlation and predictive analyses via ML tools, and trigger architectural improvements for next experiment executions. **Preconditions**: a list of test-specific information about equipment configuration and traffic description is provided in this field. Additionally, the description of the initial state of the System Under Test (SUT), required to start executing a test case sequence, is provided. **Applicability**: this field reports a list of features and capabilities which are required by the system in order to guarantee the feasibility of the test. **Test case sequence**: this field specifies the sequence of actions to be performed during the execution of the test case. Besides the test case reported in Table 2 above, the 5 GENESIS Consortium has already defined several test cases, including the ones for assessing latency KPIs (see Sections 5 and 6). Test cases covering further 5G KPIs are also available in [25].