...
When a crewmember opens the a tab, the front-end does a call to the back-end. 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 SensorWithGraphDAO is the information expert of them.
SD 2 Select sensor
We decided that making a sequence diagram is not needed for this user action to the system. The crewmember will click on the desired sensor to view a graph from. After the user clicks on the sensor, it wil instantly show the types of graph linked to the sensor. This is something that happens on the front-end, thats why we decided its unnecessary.
SD 3 Select graph
The crewmember interacts with the front-end by clicking on the desired graph type. This will call a method to create the graph on the sidebar component. This is because the sidebar component is the controller. The sidebar component will interact with GlobalComponent because he is the information expert. GlobalComponent knows everything about graph.
Design decision
Decision | Description |
|---|---|
Problem/Issue | There is no graph linked to a sensor. |
| Decision | There will no be no available graphs to add to a tab. |
| Alternatives | Give every sensor a normal table (for example), so there is always a graph available. |
| Arguments | Not every sensor is has good enough data for a normal table. |
SD 3 Select 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.
...