Skip to content

Commit

Permalink
Update doc 11
Browse files Browse the repository at this point in the history
  • Loading branch information
Pelayori committed Apr 28, 2024
1 parent 3206f42 commit 0afa4f0
Showing 1 changed file with 9 additions and 3 deletions.
12 changes: 9 additions & 3 deletions docs/src/11_technical_risks.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,21 @@ ifndef::imagesdir[:imagesdir: ../images]
|===
| Priority | Risk | Description

| High | Migration to Java | Migration from the current project language, JavaScript (JS), to Java
| High | Architecture in Spring Boot | The architecture of the project will be based on Spring Boot, which is a framework that we are not that familiar with, or not at all for some members. This could lead to a delay in the development of the project.
| Medium | Wikidata | The project will use Wikidata as a source of data. We have never used Wikidata before, so we will have to learn how to use it.
| Medium | IDE Configuration | Version compatibility, extensions and other preferences to work perfectly without conflicts
| Medium | Database | Discuss which database is best for the project
| Low | Docker | Know how docker works, what it is for, how it is used and what its alternatives could be.
| Medium | Docker | Know how docker works, what it is for, how it is used and what its alternatives could be.
| Low | Database | The database decision will not be taken based on what technology we know better, but on what is best for the project. Usage of JPA, Hibernate allows us to focus on the business logic and not on the database.


|===

[cols="1,2,3a", options="header"]
|===
| Priority | Debt | Description

| Medium | Documentation | The documentation of the project will be done in parallel with the development of the project. This could lead to a delay in the development of the project.
| Medium | Testing | The project will have unit and integration tests, we ensure tests cover the majority of the code. However due to time constraints and how the project is structured, we may not be able to cover all the code with all the possible cases. The aim is to cover at least 80% of the code.
| Low | Code Quality | The code quality will be ensured by the use of SonarCloud, but due to time constraints, we may not be able to fix all the issues that SonarCloud will find.
| Low | Security | The project will have security measures in place. Standard practices are put in place. Tougher security measures will not be implemented due to performance constraints.
|===

0 comments on commit 0afa4f0

Please sign in to comment.