3.2 - technical context diagram

Arquisoft · Feb 17, 2024 · 7738d09 · 7738d09
1 parent c3be45d
commit 7738d09
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 18 deletions.
diff --git a/docs/images/technicalDiagram.png b/docs/images/technicalDiagram.png
diff --git a/docs/src/03_system_scope_and_context.adoc b/docs/src/03_system_scope_and_context.adoc
@@ -4,11 +4,6 @@ ifndef::imagesdir[:imagesdir: ../images]
 == System Scope and Context
 
 
-
-
-
-
-
 === Business Context
 
 [role="arc42help"]
@@ -22,23 +17,30 @@ image::business-context.png[Business Context Diagram, 600, 400]
 **<optionally: Explanation of external domain interfaces>**
 
 === Technical Context
+The application structure is the following:
 
-[role="arc42help"]
-****
-.Contents
-Technical interfaces (channels and transmission media) linking your system to its environment. In addition a mapping of domain specific input/output to the channels, i.e. an explanation which I/O uses which channel.
+image::technicalDiagram.png[Technical Diagram, 600, 400]
 
-.Motivation
-Many stakeholders make architectural decision based on the technical interfaces between the system and its context. Especially infrastructure or hardware designers decide these technical interfaces.
+.Explanation of the Diagram
 
-.Form
-E.g. UML deployment diagram describing channels to neighboring systems,
-together with a mapping table showing the relationships between channels and input/output.
 
-****
+The application will be deployed on an Azure Server. It will consist of the following:
+
+The client communicates with the web app, the front-end of the application. Developed with *React* and *JavaScript*, this application retrieves information from the server, interacting with the *Gateway*.
+
+We employ a facade pattern on the server, with a dedicated *Gateway service* redirecting requests to different internal services.
+
+The services include:
+
+- *Authentication Service*
+- *Users Service*
+- *Question Generator Service*
+- *Game Service*
+- *Groups Service*
+
+All these services interact with the *MongoDB* database, retrieving and adding information.
+
+To generate questions automatically, communication with the *WikiData API* is necessary. The *Question Generator Service* houses an algorithm for question generation.
 
-**<Diagram or Table>**
 
-**<optionally: Explanation of technical interfaces>**
 
-**<Mapping Input/Output to Channels>**