| Principles |
Characteristics |
| Integrity/manageability |
Availability of a single integrated IT architecture (a single IT architect) |
| Uniqueness/deduplication |
Definition of unique data (PDU) and unique services (PS) in the area of responsibility of one business/government agency. The exception is the duplication/erosion of PS and database (under a single architectural control of IT) |
| Formalization/algorithmization. |
Bringing services from manual/semi-automated, vaguely formalized unstructured control objects to PS with structured PDU (for example, judges will have to make decisions in a strict structured format that is accessible to machine interpretation) |
| Blockiness/Efficiency |
Implementation of End-To-End processes (services completed in their meaning), which are a logical workflow of PS/PDU with maximum re-use of PS/PDU of adjacent state bodies (control of the absence of duplication of services by state bodies on the part of the customer-state) |
| Flaky/flexible control |
A clear division of the architecture into a triad of front scenarios (EFS), back scenarios (KMD), and interaction bus (EIP) between systems. Each of the three components must be integral (a single IT implementation with derived open communication protocols) |
| Speed of development and implementation |
development teams work in Agile, flexible rules for the formation of technical tasks, financing, implementation |
