UXPROD-4082 NFR Scorecard

Status

 IN PROGRESS 

Date-time

 

Dev Team

Spitfire

Architect
Product Owner
Scrum Master
Team Lead
Prod Ticket

UXPROD-4082 - Getting issue details... STATUS

Arch Ticket

ARCH-36 - Getting issue details... STATUS  

Tech DesignLong term solution for migrating authority records
ReleaseRamsons (R2 2024)

Technical Design

Related Architectural Tickets:

  1. ARCH-36 - Getting issue details... STATUS
  2. ARCH-38 - Getting issue details... STATUS
  3. ARCH-46 - Getting issue details... STATUS



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

 COMPLIANT



3

Manageability

NFR.Baseline.Manageability.1

Application logs are collected in a unified form and location

 COMPLIANT



4

NFR.Baseline.Manageability.2

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

 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

 COMPLIANT




NFR.AuthorityMigration.Performance.1The max number of records in the source file: 12 000 000+ records COMPLIANT

6

Security

NFR.Baseline.Security.1

Tenant data must be isolated from other tenants

 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)

 COMPLIANT



8

NFR.Baseline.Security.3

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

 COMPLIANT



9

Testability

NFR.Baseline.Testability.1

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

 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

 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

 NOT APPLICABLE


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