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:
- Criteria specify the operation of a system rather than than specific behaviors or functions.
- Cannot be met by custom development or batch job design.
- 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
Use the respective release NFR registers to raise the request |
NFR management process:
- Requestor to fill up columns B to G with the relevant information and set status (column G) to "New".
- Send email to Technology lead (sascha.wenninger-ext@syensqo.com) to review NFR.
- If NFR is valid, a technology team member will be assigned.
- Assigned technology team and requestor will work together to implement and test the solution.
- Assigned technology team and requestor are to ensure relevant documents and test scripts are updated.
- Assigned technology team to seek Technology lead approval before