Versions Compared

Key

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


Info

This is a baseline NFR Scorecard template. To use it in any specific feature, please

  • copy this page replacing xxxx with the feature number in Jira,
  • use the new page to work with NFR Scorecard for your feature.


Info

Please, refer to NFR Scorecard practice for detailed information


Page Properties


Status

Status
titleNEW
/
Status
colourYellow
titleIN PROGRESS
/
Status
colourGreen
titleCOMPLETED

Date-time

<date and time of last update>

Dev Team


Architect


Product Owner


Scrum Master


Team Lead


Prod Ticket

<link to Jira ticket>

Arch Ticket

<link to Jira ticket>

Tech Design
ReleaseQuesnelia (R1 2024) / Ramsons (R2 2024) / Trillium (R1 2025)




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




3

Manageability

NFR.Baseline.Manageability.1

Application logs are collected in a unified form and location




4

NFR.Baseline.Manageability.2

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




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




6

Security

NFR.Baseline.Security.1

Tenant data must be isolated from other tenants




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)




8

NFR.Baseline.Security.3

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




9

Testability

NFR.Baseline.Testability.1

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




10

NFR.Baseline.Testability.2

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




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





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

...