You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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 - 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

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