BP-137 add documentation to arch/src/02_architecture_constraints.adoc and 09_design_decisions.adoc
diff --git a/oKBereitschaftsplanungDoku/arch/src/02_architecture_constraints.adoc b/oKBereitschaftsplanungDoku/arch/src/02_architecture_constraints.adoc
index a50221e..57c4371 100644
--- a/oKBereitschaftsplanungDoku/arch/src/02_architecture_constraints.adoc
+++ b/oKBereitschaftsplanungDoku/arch/src/02_architecture_constraints.adoc
@@ -19,13 +19,13 @@
|Component|Constraints
|Basis components of the reference platform
a|* Application Server Tomcat
-* JPA EclipseLink
* Database PostgreSQL
|Programming Language Backend
a|* Java 1.8
* REST/JSON Interfaces
* Eclipse Link as ORM
+* JUnit + Mockito
|Programming Language Frontend
a|* Angular 6.0.0 (Javascript, Typescript, HTML5, CSS3)
@@ -33,7 +33,7 @@
* According to oK-GUI-Styleguide
|Java QA environment
-a| * Sonarqube 5.6.6
+a| * Sonarqube 6.4
|IDE
a|* Not restricted (Eclipse, Microsoft Visual Code ...)
diff --git a/oKBereitschaftsplanungDoku/arch/src/09_design_decisions.adoc b/oKBereitschaftsplanungDoku/arch/src/09_design_decisions.adoc
index 7ae0e27..5d5fc43 100644
--- a/oKBereitschaftsplanungDoku/arch/src/09_design_decisions.adoc
+++ b/oKBereitschaftsplanungDoku/arch/src/09_design_decisions.adoc
@@ -24,14 +24,16 @@
- The Standby Planning module is currently splittet into three components. Backend, Frontend and database. It uses moduls from openK like 'Auth & Auth' but has not other interaction to the module. So far there are no interfaces that should be called from other modules.
|========================================================
-.timetable of decissons
+.timetable of decisons
[options="header"]
|========================================================
|Date|Short|Description
-|2018-06-20|Fontend - Backend - DB|At this point the module is splitted in 3 different projects.
+|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
- Database
Frontend and Backend have different components but at this point it would not much sencse 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-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.
|========================================================
\ No newline at end of file
