Merge pull request #35 from Arquisoft/pablo

cambios documentacion apartados 1, 4, 8, 10

docs/src/01_introduction_and_goals.adoc

@@ -30,7 +30,7 @@ It consists of an application in which users can register and enter to play the
 [options="header",cols="1,2"]
 |===
 |Goals|Details
-| _Privacity_ | _The data of registered users will be saved, ensuring their security_ 
+| _Performance_ | _We are going to need the application to have a good performance since we are going to make several calls and we need that these calls do not take too much time for the system to be efficient and dynamic during its use_ 
 | _Usability_ | _The use of the application must be an intuitive and simple process for the client user_
 | _Maintainability_ | _We will try to take care of the architecture of the application so that functionality can be added, modified or removed with as few changes as possible_
 | _Testeability_| _Our application may also be testable, that is, it will be subjected to a series of unit tests that we will perform to ensure proper operation of the system, in addition to identifying small errors and being able to correct them in such a case_

docs/src/04_solution_strategy.adoc

@@ -20,13 +20,13 @@ ifndef::imagesdir[:imagesdir: ../images]
 
 === Decisions on how to achieve key quality goals
 
-* Usability: the team will take care to design a clear and accessible interface for any user. This will be based on web usability standards.
+* Usability: The team will take care to design a clear and accessible interface for any user. This will be based on web usability standards.
 
-* Privacy: users' private information will be stored in such a way that it will not be accessible to external factors.
+* Performance: Minimize delays in data processing, communication, or task execution to improve overall system responsiveness. As well, optimize system components, algorithms, and configurations.
 
-* Security: we will take care to implement all the measures we deem appropriate to secure our application.
+* Maintainbility: The architecture of the application must allow new functionalities to be added or existing ones to be modified with as few changes as possible.
 
-* Testability: this is an important quality objective to ensure that the software is reliable, robust and error-free. It is important to implement appropriate software development practices, such as separation of concerns and modular design.
+* Testability: This is an important quality objective to ensure that the software is reliable, robust and error-free. It is important to implement appropriate software development practices, such as separation of concerns and modular design.
 
 === Relevant Organizational Decisions
 

docs/src/08_concepts.adoc

@@ -9,10 +9,10 @@ ifndef::imagesdir[:imagesdir: ../images]
 * Hacer el diagrama del dominio
 
 
-=== Privacity
-Security is a very important concept in the context of a system. Since we manage user information, it is important to ensure that the information is secure and that the system is not compromised.
+=== 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.
 
-In addition, we add back-end security to prevent unauthorized requests to the RestAPI, as well as to prevent the execution of malicious code.
+We are going to look for a good performance with the code optimization, wihout 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.

docs/src/10_quality_requirements.adoc

@@ -10,11 +10,23 @@ image::10_1_Quality_Tree.png[Business Context Diagram]
 
 === Quality Scenarios
 
-[options="header",cols="1,3"]
+[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._ | _High_
-| _Usability_ | _We want to offer the user the possibility to see his personal statistics, as well as a service of access to information and data storage, in an intuitive and efficient system for customers (as fast as possible)._ | _High_
-| _Maintainability_ | _The design and architecture will allow for flexibility in the face of unexpected events during development, this feature is important because we want to reduce costs in terms of time._ | _Medium_
-| _Testeability_| _The application will be subjected to unit, acceptance and load testing to prove that it works correctly. If new functionality is added to the map, it must be thoroughly tested before deployment._ | _High_
+| 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. 
+| High
+
+| *_Usability_* 
+| We want to offer the user the possibility to see his personal statistics, as well as a service of access to information and data storage, in an intuitive and efficient system for customers (as fast as possible). 
+| High
+
+| *_Maintainability_* 
+| The design and architecture will allow for flexibility in the face of unexpected events during development, this feature is important because we want to reduce costs in terms of time. 
+| Medium
+
+| *_Testeability_* 
+| The application will be subjected to unit, acceptance and load testing to prove that it works correctly. If new functionality is added to the map, it must be thoroughly tested before deployment.
+| High
 |===