Sequence Diagram for Temp Sensor #90
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent Issue #89
Will be adding a description on Tuesday
I added the entry point to the diagram since frontend requests go through it before tempService
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, it sends it via the entryPoint, which forwards it to tempService. TempService gets the latest temperature data from the database and sends the response back through entryPoint to frontend.
Reviewed both versions of the diagram, and I think the first version without the 'entrypoint' would be the best one to use as the 'entrypoint' part from the second version isn't reflected much in the code.
This can be added to the wiki now.
Oki I'll fix it