Purpose

The purpose of this guide is to outline how Non-functional requirements are recorded and met in SyWay project

 Defination

Non-functional requirements definition:

1. Criteria specify the operation of a system rather than than specific behaviors or functions.
2. Cannot be met by custom development or batch job design.
3. Require the technology team to solution and implement.

Below are some examples of NFR: 

• Performance: Scenarios to be included in performance test - Online transaction A should not take more than 10s to complete. 
• Monitoring: Business users to receive alerts when certain interfaces or batch job fails.
• Security: Data encryption for a particular table or field.
• Compliance: Interface logs to be retained for 7 years for audit requirements. 

Process

NFR management process:

1. Requestor to fill up columns B to G with the relevant information and set status (column G) to "New".
2. Send email to Technology lead (sascha.wenninger-ext@syensqo.com) to review NFR.
3. If NFR is valid, a technology team member will be assigned. 
4. Assigned technology team and requestor will work together to implement and test the solution. 
5. Assigned technology team and requestor are to ensure relevant documents and test scripts are updated.
6. Assigned technology team to seek Technology lead approval before