RU2704873C1 - System and method of managing databases (dbms) - Google Patents

Abstract

FIELD: information technology.

SUBSTANCE: invention relates to means of managing database systems (DBMS). Disclosed is a DBMS management system which provides clients with interaction with databases containing data and metadata. System comprises a subsystem for constructing a graphical logic model of a domain, a subsystem of a unified user interface and a cloud subsystem. Unified user interface subsystem, in its turn, has a module for creating and controlling display of information, an autogeneration module of screen forms, a module for creating links between displayed elements, a module for creating a unified user interface. Separation of business processes into an independent set of modules for designing and processing formalized descriptions of business processes in standard BPMN2. Transferring control tasks of the user interface tasks and interaction tasks with external systems to the business processes alienated from the system core.

EFFECT: wider range of technical means aimed at creating a system and method of controlling a DBMS, which provide the following capabilities: constructing a graphical logical model of a domain, providing access to DBMS data through a subsystem of a unified user interface client-server, enabling separation of data through a subsystem of the cloud.

24 cl, 6 dwg

Description

Technical field

The invention relates to technologies for managing database systems (DBMS).

State of the art

In accordance with the main stages of database design, after constructing the conceptual model, a database management system is selected, with which the database will be organized and working with it. Each DBMS supports certain types and types of data, as well as a means of representing the relationships between the data that make up the DBMS data model. The next stage of database design is to represent the conceptual model using the DBMS model or to map the conceptual model to the DBMS data model. This step is often called logical database design. The resulting model is often also called a conceptual model or schema (but a DBMS data model specified to the concepts). In some sources, the resulting model is called the logical data structure.

The concept of a data model can be characterized in different ways. On the one hand, a data model is a way of structuring data, which is considered as some abstraction in isolation from the subject area. On the other hand, the data model is a tool for representing the conceptual model of the subject area and the dynamics of its change in the form of a database. Given both of the above sides, we define the basic structures of data models used to represent the conceptual model of the subject area (entities, attributes, relationships). A data item (field) is the smallest named unit of data. Used to represent an attribute value. A record is a named set of fields. Used to represent a set of attributes of an entity (entity record). A record instance is a record with specific field values. A data aggregate is a named collection of data elements within a record that can be considered as a whole.

A file is a named set of record instances of the same type. Used to represent a homogeneous set of entities. A file set is a named collection of files processed in a system. Used to represent multiple sets of entities. We introduce the concept of “group”, summarizing the concepts of “aggregate” and “record”. A group is a named collection of data elements or data elements and other groups. The most important concept of the conceptual model is the concept of the relationship between entities (sets of entities).

In data models, the corresponding concept is reflected in the concept of “group relationship”. A group relation is a named binary relation defined on two sets of instances of the groups in question. By the nature of binary bonds, group relations of the form 1: 1, 1: M, M: 1, M: N are distinguished. Pairs of numbers are called group ratio coefficients. In a group relationship, one member of the group is designated as the owner of the relationship, the other as a member.

A database is a named collection of group instances and group relationships. To represent a group relationship, two forms are used: a) Graph. Groups are represented by the vertices of the graph, connections between groups — arcs directed from the owner group to the member group with the name of the relation and coefficient. By the type of graphs distinguish: hierarchical model (graph without cycles - a tree); network model (general directed graph), b) Tabular. The relationship between groups is represented by a table whose columns represent the keys of the corresponding groups. For the formal description of the table, the mathematical (set-theoretic) concept of the relation is used. The corresponding data model is called the relational model.

The prior art, many solutions are known that reveal various principles of DBMS management.

In the application US 2016 / 321,376 A1, published on November 3, 2016, technologies for storing and retrieving data using a related data model having a tree format are disclosed, while the elements of this model are connected to each other. Also in this solution, a cloud computing platform is disclosed, which can store, including data presented in the form of a graph.

In the application US 2017 / 212,914 A1, published on July 27, 2017, technologies for storing data elements in the form of graphs having hierarchical nodes and relations between elements are disclosed. Also in this solution, user interfaces are disclosed that allow retrieving data from graphs, and data storage in cloud systems is disclosed.

US Pat. No. 5,201,046 A1, published April 6, 1993, discloses a database management system that stores, retrieves, and processes oriented graph structures in a relational database.

The application US 2009/031230 A1, published January 29, 2009, discloses technologies for dynamically customizing the user interface for a relational database. However, these solutions do not implement the following features:

сочетание классического реляционного персистентного хранилища с неизменной (не зависящей от предметной области и варианта использования) физической структурой и представления данных для использования пользователями и программами в виде графа;

a combination of a classical relational persistent storage with an unchanged (independent of the subject area and use case) physical structure and data presentation for use by users and programs in the form of a graph;

использование специфицированного фиксированного интерфейса для манипуляции и обмена данными в терминах графа;

using a specified fixed interface for manipulating and exchanging data in terms of a graph;

разделение системы на облачный сервис для работы с метаданными и эксплуатационный комплект для заказчика;

dividing the system into a cloud service for working with metadata and an operational kit for the customer;

поставку и сопровождение информационного наполнения метаописаний и онтологий предметных областей с использованием труда соответствующих экспертов;

delivery and maintenance of information content of meta descriptions and ontologies of subject areas using the labor of relevant experts;

реализацию логической модели на различных языках программирования, в различных операционных средах с использованием различных СУБД (в т.ч. не реляционных) в качестве персистентного хранилища.

implementation of the logical model in various programming languages, in various operating environments using various DBMSs (including non-relational ones) as a persistent storage.

The main objectives of the declared decision are:

создание неизменного по физической структуре способа хранения данных вне зависимости от предметной области и варианта использования;

the creation of a method of storing data unchanged in physical structure, regardless of the subject area and use case;

создание неизменного способа представления данных вне зависимости от предметной области;

creating an invariable way of presenting data regardless of the subject area;

решение вопроса перенастройки пользовательского интерфейса без внесения изменений в программный код;

resolving the issue of reconfiguring the user interface without making changes to the program code;

решение вопроса перестройки прикладной модели данных (метаописания) без внесения изменений в программный код;

solving the issue of restructuring the applied data model (meta description) without making changes to the program code;

решение вопроса о переносе нагрузки по проектированию, внедрению и адаптации к предметной области с программистов-разработчиков на аналитиков, экспертов и пользователей;

solving the problem of transferring the load of designing, implementing and adapting to the subject area from programmers to analysts, experts and users;

создание единого информационного пространства в гетерогенной программно-аппаратной и информационной среде, где недостаточно операций с данными и требуется выход на уровень согласования метаданных (онтологий);

creation of a single information space in a heterogeneous software and hardware and information environment, where there are not enough data operations and it is necessary to reach the level of metadata (ontology) coordination;

создание пополняемого пула (репозитория) готовых решений и полуфабрикатов для различных предметных областей и вариантов использования с привлечением сообществ разработчиков, пользователей, заинтересованных клиентов и заказчиков.

creation of a replenished pool (repository) of ready-made solutions and semi-finished products for various subject areas and use cases involving communities of developers, users, interested clients and customers.

Использование решений с открытым кодом.

Using open source solutions.

Thus, the unresolved problem of expanding the arsenal of technical means that would allow creating such a DBMS that implements the following features: constructing a graphical logical model of the subject area, providing access to the DBMS data through the subsystem of the unified user interface client-server, ensuring data separation through the subsystem the clouds.

The way out of this situation may be the creation of a database management system and method (DBMS) that provides customers with interaction with databases containing data and metadata, which also implement at least the following features: constructing a graphical logical model of the subject area, providing access to DBMS data through the subsystem of the unified user interface client-server, providing data separation through the cloud subsystem.

Disclosure of invention

The technical result of the present invention is to create a DBMS management system and method, providing customers with interaction with databases containing data and metadata, which also implement at least the following features: constructing a graphical logical model of the subject area, providing access to the DBMS data through the subsystem unified user interface client-server, providing data sharing through the cloud subsystem.

This technical result is achieved due to the proposed database management system (DBMS), which provides customers with interaction with databases containing data and metadata, configured to implement at least the following:

представления данных на логическом уровне посредством подсистемы построения графовидной логической модели предметной области и на физическом уровне посредством подсистемы построения неизменной, не зависящей от предметной области, физической структуры реляционных таблиц, где подсистема построения логической модели предметной области, содержит, по меньшей мере, следующее:

presenting data at a logical level by means of a subsystem for constructing a graph-like logical model of a subject domain and at the physical level by means of a subsystem for constructing a physical structure of relational tables, which does not depend on a domain, where the subsystem for constructing a logical model of a domain contains at least the following:

a. domain analysis module, configured to present data in the form of diagrams of use cases,

b. module for compiling meta-descriptions of a subject domain, configured to create a domain defining a subject domain,

c. a module for determining information resources reflecting objects of a subject area, configured to compile a list of information resources reflecting objects of a subject area,

d. an attribute assignment module for information resources, configured to assign to each information resource a set of attributes — properties that reflect the properties of the information resource,

e. a module for establishing links between information resources, configured to establish links between resource objects, while the connections have informational significance and contain the following properties: globally unique identifier for the connection, globally unique identifier of the parent node, globally unique identifier of the child node, pointer to attribute the parent node that refers to the child resource, a multiplicity of communication that defines a group relationship of the type 1: 1, 1: M, M: 1, M: N,

f. a module for defining marker interfaces for information resources, configured to mark information resources with matching attributes for a set of attributes,

g. a module for determining classifiers, made with the possibility of marking information resources with specified labels to implement at least the allocation, grouping of information resources,

where, as a result of the functions implemented at the ag stages, the subsystem for constructing a graph-like logical model of the subject domain constructs the indicated model, which contains information resources, attributes of information resources and the relationship between information resources, the model is stored in a relational structure and used to create it copies of information resources,

where the subsystem for constructing the physical structure of relational tables is configured to divide storage space, at least for tables, database indexes, and also, with the possibility of network distribution of data storage in databases using clustering;

обеспечения доступа к данным посредством подсистемы унифицированного пользовательского интерфейса клиент-сервер, где подсистема унифицированного пользовательского интерфейса содержит:

providing access to data through the subsystem of the unified user interface client-server, where the subsystem of the unified user interface contains:

a module for creating and managing information display, configured to create information display layout options, with the ability to specify a set of information display elements — widgets that can be specified and replenished, widgets are located in the layout areas, in accordance with various layout options,

a module for creating links between the displayed elements of the displayed information, configured to set the relationships between fields, widget columns,

module for creating a unified user interface, configured to:

creating the specified user interface using the specified modules for creating and managing the display of information, the module for creating links between the displayed information elements,

storage of widgets - elements of the displayed information in the given templates and layouts,

expanding the functionality of the user interface by adding new functions using dynamically tuned scripts;

module for auto-generation of screen forms from preset templates;

выделения реализации прикладной бизнес логики в самостоятельный набор модулей, позволяющий, как минимум:

separation of the implementation of applied business logic into an independent set of modules that allows, at least:

производить визуальное формализованное построение бизнес процессов силами экспертов предметной области

to produce visual formalized construction of business processes by subject matter experts

осуществлять функциональное связывание бизнес процессов с управлением данными с использованием адаптированных средств проектирования, доступных экспертам и аналитикам предметных областей

carry out functional linking of business processes with data management using adapted design tools available to experts and domain analysts

обеспечить формализованное представление бизнес-процессов в принятых стандартах и форматах - BPMN(2), XML

provide a formalized representation of business processes in accepted standards and formats - BPMN (2), XML

посредством бизнес процессов осуществлять управление отображением информации и сложным поведением пользовательского интерфейса

through business processes, manage the display of information and the complex behavior of the user interface

посредством конструируемых экспертами и аналитиками предметных областей бизнес процессов реализовывать взаимодействие с внешними источниками и потребителями данных, регламентные процедуры

through business processes constructed by experts and analysts of subject areas, implement interaction with external data sources and consumers, regulatory procedures

обеспечения разделения данных посредством подсистемы облачного сервиса - подсистемы облака, которая организует централизованное управление метаданными и метомоделями - метопописания предметных областей, содержащие информационные ресурсы, атрибуты, связи,

providing data separation through the cloud service subsystem - the cloud subsystem, which organizes the centralized management of metadata and metomodels - metadata descriptions of subject areas containing information resources, attributes, communications,

where the cloud subsystem also contains repositories, a user interface for working with repositories, an access control module, an application server, a database server, while the repositories are divided into the following groups:

репозиторий метамоделей различных предметных областей,

repository of metamodels of various subject areas,

репозиторий функциональных модулей,

functional module repository

репозиторий геоданных,

geodatabase repository

репозиторий классификаторов и справочников,

repository of classifiers and directories,

репозиторий визуальных решений - каркасов приложений для различных вариантов использования и различных предметных областей,

visual solutions repository - application frameworks for various use cases and various subject areas,

where the tools of the cloud subsystem are configured to:

создавать метамодели новых предметных областей,

create metamodels of new subject areas,

редактировать существующие метамодели,

edit existing metamodels,

загружать и редактировать новые данные: геоданные, классификаторы и справочники,

upload and edit new data: geodata, classifiers and directories,

администрировать пользователей и доступ к ресурсам облака.

administer users and access to cloud resources.

In one particular embodiment, at least query languages are used to access data, where SQL queries are used at the lower level, and at least the following languages are used at the logical level: Java, Cypher, Resource Query Language (RQL )

In another particular embodiment, to ensure the separation of data, partitioning is used — separate storage of data and indices, where partitioning is used: at the operational processing level, this is realized, at least, through persistent storage, a cache in memory; at the storage level it is used by dividing the storage space, by means of clusters and grids; at the level of business logic, it is used by creating certain schemes and structures containing at least the following: geodata, calendars, time series, classifiers and reference books, metamodels, events, default data, business processes.

In another particular embodiment, the data separation step also includes the division of data at the meta level into data and metadata, where the metadata consists of a description of subject areas in terms of information resources, attributes and relationships, directories, classifiers.

In another particular embodiment, the DBMS also contains an operational installation kit, which is created on the basis of information and data received from the cloud service for a specific user and contains: a set of meta descriptions that meets a given subject area and meets user requirements, a set of initial data necessary to start operation , a set of functional modules that implements the functional requirements of users.

In another particular embodiment, access to the system’s data is provided through a kernel that implements bidirectional transformation of queries and data between a relational representation and a representation in the form of a graph-like logical model of a domain, and implemented in a managed cache in RAM, where the kernel implements a fixed, uniform, unified data manipulation interface as nodes of a graph model.

In another particular embodiment, the data manipulation interface is: a low-level interface between programs, designed for interaction at the level of programs and program modules using various programming languages, a data exchange interface based on the exchange of requests for data and answers in a machine-readable form.

In another particular embodiment, the subsystem of the unified user interface is also configured to store data characterizing the design elements of the interface, such as signatures to form fields, headings of forms and tables, in a formalized form.

In another particular embodiment, through the cloud service subsystem, users, after authorization, gain access to the cloud and its resources - repositories, also users create a metamodel in the workspace, filling it with everything necessary, then the metamodel can be exported and transferred to the users site to the workspace An environment where, on the basis of a metamodel, data instances are created with which users work.

In another particular embodiment, repositories provide access to at least the following functional modules: information resource and attribute editor, screen designer, search engine, tools for configuring the connection of external systems and databases, visual metadata navigation tools, classifier loader , classifier editor, streaming data visualizer, subject area management tools, namespace management tools, reference and reference information management tools formation, means of visual navigation of data.

In one particular embodiment, compliance with W3C standards regarding the specifications of ontologies RDF, OWL is ensured.

In another particular embodiment, the possibility of formalized data exchange with other systems at various levels is realized.

The technical result is also achieved due to the proposed method of managing a DBMS, which provides customers with interaction with databases containing data and metadata, where the method contains stages in which at least the following is carried out:

представление данных на логическом уровне посредством подсистемы построения графовидной логической модели предметной области и на физическом уровне посредством подсистемы построения физической структуры реляционных таблиц,

presentation of data at a logical level through a subsystem for constructing a graph-like logical model of a domain and at a physical level through a subsystem for constructing a physical structure of relational tables,

where the subsystem for constructing a logical model of the subject area is configured to implement at least the following:

a. presenting data in the form of a use case diagram through a domain analysis module,

b. create a domain that defines the subject area through the module for compiling meta descriptions of the subject area,

c. compiling a list of information resources reflecting the objects of the subject area by means of a module for determining information resources reflecting the objects of the subject area,

d. assigning to each information resource a set of attributes - properties that reflect the state of the information resource through the module of attribute assignment to information resources,

e. establishing links between resource objects by means of a linking module between information resources, and the relationships are informational in importance and contain the following properties: globally unique identifier for the link, globally unique identifier for the parent node, globally unique identifier for the parent node, pointer to the attribute of the parent node, which refers to a child resource, a multiplicity of relationship that defines a one-to-many or one-to-one relationship,

f. marking information resources with matching signs for a set of attributes by means of a module for specifying marker interfaces for information resources,

g. marking of information resources with given marks by means of the classifier definition module, where such marking is carried out for at least allocation, grouping of information resources,

where, as a result of the functions implemented at the ag stages, the subsystem for constructing a graph-like logical model of the subject domain constructs the indicated model, which contains information resources, attributes of information resources and the relationship between information resources, the model is stored in a relational structure and used to create it copies of information resources,

where the subsystem for constructing the physical structure of relational tables is configured to divide storage space, at least for tables, database indexes, and also, with the possibility of network distribution of data storage in databases using clustering;

обеспечение доступа к данным посредством подсистемы унифицированного пользовательского интерфейса клиент-сервер, где подсистема унифицированного пользовательского интерфейса выполнена с возможностью:

providing access to data through the subsystem of the unified user interface client-server, where the subsystem of the unified user interface is configured to:

creating options for displaying information, with the ability to specify a set of information display elements - widgets that can be specified and replenished, widgets are located in the layout areas, in accordance with various layout options through the module for creating and controlling the display of information,

set relationships between fields, widget columns using the module for creating links between displayed elements of displayed information,

to bind user interface events - user actions, display or concealment, arrival or sending data with a business process that performs automated control of the user interface and interaction with the server part

the implementation of the following steps through the module creating a unified user interface:

creating the specified user interface using the specified modules for creating and managing the display of information, the module for creating links between the displayed information elements,

storage of widgets - elements of the displayed information in the given templates and layouts,

expanding the functionality of the user interface by adding new functions using dynamically tuned scripts;

module for auto-generation of screen forms from preset templates;

обеспечение разделения данных посредством подсистемы облачного сервиса - подсистемы облака, которая организует централизованное управление метаданными и метомоделями - метопописания предметных областей, содержащие информационные ресурсы, атрибуты, связи,

providing data separation through the cloud service subsystem - the cloud subsystem, which organizes the centralized management of metadata and metomodels - metadata descriptions of subject areas containing information resources, attributes, communications,

where the cloud subsystem also contains repositories, a user interface for working with repositories, an access control module, an application server, a database server, while the repositories are divided into the following groups:

репозиторий метамоделей различных предметных областей,

repository of metamodels of various subject areas,

репозиторий функциональных модулей,

functional module repository

репозиторий геоданных,

geodatabase repository

репозиторий классификаторов и справочников,

repository of classifiers and directories,

репозиторий визуальных решений - каркасов приложений для различных вариантов использования и различных предметных областей,

visual solutions repository - application frameworks for various use cases and various subject areas,

where the tools of the cloud subsystem are configured to:

создавать метамодели новых предметных областей,

create metamodels of new subject areas,

редактировать существующие метамодели,

edit existing metamodels,

загружать и редактировать новые данные: геоданные, классификаторы и справочники,

upload and edit new data: geodata, classifiers and directories,

администрировать пользователей и доступ к ресурсам облака.

administer users and access to cloud resources.

In one particular embodiment, at least query languages are used to access data, where SQL queries are used at the lower level, and at least the following languages are used at the logical level: Java, Cypher, Resource Query Language (RQL )

In another particular embodiment, to ensure the separation of data, partitioning is used — separate storage of data and indices, where partitioning is used: at the operational processing level, this is realized, at least by means of persistent storage, a cache in memory; at the storage level it is used by dividing the storage space, by means of clusters and grids; at the level of business logic, it is used by creating certain schemes and structures containing at least the following: geodata, calendars, time series, classifiers and reference books, metamodels, events, default data, business processes.

In another particular embodiment, the data separation step also includes the division of data at the meta level into data and metadata, where the metadata consists of a description of subject areas in terms of information resources, attributes and relationships, directories, classifiers.

In another particular embodiment, the DBMS also contains an operational installation kit, which is created on the basis of information and data received from the cloud service for a specific user and contains: a set of meta descriptions that meets a given subject area and meets user requirements, a set of initial data necessary to start operation , a set of functional modules that implements the functional requirements of users.

In another particular embodiment, access to the system’s data is provided through a kernel that implements bidirectional transformation of queries and data between a relational representation and a representation in the form of a graph-like logical model of a domain, and implemented in a managed cache in RAM, where the kernel implements a fixed, uniform, unified data manipulation interface as nodes of a graph model.

In another particular embodiment, the data manipulation interface is: a low-level interface between programs, designed to interact at the level of programs and program modules, using various programming languages, a data exchange interface based on the exchange of requests for data and answers in a machine-readable form.

In another particular embodiment, the subsystem of the unified user interface is also configured to store data characterizing the design elements of the interface, such as signatures to form fields, headings of forms and tables, in a formalized form.

In another particular embodiment, through the cloud service subsystem, users, after authorization, gain access to the cloud and its resources - repositories, also users create a metamodel in the workspace, filling it with everything necessary, then the metamodel can be exported and transferred to the users site to the workspace An environment where, on the basis of a metamodel, data instances are created with which users work.

In another particular embodiment, repositories provide access to at least the following functional modules: information resource and attribute editor, screen designer, search engine, tools for configuring the connection of external systems and databases, visual metadata navigation tools, classifier loader , classifier editor, streaming data visualizer, subject area management tools, namespace management tools, reference and reference information management tools formation, means of visual navigation of data.

In one particular embodiment, compliance with W3C standards regarding the specifications of ontologies RDF, OWL is ensured.

In another particular embodiment, the possibility of formalized data exchange with other systems at various levels is realized.

Brief Description of the Drawings

The group of claimed inventions is illustrated by drawings, where:

in FIG. 1 shows an extended DBMS schema;

in FIG. 2 shows a structural diagram of the claimed system according to an independent clause;

in FIG. 3 shows the modules of the subsystem for constructing a graph-shaped model of the subject area;

in FIG. 4 shows the main modules that are part of the subsystem of the unified user interface;

in FIG. 5 shows the main functionality of the cloud subsystem;

in FIG. Figure 6 shows an example of a domain metamodel.

Description of Embodiments

The following is a description of exemplary embodiments of the claimed inventions with reference to the drawings. However, the present invention is not limited to these embodiments only. It will be apparent to those skilled in the art that other variations fall within the scope of the claimed group of inventions described in the claims.

In the context of this description, the terms “subsystem”, “module”, “database” should be understood as the standard concepts of these terms that are established in the prior art, implying software and hardware functional units that can be implemented using machine algorithms.

In FIG. 1 shows an extended DBMS schema that provides clients with interaction with databases containing at least data and metadata. DBMS provides various data representations:

- at a logical level, data is presented in the form of a directed graph with properties: the nodes of the graph represent structured entities - meta descriptions and meaningful information, the edges of the graph represent relationships between entities. Edges have a direction from the parent to the child;

- at the physical level, data is presented in the form of a finite fixed set of tables implemented using a relational DBMS.

The DBMS implements data separation at the following levels:

a. meta-level, where data is divided into:

metadata, structured descriptions, structuring at a logical level is implemented as a directed graph with properties; while metadata is a set of directories, classifiers, reference information, structured descriptions of subject areas;

b. Attributes level, according to which the information object includes:

- globally unique identifier,

- human-readable name,

- machine-readable alphanumeric tag

- data type corresponding to the attribute:

- a primitive type containing:

- text

- numerical

- date / time / date-time,

- logical switch,

- intermediate type, including:

- geodata,

- arrays

- Key-value cards,

- intervals

-object type containing:

- a pointer to an Information resource through its globally unique identifier,

from. the level of communication, according to which the information object, includes:

- globally unique identifier,

- globally unique identifier of the parent node (information resource),

- globally unique identifier of a child node (Information resource),

- a globally unique identifier for the attribute of the parent node through which a link to the child node is established,

- specific properties of relationships described in the form of a Key-Value map.

In FIG. 2 shows a structural diagram of the claimed database system. According to FIG. 2, DBMS, in one of the private options for implementing the claimed solution, contains: a subsystem for constructing a graph-like logical model of a domain, a subsystem of a unified user interface, a cloud subsystem.

In FIG. Figure 3 shows at least the basic modules of the subsystem for constructing a graph-like model of the subject area. The subsystem for constructing a graph model contains at least 7 modules: a domain analysis module (module 1), a domain meta description module (module 2), a module for determining information resources reflecting domain objects (module 3), an attribute assignment module for information resources (module 4), a module for establishing links between information resources (module 5), a module for specifying marker interfaces for information resources (module 6), a module for determining classifiers (module 7).

In module 1, the study and analysis of the subject area is carried out, where as a result of these actions they get a representation corresponding to the data use case diagram for the main objects (entities) of the subject area.

In module 2, meta descriptions of the subject area are compiled. As well as the creation of a domain (domain) that defines the newly created subject area. All newly created information resources receive a sign of belonging to the created domain. Reuse of resources from other domains is allowed. Belonging to the domain determines the semantic context and content of the information resource. A domain is, in a sense, the equivalent of a subject domain.

Module 3 compiles information resources that reflect the objects of the subject area. In this case, information about previously created resources is used to avoid duplication as much as possible. Previously created information resources are reused. Each information resource has its own globally unique identifier.

Module 4 is designed to assign attributes to information resources. Each newly created information resource receives a set of its own attributes - properties that reflect the state of the information resource. Properties can be of a primitive type, such as numeric or text. Properties can be of the type "link to another information resource". The resource referenced determines the type of attribute. Attributes of information resources are also reused as much as possible to avoid their repetition in various resources. So, for example, the attribute "Start date" has a primitive type "date" and can be used in various information resources in various contexts. In other words, attributes should be used as a glossary of terms for use in describing the composition of information resources. The list of attributes is replenished only as necessary in the absence of a suitable attribute. Each attribute has signs of belonging to a "namespace" (name space). "Namespace" - a named set (set) of attributes, which is an analogue of a specialized glossary of terms. This is necessary to solve the problem of using homonyms in different contexts (subject areas). For example, the words "schedule", "outfit", "braid", "environment" can have different semantic meanings in different subject areas.

Module 5 allows you to establish communication information resources. Connections between objects have independent informational significance and contain the following properties:

1. globally unique communication identifier,

2. globally unique identifier of the parent node,

3. globally unique identifier of the child node,

4. pointer to the attribute of the parent node that refers to the child resource

5. the multiplicity of communication, determining the relationship of the type "one-to-many" or "one-to-one."

In module 6, information resources are marked with given labels. Additionally, information resources can be equipped with marker interfaces - signs of compliance of a set of attributes with one or another definition. So, for example, the information resource “Individual” in some subject areas may receive the “Intruder” marker, which means that potentially any “Individual” with which we work may become an “Intruder" and a predetermined set of information will be required (attributes), which is just provided by the description of the marker interface "Intruder", which can contain information characterizing an individual as an intruder.

Module 7 is designed to classify information resources so that they can be compared, allocated, grouped based on the values of the assigned classifiers. The claimed system maintains a centralized repository of classifiers. Existing classifiers are maximally reused in various subject areas. New classifiers are uploaded to the repository through mapping maps of the keys and values of the "source classifier" and the "target classifier" stored in the system repository.

As a result of the steps and actions performed by modules 1-7, the output is a logical graph-shaped model of the domain containing information resources, attributes of information resources and the relationship between information resources. The physically obtained model is stored in a relational structure, which does not change and does not depend on the described domain, since the description is made in a unified graph-like logical representation. In other words, in the proposed structure it’s the same as describing: operational activities of an organization, data from sensors of an industrial system, a warehouse of goods, the organizational structure and personnel of an enterprise, or something else. The graph-like logical model basically remains unchanged, as does the physical structure of its storage. The created domain metamodel is subsequently used to create, on its basis, copies of information resources containing real information relating to practical activities within the domain.

An example of such a model is shown in FIG. 6, which considers information resources related to control at a checkpoint. Additionally, a file with a description of the metamodel data scheme "Metamodel" is attached, which stores meta descriptions of information resources and attributes.

Another subsystem that is part of the claimed system is a subsystem of a unified user interface, the main modules of which are presented in FIG. four.

The unified construction of the user interface is based on the following properties of the claimed system associated with the storage and presentation of data, as well as with typical display options:

1. All data is logically represented in the form of information resources, attributes and relationships between them. This information is available in the metamodel;

2. at the physical level, the storage model is unchanged and does not depend on the subject area;

3. A set of typical options for displaying information is highlighted:

1. general layout (Layout). The set of options can be determined in advance and further expanded and modified as necessary. Options are selected by analysts and reused in different tasks.

2. a set of information display elements (widgets): tables with columns, forms, forms, etc. A set of widgets is determined in advance and replenished as necessary. Widgets are selected by analysts and placed in the layout in areas determined by the previously selected layout option.

4. unified client-server interaction interface. Based on a domain-independent representation of data in the form of information resources and attributes. The format of HTTP requests in the form of a URL string is also objectively independent. One way or another is requested: "information resources of a given type, having the values of certain properties specified in the query string" and nothing about the subject area, as such;

5. The binding of fields and columns of widgets with data occurs at the level of working with the metamodel. So, for example, to display the list of “Individuals”, the information resource “Individual” is selected. Next, from the metadata of the Resource "Individual" attributes are selected, the essence is the columns of the future table. Next, the widget type "Table" is assigned;

6. the result is a typical MVC bundle (Model-View-Controller), where we have a model defined by the selected columns with properties known from the meta description, the visual solution (View) - the selected widget, the controller a unified software interface that connects the model with the widget;

Since all the steps described above are subject-independent, the interface for working with them is also unified and transferred to analysts and subject specialists. UI design elements, such as form field labels, form and table headings, etc. stored in a formalized form. Screen solutions, like all information in the claimed system, are presented and stored in the form of information resources and attributes.

Functional solutions of the user interface are extensible using dynamically embedded scripts that are written and stored as data and used at the stage of execution of the main code.

At the functional level, the unified user interface subsystem contains at least the following modules: an information display creation and control module, configured to create information display layout options, with the ability to specify a set of information display elements — widgets that can be specified and replenished, widgets are located in the layout areas, in accordance with various layout options, a module for creating links between displayed display elements information, made with the ability to specify the relationship between fields, widget columns, a module for automatically generating screen forms from predetermined templates, a unified user interface creation module, configured to: create a specified user interface using the indicated information creation and control modules, and the connection between displayed elements of information, storage of widgets - elements of displayed information in specified templates and layouts, expansion of functions onala user interface by adding new functions using dynamically configurable scripts.

The claimed DBMS also includes the cloud subsystem shown in FIG. 5.

The cloud service is designed to organize centralized collective work with metadata and metamodels. Cloud service does not work with actual data. This is not a "working environment", i.e. not a "production environment". It contains repositories, a user interface for working with repositories, an access control subsystem, an application server and a database server. Repositories are divided into the following groups:

репозиторий метамоделей различных предметных областей

repository of metamodels of various subject areas

репозиторий функциональных модулей

function module repository

репозиторий геоданных

geodata repository

репозиторий классификаторов и справочников

classifier and reference repository

репозиторий визуальных решений (каркасов приложений) для различных вариантов использования и различных предметных областей.

repository of visual solutions (application frameworks) for various use cases and various subject areas.

Moreover, the tools allow you to:

создавать метамодели новых предметных областей

create metamodels of new subject areas

редактировать существующие метамодели

edit existing metamodels

загружать и редактировать новые данные: геоданные, классификаторы и справочники

upload and edit new data: geodata, classifiers and reference books

администрировать пользователей и доступ к ресурсам облака

administer users and access to cloud resources

Users - enterprises and their employees, individual individual users receive authorized access to the cloud and its resources - repositories. In their own workspace (workspace), users create their own metamodel and fill it with the necessary initial data to start work. In this case, ready-made solutions from repositories are used. The metamodel prepared in this way is exported and transferred to the client’s site in the production environment, where data copies are created on the basis of the metamodel and users work with them.

The following is a list of the main functional modules available in the repository:

редактор информационных ресурсов и атрибутов;

editor of information resources and attributes;

конструктор экранных форм;

screen designer;

поисковая подсистема;

search subsystem;

настройщик подключения внешних систем и баз данных;

connection tuner for external systems and databases;

средства визуальной навигации по метаданным;

visual metadata navigation tools;

загрузчик классификаторов;

classifier loader;

редактор классификаторов;

classifier editor;

визуализатор (монитор) потоковых данных;

visualizer (monitor) of streaming data;

управление предметными областями (доменами);

management of subject areas (domains);

управление пространствами имен (namespaces);

namespaces management;

средства управление нормативно-справочной информацией;

reference management tools;

средства визуальной навигации по данным;

visual navigation tools for data;

конструктор расчетных процедур;

designer of settlement procedures;

аналитическая подсистема;

analytical subsystem;

средства управление геоданными;

location management tools;

конструктор-построитель отчетов;

report builder;

рабочая среда разработки (workspace);

development environment (workspace);

средства администрирования пользователей;

user administration tools;

средства управление разграничением доступа к данным;

facilities for managing access to data;

средства использование репозиторев;

repository utilization;

конструктор бизнес-правил;

Business Rules Designer

конструктор бизнес-процессов;

business process designer;

контроль управления функционированием;

performance management control;

техническое обслуживание и сопровождение;

maintenance and support;

управление конфигурациями;

configuration management;

обмен данными, синхронизация;

data exchange, synchronization;

загрузка/выгрузка информационных ресурсов и атрибутов.

loading / unloading of information resources and attributes.

Summarizing the foregoing, it should be noted that the DBMS and system used to control this DBMS also have the following distinctive features:

переиспользование метамоделей и их элементов в новых метамоделях с использованием разбиения информационных ресурсов и атрибутов на домены (предметные области) и пространства имен (name spaces);

reuse of metamodels and their elements in new metamodels using a breakdown of information resources and attributes into domains (subject areas) and name spaces (name spaces);

прозрачное единообразное представление метамодели любой предметной области, недостижимое средствами традиционных реляционных СУБД;

transparent uniform presentation of the metamodel of any subject area, unattainable by means of traditional relational DBMSs;

максимальное использование аспектов унифицированного представления данных в виде графа для решения вопросов расширения сфер применения, минимизации привлечения технических специалистов на этапах внедрения, - в основном работают аналитики и специалисты-предметники, унификация пользовательского интерфейса, сопряжение самых разнородных предметных областей, унификация работы с данными (манипуляция данными). Унифицированный программный интерфейс для манипуляции данными, как узлами ориентированного графа со свойствами, определенными метамоделью;

maximizing the use of aspects of the unified presentation of data in the form of a graph to solve issues of expanding the scope of application, minimizing the involvement of technical specialists at the implementation stages, mainly analysts and subject specialists work, unifying the user interface, pairing the most diverse subject areas, unifying working with data (manipulation data). Unified programming interface for manipulating data as nodes of a directed graph with properties defined by a metamodel;

максимальное использование свойств традиционной, реляционной СУБД: транзакционность, ограничения целостности, оптимизация модели хранения в зависимости от варианта использования. По-разному хранятся данные временных рядов, событийной логики, списочно-реестровые данные и т.д. По-разному реализуется связывание данных в зависимости от типа множественности связи. Использование партиционирования - раздельного хранения данных и индексов, а так же раздельное хранение структур, ориентированных преимущественно на вставку, на изменение, на поиск данных;

maximum use of the properties of a traditional, relational DBMS: transactionality, integrity constraints, storage model optimization depending on the use case. Differently stored data are time series, event logic, list and registry data, etc. Data binding is implemented differently depending on the type of multiplicity of communication. Using partitioning — separate storage of data and indexes, as well as separate storage of structures oriented mainly to insert, change, and search data;

использование новых встроенных типов данных для оптимизации физической реляционной модели под логическую графовую модель: jsonb - бинарное индексируемое поле типа json, гео данные для представления точек, линий, полигонов и мультиполигонов, интервальные данные и т.д;

the use of new built-in data types to optimize the physical relational model for a logical graph model: jsonb - a binary indexed field of the json type, geo data for representing points, lines, polygons and multipolygons, interval data, etc.

обязательное строгое использование метамодели при работе в рабочем окружении. Это исключает «замусоривание» данных лишними связями, классификаторными признаками и т.д;

mandatory strict use of the metamodel when working in a work environment. This eliminates the “littering" of data with unnecessary connections, classificatory signs, etc.

расширяемость заявленной системы за счет использования возможности маппинга графа на традиционные реляционные структуры и обратно. Это дает возможность расширять функциональные возможности системы за счет интеграции с другими системами и базами данных, как на уровне данных, так и на уровне функциональном;

the extensibility of the claimed system due to the use of the ability to map the graph to traditional relational structures and vice versa. This makes it possible to expand the functionality of the system through integration with other systems and databases, both at the data level and at the functional level;

предоставление конечным пользователям готовых прикладных (отраслевых) решений, основанных на имеющихся в облачном репозитории наборах метамоделей и других данных.

providing end users with ready-made application (industry) solutions based on the sets of metamodels and other data available in the cloud repository.

None of these features can be called completely unique. Here we should talk about a set of features that affect the technical result achieved, which consists in creating a DBMS management system and method that provides customers with interaction with databases containing data and metadata, which also implement at least the following features: building a graphical logical domain models, providing access to DBMS data through the subsystem of the unified user interface client-server, ensuring data separation a subsystem of the cloud subsystem.

Embodiments of the present invention may be implemented using software, hardware, software logic, or a combination thereof. In an embodiment, program logic, software, or a set of instructions are stored on one of various traditional computer-readable media. In the context of this document, a “machine-readable medium” may be any medium or means that may contain, store, transmit, distribute or transport instructions for use by an instruction execution system, equipment or device, such as a computer. A computer-readable medium may include a non-volatile computer-readable medium, which may be any medium or means containing or storing instructions for use by, or for use in connection with, an instruction execution system, equipment or device, such as a computer.

In one embodiment, a circuit or user interface circuit may be provided that is configured to provide at least some of the control functions described above.

If necessary, at least part of the various functions discussed in this description can be performed in a different order than that presented and / or simultaneously with each other. In addition, if necessary, one or more of the functions described above may be optional or may be combined.

Although various aspects of the present invention are described in the independent claims, other aspects of the invention include other combinations of features from the described embodiments and / or dependent claims in conjunction with features of the independent claims, and the combinations are not necessarily explicitly stated in the claims.

Claims (98)

1. Database management system (DBMS), providing customers with interaction with databases containing data and metadata, configured to implement at least the following:

presentation of data at a logical level through a subsystem for constructing a graph-like logical model of a domain and at a physical level through a subsystem for constructing a physical structure of relational tables, where the subsystem for constructing a logical model of the subject area, contains at least the following: a. domain analysis module, configured to present data in the form of use case diagram, b. module for compiling meta-descriptions of a subject domain, configured to create a domain defining a subject domain, c. a module for determining information resources reflecting objects of a subject area, configured to compile a list of information resources reflecting objects of a subject area, d. an attribute assignment module for information resources, configured to assign to each information resource a set of attributes — properties that reflect the state of the information resource, e. a module for establishing links between information resources, configured to establish links between resource objects, while the connections have informational significance and contain the following properties: globally unique identifier for the connection, globally unique identifier of the parent node, globally unique identifier of the child node, pointer to attribute a parent node that refers to a child resource, a multiplicity of relationship that defines a one-to-many relationship or one-to-one relationship, f. a module for defining marker interfaces for information resources, configured to mark information resources with matching attributes for a set of attributes, g. a module for determining classifiers, made with the possibility of marking information resources with specified labels to implement at least the allocation, grouping of information resources, where, as a result of the functions implemented at the ag stages, the subsystem for constructing a graph-like logical model of the subject domain constructs the indicated model, which contains information resources, attributes of information resources and the relationship between information resources, the model is stored in a relational structure and used to create it copies of information resources, where the subsystem for constructing the physical structure of relational tables is configured to divide storage space, at least for tables, database indexes, and also, with the possibility of network distribution of data storage in databases using clustering;

providing access to data through the subsystem of the unified user interface client-server, where the subsystem of the unified user interface contains: a module for creating and managing information display, configured to create information display layout options, with the ability to specify a set of information display elements — widgets that can be specified and replenished, widgets are located in the layout areas, in accordance with various layout options, a module for creating links between the displayed elements of the displayed information, configured to set the relationships between fields, widget columns, module for creating a unified user interface, configured to: creating the specified user interface using the specified modules for creating and managing the display of information, the module for creating links between the displayed information elements, storage of widgets - elements of the displayed information in the given templates and layouts, expanding the functionality of the user interface by adding new functions using dynamically tuned scripts; module for auto-generation of screen forms from preset templates;

a set of modules for implementing applied business logic, allowing at least:

to produce visual formalized construction of business processes by subject matter experts

carry out functional linking of business processes with data management using adapted design tools available to experts and domain analysts

provide a formalized representation of business processes in accepted standards and formats - BPMN (2), XML

through business processes, manage the display of information and the complex behavior of the user interface

through business processes constructed by experts and analysts of subject areas, implement interaction with external data sources and consumers, regulatory procedures

ensuring data separation through the cloud service subsystem - the cloud subsystem that organizes the centralized management of metadata and metamodels - meta descriptions of subject areas containing information resources, attributes, communications, where the cloud subsystem also contains repositories, a user interface for working with repositories, an access control module, an application server, a database server, while the repositories are divided into the following groups:

repository of metamodels of various subject areas,

functional module repository

geodatabase repository

repository of classifiers and directories,

visual solutions repository - application frameworks for various use cases and various subject areas, where the tools of the cloud subsystem are configured to:

create metamodels of new subject areas,

edit existing metamodels,

upload and edit new data: geodata, classifiers and directories,

administer users and access to cloud resources. 2. The system according to claim 1, characterized in that at least query languages are used to access the data, where SQL queries are used at the lower level, and at least the following languages are used at the logical level: Java, Cypher, Resource Query Language (RQL). 3. The system according to claim 1, characterized in that partitioning is used to ensure data separation — separate storage of data and indices, where partitioning is used: at the operational processing level, this is realized, at least by means of persistent storage, a cache in memory; at the storage level it is used by dividing the storage space, by means of clusters and grids; at the level of business logic, it is used by creating certain schemes and structures containing at least the following: geodata, calendars, time series, classifiers and reference books, metamodels, events, default data, business processes. 4. The system according to claim 1, characterized in that the data separation step also includes dividing the data at the meta level into data and metadata, where the metadata consists of a description of subject areas in terms of information resources, attributes and relationships, directories, classifiers. 5. The system according to p. 1, characterized in that the DBMS also contains an operational installation kit, which is created on the basis of information and data received from the cloud service for a specific user and contains: a set of meta descriptions that meet a given subject area and meet user requirements, a set the source data necessary to start operation, a set of functional modules that implements the functional requirements of users. 6. The system according to claim 1, characterized in that access to the system’s data is provided through the kernel, which implements bidirectional transformation of queries and data between the relational representation and the representation in the form of a graph-like logical model of the subject area, and implemented in a managed cache in RAM, where the kernel implements a fixed, uniform, unified interface for manipulating data as nodes of a graph model. 7. The system according to claim 6, in which the data manipulation interface is: a low-level interface between programs, designed for interaction at the level of programs and program modules using various programming languages, a data exchange interface based on the exchange of requests for data and answers in machine readable form. 8. The system according to claim 1, characterized in that the subsystem of the unified user interface is also configured to store data characterizing the design elements of the interface, such as signatures to form fields, headings of forms and tables, in a formalized form. 9. The system according to claim 1, characterized in that through the subsystem of the cloud service, users, after authorization, gain access to the cloud and its resources - repositories, also users create a metamodel in the workspace, filling it with everything necessary, then the metamodel can be exported and transferred to the user’s platform in a working environment, where data copies are created on the basis of the metamodel, with which users work. 10. The system according to p. 9, characterized in that the repositories provide access to at least the following functional modules: editor of information resources and attributes, designer of screen forms, search subsystem, tools for configuring the connection of external systems and databases, visual tools metadata navigation, classifier loader, classifier editor, streaming data visualizer, subject area management tools, namespace management tools, normative management tools accurate information, visual data navigation tools. 11. The system according to p. 1, characterized in that compliance with W3C standards regarding the specifications of ontologies RDF, OWL is ensured. 12. The system according to claim 1, characterized in that it also implements the possibility of a formalized data exchange with other systems at various levels. 13. A method for managing a DBMS that provides clients with interaction with databases containing data and metadata, where the method comprises steps in which at least the following is carried out:

presentation of data at a logical level through a subsystem for constructing a graph-like logical model of a domain and at a physical level through a subsystem for constructing a physical structure of relational tables, where the subsystem for constructing a logical model of the subject area is configured to implement at least the following: a. presenting data in the form of a use case diagram through a domain analysis module, b. create a domain that defines the subject area through the module for compiling meta descriptions of the subject area, c. compiling a list of information resources reflecting the objects of the subject area by means of a module for determining information resources reflecting the objects of the subject area, d. assigning to each information resource a set of attributes - properties that reflect the state of the information resource through the module of attribute assignment to information resources, e. establishing links between resource objects by means of a linking module between information resources, and the relationships are informational in importance and contain the following properties: globally unique identifier for the link, globally unique identifier for the parent node, globally unique identifier for the parent node, pointer to the attribute of the parent node, which refers to a child resource, a multiplicity of relationship that defines a one-to-many relationship or one-to-one relationship, f. marking information resources with matching signs for a set of attributes by means of a module for specifying marker interfaces for information resources, g. marking of information resources with given marks by means of the classifier definition module, where such marking is carried out for at least allocation, grouping of information resources, where, as a result of the functions implemented at the ag stages, the subsystem for constructing a graph-like logical model of the subject domain constructs the indicated model, which contains information resources, attributes of information resources and the relationship between information resources, the model is stored in a relational structure and used to create it copies of information resources, where the subsystem for constructing the physical structure of relational tables is configured to divide storage space, at least for tables, database indexes, and also, with the possibility of network distribution of data storage in databases using clustering;

providing access to data through the subsystem of the unified user interface client-server, where the subsystem of the unified user interface is configured to: creating options for displaying information, with the ability to specify a set of information display elements - widgets that can be specified and replenished, widgets are located in the layout areas, in accordance with various layout options through the module for creating and controlling the display of information, set relationships between fields, widget columns using the module for creating links between displayed elements of displayed information, the implementation of the following steps through the module creating a unified user interface: creating the specified user interface using the specified modules for creating and managing the display of information, the module for creating links between the displayed information elements, storage of widgets - elements of the displayed information in the given templates and layouts, expanding the functionality of the user interface by adding new functions using dynamically tuned scripts; module for auto-generation of screen forms from preset templates;

a set of modules for implementing applied business logic, allowing at least:

to produce visual formalized construction of business processes by subject matter experts

carry out functional linking of business processes with data management using adapted design tools available to experts and domain analysts

provide a formalized representation of business processes in accepted standards and formats - BPMN (2), XML

through business processes, manage the display of information and the complex behavior of the user interface

through business processes constructed by experts and analysts of subject areas, implement interaction with external data sources and consumers, regulatory procedures

providing data separation through the cloud service subsystem - the cloud subsystem, which organizes the centralized management of metadata and metamodels - meta descriptions of subject areas containing information resources, attributes, communications, where the cloud subsystem also contains repositories, a user interface for working with repositories, an access control module, an application server, a database server, while the repositories are divided into the following groups:

repository of metamodels of various subject areas,

functional module repository

geodatabase repository

repository of classifiers and directories,

visual solutions repository - application frameworks for various use cases and various subject areas, where the tools of the cloud subsystem are configured to:

create metamodels of new subject areas,

edit existing metamodels,

upload and edit new data: geodata, classifiers and directories,

administer users and access to cloud resources. 14. The method according to p. 13, characterized in that at least query languages are used to access the data, where SQL queries are used at the lower level, and at least the following languages are used at the logical level: Java, Cypher, Resource Query Language (RQL). 15. The method according to p. 13, characterized in that to ensure the separation of data, partitioning is used — separate storage of data and indices, where partitioning is used: at the operational processing level, this is implemented, at least by persistent storage, a cache in memory; at the storage level it is used by dividing the storage space, by means of clusters and grids; at the level of business logic, it is used by creating certain schemes and structures containing at least the following: geodata, calendars, time series, classifiers and reference books, metamodels, events, default data, business processes. 16. The method according to p. 13, characterized in that the data separation step also includes dividing the data at the meta level into data and metadata, where the metadata consists of a description of subject areas in terms of information resources, attributes and relationships, directories, classifiers. 17. The method according to p. 13, characterized in that the DBMS also contains an operational installation kit, which is created on the basis of information and data received from the cloud service for a specific user and contains: a set of meta descriptions that meet a given subject area and meet user requirements, a set the source data necessary to start operation, a set of functional modules that implements the functional requirements of users. 18. The method according to p. 13, characterized in that access to the system data is provided through the kernel, which implements bidirectional transformation of queries and data between the relational representation and the representation in the form of a graph-like logical model of the subject area, and implemented in a managed cache in random access memory, where the kernel implements a fixed, uniform, unified interface for manipulating data as nodes of a graph model. 19. The method according to p. 18, characterized in that the data manipulation interface is: a low-level interface between programs, designed to interact at the level of programs and program modules using various programming languages, a data exchange interface based on the exchange of requests for receiving data and responses in machine-readable form. 20. The method according to p. 13, characterized in that the subsystem of the unified user interface is also configured to store data characterizing the design elements of the interface, such as signatures to form fields, headings of forms and tables, in a formalized form. 21. The method according to p. 13, characterized in that through the subsystem of the cloud service, users, after authorization, gain access to the cloud and its repository resources, users also create a metamodel in the workspace, filling it with everything necessary, then the metamodel can be exported and transferred to the users ’site in a working environment, where data instances are created on the basis of the metamodel, with which users work. 22. The method according to p. 21, characterized in that the repositories provide access to at least the following functional modules: information resource and attribute editor, screen designer, search subsystem, means for configuring the connection of external systems and databases, visual means metadata navigation, classifier loader, classifier editor, streaming data visualizer, subject area management tools, namespace management tools, normative management tools internal information, means for visual navigation data. 23. The method according to p. 13, characterized in that compliance with the W3C standards regarding the specifications of the RDF, OWL ontologies is ensured. 24. The method according to p. 13, characterized in that it also implements the possibility of a formalized data exchange with other systems at various levels: information exchange, functional interaction.

Images