Merge pull request #36 from Arquisoft/doc_fixes_571011

Fixed the diagrams from parts 5, 7, 10 and 11

docs/05_building_block_view.adoc

@@ -9,7 +9,7 @@ Motivation::
 
 This diagram is motivated by the need of having a clear separation of the composition of the application.
 
-[plantuml,"Deployment diagram",png]
+[plantuml,"BuildingBlockView", png]
 ----
 @startuml
 
@@ -109,7 +109,7 @@ No issues, problems or risks are known.
 
 Currently, the only layer we have somewhat structured is the persistance layer. 
 
-[plantuml,"Deployment diagram",png]
+[plantuml,png, id = "PersistenceLayer"]
 ----
 @startuml
 

docs/07_deployment_view.adoc

@@ -7,10 +7,9 @@
 
 Given that we currently do not know much about hosting the application, at this moment we will follow a simple approach that will likely change in the future.
 
-[plantuml,"Deployment diagram",png]
+[plantuml,"Deployment diagram",png, id = "DeployDiagramView"]
 ----
 @startuml
-
 header Deployment view
 title Deployment view
 
@@ -23,17 +22,12 @@ agent Pod2
 agent Pod3
 agent PodN
 
-Pod1 ---> "LoMap Platform"
-Pod1 <--- "LoMap Platform"
-Pod2 ---> "LoMap Platform"
-Pod2 <--- "LoMap Platform"
-Pod3 ---> "LoMap Platform"
-Pod3 <--- "LoMap Platform"
-PodN ---> "LoMap Platform"
-PodN <--- "LoMap Platform"
-
-"Database server" -> "LoMap Platform"
-"Database server" <- "LoMap Platform"
+Pod1 <--> "LoMap Platform"
+"LoMap Platform" <--> Pod2
+PodN <--> "LoMap Platform"
+"LoMap Platform" <-> "Pod3"
+
+"Database server" <-> "LoMap Platform"
 
 @enduml
 ----

docs/11_technical_risks.adoc

@@ -1,10 +1,6 @@
 [[section-technical-risks]]
 == Risks and Technical Debts
 
-
-[role="arc42help"]
-
-
 As it stands now, we have identified some important risks before starting coding the project.
 
 |===