diff --git a/Readme.md b/Readme.md
index 88e42956b6984600a333650c6e265c4067eb8201..6da1e7af6bf8910f00681b82b525468fc69ff6c8 100644
--- a/Readme.md
+++ b/Readme.md
@@ -6,7 +6,7 @@ More info at [TDL website](https://tdl.etsi.org)
 
 ## Installing the plug-ins
 
-The TDL tools are available as a set of Eclipse plug-ins. You need to first be able to run Eclipse. The [Eclipse Modeling Tools](https://www.eclipse.org/downloads/packages/release/2020-06/r/eclipse-modeling-tools) distribution contains most of the necessary prerequisites for the TDL tools.
+The TDL tools are available as a set of Eclipse plug-ins. You need to first be able to run Eclipse. The [Eclipse Modeling Tools](https://www.eclipse.org/downloads/packages/release/2021-06/r/eclipse-modeling-tools) distribution contains most of the necessary prerequisites for the TDL tools.
 
 Once Eclipse is up and running, you need to add the [update site](https://tdl.etsi.org/eclipse/latest/) for the TDL tools: 
 
@@ -66,7 +66,10 @@ More information on using the plugins is available at [Usage wiki](https://labs.
 
 The generation of data types and other elements based on OpenAPI yaml specifications is based on the [KaiZen OpenAPI Parser](https://github.com/RepreZen/KaiZen-OpenApi-Parser). The corresponding [Eclipse plug-in](https://marketplace.eclipse.org/content/kaizen-openapi-editor) needs to be installed before installing the importer. While the transformation components can be installed individually, the user-interface currently depends on all the transformation plug-ins.
 
-The implementation currently supports: TODO
+The implementation currently supports: 
+ * Importing of data definitions under `components/schemas`.
+ * Data mappings to the base OpenAPI definition for traceability.
+ * Annotations with warnings regarding conventions.
 
 Part of the implementation was developed as a lab project with contributions from:
  * Lennart Thiesen
@@ -78,10 +81,16 @@ Part of the implementation was developed as a lab project with contributions fro
 ## Implementation of the ASN.1 import into TDL
 The generation of data types based on ASN.1 specifications is based on the [BeanIt ASN1Bean](https://github.com/beanit/asn1bean) (formerly known as jASN).
 
-The implementation currently supports: TODO
+The implementation currently supports: 
+ * Importing of data definitions within the module (imports from other modules are currently not resolved).
+ * Application of annotations or data constraints (e.g. for `CHOICE` data types or other modifiers).
 
 ## Implementation of the transformation of Structured Test Objectives to TDL Test Descriptions
-The transformation of Structured Test Objectives into TDL Test Descriptions currently supports : TODO
+The transformation of Structured Test Objectives into TDL Test Descriptions currently supports:
+ * Transforming of inline data descriptions within `EventOccurrences` into corresponding data types.
+ * Generation of `TestConfigurations` based on the `EventSequences` within the Structured Test Objective.
+ * Generation of `TestDescription` skeletons based on the `EventSequences` within the Structured Test Objective with references to it.
+ * Importing of the base package and imported packages.
 
 ## Implementation of the TDL mapping to TTCN-3