Have directory structure after benchmark execution

README.md

@@ -43,25 +43,6 @@ flowchart TD;
   instrumentedCall-->Kieker;
 ```
 
-## Directory Structure
-
-- analysis = analysis scripts
-- benchmark = moobench code
-- continuous-integration = obsolete
-- docker = Dockerfile to be used in automated runs on our intrestructure
-- frameworks = benchmark setups for the different frameworks for the respective language
-  - Kieker-java
-  - Kieker-python
-  - OpenTelementry-java
-  - SPASSmeter (currently not maintained)
-  - inspectIT-java
-- gradle = build system, gradle libraries
-- tools = tooling used to support benchmarks and process results
-  - compile-results = adds new results to a result log and computes partial
-    views of the results for presentation in websites
-  - getConfidenceIntervalTable = compute the confidence interval table
-  - receiver = receiver for Kieker TCP probe output
-
 ## Benchmark Execution
 
 Initially, the following steps are required:
@@ -108,6 +89,25 @@ cd frameworks/OpenTelemetry-java/
 ./benchmark.sh
 ```
 
+## Directory Structure
+
+- analysis = analysis scripts
+- benchmark = moobench code
+- continuous-integration = obsolete
+- docker = Dockerfile to be used in automated runs on our intrestructure
+- frameworks = benchmark setups for the different frameworks for the respective language
+  - Kieker-java
+  - Kieker-python
+  - OpenTelementry-java
+  - SPASSmeter (currently not maintained)
+  - inspectIT-java
+- gradle = build system, gradle libraries
+- tools = tooling used to support benchmarks and process results
+  - compile-results = adds new results to a result log and computes partial
+    views of the results for presentation in websites
+  - getConfidenceIntervalTable = compute the confidence interval table
+  - receiver = receiver for Kieker TCP probe output
+
 ## Data Analysis
 
 Each benchmark execution calls an R script providing mean, standard deviation