This guide outlines how Non-Functional Requirements are recorded and met in the SyWay project

Definition

Non-Functional Requirements (NFR) 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.

When creating NFRs, please be aware of a few important points: 

  • A NFR must be specific and targeted to a system, solution, or work stream
  • A NFR is not covered in other requirement registers (such as the Legal and Regulatory Requirement register)
  • Avoid statements which are so general and non-specific that it is impossible to ascertain whether or not compliance is achieved. For example "System performance must be adequate" or "data must be backed up regularly". 
  • Avoid requirements that are best handled inside a more specific deliverable; for example sending alerts when a batch job fails will be captured in the design for that job - it does not need to be duplicated here. 

Items which do not adhere will be rejected in the review. 

Process

Use the Release-aligned NFR registers to register a NFR: 

1Acceptance test is to be validated by requestor.

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


  • No labels