...
Decision | Description |
|---|---|
Problem/Issue | The name of the racecar is not stored in the database because this is not necessary at the moment |
| Decision | In the constructor of RaceDTO the car get's the value "BMW 320 4fl E46" assigned |
| Alternatives | Store it in the database, leave it empty |
| Arguments | The BMW is the only car they intend to use in the near future so it's not necessary to make a new table for racecar. |
Place Graph
When a crewmember opens the a tab, the front-end does a call to the backend. It calls a method to SensorWithGraphRecource. This is the controller of the SensorWithGraphDAO that gets the data which is needed for displaying graphs on the front-end. The SensorWithGraphDAO creates two DTO's. This is because he is the information expert of them.
Design decision
Decision | Description |
|---|---|
Problem/Issue | There is no graph linked with a sensor. |
| Decision | There will no be no available graphs to add on the graph. |
| Alternatives | Give every sensor a line graph (for example), so there is always a graph available. |
| Arguments | Not every sensor is able to give a functional line graph. |
Database Design
This is the database setup we will use for the RegterschotRacing API. A full description of every tables usage and datatypes can be found below.
...