Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sections 3.2 and 10 enhanced #68

Merged
merged 3 commits into from
Feb 29, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
13 changes: 8 additions & 5 deletions docs/src/03_system_scope_and_context.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -76,20 +76,23 @@ together with a mapping table showing the relationships between channels and inp

****

**<Diagram or Table>**
.Table of the Technical Context
[cols="2,2"]
|===
| **Component** | **Technologies Used**
| Front-end | HTML, CSS, JavaScript (Svelte/React)
| Back-end | .NET/node.js, API de Wikidata
| Front-end | HTML, CSS (Tailwind), JavaScript (React)
| Back-end | .NET/node.js, Wikidata's API
| Database | MongoDB
| Arquitechture | Microservices
| Deployment and Maintenance | Docker
|===

**<optionally: Explanation of technical interfaces>**

**<Mapping Input/Output to Channels>**
.Diagram of the Technical Context
image::3_2-Technical-Context-Diagram-EN.png["Technical Context"]


.Mapping Input/Output to Channels
[cols="2,2"]
|===
| **Component** | **Functionality**
Expand Down
14 changes: 7 additions & 7 deletions docs/src/10_quality_requirements.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -87,24 +87,24 @@ Tabular or free form text.

| *Performance*
| The application must have a reasonable response time. Slow applications are not positively popular in society.
| The application must be able to give a fast response time to the users so the game is dynamic and entertaining.
| The application must be able to give a response time of at least 5 seconds with 10 concurrent users.
| Very high

| *Security*
| Our web must be secure not only to protect data but to provide a realiable solution to our users. If we can't assure our clients the web is secure, no one will use it.
| Data will be only accessible by its owner. If a user tries to access other people's information, the system will deny the operation, as data will be stored in a secure system.
| Very high

| *Portability*
| To reach the maximum number of users the application must work in the maximum number of infrastructures.
| When users access the web from different browsers and devices, it must work and provide all the possible functionalities.
| Very high

| *Usability*
| To make the website stand out from the competition, it must be easy to use, attract attention and be aestethic.
| When the user wants to do something in the application, he/she should be able to do it without difficulty, guided by the interface elements.
| The user must be able to do identify the game elements shown in the screen as well as the menu for the different functionalities as the view profile or the logout ones.
| Very high

| *Portability*
| To reach the maximum number of users the application must work in the maximum number of infrastructures.
| The game experience and functionalities must be the same independently from the device which the user is connecting from.
| High

| *Testability*
| All features of the application must be testable in order to verify that the web built was the one asked for.
| The unit tests passed by the developers must generate an observable output.
Expand Down