Non-functional Requirements

Performance Efficiency

Code	Description
NFR1	Responses to all user-initiated actions in the web-interface must be be rendered in less than 1 second.
NFR2	Data from the racecar is sent towards the web-application twenty times per second. The application should thus update the data it is displaying twenty times a second.

Code	Description
NFR4	The application must be protected against SQL-injection sand other safety hazards to ensure no user can hack themselves into the race's data and alter said data.
NFR5	Passwords must be hashed before they are stored into the database to ensure no user account can be hacked by an outsider.

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.

Code	Description
NFR7	All 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 must be no code smells such as feature envy, shotgun surgery and tradition breaker present in the code. This is to ensure the expandability of our application in the future.

Code	Description
NFR9	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, no matter their origin.
NFR10	The main color used for documetation should be #148484(). The secondary, complementary color to use in addition to the main color should be #81c8bd().
NFR11	Data is stored in plain text.

Code	Description
NFR12	All systems made by smalltalk should be sound and solid, so future groups can work with our code without having to rewire all of our code.
NFR13	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 annoying bugs or errors.