Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 04_solution_strategy.adoc #47

Merged
merged 1 commit into from
Feb 19, 2024
+7 −7
Merged

Update 04_solution_strategy.adoc #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions docs/src/04_solution_strategy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
ifndef::imagesdir[:imagesdir: ../images]

[[section-solution-strategy]]
= Solution Strategy
== Solution Strategy

[role="arc42help"]
== Contents
=== Contents
This page contains a short summary and explanation of the fundamental decisions and solution strategies, that shape system architecture.

---

=== Technology Decisions
==== Technology Decisions
Below, all the technologies to be used in the development of the application are listed:

* *JavaScript / React:* A JavaScript library designed to facilitate the development of web applications.
Expand All @@ -20,7 +20,7 @@ Below, all the technologies to be used in the development of the application are

---

=== Top-Level Decisions
==== Top-Level Decisions
In this section, a summarized list of all decisions regarding the architecture of the application is included.

|===
Expand All @@ -36,7 +36,7 @@ In this section, a summarized list of all decisions regarding the architecture o

---

=== Quality Goals
==== Quality Goals
Next, several quality goals are established, along with the decisions made to achieve them.

|===
Expand All @@ -58,7 +58,7 @@ Next, several quality goals are established, along with the decisions made to ac

---

=== Relevant Organizational
==== Relevant Organizational
Regarding the organization of the team, we have decided to use agile methodologies for better and faster group work. In this project, we will follow the best practices of the SCRUM framework.

Practices to be followed:
Expand All @@ -72,7 +72,7 @@ Additionally, "Issues" and the GitHub-provided Kanban (ToDo - In Progress - Done

---

=== Motivation
==== Motivation
This section addresses the fundamental decisions for the project's architecture.

|===
Expand Down