diff options
| -rw-r--r-- | docs/Sprint3_FAT.md | 20 | ||||
| -rw-r--r-- | docs/design.md | 4 |
2 files changed, 22 insertions, 2 deletions
diff --git a/docs/Sprint3_FAT.md b/docs/Sprint3_FAT.md new file mode 100644 index 0000000..e7f6ab5 --- /dev/null +++ b/docs/Sprint3_FAT.md @@ -0,0 +1,20 @@ +## Functional requirements +1. [] The network has atleast three nodes in a network +2. [] A node in a network has one button and one led +9. [] Nodes are in a bluetooth mesh network +10. [] Client is connected to the mesh network and internet +13. [] Nodes contain one sensor element and one actuator element +14. [] Nodes send and receive bluetooth messages + +## Technical requirements +3. [] Nodes can control multiple LEDs +4. [] Client application can control atleast 1 button and LED +5. [] The simulated node can interect and be interacted with physical nodes +6. [] Nodes can dynamically be registered during runtime +7. [] Nodes can be provisioned by the border router + +11. [] Client can monitor and control mesh network +12. [] Nodes (inputs/outputs) can be bound to eachother +15. [] Nodes can signed out/in via client +21. [] Client can connect to other nodes + diff --git a/docs/design.md b/docs/design.md index 5d231fc..199aa0c 100644 --- a/docs/design.md +++ b/docs/design.md @@ -97,11 +97,11 @@ Every node has a total of three elements which consist of one button and two lig ## Provisioning -The provisioner uses the PB-ADV instead of the PB-GATT provisioning protocol. This might change in the future depending on the beacon information and if there is enough time to switch from PB-ADV to PB-GATT. +The provisioner uses the PB-ADV instead of the PB-GATT provisioning protocol. This is because the PB-ADV is the standard protocol. Also, the PB-GATT provisioning method cost to much time to make it work. ## Semaphore -For now, there are two semaphores created in the provisioner software. The first one is created for an unprovisioned beacon signal from the provisionee. Also, the second semaphore is used for adding a node to the network. All these semaphores are to make sure there is only one signal at a time. +There are two semaphores created in the provisioner software. The first one is created for an unprovisioned beacon signal from the provisionee. Also, the second semaphore is used for adding a node to the network. All these semaphores are to make sure there is only one signal at a time for processing on the background. # Used software and library versions |