Context Model for the system #83

Closed
opened 2026-04-01 12:27:49 +00:00 by a24vinla · 6 comments
Collaborator

This will most likely be an ongoing issue as the system and our knowledge of it expands. It would however be beneficial to have a shared understanding which we can build on.

Parent Issue: #6

This will most likely be an ongoing issue as the system and our knowledge of it expands. It would however be beneficial to have a shared understanding which we can build on. Parent Issue: https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/6
b25marem added spent time 2026-04-02 12:57:26 +00:00
5 hours 30 minutes
b25marem deleted spent time 2026-04-02 12:59:46 +00:00
- 5 hours 30 minutes
Collaborator
No description provided.
Collaborator

Context diagram illustrates how the system interacts with external entities sensor, helping to define system boundaries and simplify complex processes. It designs to depict the interactions between a system and its external environment.

Central System: The main function or process of the system being developed, typically represented as a circle in the center of the diagram.
External Entities: Sensor interact with the central system.
Data Flow: Arrows indicate the flow of information between the system and external entities, often labeled to describe the type of data exchanged.

Context diagram illustrates how the system interacts with external entities sensor, helping to define system boundaries and simplify complex processes. It designs to depict the interactions between a system and its external environment. Central System: The main function or process of the system being developed, typically represented as a circle in the center of the diagram. External Entities: Sensor interact with the central system. Data Flow: Arrows indicate the flow of information between the system and external entities, often labeled to describe the type of data exchanged.
Collaborator

Overall, I think the diagram gives a good overview of the system. My main issue is that it is somewhat ambiguous regarding the databases. At the moment, the system uses two different database systems (SQLite and Postgres) and I think it should be a bit more explicit what database eg. the service API fetches data from.
Also it says TempSensorMacup in the bottom left.
Other than that I thought it was really good.

Overall, I think the diagram gives a good overview of the system. My main issue is that it is somewhat ambiguous regarding the databases. At the moment, the system uses two different database systems (SQLite and Postgres) and I think it should be a bit more explicit what database eg. the service API fetches data from. Also it says TempSensorMacup in the bottom left. Other than that I thought it was really good.
Collaborator

image

![image](/attachments/1841ff42-fd36-47a1-9bad-126817b131b7)
256 KiB
Collaborator

I simplified the context diagram by focusing only on external entities and correcting the data flow. I ensured that sensor data flows through the MQTT broker and added a return flow from the database to the system.

The diagram represents how the system interacts with external components and provides a high-level overview of data flow between the sensor, MQTT broker, database, and frontend

I simplified the context diagram by focusing only on external entities and correcting the data flow. I ensured that sensor data flows through the MQTT broker and added a return flow from the database to the system. The diagram represents how the system interacts with external components and provides a high-level overview of data flow between the sensor, MQTT broker, database, and frontend
Collaborator

I think this context diagram gives a clear picture of what type of communication (sending/retrieving data) the application has with what components. I would not change anything and in my opinion this issue can be closed.

I think this context diagram gives a clear picture of what type of communication (sending/retrieving data) the application has with what components. I would not change anything and in my opinion this issue can be closed.
Sign in to join this conversation.
No milestone
No project
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#83
No description provided.