BP 588: added design/architecture decisions
diff --git a/oKBereitschaftsplanungDoku/arch/src/09_design_decisions.adoc b/oKBereitschaftsplanungDoku/arch/src/09_design_decisions.adoc
index 11be663..52f5a9e 100644
--- a/oKBereitschaftsplanungDoku/arch/src/09_design_decisions.adoc
+++ b/oKBereitschaftsplanungDoku/arch/src/09_design_decisions.adoc
@@ -28,6 +28,7 @@
 [options="header"]
 |========================================================
 |Date|Short|Description
+|2018-05-29|Fontend Framework|We chose to use the current version of Angular (6.1.0) in order to have a stable environment. An older version like Angular 4 was no option since the newer version has several bugfixes and optimizations. Angular JS was no alternative for us.
 |2018-05-29|Fontend - Backend - DB|At this point the module is splitted in 3 different projects. 
 - Frontend: Angular with cli build
 - Backend: Java with Maven build
@@ -35,6 +36,8 @@
 Frontend and Backend have different components but at this point it would not make much sense to modulize them. (Diffenrent .jars, for example, would be more effort than benefit.) 
 |2018-05-29|Camunda BPM|Camunda BPM is used as BPMN engine to route processes.
 |2018-05-29|Tools and APIs|The technical constraints are documented in the 02_architecture_constraints.adoc and defined in the backend (spbe) pom.xml
-|2018-05-29|ng2-daterangepicker|The source code of the date picker openK prefered is not maintained since 10 month. The last change was an ugrade to angular 4. Because the Standby Planning module uses angular 6 we decide not to use this date picker.   
+|2018-05-29|ng2-daterangepicker|The source code of the date picker openK prefered is not maintained since 10 month. The last change was an ugrade to angular 4. Because the Standby Planning module uses angular 6 we decide not to use this date picker. Instead we chose to use the datepicker from ng-bootstrap (https://ng-bootstrap.github.io) which is well maintained.
+|2018-06-14|AG-Grid for tables|The Product Owner preferred the usage of AG-Grid in this Project. As we did not see any disadvantages we agreed and used AG-Grid from now on. The alternative standard HTML-Tables were therefore obsolete.
 |2018-06-29|no use of bom.xml|A bom.xml is not needed as long no further modularization is needed for the backend modul. The pom.xml file is enough to describe the external used .jars.
+|2018-10-23|Standard HTML Tables for View "Abfrage aktuelle Bereitschaft"|For the View "Abfrage aktuelle Bereitschaft" it was required that it is responsive in order to use it on mobile devices and on Computers. We couldn´t get the AG-Grid responsive and therefore asked the Product Owner to use Standard HTML Tables. He agreed - (https://openkonsequenz.atlassian.net/browse/BP-187?focusedCommentId=10277&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-10277).
 |========================================================
\ No newline at end of file