Merge pull request #43 from Arquisoft/develop

Cambios visualizacion de la documentacion
Arquisoft · Feb 25, 2024 · 1e5c6fe · 1e5c6fe
2 parents aaaf69d + a0edd2d
commit 1e5c6fe
Show file tree

Hide file tree

Showing 7 changed files with 8 additions and 9 deletions.
diff --git a/docs/images/DOCsection5-1.png → docs/images/DOCsection5_1.png b/docs/images/DOCsection5-1.png → docs/images/DOCsection5_1.png
diff --git a/docs/images/DOCsection5-2.png → docs/images/DOCsection5_2.png b/docs/images/DOCsection5-2.png → docs/images/DOCsection5_2.png
diff --git a/docs/images/DOCsection5-3.png → docs/images/DOCsection5_3.png b/docs/images/DOCsection5-3.png → docs/images/DOCsection5_3.png
diff --git a/docs/images/DOCsection8-1.png → docs/images/DOCsection8_1.png b/docs/images/DOCsection8-1.png → docs/images/DOCsection8_1.png
diff --git a/docs/src/05_building_block_view.adoc b/docs/src/05_building_block_view.adoc
@@ -8,7 +8,7 @@ ifndef::imagesdir[:imagesdir: ../images]
 
 === Whitebox Overall System
 
-image::DOCsection5-1.png[Level 1]
+image:DOCsection5_1.png["Level 1"]
 
 .Motivation
 WIQ is the general structure of the system, where the users are going to register in the database, play answering the questions generated with Wikidata or view their previous games among other functionalities. 
@@ -31,7 +31,7 @@ WIQ is the general structure of the system, where the users are going to registe
 
 === Level 2
 
-image::DOCsection5-2.png[Level 2]
+image::DOCsection5_2.png["Level 2"]
 
 .Motivation
 Shows how is the system internally in general terms. 
@@ -57,7 +57,7 @@ Shows how is the system internally in general terms.
 
 === Level 3
 
-image::DOCsection5-3.png[Level 3]
+image:DOCsection5_3.png["Level 3"]
 
 .Motivation
 Detailed structure of the system. Focused on the components of the Webapp, Users API and Questions API.

diff --git a/docs/src/08_concepts.adoc b/docs/src/08_concepts.adoc
@@ -6,12 +6,12 @@ ifndef::imagesdir[:imagesdir: ../images]
 
 === Domain model
 
-image::DOCsection8-1.png[Domain model]
+image:DOCsection8-1.png["Domain model"]
 
 === Performance
 A system that performs well provides a positive user experience. Users expect applications and services to respond promptly to their requests. A higher performance leads to increased user satisfaction and engagement. Also, a good performance help to get a better efficiency.
 
-We are going to look for a good performance with the code optimization, wihout overloading the system and memory and doing some performance test.
+We are going to look for a good performance with the code optimization, without overloading the system and memory and doing some performance test.
 
 === Usability
 Usability is a fundamental aspect of any application, as it determines the ease and efficiency with which users can interact with it. To ensure the usability of our application, we have followed a series of specific practices and techniques.

diff --git a/docs/src/10_quality_requirements.adoc b/docs/src/10_quality_requirements.adoc
@@ -5,17 +5,16 @@ ifndef::imagesdir[:imagesdir: ../images]
 
 === Quality Tree
 
-:imagesdir: ../images
-image::10_1_Quality_Tree.png[Business Context Diagram]
+image:10_1_Quality_Tree.png[Business Context Diagram]
 
 === Quality Scenarios
 
 [options="header",cols="1,3,3"]
 |===
 | Quality Requirements | Scenarios | Priority
 
-| *_Privacity_* 
-| We will respect the privacy of the users, the user's data will be protected at all times. We will ensure the highest possible security, storing the user's sensitive information securely and trying to prevent any kind of attack or risk. 
+| *_Performance_* 
+| We'll run some performance testing and search for a good code optimization performance without taxing the system's resources or memory. Optimize the setups, algorithms, and system parts as well.
 | High
 
 | *_Usability_*