...
Code | Description |
|---|---|
| NFR1 | Responses to all user-initiated actions in the web-interface must be be rendered on our systems in less than 3 seconds. |
Security
Code | Description |
|---|---|
| NFR4NFR2 | The application must be protected against SQL-injections and other safety hazards to ensure no user can hack themselves into the race's data and alter said data. |
| NFR5NFR3 | Passwords must be hashed before they are stored into the database to prevent no user account can be hacked by an outsider. |
Reliability
| Code | Description |
|---|---|
| NFR7NFR4 | All data sent by the racecar must be accurate to the last decimal stored in the database or received from the broker. This way, the analyzing racecrew can work with actual accurate data instead of rounded numbers. |
| NFR8NFR5 | There must be no code smells such as feature envy, shotgun surgery and tradition breaker present in the code. This is to ensure the reliability of our application in the future. |
Documentation
| Code | Description |
|---|---|
| NFR9NFR6 | All documentation has to be made in English to allow other groups that will continue our work after us to understand why we made certain choises. |
| NFR10NFR7 | The main color used for the web-application should be #148484( |
Supportability
| Code | Description |
|---|---|
| NFR12NFR8 | All systems made by smalltalk should have an A rating on sonarqube reliability, security and maintainability, so future groups can work with our code without having to rewrite all of our code. |
| NFR13NFR9 | Our code should be tested thoroughly, with at least 80% of the lines being tested by unit-tests. This way we know our code is working and does not contain any bugs or errors. |