subir la docu

docs/src/04_solution_strategy.adoc

@@ -6,15 +6,17 @@
 
 The following technologies are used in the development of our application:
 
-* *_React_*: We chose React as our JavaScript library for building user interfaces due to its efficiency, flexibility, and the ability to create reusable UI components. React is also a popular framework that we had not previously worked with and were interested in learning. This choice aligns with our goal of maintaining a consistent and efficient codebase while expanding our technical skills.
-* *_JavaScript_*: JavaScript was chosen as the language for application development due to its versatility, wide support across various platforms, and its status as the standard language for web development. Additionally, using JavaScript both on the client and server sides allows for a more streamlined and efficient development process.
-* *_MongoDB_*: MongoDB was selected as our database due to its scalability and flexibility in handling data. This non-relational database aligns with our needs for a fluid and intuitive data handling process. While MySQL, a relational database, offers structured query language and consistency, we opted for MongoDB because it provides more flexibility in terms of data storage and retrieval, which is more suitable for our application's needs.
+* *_React_*: We chose React as our JavaScript library for building user interfaces due to its efficiency, flexibility, and the ability to create reusable UI components. React is also a popular framework that we had not previously worked with and were interested in learning. This choice aligns with our goal of maintaining a consistent and efficient codebase while expanding our technical skills. Link to the architectural decision * https://github.com/Arquisoft/wiq_es05c/wiki/Architecture-Decision-1[Architecture Decision 1-Language Selection for documentation]
+* *_JavaScript_*: JavaScript was chosen as the language for application development due to its versatility, wide support across various platforms, and its status as the standard language for web development. Additionally, using JavaScript both on the client and server sides allows for a more streamlined and efficient development process. Link to the architectural decision * https://github.com/Arquisoft/wiq_es05c/wiki/Architecture-Decision-1[Architecture Decision 1-Language Selection for documentation]
+* *_MongoDB_*: MongoDB was selected as our database due to its scalability and flexibility in handling data. This non-relational database aligns with our needs for a fluid and intuitive data handling process. While MySQL, a relational database, offers structured query language and consistency, we opted for MongoDB because it provides more flexibility in terms of data storage and retrieval, which is more suitable for our application's needs. Link to the architectural decision * https://github.com/Arquisoft/wiq_es05c/wiki/Architecture-Decision-3[Architecture Decision 3-Database Platform]
 === Top-level Decomposition
 ==== IDE
 We have chosen Visual Studio Code as our platform since we have experience with it and it is the platform we will work best with.
 
 ==== Diagram design tools
 We will use PlantUML as the tool for creating diagrams since it is the recommended one for the course.
+We use PowerPoint for the business context diagrams.
+We use Draw.io for the building block view diagrams.
 
 === Key Quality Goals
 
@@ -27,7 +29,8 @@ We will use PlantUML as the tool for creating diagrams since it is the recommend
 * *_Adaptability_*: The application should be adaptable to different devices, including desktops, tablets, and mobile phones. This ensures that the game can reach a wider audience and provide a good user experience regardless of the device used.
 
 === Organizational decisions
+
 Here are the organization decisions made:
+
 * *_Language_*: We will use English as the primary language for both documentation and code.
-* *_GitHub issues_*: We will use GitHub issues as the main source for problem resolution, so that whenever something poses an obstacle, it will be documented in GitHub issues.
-* *_GitHub projects_*: GitHub projects allow us to organize work based on issues in a Kanban-style, enabling us to see issues that are in progress, those that are not, and those that are completed.
+* *_GitHub issues_*: We will use GitHub issues as the main source for problem resolution, so that whenever something poses an obstacle, it will be documented in GitHub issues.