You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/03_context_and_scope.adoc
+29-5Lines changed: 29 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,8 +73,32 @@ together with a mapping table showing the relationships between channels and inp
73
73
****
74
74
endif::arc42help[]
75
75
76
-
**<Diagram or Table>**
77
-
78
-
**<optionally: Explanation of technical interfaces>**
79
-
80
-
**<Mapping Input/Output to Channels>**
76
+
The following table describes the technical interfaces and the channels used to link the system components and external entities.
77
+
78
+
[cols="1,3", options="header"]
79
+
|===
80
+
|Component / Channel |Description
81
+
|**User Device** |Computer, laptop, or mobile device used to access the system via a secure HTTPS connection.
82
+
|**Web Application (Frontend)** |Developed in TypeScript. Manages matches, communicates with the Rust module, and interacts with Firebase and the Bot API.
83
+
|**Rust Game Logic Module** |Component responsible for match outcomes and bot moves. Exposes a web service endpoint for the Frontend.
84
+
|**Firebase Database** |Cloud persistence layer for user information and statistics via Firebase SDK.
85
+
|**Public API for Bots** |Interface for external bots to interact with the system over HTTPS.
86
+
|**Deployment Platform (Azure)** |Cloud infrastructure hosting the Rust backend and WebApp, ensuring HTTPS and availability.
87
+
|===
88
+
89
+
image::Technical_Context_Component_diagram.png[Diagrama de Contexto, width=600, align="center"]
90
+
91
+
==== Mapping Input/Output to Channels
92
+
93
+
The following table maps the domain-specific inputs and outputs to their respective technical channels and protocols.
0 commit comments