requirementspecification.md

@@ -119,12 +119,32 @@ Here you can familiarize yourself with stories and paths.
 
 ## Functional Requirements
 
-| Id | Description | Category | Assigned to |  
-|:-:|:-:|:-:|:-:|
-| [#FR001]() ||||
-
-## Non-functional Requirements
+| Id | Description | Category |
+|:-|:-|:-|
+| [#FR001]() | RuuviTag should be reusable by releasing the bluetooth id from server database manually | Sensor / IoT |
+| [#FR002]() | Front-end backend should be able to easily switch between multiple RuuviTag links mode to single RuuviTag link mode by enabling a boolean value inside the python script| Front-end backend |
+| [#FR003]() | Patient can change character in the character selection screen when nearby by shaking the RuuviTag | Sensor / Front-end |
+| [#FR004]() | RuuviTag should be quarantine proof (Easily sterilaziable) | Sensor / IoT |
+| [#FR005]() | In fishing game module, the child pulls the fish out of the water by shaking the RuuviTag | Front-end |
+| [#FR006]() | Front-end should display the appropriate virtual friend based on the MacID OR Bluetooth ID stored in the database | Database |
+| [#FR007]() | In impossible game like module the kid makes the virtual friend jump by shaking RuuviTag | Front-end |
+| [#FR008]() | RuuviTag should be durable enough to not loose tiny parts, that could get lodged in childs throat | Security |
+| [#FR009]() | Virtual friend characters should not be scary and they should be adorable for children | Front-end |
+| [#FR010]() | Virtual friend characters should be modifiable to match the childs personality | Front-end |
+
+## Non-Functional Requirements
 
+| Id | Description | Category |
+|:-|:-|:-|
+| [#NR001]() | front-end backend should wait for a second or two once new RuuviTag has been found, incase bluetooth signal strenth spikes because of device activation | Sensor / IoT |
+| [#NR002]() | Front-end should be able to run in Raspberry pi 3 | Front-end | 
+| [#NR003]() | Front-end should release the RuuviTag once the signal reaches minimum aggreed signal stregth | Front-end |
+| [#NR004]() | Front-end should not switch RuuviTag once the terminal has been activated and not deactivated properly | Front-end | 
+| [#NR006]() | RuuviTag battery should last more than 3 days | Sensor / IoT |
+| [#NR007]() | Front-end backend should calculate the RuuviTag distance, as accurate as 1 meter. | Sensor / IoT |
+| [#NR008]() | Every component of the whole system, should communicate with system backend with gRPC for maximum compatibility | Backend |
+| [#NR009]() | RuuviTag should use bluetooth ID or MacID as a unique identifier in database as a key | Database |
+| [#NR010]() | The system should not be accessible by outside and the whole environment should be closed. | Security |
 ### Usability
 
 | Id | Description | Category | Assigned to |