Purpose

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

Definition

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 (e.g. Online transaction A should not take more than 10s to complete)
• Security: Data sets that must be only visible to certain organizations in Syensqo and cannot be met using SAP security role framework.
• Compliance: Logs related to bank interfaces must be retained for 7 years as mentioned in the regulatory requirement tracker.

NFR raised must have specific and targeted to their workstream, and are not covered in other processes For example:

• Avoid raise general NFR - System must be monitored or backed up regularly as Technology team will be managing system wide NFR.
• Requirements that can be covered by other processes - Sending alerts to users when batch job fails will be captured in batch job design.

Process

¹Acceptance test is to be validated by requestor.

²Both requestor and technology team assignee will need to ensure relevant documents are updated (project plan, business process, design document, operational manuals, test scripts etc.)