From 14c9a4b78f7490efa5e9c2e1a3f4b891b2b45a6a Mon Sep 17 00:00:00 2001 From: AdrianSantamarina Date: Wed, 14 Feb 2024 17:38:09 +0100 Subject: [PATCH] =?UTF-8?q?Parte=204=20de=20la=20documentaci=C3=B3n,=20fal?= =?UTF-8?q?ta=20por=20completar=20con=20decisiones=20aun=20no=20tomadas?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/src/04_solution_strategy.adoc | 39 ++++++++++++------------------ package-lock.json | 6 +++++ 2 files changed, 21 insertions(+), 24 deletions(-) create mode 100644 package-lock.json diff --git a/docs/src/04_solution_strategy.adoc b/docs/src/04_solution_strategy.adoc index 7bf03f7a..af77cfc7 100644 --- a/docs/src/04_solution_strategy.adoc +++ b/docs/src/04_solution_strategy.adoc @@ -1,32 +1,23 @@ -ifndef::imagesdir[:imagesdir: ../images] - [[section-solution-strategy]] == Solution Strategy +=== Technology Decisions +The following technologies are used in the development of our application: +* *React*: JavaScript library for building efficient user interfaces. +* *JavaScript*: Chosen language for application development. +* *GitHub*: Platform that allows us to have a repository where to develop the project and perform different actions such as creating issues or tasks. +* *MongoDB*: Non-relational database we will use for the project. +* *Docker*: Virtualization platform where we will deploy the project. +* *Wikidata*: Wikidata is a knowledge base that provides data sources, used to obtain information for the game. In this case, it is mandatory. -[role="arc42help"] -**** -.Contents -A short summary and explanation of the fundamental decisions and solution strategies, that shape system architecture. It includes - -* technology decisions -* decisions about the top-level decomposition of the system, e.g. usage of an architectural pattern or design pattern -* decisions on how to achieve key quality goals -* relevant organizational decisions, e.g. selecting a development process or delegating certain tasks to third parties. - -.Motivation -These decisions form the cornerstones for your architecture. They are the foundation for many other detailed decisions or implementation rules. - -.Form -Keep the explanations of such key decisions short. - -Motivate what was decided and why it was decided that way, -based upon problem statement, quality goals and key constraints. -Refer to details in the following sections. +=== Top-level Decomposition -.Further Information +=== Key quality goals -See https://docs.arc42.org/section-4/[Solution Strategy] in the arc42 documentation. -**** +=== 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. \ No newline at end of file diff --git a/package-lock.json b/package-lock.json new file mode 100644 index 00000000..5e65dbe1 --- /dev/null +++ b/package-lock.json @@ -0,0 +1,6 @@ +{ + "name": "wiq_es05c", + "lockfileVersion": 2, + "requires": true, + "packages": {} +}