Non Functional Requirements NFRs

These are system level requirements that apply to the aggregate of the individual contributing modules.

Security

1. Changes on the software/tool shall not give way to cross site scripting attacks.
2. The tool’s availability and reliability shall not be affected after any form of attack.
3. After locally installing the application, running application modules shall not write to system space directories without permissions.
4. The application shall document all external package dependencies that require local install for the application to execute.

Privacy

1. Maintenance process should not disrupt the already existing read data privacy.
2. The use of external open-source weather databases shall not violate any user agreements or privacy policies.

Usability

1. Feature enhancements shall be backwards compatible.
2. Code shall adhere to style guidelines in PEP8.

Reliability

1. Application shall be able to perform all the required functions even after maintenance.

Availability

1. Users should be able to use the tool any time across the week.
2. In case of a feature upgrade, feature should be up and running within few hours of notification.

Performance

1. Performance metrics (system crashes per hour/maximum function execution time/ maximum memory usage) shall not be compromised by any feature enhancements or issue fixes.