...
The crewmember deletes a graph on the webpage. the front-end does a call to the back-end. The resource is only responsible for returning the response so it gets delegated to GraphService. The GraphService delegates this to the GraphDAO because deleting the data from the database is not the responsibility of the service. In the GraphDAO the graph gets deleted from the database. The benefit of this structure is that you can easily swap the classes which results in low cohesion and high coupling. This structure is based of the the layer pattern.
Decision | Description |
|---|---|
Problem/Issue | graph and tab ID are not the same in the front and backend |
| Decision | We use the ID from the front-end to get the right ID for the backend |
| Alternatives | Use the ID from the database in the front-end |
| Arguments | Making them the same would break a lot of functionalities. We didn't have enough time so this was our only option to keep the functionalities. |
Sequence diagram addGraph
...