diff --git a/documentation/design/01-introduction.md b/documentation/design/01-introduction.md
index a30f106c6a4d30c98d00487d8a15c2eb7af271a6..9fe5528605a2ea2800b23fc106ad247fb91f3dad 100644
--- a/documentation/design/01-introduction.md
+++ b/documentation/design/01-introduction.md
@@ -22,12 +22,18 @@ Some unsorted thoughts the be ordered yet:
 * modules should be loaded (or unloaded) during runtime of the controller core
 * reuse existing software if possible and if those are stable, i.e., documented, maintained etc,  on a long time
 
-
-## Structure of this Memo
-
 ## Use Cases to be considered
 
 The development of a general purpose SDN controller is not the primary goal at this early stage of the project.
 Instead there are two use cases to be considered in the implemenation works that are currently ongoing:
 * Primary: optical domain SDN-controller for the CoCSN project
 * Secondary: SDN-controller for our local labs to manage an Ethernet-based lab environment
+
+## Structure of this Memo
+
+This memo starts with this introduction that sets the stage for the theoretical underpinings of the SDN-controller
+and the acutal implementation (and the various choice for this). Chapter 2 discusses the related work and chapter 3
+outlines the theoretical foundations related to the control of networks and their relation to SDN. Chapter 4 uses
+the output of Chapter 3 to define the conceptual design of the goSDN controller and some discussions about the pro
+and cons of conceptual design. Chapter 5 describes the actual design of the current goSDN implementation and is 
+meant to be a compendium for the source code.