diff --git a/oKBereitschaftsplanungDoku/arch/architecture.html b/oKBereitschaftsplanungDoku/arch/architecture.html
index aa9eab1..c3bca33 100644
--- a/oKBereitschaftsplanungDoku/arch/architecture.html
+++ b/oKBereitschaftsplanungDoku/arch/architecture.html
@@ -5,7 +5,7 @@
 <!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]-->
 <meta name="viewport" content="width=device-width, initial-scale=1.0">
 <meta name="generator" content="Asciidoctor 1.5.5.dev">
-<title>Building Block View</title>
+<title></title>
 <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700">
 <style>
 /* Asciidoctor default stylesheet | MIT License | http://asciidoctor.org */
@@ -422,39 +422,478 @@
 <div id="header">
 </div>
 <div id="content">
+<hr>
+<style>
+.arc42help {font-size:small; width: 14px; height: 16px; overflow: hidden; position: absolute; right: 0px; padding: 2px 0px 3px 2px;}
+.arc42help::before {content: "?";}
+.arc42help:hover {width:auto; height: auto; z-index: 100; padding: 10px;}
+.arc42help:hover::before {content: "";}
+@media print {
+	.arc42help {display:hidden;}
+}
+</style>
+<h1 id="true-span-class-image-img-src-images-open-konsequenz-jpg-alt-openk_logo-span" class="sect0"><a class="anchor" href="#true-span-class-image-img-src-images-open-konsequenz-jpg-alt-openk_logo-span"></a><span class="image"><img src="images/open-konsequenz.jpg" alt="openK_logo"></span></h1>
 <div class="sect1">
-<h2 id="section-building-block-view"><a class="anchor" href="#section-building-block-view"></a>Building Block View</h2>
+<h2 id="truearchitecture-description-for-standby-planning-module"><a class="anchor" href="#truearchitecture-description-for-standby-planning-module"></a>Architecture description for "Standby Planning" module</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>The following image shows the structure of the modul 'StandbyPlanning'
-<span class="image"><img src="../images/ok_arch_overview.png" alt="openK_logo"></span></p>
+<p><strong>Acknowledgement</strong></p>
+</div>
+<div class="paragraph">
+<p>The following document contains the description of the architecture of the openKonsequenz "Standby Planning" module and is based on the arc42 asciidoc template.</p>
+</div>
+<div class="paragraph">
+<p>Template Revision: 7.0 DE (asciidoc-based), January 2017</p>
+</div>
+<div class="paragraph">
+<p>&#169;
+We acknowledge that this document uses material from the
+arc 42 architecture template, <a href="http://www.arc42.de" class="bare">http://www.arc42.de</a>.
+Created by Dr. Peter Hruschka &amp; Dr. Gernot Starke.</p>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-introduction-and-goals"><a class="anchor" href="#section-introduction-and-goals"></a>1. Introduction and Goals</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="truerequirements-overview"><a class="anchor" href="#truerequirements-overview"></a>1.1. Requirements Overview</h3>
+<div class="paragraph">
+<p>The module "Standby Planning" should support a user by creating a standby schedule and giving the employee (standby_user) the chance to see when he/she has a planned standby time.
+Therefore the person who make the plan has the change to define groups and functions, connect them to regions, on which he/she can filter to switch standby times, for example.
+Also the user has the change to start an automatic generation process in the planning phase were he/she can choose a standby cycle that defines to which times an standby time start or ends.
+The full requirements of the module are specified in the external specification.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="truequality-goals"><a class="anchor" href="#truequality-goals"></a>1.2. Quality Goals</h3>
+<div class="paragraph">
+<p>The following documents contain the quality goals in detail:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Architecture Committee Handbook v1.3.1 from 05-09-2017</p>
+</li>
+<li>
+<p>Quality Committee Handbook v1.1.1 from 11-09-2017</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The architecture is based on the AC-Handbook. The quality demands are described in the QC-Handbook.
+Both specifications were fully complied with in the project, so that a high quality is given.</p>
+</div>
+<div class="paragraph">
+<p>The code quality regarding static code analysis and unit test code coverage on the backend and fronend sides
+are ensured by the use of sonarqube. The rule set and the qualtity gate are defined by the default, the
+so called "sonar way".</p>
+</div>
+<div class="paragraph">
+<p>The module 'Standby Planning' is part of the Eclipse project 'Eclipse openK User Modules'.
+This project bases on the Eclipse Public Licence 2.0.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="truestakeholder"><a class="anchor" href="#truestakeholder"></a>1.3. Stakeholder</h3>
+<table class="tableblock frame-all grid-all spread">
+<caption class="title">Tabelle 1. Stakeholders</caption>
+<colgroup>
+<col style="width: 33.3333%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3334%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Role/Name</th>
+<th class="tableblock halign-left valign-top">Contact</th>
+<th class="tableblock halign-left valign-top">Expectations</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Product Owner (represents the Distribution System Operators)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Oliver Frank, Heinrich Schubert</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The software must fulfil their functional and nonfunctional Requirements.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Module Developer</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Maximillian Ridder, Christoph Weber, Markus Wolf, Saverio Mancuso, Jan Gerste</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">All relevant business and technical information must be available for implementing the software.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">External Reviewer (represents the AC/QC)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Thorsten Meyer</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The software and the documentation is realized according the Quality and Architecture Handbook of openKONSEQUENZ.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">External Reviewer (represents the Eclipse-Requirements)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Angelika  Wittek</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The software is  licensed under the EPL 2.0. It must be validated that all requirements are fulfilled.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">System Integrator</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">n.n.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A documentation for the integration of the module in the DSO specific environments must be available.</p></td>
+</tr>
+</tbody>
+</table>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-architecture-constraints"><a class="anchor" href="#section-architecture-constraints"></a>2. Architecture Constraints</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>TODO: LINK zum Eclipse Repository anpassen</p>
+</div>
+<div class="paragraph">
+<p>The main architecture constraints are:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><strong>Public License</strong> The module must be available under the "Eclipse Public License 2.0".</p>
+</li>
+<li>
+<p><strong>Availability</strong> The source code of the module must be accessible to any interested person/company.
+Therefore the project is published at <a href="https://projects.eclipse.org/projects/technology.openk-usermodules/developer" class="bare">https://projects.eclipse.org/projects/technology.openk-usermodules/developer</a></p>
+</li>
+</ul>
+</div>
+<div class="sect2">
+<h3 id="truetechnical-constraints"><a class="anchor" href="#truetechnical-constraints"></a>2.1. Technical Constraints</h3>
+<div class="paragraph">
+<p>The following technical constraints are given:</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<caption class="title">Tabelle 2. Technical Contraints</caption>
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Component</th>
+<th class="tableblock halign-left valign-top">Constraints</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Basis components of the reference platform</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>Application Server Tomcat</p>
+</li>
+<li>
+<p>Database PostgreSQL</p>
+</li>
+</ul>
+</div></div></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Programming Language Backend</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>Java 1.8</p>
+</li>
+<li>
+<p>REST/JSON Interfaces</p>
+</li>
+<li>
+<p>Eclipse Link as ORM</p>
+</li>
+<li>
+<p>JUnit + Mockito</p>
+</li>
+</ul>
+</div></div></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Programming Language Frontend</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>Angular 6.1.0 (Javascript, Typescript, HTML5, CSS3)</p>
+</li>
+<li>
+<p>Bootstrap</p>
+</li>
+<li>
+<p>According to oK-GUI-Styleguide</p>
+</li>
+</ul>
+</div></div></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Java QA environment</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>Sonarqube 6.4</p>
+</li>
+</ul>
+</div></div></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">IDE</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>Not restricted (Eclipse, Microsoft Visual Code &#8230;&#8203;)</p>
+</li>
+</ul>
+</div></div></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Build system</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>Backend: Maven</p>
+</li>
+<li>
+<p>Frontend: NodeJS + Angular/cli</p>
+</li>
+</ul>
+</div></div></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Libraries, Frameworks,Components</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>Used Libraries/Frameworks have to be compatible to the Eclipse Public License</p>
+</li>
+</ul>
+</div></div></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Architecture Documentation</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>According ARC42-Template</p>
+</li>
+</ul>
+</div></div></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="truetechnical-dependencies"><a class="anchor" href="#truetechnical-dependencies"></a>2.2. Technical Dependencies</h3>
+<div class="sect3">
+<h4 id="truemodules"><a class="anchor" href="#truemodules"></a>2.2.1. Modules</h4>
+<div class="paragraph">
+<p>The following modules are required to use the 'Standby Planning':</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<caption class="title">Tabelle 3. Modules</caption>
+<colgroup>
+<col style="width: 33.3333%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3334%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name of the module</th>
+<th class="tableblock halign-left valign-top">Purpose</th>
+<th class="tableblock halign-left valign-top">Status of the module</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">'Auth&amp;Auth'</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Authentification and Authorization</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">available</p></td>
+</tr>
+</tbody>
+</table>
 </div>
 <div class="sect3">
-<h4 id="truefrontend-tier-spfe"><a class="anchor" href="#truefrontend-tier-spfe"></a>Frontend - Tier (spfe)</h4>
+<h4 id="truelibraries"><a class="anchor" href="#truelibraries"></a>2.2.2. Libraries</h4>
 <div class="paragraph">
-<p>This component implements the presentation logic for the standby-planning-module using the Angular-TypeScript framework. The Frontend is a so called <strong>Single Page Application</strong> (SPA) because it behaves like a single HTML-page. The name of the war file is <strong>spfe</strong>.</p>
+<p><strong>Frontend</strong></p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Dependency</th>
+<th class="tableblock halign-left valign-top">Reason for Usage</th>
+</tr>
+</thead>
+<tfoot>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">primeng/primeicons</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">PrimeNG is a huge library which offers different angular components like multiselect boxes, context menu or toast messages. These components are part of our application.</p></td>
+</tr>
+</tfoot>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">@angular/* libraries</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Comes with Angular</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">classlist.js, core-js, rxjs, web-animations-js, zone.js</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Comes with Angular</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">@ng-bootstrap/ng-bootstrap</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">This dependency provides a load of different bootstrap/angular components. Mostly we use the datepicker/timepicker but some other components found it&#8217;s way into the application as well.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ag-grid, ag-grid-angular</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">This library is used to display tables. It provides functionality like filtering out of the box. This library was preferred by the Product Owner and therefore we used it.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">bootstrap</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">As we want a responsive application in general there is no way around bootstrap in these days. Therefore we put it into our application.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">font-awesome</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To make our app more appealing to the users we are using font-awesome to get range of nice icons into our application.</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>TODO: Pfad zu den Datein (Bibliotheken) ergaenzen.</p>
 </div>
 <div class="paragraph">
-<p>It divides the GridMeasureFE into three layers:</p>
+<p>The used libraries can be found here:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Backend</p>
+<div class="ulist">
+<ul>
+<li>
+<p>pom.xml of the module</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Frontend</p>
+<div class="ulist">
+<ul>
+<li>
+<p>package.json</p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-system-scope-and-context"><a class="anchor" href="#section-system-scope-and-context"></a>3. System Scope and Context</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="truebusiness-context"><a class="anchor" href="#truebusiness-context"></a>3.1. Business Context</h3>
+<div class="paragraph">
+<p>The user module 'Standby Planning' communicates via Restful Webservices with the following modules:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><strong>Core Module 'Auth &amp; Auth'</strong> The 'Standby Planning' can only be used by authorized users.Therefore, it is essential to invoke the module 'Auth &amp; Auth' for authorization and authentication purposes.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p><strong>&lt;Diagramm und/oder Tabelle&gt;</strong>
+TODO Diagramm erstellen und hinzufügen</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="truetechnical-context"><a class="anchor" href="#truetechnical-context"></a>3.2. Technical Context</h3>
+<div class="paragraph">
+<p>The following aspects have to be taken into account for external communication of the module Standby Planning:</p>
+</div>
+<div class="paragraph">
+<p>RESTful web services are used as interface-technology.</p>
+</div>
+<div class="paragraph">
+<p>Each external interface (interfaces between modules or external systems) has to be documented.</p>
+</div>
+<div class="paragraph">
+<p>Dependencies of modules to services realized by other modules have to be specified and documented explicitly.</p>
+</div>
+<div class="paragraph">
+<p>The interfaces of the module 'Standby Planning' are described in the interface documentation.</p>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-solution-strategy"><a class="anchor" href="#section-solution-strategy"></a>4. Solution Strategy</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The module 'Standby Planning' bases on a three-tier architecture:</p>
 </div>
 <div class="olist arabic">
 <ol class="arabic">
 <li>
-<p><strong>Components</strong> - The components (Pages, Lists, Dialogs, Common Comp.) represent the presentation layer and the control layer. A component contains the control logic (.ts-file), an HTML-fragment as presentation description (.html-file) and a style definition (.css-file).</p>
+<p><strong>Frontend</strong> - The GUI is implemented as a web-frontend.</p>
 </li>
 <li>
-<p><strong>Services</strong> - The service component communicates with the interfaces of the backend via HTTP requests by using the model component.</p>
+<p><strong>Backend</strong> - The business functionalities are implemented in the backend tier. It provides the business functions via RESTful Webservices.</p>
 </li>
 <li>
-<p><strong>Model</strong> - The model corresponds to the View-Model of the backend tier.
-.frontend_picture
-<span class="image"><img src="../images/ok_arch_frontend.png" alt="ok_arch_frontend.png"></span></p>
+<p><strong>Database</strong> - The database stores all module specific data.</p>
 </li>
 </ol>
 </div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-building-block-view"><a class="anchor" href="#section-building-block-view"></a>5. Building Block View</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The following image shows the structure of the modul 'StandbyPlanning'
+<span class="image"><img src="./images/ok_arch_overview.png" alt="openK_logo"></span></p>
+</div>
+<div class="sect2">
+<h3 id="truefrontend-tier-spfe"><a class="anchor" href="#truefrontend-tier-spfe"></a>5.1. Frontend - Tier (spfe)</h3>
+<div class="paragraph">
+<p>This component implements the presentation logic for the standby-planning-module using the Angular framework. The Frontend is a so called <strong>Single Page Application</strong> (SPA) because it behaves like a single HTML-page. The name of the war file is <strong>spfe</strong>.</p>
+</div>
+<div class="paragraph">
+<p>Technical the frontend consists of the following building blocks:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p><strong>Modules</strong> - There is one Core Module which holds all the singleton assets of the application like login, authentication service, navbar,etc. The Shared Module keeps all the reuseable elements like general components, directives, etc. In addition to these two Modules there are several Feature Module which encapsulate one functional requirement each like masterdata-management, standby-planning or reports.</p>
+</li>
+<li>
+<p><strong>Services</strong> - Each Module has itś own Services which are mostly used to make restcalls to the backends.</p>
+</li>
+<li>
+<p><strong>Components</strong> - In each Module you will find a component section which holds the different Components.
+.frontend_picture
+<span class="image"><img src="./images/ok_arch_frontend.png" alt="ok_arch_frontend.png"></span></p>
+</li>
+</ol>
 </div>
 <div class="sect3">
-<h4 id="truebackend-tier-spbe"><a class="anchor" href="#truebackend-tier-spbe"></a>Backend - Tier (spbe)</h4>
+<h4 id="truebackend-tier-spbe"><a class="anchor" href="#truebackend-tier-spbe"></a>5.1.1. Backend - Tier (spbe)</h4>
 <div class="paragraph">
 <p>This component implements the business functionality of the planned grid measures. And it provides services, that the <strong>spfe</strong> – SPA can use the functions in the frontend. The name of the war file is <strong>spbe</strong>.</p>
 </div>
@@ -503,29 +942,29 @@
 </div>
 <div class="paragraph">
 <div class="title">backend_picture</div>
-<p><span class="image"><img src="../images/ok_arch_backend.png" alt="ok_arch_backend.png"></span></p>
+<p><span class="image"><img src="./images/ok_arch_backend.png" alt="ok_arch_backend.png"></span></p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="truedatabase-tier"><a class="anchor" href="#truedatabase-tier"></a>Database - Tier</h4>
+<h4 id="truedatabase-tier"><a class="anchor" href="#truedatabase-tier"></a>5.1.2. Database - Tier</h4>
 <div class="paragraph">
 <p>The database has the name "BP" and needs a user "bp". The project generates the needed tables and keys during startup. All needed data for the Standby-Planning application will be stored here. Also the camunda database will be used for storing process relevant data.</p>
 </div>
 <div class="paragraph">
 <div class="title">database_picture</div>
-<p><span class="image"><img src="../images/ok_arch_db.png" alt="ok_arch_db.png"></span></p>
+<p><span class="image"><img src="./images/ok_arch_db.png" alt="ok_arch_db.png"></span></p>
 </div>
 <div class="paragraph">
 <div class="title">database_tables</div>
-<p><span class="image"><img src="../images/ok_db_model_001.png" alt="ok_db_model_001.png"></span></p>
+<p><span class="image"><img src="./images/ok_db_model_002.png" alt="ok_db_model_002.png"></span></p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="trueprogram-configuration"><a class="anchor" href="#trueprogram-configuration"></a>Program Configuration</h4>
+<h4 id="trueprogram-configuration"><a class="anchor" href="#trueprogram-configuration"></a>5.1.3. Program Configuration</h4>
 <div class="sect4">
 <h5 id="truefrontend-configuration"><a class="anchor" href="#truefrontend-configuration"></a>Frontend Configuration</h5>
 <div class="paragraph">
-<p>In Frontend tier we are environment files to configure the application.
+<p>In Frontend tier there are environment files to configure the application.
 The files can be found in the frontend git under \src\environments.</p>
 </div>
 <div class="paragraph">
@@ -549,18 +988,277 @@
 <div class="paragraph">
 <p>Not defined yet.</p>
 </div>
+<div style="page-break-after: always;"></div>
 </div>
 </div>
 </div>
 </div>
 </div>
 </div>
+<div class="sect1">
+<h2 id="section-runtime-view"><a class="anchor" href="#section-runtime-view"></a>6. Runtime View</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="truelogin-authentication"><a class="anchor" href="#truelogin-authentication"></a>6.1. Login / Authentication</h3>
+<div class="paragraph">
+<p>TODO: Authentifizierung beschreiben
+TODO: Ablaufplaene (BPMN) beschreiben</p>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-deployment-view"><a class="anchor" href="#section-deployment-view"></a>7. Deployment of the application components</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="truedeployment-of-the-frontend"><a class="anchor" href="#truedeployment-of-the-frontend"></a>7.1. Deployment of the frontend</h3>
+<div class="paragraph">
+<p>Not defined yet.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="truedeployment-of-the-backend"><a class="anchor" href="#truedeployment-of-the-backend"></a>7.2. Deployment of the backend</h3>
+<div class="paragraph">
+<p>Not defined yet.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="truedeployment-of-the-database"><a class="anchor" href="#truedeployment-of-the-database"></a>7.3. Deployment of the database</h3>
+<div class="paragraph">
+<p>Not defined yet.</p>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-concepts"><a class="anchor" href="#section-concepts"></a>8. Concepts</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Not defined yet.</p>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-design-decisions"><a class="anchor" href="#section-design-decisions"></a>9. Design Decisions</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>All architecture decisions based on the Architecture Committee Handbook. There are no other deviations then the following.</p>
+</div>
+<div class="sect2">
+<h3 id="truebdew-whitepaper-anforderungen-an-sichere-steuerungs-und-telekommunikationssysteme"><a class="anchor" href="#truebdew-whitepaper-anforderungen-an-sichere-steuerungs-und-telekommunikationssysteme"></a>9.1. BDEW Whitepaper "Anforderungen an sichere Steuerungs- und Telekommunikationssysteme "</h3>
+<div class="paragraph">
+<p>During the development of this module the whitepaper of the BDWE will be used as basis concept, but only for the given four aspects with the here given exclusions.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<caption class="title">Tabelle 4. aspects from BDWE whitepaper</caption>
+<colgroup>
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 25%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">aspect</th>
+<th class="tableblock halign-left valign-top">german</th>
+<th class="tableblock halign-left valign-top">priority</th>
+<th class="tableblock halign-left valign-top">description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">integrity</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Integrität</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">high</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">- Integrity testing of module specific configuration files will be checked on DEV and TEST system manualy before they will be deployed to PROD.
+</p><p class="tableblock">- A crypted checksum for system-, config- and application files will not be implemented.
+</p><p class="tableblock">- user information will be handled with the 'Auth &amp; Auth' core module. Therefore there are no real user data sended in the module. Just the crypted bearer value.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">availability</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Verfügbarkeit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">normal</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">In the document the aspect availability is mostly described as a hardware based topic and has not really much to do with development of this module. The only point that fits is the patching situation. (p.12) But because of the normal priority a short downtime should be acceptable. A server start is recommended but not necessary. But the application contexts need to be undployed and deployed. Therefore a short downtime is needed.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">intimacy</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Vertraulichkeit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">normal</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">At the moment there is no intimacy classifaction defined. The Standby Planning module uses user data for generation standby plans. All the data are stored in a local database with restricted access. The Module uses HTTP-Rest requests for getting the data to UI. Therefore restrictions can be set that only users with special roles can be granted access.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">maintainability</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Wartbarkeit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">normal</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">- There is no defined maintainability contract at the moment.
+</p><p class="tableblock">- The Standby Planning module is currently splittet into three components. Backend, Frontend and database. It uses moduls from openK like 'Auth &amp; Auth' but has not other interaction to the module. So far there are no interfaces that should be called from other modules.</p></td>
+</tr>
+</tbody>
+</table>
+<table class="tableblock frame-all grid-all spread">
+<caption class="title">Tabelle 5. timetable of decisons</caption>
+<colgroup>
+<col style="width: 33.3333%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3334%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Date</th>
+<th class="tableblock halign-left valign-top">Short</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-05-29</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Fontend Framework</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-05-29</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Fontend Buildmechanism</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">We decided to stay as close to the native and recommended build mechanism as possible. Therefore we are using Angular CLI as our build- and testtool. We opposed to use Maven for Frontendbuild as this brings additional complexity into the build process and is far away from the recommended and accepted way in the community.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-05-29</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Fontend - Backend - DB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 make much sense to modulize them. (Diffenrent .jars, for example, would be more effort than benefit.)</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-05-29</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Camunda BPM</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Camunda BPM is used as BPMN engine to route processes.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-05-29</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Tools and APIs</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The technical constraints are documented in the 02_architecture_constraints.adoc and defined in the backend (spbe) pom.xml</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-05-29</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ng2-daterangepicker</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 (<a href="https://ng-bootstrap.github.io" class="bare">https://ng-bootstrap.github.io</a>) which is well maintained.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-06-14</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AG-Grid for tables</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-06-29</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">no use of bom.xml</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2018-10-23</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Standard HTML Tables for View "Abfrage aktuelle Bereitschaft"</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 - (<a href="https://openkonsequenz.atlassian.net/browse/BP-187?focusedCommentId=10277&amp;page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-10277" class="bare">https://openkonsequenz.atlassian.net/browse/BP-187?focusedCommentId=10277&amp;page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-10277</a>).</p></td>
+</tr>
+</tbody>
+</table>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-quality-scenarios"><a class="anchor" href="#section-quality-scenarios"></a>10. Quality scenarios</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>not described yet.</p>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-technical-risks"><a class="anchor" href="#section-technical-risks"></a>11. Risks and Technical Debts</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>(Currently there aren&#8217;t any known issues)</p>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-glossary"><a class="anchor" href="#section-glossary"></a>12. Glossary</h2>
+<div class="sectionbody">
+<table class="tableblock frame-all grid-all spread">
+<caption class="title">Tabelle 6. Abbreviations and glossary terms</caption>
+<colgroup>
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 25%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Short</th>
+<th class="tableblock halign-left valign-top">Long</th>
+<th class="tableblock halign-left valign-top">German</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AC</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Architecture Committee</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Architektur-Komittee</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Gives Framework and Constraints according to architecture for oK projects.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">DAO</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Data Access Objects</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">DTO</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Data Transfer Object</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">EPL</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Eclipse Public License</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Underlying license model for Eclipse projects like elogbook@openK</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">REST</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Representational State Transfer</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Representational State Transfer bezeichnet ein Programmierparadigma für verteilte Systeme, insbesondere für Webservices.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">oK</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">openKONSEQUENZ</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">openKONSEQUENZ</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Name of the consortium of DSOs</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">QC</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Quality Committee</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Qualitätskomitee</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Gives framework and constraints according to quality for oK projects.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2018-07-02 15:48:47 MS
+Last updated 2018-12-19 14:47:19 MZ
 </div>
 </div>
-<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/8.9.1/styles/github.min.css">
+<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/8.9.1/styles/solarized_dark.min.css">
 <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/8.9.1/highlight.min.js"></script>
 <script>hljs.initHighlighting()</script>
 </body>