UXPROD-4559 NFR Scorecard

Please, refer to NFR Scorecard practice for detailed information

Status

NEW

Date-time

Dev Team

Vega

Architect
Team Lead
Scrum Master
Product Owner

Stephanie Buck / Anne Ekblad 

Prod Ticket

UXPROD-4559 - Getting issue details... STATUS

Arch Ticket

ARCH-127 - Getting issue details... STATUS

Tech Design
ReleaseQuesnelia (R1 2024)

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

 COMPLIANT



2

NFR.Baseline.Availability.2

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

 NOT VERIFIED


We follow this requirement by design, but it makes sense to check the implementation

OkApi-based timer used; Kafka events processing

ACTION ITEM Conduct performance testing

3

Manageability

NFR.Baseline.Manageability.1

Application logs are collected in a unified form and location

 COMPLIANT


new code follows this
4

NFR.Baseline.Manageability.2

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



There are few configurations. Access parameters to the database or Kafka - the standard approach is used

 NOTE: a feature flag - should be a part of mod-tlr (TBD...)
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




LEGEND: Enumeration of possible statuses

COMPLIANT Compliance checked and confirmed

NOT VERIFIED Compliance not checked

NON COMPLIANT Compliance checked, and non-compliance found

NOT APPLICABLE Сompliance not required, requirement not applicable