Please, refer to NFR Scorecard practice for detailed information

Status	IN PROGRESS
Date-time	01 Feb 2024
Dev Team	Firebird
Architect	Taras Spashchenko
Product Owner	Magda Zacharska
Scrum Master	Mikita Siadykh
Team Lead	Viachaslau Khandramai (Deactivated)
Prod Ticket	UXPROD-4127 - Getting issue details... STATUS
Arch Ticket	ARCH-119 - Getting issue details... STATUS
Tech Design	Data Export redesign
Release	Quesnelia (R1 2024)

	Quality Attribute	NFR ID	Non-Functional Requirement	Preliminary Analysis (Before feature started)- Date and Status	Final Analysis (After feature completed) - Date and Status	Notes and Comments
1	Availability	NFR.Baseline.Availability.1	Modules are designed and implemented following the Stateless principle	01 Feb 2024 COMPLIANT
2	Availability	NFR.Baseline.Availability.2	Load/performance testing must be conducted for at least 2 instances	Feb 1, 2024 COMPLIANT
3	Manageability	NFR.Baseline.Manageability.1	Application logs are collected in a unified form and location	Feb 1, 2024 COMPLIANT
4	Manageability	NFR.Baseline.Manageability.2	All custom configuration values are placed in the settings, not in the program code	Feb 1, 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	Feb 1, 2024 NOT APPLICABLE
	Performance	NFR.DataExport.Performance.1	Export of 22M SRS records in 24 hours without significantly impacting the performance of other FOLIO modules (cataloging, check-in, check-out, data import)	Feb 1, 2024 NOT APPLICABLE
		NFR.DataExport.Performance.2	TODO: Define the max number of concurrently running export jobs
6	Security	NFR.Baseline.Security.1	Tenant data must be isolated from other tenants	Feb 1, 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)	Feb 1, 2024 COMPLIANT
8		NFR.Baseline.Security.3	No sensitive information in logs (logins, passwords, API keys)	Feb 1, 2024 COMPLIANT
9	Testability	NFR.Baseline.Testability.1	Unit-test coverage for new code created/changed during the implementation of the feature >= 80%	Feb 1, 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	Feb 1, 2024 COMPLIANT
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	Feb 1, 2024 COMPLIANT

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

Browser not supported