Update infrastructure documentation with functional, technical, and UML diagrams
This commit is contained in:
@@ -8,12 +8,16 @@
|
||||
|
||||
### functional
|
||||
|
||||
In the top layer of the infrastructure documentation, we are showing the functional flows of the information trafic between the user and the sensor/enquete that are located in the same room. The traffic consists of enviromental sensor values like temperature, humidity etc. Also it is showing the user input at the enquete device to the database that is hosted at the brain of the operation.
|
||||
|
||||
[functional Infra](../assets/funcionalInfra.png)
|
||||
|
||||
### Technical
|
||||
|
||||
In the middel layer we are showing the data flow and processing of the data at component level. It consists of 2 area's with 3 parts, namelie the server room and the building as in the common area. Here we send the data in JSON form that is collected at the enquete node (this is the feedback data) and the sensor node (this is the environmental data). This is sent to the database through the websocket that is running on the raspberry pi and than via a rest api sent to the database. If one of the operational manager would log in to the website. They would see the incomming sensor node data that is comming through, but also the data that is already collected and stored in the database.
|
||||
|
||||
[technical Infra](../assets/technicalInfra.png)
|
||||
|
||||
### UML diagram of software
|
||||
|
||||
At the lowest level of our system we are showing how the software is designed. This is shown as a UML diagram. The diagram is made with mermaid. This shows the work flow of the different parts of the software which is running on the main server, for which we are using a Raspberry pi. The pi is located on the 6th floor of the school building in a locked server room.
|
||||
|
Reference in New Issue
Block a user