Non-functional Requirements

Performance Efficiency

Code	Description
NFR1	Responses to all user-initiated actions in the web-interface must be be rendered on our systems 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.
NFR3	The application requires a connection to the Internet at all times, as it will need connection to the Internet to retrieve all of its data.
3 seconds.

Code	Description
NFR4NFR2	The application must be protected against SQL-injectionsand 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 ensure prevent 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
NFR7NFR4	All data sent by the racecar race car must be accurate to the last decimal stored in the database or received from the racecarbroker. This way, the analysing racecrew race crew can work with actual accurate data instead of rounded numbers.
NFR8NFR5	There should must be no bad smells 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.

Code	Description
NFR9NFR6	All documentation has to must be written made in English to allow other groups that will continue our work after us to understand why we made certain choices.
NFR10NFR7	#148484 is the The main color and the secondary color is #81c8bd.
NFR11	Data is stored in plain text.
used for the web-application should be #148484(Image Added). The secondary, complementary color to use in addition to the main color should be #81c8bd(Image Added).

Code	Description
NFR12NFR8	All systems made systems should be expandableby smalltalk should have an A rating on SonarQube reliability, security and maintainability, so future work or expansion of current features is easy to implement. groups can work with our code without having to rewrite all of our code.
NFR9	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	NFR13	All unit test must be a success with an 80% line coverage.