Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Quality Attribute

NFR ID

Non-Functional Requirement

Preliminary Analysis (Before feature started)- Date and Status

Final Analysis (After feature completed) - Date and StatusNotes and Comments
1

Availability

NFR.Baseline.Availability.1

Modules are designed and implemented following the Stateless principle

Mar 2, 2023   

Status
subtletrue
colourGreen
titleCOMPLIANT



2

NFR.Baseline.Availability.2

Load/performance testing must be conducted for at least 2 instances

  

Status
subtletrue
colourGreen
titleCOMPLIANT



3

Manageability

NFR.Baseline.Manageability.1

Application logs are collected in a unified form and location

  

Status
subtletrue
colourGreen
titleCOMPLIANT



4

NFR.Baseline.Manageability.2

All custom configuration values are placed in the settings, not in the program code

  

Status
subtletrue
colourGreen
titleCOMPLIANT



5

Performance

NFR.Baseline.Performance.1

Components are performance tested and compared to the prior release baseline; performance may not degrade more than 5% in exceptional cases

  

Status
subtletrue
colourYellow
titleNOT VERIFIED


Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyPERF-889

MaintainabilityNFR.ClassificationBrowse.Maintainability.1The extension of functionality should not require changing technical solution  
Status
subtletrue
colourGreen
titleCOMPLIANT


6

Security

NFR.Baseline.Security.1

Tenant data must be isolated from other tenants

  

Status
subtletrue
colourGreen
titleCOMPLIANT


For ECS environment sharing the data in central tenant is intended
7

NFR.Baseline.Security.2

Secrets (such as usernames, passwords, API keys, and/or their combinations) are not stored in source repositories (i.e. Github)

  

Status
subtletrue
colourGreen
titleCOMPLIANT



8

NFR.Baseline.Security.3

No sensitive information in logs (logins, passwords, API keys)

  

Status
subtletrue
colourGreen
titleCOMPLIANT



9

Testability

NFR.Baseline.Testability.1

Unit-test coverage for new code created/changed during the implementation of the feature >= 80%

  

Status
subtletrue
colourGreen
titleCOMPLIANT



10

NFR.Baseline.Testability.2

E2E-test coverage - # of automated test cases from test rail to # of all test cases at a particular feature

  

Status
subtletrue
colourGreen
titleCOMPLIANT



11

NFR.Baseline.Testability.3

Karate-test coverage - # of test to # of new endpoints that were created (or existing endpoints that were changed) in the feature scope

  

Status
subtletrue
colourGreen
titleCOMPLIANT




InteroperabilityNFR.ClassificationBrowse.Interoperability.1The solution should provide the capability to support the ECS environment  
Status
subtletrue
colourGreen
titleCOMPLIANT



ReusabilityNFR.ClassificationBrowse.Reusability.1The solution should provide an approach that can be reused for a group of similar search indexes.  
Status
subtletrue
colourGreen
titleCOMPLIANT



AccessibilityNFR.MarcValidation.Accessibility.1Automated tests for WCAG 2.1 AA compliance  
Status
subtletrue
colourGreen
titleCOMPLIANT



Info
iconfalse
titleLEGEND: Enumeration of possible statuses


Status
subtletrue
colourGreen
titleCOMPLIANT
Compliance checked and confirmed

Status
subtletrue
colourYellow
titleNOT VERIFIED
Compliance not checked

Status
subtletrue
colourRed
titleNON COMPLIANT
Compliance checked, and non-compliance found

Status
subtletrue
titleNot Applicable
Сompliance not required, requirement not applicable

...