Platform quality attributes
🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions. |
1. General description
This section shows the non-functional requirements that the Registries Platform must fulfil.
For each quality attribute, the following information is provided: overview of approach, implementation in solution architecture, key metrics. Additionally, links to the technical design of the corresponding subsystems, and sections with detailed descriptions are provided.
Registry classification and operation conditions are taken into account when defining target values for metrics.
By purpose, we differentiate the following Registries:
-
Strategic — intended for general use by all subjects of information relations within given authority and (or) rights.
-
Tactical — intended for specialized use by a restricted list of subjects within given authority.
-
Operative — intended for dedicated use by a restricted list of subjects within given authority; typically not the master-Registry for other Registries.
We differentiate the following Registry operation conditions:
-
Production hours — officer’s work hours, 8 to 18 on weekdays
-
Peak hours — 3 hours during production hours
-
Evening hours — +2 hours after production hours
-
Shadow hours — all other hours
2. Quality attributes
Quality attribute | Description |
---|---|
This quality attribute defines the extent of system independence from the type of infrastructure it can be deployed on. |
|
This attribute defines the capability of a system to process growing workloads without serious drops in general performance, or the capability to instantly adapt by increasing resource provision. |
|
This attribute defines the percentage of time the system is available and ready to process requests. |
|
This attribute defines the capability of a system to process any request within a restricted time interval and provide the processing of the required requests number in the set time interval without an increase in the time defined for their processing. |
|
This attribute defines the capability of a system to protect data and information from unauthorized access, providing access to authorized users and systems at the same time. |
|
This quality attribute defines the capability of a system to record and provide detailed information in the form of event logs, monitoring metrics, and user transaction tracing data, in order to simplify problem identification and solving by system administrators. |
|
This quality attribute defines the capability of a system to record and provide information on important technical and business events, connected with system operation by end users. The provided information may be used to detect and solve problems in system functionality. |
|
This quality attribute defines the capability of a system to effectively interact with other systems for data exchange. |
|
The quality attribute defines the presence and level of capabilities for servicing and managing system settings during operation. |
|
The quality attribute determines the level of complexity and speed of making changes to the system to expand functionalities and correct defects. |
|
The quality attribute determines the level of complexity for testing and debugging the system when changes are introduced. |