You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Non-functional Requirements

<Describe non-functional requirements in this section. Please refer to existing software quality models like ISO_IEC_IEEE_25010 or FURPS+.>

Performance Efficiency


Code

Description

NFR1Responses to all user-initiated actions in the web-interface need to be rendered in less than 1 second.
NFR2The data from the racecar needs to be processed twenty times per second.
NFR3The application maintains connection to the internet at all times.

Security

Code

Description

NFR4The application is protected against SQL injection.
NFR5Passwords should be hashed before being stored in a database.

Usability

Code

Description

NFR6The code should contain commentary, so that it's possible for another team to understand the code.

Reliability

Code

Description

NFR7The data should be accurate to about x percent.
NFR8There should be no bad smells present in the code.

Documentation

Code

Description

NFR9All documentation has to be written in English.
NFR10

#148484 is the main color and the secondary color is #81c8bd.

NFR11Data is stored in plain text.

Supportability

CodeDescription
NFR12All made systems should be expandable, so future work or expansion of current features is easy to implement. 
NFR13All unit test must be a success with an 80% line coverage.
  • No labels