UXPROD-4082 NFR Scorecard

1

Availability

NFR.Baseline.Availability.1

Modules are designed and implemented following the Stateless principle

Apr 18, 2024 COMPLIANT

2

NFR.Baseline.Availability.2

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

Apr 18, 2024 COMPLIANT

3

Manageability

NFR.Baseline.Manageability.1

Application logs are collected in a unified form and location

Apr 18, 2024 COMPLIANT

4

NFR.Baseline.Manageability.2

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

Apr 18, 2024 COMPLIANT

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

Apr 18, 2024 COMPLIANT

NFR.AuthorityMigration.Performance.1

The max number of records in the source file: 12 000 000+ records

Apr 18, 2024 COMPLIANT

6

Security

NFR.Baseline.Security.1

Tenant data must be isolated from other tenants

Apr 18, 2024 COMPLIANT

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)

Apr 18, 2024 COMPLIANT

8

NFR.Baseline.Security.3

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

Apr 18, 2024 COMPLIANT

9

Testability

NFR.Baseline.Testability.1

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

Apr 18, 2024 COMPLIANT

10

NFR.Baseline.Testability.2

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

Apr 18, 2024 Not Applicable

Only backend feature, no UI implementation, and hence no E2E test. The feature is not testable with karate. The main testing for the feature - performance testing.

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

Apr 18, 2024 Not Applicable