generated from Arquisoft/viade_0
-
Notifications
You must be signed in to change notification settings - Fork 4
MM_20 02 2020
Daniel Finca edited this page Mar 5, 2020
·
1 revision
- Diego Ramírez Amandi
- Óscar Sánchez Campo
- Jesús Quesada Matilla
- Pablo Fernández Martínez
- Nicolás Mencía Gómez
- Daniel Finca Martínez
Presented the first draft of the documentation (release created v0.1)
-
- Remove '?' help
- Typo on "The system will be based on a decentralized architecture where data is stored inside the pod of each user."
- Code finesse or similar explanation for the quality of the application
- Stakedholders' end users must be defined deeper, as they may include people who go on routes and whant to save them or people who just want to check from their homes routes they may do.
-
- Move react native to point 4 (it is not 100% a constraint, but something we will use to complete the project [similarly to node.js, docker, browser agnostic, smartphone access, ESLint...])
- Take a look to every single constraint written in technical constraints to separate the actual constraints imposed for the system by (in this case) the teachers and the ones we have included to propose a solution to the problem.
-
- First diagram too simple, diagrams in general are too simple. Good but not enough.
- Diagrams should be checked, user pods missing. Interaction in between user's pods, etc.
-
- We don't need to write too much in the first part.
-
- Point 7 is a little vague (describe colour pattern used in diagram)