From 2b9f88613745131d66ebe5fa42871f979b6ea13f Mon Sep 17 00:00:00 2001 From: UO287568 Date: Mon, 26 Feb 2024 21:31:12 +0100 Subject: [PATCH] =?UTF-8?q?Cambios=20en=20los=20puntos=209=20y=2010=20de?= =?UTF-8?q?=20la=20documentaci=C3=B3n.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/src/09_architecture_decisions.adoc | 4 ++-- docs/src/10_quality_requirements.adoc | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/src/09_architecture_decisions.adoc b/docs/src/09_architecture_decisions.adoc index f21961ac..ee395a22 100644 --- a/docs/src/09_architecture_decisions.adoc +++ b/docs/src/09_architecture_decisions.adoc @@ -36,5 +36,5 @@ There you will find links and examples about ADR. The purpose of this section is to create an ordered list of architectural decisions that we will make as we develop the project. This list will be ordered according to the importance of the decision. -1. *Protection of the master branch*: This decision was made at the beginning of the first team meeting. Without a doubt, this is the most important architectural decision, as it will mean not being able to modify the master branch without all members having previously reviewed the modifications, so that nothing is added that could affect the functioning of the main branch. In addition to this, a develop branch was also created, which will function as a main2.0 branch for adding progress as it is made. To add to this branch also requires the approval of some members of the team. -2. *Switch from JavaScript to Java with Spring*: This is a decision we took on Tuesday 6 February, after the second session. So far this project is one of the most important decisions so far, as it will mean not using the base project and starting another application in another programming language. We have come to this decision because we consider it much more accessible to use the Java language, as it has been taught from the beginning of the course. Moreover, with what we learn in the subject SDI (Distributed Systems and Internet) we can apply it all to web development, using the Spring framework. We have also found a Java library with which we can use Wikidata very easily. It was a unanimous decision that will make it easier for us to work smoothly in the long run. \ No newline at end of file +* https://github.com/Arquisoft/wiq_es04b/wiki/Record-of-architectural-decisions#protection-of-the-master-branch[ADR 01] - Protection of the master branch +* https://github.com/Arquisoft/wiq_es04b/wiki/Record-of-architectural-decisions#switch-from-javascript-to-java-with-springboot[ADR 02] - Switch from JavaScript to Java with Spring \ No newline at end of file diff --git a/docs/src/10_quality_requirements.adoc b/docs/src/10_quality_requirements.adoc index 4b1fd459..837fb423 100644 --- a/docs/src/10_quality_requirements.adoc +++ b/docs/src/10_quality_requirements.adoc @@ -46,7 +46,7 @@ In any case the tree should include links to the scenarios of the following sect **** -_Nota: Los puntos (1), (2), (3) de la siguiente tabla repiten los requisitos de calidad de nivel superior del capítulo 1.2._ +_Note: Items (1), (2), (3) in the table below repeat the higher-level quality requirements of Chapter 1.2._ [cols="4", options="header"] |===