Skip to content

Commit 1424a8b

Browse files
authored
Fix errors and upload Technical Context documentation (#14)
1 parent e715b77 commit 1424a8b

File tree

3 files changed

+29
-5
lines changed

3 files changed

+29
-5
lines changed
235 KB
Loading
139 KB
Loading

docs/src/03_context_and_scope.adoc

Lines changed: 29 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -73,8 +73,32 @@ together with a mapping table showing the relationships between channels and inp
7373
****
7474
endif::arc42help[]
7575

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.
94+
95+
[cols="1,2,2", options="header"]
96+
|===
97+
|Channel |Input |Output
98+
|**HTTPS (Browser → WebApp)** |User moves, bot strategy selection, login registration info. |Board updates, results, statistics.
99+
|**HTTP JSON/YEN (WebApp → Rust)** |Board state (YEN), active player, strategy. |Match outcome, bot move.
100+
|**Firebase SDK (WebApp ↔ Firebase)** |User registration, results, statistics. |Data persistence and retrieval.
101+
|**HTTPS (API → Bot)** |Board state (YEN), strategy parameters. |Bot move response.
102+
|===
103+
104+
image::Technical_Context_Sequence_diagram.png[Diagrama de Secuencia, width=600, align="center"]

0 commit comments

Comments
 (0)