...
Code | Description |
|---|---|
| NFR1 | Responses to all user-initiated actions in the web-interface need to must be be rendered in less than 1 second. |
| NFR2 | The data Data from the racecar needs to be processed is sent towards the web-application twenty times per second. The application should thus update the data it is displaying twenty times a second. |
| NFR3 | The application maintains requires a connection to the internet Internet at all times, as it will need connection to the Internet to retrieve all of its data. |
Security
Code | Description |
|---|---|
| NFR4 | The application is must be protected against SQL injection-injectionsand other safety hazards to ensure no user can hack themselves into the race's data and alter said data. |
| NFR5 | Passwords should must be hashed before being stored in a databasethey are stored into the database to ensure no user account can be hacked by an outsider. |
Usability
Code | Description |
|---|---|
| NFR6 |
| All code written by smalltalk should contain |
| ample commentary to provide later groups that will work on the same product a sound foundation to continue working with. |
Reliability
| Code | Description |
|---|---|
| NFR7 | The data should be accurate to about x percentAll data sent by the racecar must be accurate to the last decimal stored in the database or received from the racecar. This way, the analysing racecrew can work with actual accurate data instead of rounded numbers. |
| NFR8 | There should be no bad smells present in the code. |
...