diff --git a/docs/src/01_introduction_and_goals.adoc b/docs/src/01_introduction_and_goals.adoc index 8a8206d..47aa6cf 100644 --- a/docs/src/01_introduction_and_goals.adoc +++ b/docs/src/01_introduction_and_goals.adoc @@ -1,3 +1,4 @@ + ifndef::imagesdir[:imagesdir: ../images] [[section-introduction-and-goals]] @@ -139,6 +140,9 @@ Table with role names, person names, and their expectations with respect to the [options="header",cols="1,2,2"] |=== |Role/Name|Contact|Expectations -| __ | __ | __ -| __ | __ | __ +| *Students* | Andrés Cadenas Blanco, Christian Fernandez Noriega , Adrián González Guadalupe and Luis Salvador Ferrero | Are the ones in charge of web development. They will work together to make the application. +| *Teachers* | Pablo González | In charge of supervising the student's teamwork, ensuring the work accomplishes the goals in the best way possible and helping in the development and solving doubts. +| *Bussineses* | RTve has hired software development company HappySw | Emphasis the SOLID part of the web and have a high understanding of this area +| *Users* | Anyone that wants to use the web | They should be able to understand how to use and move around the web with ease |=== + diff --git a/docs/src/02_architecture_constraints.adoc b/docs/src/02_architecture_constraints.adoc index 226e501..2908f75 100644 --- a/docs/src/02_architecture_constraints.adoc +++ b/docs/src/02_architecture_constraints.adoc @@ -1,27 +1,70 @@ -ifndef::imagesdir[:imagesdir: ../images] - -[[section-architecture-constraints]] -== Architecture Constraints - - -[role="arc42help"] -**** -.Contents -Any requirement that constraints software architects in their freedom of design and implementation decisions or decision about the development process. These constraints sometimes go beyond individual systems and are valid for whole organizations and companies. - -.Motivation -Architects should know exactly where they are free in their design decisions and where they must adhere to constraints. -Constraints must always be dealt with; they may be negotiable, though. - -.Form -Simple tables of constraints with explanations. -If needed you can subdivide them into -technical constraints, organizational and political constraints and -conventions (e.g. programming or versioning guidelines, documentation or naming conventions) - - -.Further Information - -See https://docs.arc42.org/section-2/[Architecture Constraints] in the arc42 documentation. - -**** +ifndef::imagesdir[:imagesdir: ../images] + +[[section-architecture-constraints]] +== Architecture Constraints + + +[role="arc42help"] +**** +.Contents +Any requirement that constraints software architects in their freedom of design and implementation decisions or decision about the development process. These constraints sometimes go beyond individual systems and are valid for whole organizations and companies. + +.Motivation +Architects should know exactly where they are free in their design decisions and where they must adhere to constraints. +Constraints must always be dealt with; they may be negotiable, though. + +.Form +Simple tables of constraints with explanations. +If needed you can subdivide them into +technical constraints, organizational and political constraints and +conventions (e.g. programming or versioning guidelines, documentation or naming conventions) + + +.Further Information + +See https://docs.arc42.org/section-2/[Architecture Constraints] in the arc42 documentation. + +**** + +Architects need a clear understanding of the areas where they have creative freedom in their design choices and where they are bound by constraints. These constraints must be addressed comprehensively, as they are non-negotiable factors within the project. However, it's important to recognize that while constraints are rigid, there may be room for negotiation and adaptation within them. + +|=== +| Constraints | Explanation + +| *Privacy (by SOLID)* +| The web application must be able to save in a secure and persistence way. + +| *GitHub* +| It will be used to coordinate the projects work, tracks changes and manage workflow. + +| *Time* +| The web application will be developed along this course, that means our time is limited and we require an efficient time management. + + +| *Documentation* +| In order to keep it clean, efficient and simple it will follow Arc42 method. + + +| *Time* +| Since the project will be done in this semester our time is limited, and we need to stick to the deadlines and manage our time in an efficient way. + + +| *Code* +| The code requires a small description of what it does. In addition, we must build it in a clean way and that is easy to expand and can adapt to changes in an easy way. + + +| *Test* +| The test has to be correctly tested in order to accomplish the desired behavior. + + +| Node.js +| Open-source, cross-platform JavaScript runtime environment and library for running web applications outside the client’s browser. + +| *Ruby* +| Dynamic, open source programming language with a focus on simplicity and productivity. + +| *JavaScript* +| Programming language that allows you to implement complex features on web page. +|=== + + diff --git a/docs/src/09_architecture_decisions.adoc b/docs/src/09_architecture_decisions.adoc index 51e9aad..9ffe83d 100644 --- a/docs/src/09_architecture_decisions.adoc +++ b/docs/src/09_architecture_decisions.adoc @@ -33,3 +33,35 @@ See https://docs.arc42.org/section-9/[Architecture Decisions] in the arc42 docum There you will find links and examples about ADR. **** +|=== +| Constraints | Explanation +| Title +| Web Server Platform: A Comprehensive Overview +| Context +| Choosing the right web server platform involves balancing technical requirements, stakeholder preferences, user considerations, and project constraints. It's a critical decision that impacts performance, security, user experience, and project success. Achieving alignment across these factors is essential for making an informed choice. +| Decision +| Oracle Cloud +| Status +| Proposed +| Consequences +| We need to suppoort the web application with the leasr cost possible +|=== + + + + + + +|=== +| Constraints | Explanation +| Title +| FrontEnd: What users see +| Context +| Choosing the right web server platform involves balancing technical requirements, stakeholder preferences, user considerations, and project constraints. It's a critical decision that impacts performance, security, user experience, and project success. Achieving alignment across these factors is essential for making an informed choice. +| Decision +| JavaScript and React +| Status +| Proposed +| Consequences +| It is important that the developers are used or can get used to the proposed lenguage with ease so its easier to mantain the code and for future developers to understand it. +|=== diff --git a/package-lock.json b/package-lock.json new file mode 100644 index 0000000..d5acb4a --- /dev/null +++ b/package-lock.json @@ -0,0 +1,6 @@ +{ + "name": "wiq_en1a", + "lockfileVersion": 3, + "requires": true, + "packages": {} +}