Adham Hashibon
--- a/doc/source/design.rst

+ 8

− 1
+++ b/doc/source/design.rst

+ 8

− 1
 Design
 ------

-The application is based on three entities, as written in the introduction:
+The application is based on four entities, as written in the introduction:

 - Multi Criteria Optimizer (MCO)
 - DataSources
 - Key Performance Indicator (KPI) Calculators
+- Notification Listeners

 There are a few core assumptions about each of these entities:

 @@ -18,6 +19,10 @@ There are a few core assumptions about each of these entities:
  numerical result. This result is passed to the KPI calculators.
 - The KPI calculators now compute the final KPIs that are then returned to
  the invoker MCO.
+- The Notification Listener listens to the state of the MCO (Started/New step
+  of the computation/Finished). It can be a remote database which is filled
+  with the MCO results during the computation (e.g. the GUI `force_wfmanager`
+  has a notification listener in order to fill the result table).


 The result can be represented with the following data flow
 @@ -32,6 +37,8 @@ The result can be represented with the following data flow
 5. one or more KPICalculators, which perform final data evaluation on the
   obtained values, eac producing KPIResult...
 6. Whose values are then returned to the MCO via the Communicator.
+7. The KPI values are then sent to the notification listeners with the
+   associated MCO parameters values

 The resulting pipeline is therefore just two layers (DataSources, then
 KPICalculators).