System models
Context Diagram:
This diagram shows the system boundaries and external interactions.
- External systems
- Frontend (requests and displays data)
- MQTT Broker (receives sensor data)
- TempSensorMock (simulated sensor)
- Database (stores and retrieves data)
Use Case Diagram
Login/Logout: Users can authenticate, gaining the appropriate access level. Issues: #9, #57, #58, #59, #60
Quest View: Users can access a basic view without authentication. Issues: #56
Add Cards: Users can add cards to their interface. Issues: #68, #44, #45, #46, #47, #48, #49, #50, #23, #24, #25, #26, #27, #28
Edit Cards: Users can edit active cards (size, color, background).
Remove Cards: Users can remove active cards.
Change Style: Edit the page style (light/dark mode, text style/color, background). Issues: #61, #62, #63, #64, #31, #32, #33, #34, #17, #18
Change User Interface: Users can create interfaces using pre-made card layouts.
Issues: #65, #66
Original issue: #87, subject to change
Sequence Diagram for Temp Sensor
The sequence diagram shows how temperature data moves through the system from sensor to frontend. ReadTempSensorMockup first gets the temperature data from TempSensorMockup via HTTP. The data is then published as JSON through MQTT (Mosquitto) to middleware. The middleware receives the data and stores it in PostgreSQL database. When frontend requests data, the request is sent to TempService. TempService gets the latest temperature data from the database and sends the response back to frontend.