SOA. SIEI. Electronic exchange or deception

Now also acute problems of integration and interaction — semantic interoperability (SI, SemanticInteroperability) sets of the created information systems are most relevant. This problem for the program systems (including inherited) used in management of global structures is especially critical: the different international unions, blocks, the states, departments, business structures, the non-state organizations, etc. both on tactical, and on strategic levels of management.

So far in the world there are no effective approaches to problem solving of sharing of a set of the programs developed on different hardware-software platforms and languages at different times by different developers in different architecture.

Software packages of the companies Microsoft SAP, Oracle and other producers represent sets of modules on separate tasks: HR, MR, FI CRM SPM MES PLM, BI… In them there are also problems of integration both in these conditionally "monolithic" systems, and with external systems of other producers. Over time, because of numerous merges, absorption, the financial market monopolization of the IT, a problem of integration of everything purchased even in the companies Microsoft, SAP, ORACLEI of others only accrue and become unsolvable.

Besides, all software products presented at the market require from business processes to correspond to a tough framework of the proposed archaic architectural concept created 5-10-30-50 years ago not adequate to dynamic changes of real life.

Interoperability and interaction

In modern determination of "Semantic interoperability of information systems" (Wikipedia) the emphasis is placed on visible and smaller (though very difficult) a part of a task: on data exchange between information systems and complete automatic interpretation by the accepting system of sense of the transmitted data.

The English word "iteroperabelnost" on deep sense conceptually differs from the Russian word "interaction". So Inter means "between", i.e. approach "cements" establishes the principle of separation something whole on a part — subsystems. Borders of these subsystems are defined. And already then, for integration again into whole, attempts are implemented by something to exchange — "among themselves", but at the same time it is necessary to manage somehow to execute this exchange consciously and in coordination on the substance of the solved case.

In this case in development of modern information technologies of integration (intelligent interaction) such clear word "exchange", but not on the word "sense" which it is really uncommon became key, individually and in detail should be defined when implementing each specific type of exchange. It seemed, the correctness of the selected approaches on implementation of "exchange" lies on a surface, especially when the following analogies are given: people as complex systems, only this way among themselves also communicate — message exchange and somehow understand each other.

Unlike it the Russian word "interaction" initially defines essentially other purpose — something is jointly interconnected to do "seamlessly" productively functionally using information management systems, i.e. the English words "trans" (end-to-end) and "active" (action) are closer to it.

At the same time understanding comes that the efficiency and human intelligent interaction lies much more deeply than primitively considered message exchange. For implementation of conscious interaction of people — first of all it was necessary their (people) systemically in identical rules to create and provide harmonization at the same time as identity, so proximity of our human genes in DNA. As capability to communicate with a dog or a cockroach at us also is, and here with semantic interaction - already on orders it is more difficult.

The fragmentariness of formulation and archaism of setting of a SI problem influences today and search of approaches, and lack of effective solutions which analysis we will give below.

Speaking about semantic interoperability appropriate to separate all software products functioning as a part of information management systems into two classes:

• infrastructure software,
• functional software.

Software products of which the abstractness of a concept of the processed information is characteristic belong to the infrastructure software. Classical examples — the word-processor, the tabular processor, the database management system (DMS), a mail system, etc.

The software products processing information according to its semantics, a form, behavior, knowledge of physical thing of management belong to the functional software.

For infrastructure programs everything is safely including in sense of interoperability. Really, the interoperability of the word-processor and a mail system is so logical, seamless, deep and adequate that millions of people use them, without thinking.

For functional programs there is absolutely other situation in connection with their following features:

• knowledge of a subject and processes of management systems is distributed between a data structure, forms of representation and algorithms of processing,
• data structures and user interfaces contain the implicit assumptions of methods of their processing for accomplishment of any subject-oriented function,
• methods of data processing and form of their visualization are always strictly connected with their storage,
• data processing is practically always based on functional activity of a control object,
• functioning of the program is specified by the subject-oriented user interface.

So functional information systems, including all the components, are always the semantic, subject-oriented systems.

The interoperability of functional information systems can and should be only semantic.

The mankind, since development of the second separate functional program system, had a problem of their integration.

The following methods of ensuring integration and interaction were applied:

Direction 1: Integration of functional information systems with implementation of subsystems of export import of "electronic documents" for each couple of different integrated systems. So formats, structure, syntax, semantics, regulations of exchange, etc. of these messages (directives, orders, references, forms, orders, instructions, plans, reports, reports, reports, documents, etc.) circulating between functional information systems, the provided certain "black boxes" were individually developed for ensuring interoperability of intersystem messages (these methods are used the last sixty years).

Direction 2: Integration of the functional systems using the "universal" environment of message exchange. So ensuring interoperability of the different systems besides provided by "black boxes" through the additional integrating systems which can include adapters, hubs, data transmission mediums, uniform storage of the general data, business modellery, the ontologies of bases of data/knowledge transferring the services accepting services, etc. Besides certain Novaya Gazeta service the focused architecture (SOA — Service-oriented Architecture) which had to provide fantastically creation of a common information space was offered and help with problem solving of incompleteness, not integrity, inconsistency, redundancy, incomparability, etc. of these different functional systems (these methods are offered the last ten years).

IT leading of IBM, Microsoft, ORACLE, SAP and others make multi-billion investments in these directions of integration, are released and software products in architecture of SOA are advertized.

But the goals of effective semantic interoperability of a set of functional information systems are still achieved by nobody. Why?

The problem of semantic interoperability becomes similar to problems of combinatory tasks. In ensuring interaction of each specific couple of program systems success can be reached (and it is often achieved). However this approach is not scaled on an end-to-end system and ensuring dynamic semantic interoperability on complexity in any way begins to exceed total complexity of development separate program a component.

All presented solutions do not "live" in dynamics of change of requirements to the integrated information systems, do not support lifecycle the functional systems, require enormous costs of resources for one more type of activity – support of interoperability, do not consider a factor of uniform time in maintenance of integrity and comparability of these different integrated systems, are not effective at quantity of systems more than 3, are not reliable, do not resolve in a complex security issues and many other things.

Besides, people, think again, open eyes, well why all do not notice complete absurdity of SOA offers, including leaders of information technologies: IBM, Microsoft, ORACLE, SAPI of others!

It is impossible to provide that the problem of semantic interoperability integrated N information management systems can be solved, having "arithmetically" added to them A M more of the new program systems providing their consolidation.

Why SOA slips. SIEI

The lack of any visible progress in application of SOA to us is explained by the fact that SOA is, it appears, in general "not technology and not a set of software tools, it is only approach or a paradigm of the organization and use of the distributed information resources, formations (i.e. new programming and reprogramming! — the author's note) a layer of so-called "services" which "belong" to the different functional systems and can be caused programmatically for interaction with them". And all world vendors began to dream on the raspiarenny subject SOA.

At the same time types of services which should be recreated in each functional program, for example, are offered such: "Web service client of receiving metadata, Web service client of obtaining statuses, Web service client of data acquisition, subsystem of registration of a request, Web service client of reception of an application, Web service client of providing metadata, Web service client of transfer of the statuses, Web service client of data transmission, magazine of control and others".

So for example, in a case with implementation of the Uniform portal of public services of the Russian Federation it is supposed that the system of interdepartmental electronic interaction (SIEI) will act on the basis of SOA as follows: the request for service completed in electronic form on the portal is transferred to service of department and further to processing by internal systems. Obviously, at variety and heterogeneity of departmental information systems, for example, to obtain data from one system, and then to process them in another and to analyze in the third, it is necessary to know features of implementation of all three systems during creation of the accepting and transferring services.

And, further, at each change of the legislation and optimization of activity of the state, it is necessary to enter changes now not only into the corresponding departmental functional information systems, but also into the relevant accepting and transferring services.

By the way, for information, the State Duma of the Russian Federation adopts about 3000 legal acts a year. And how many 83 regions, and how many in day, and what number of significant changes in each document?

What is regulated by a SOA paradigm as she solves these problems what maintenance of a set of the legal acts and so-called standards adopted in the world, including, for example, in Russia concerning implementation SIEI using architecture of SOA?

Let's try to generalize these numerous multipage standards, regulations, rules, technical requirements, protocols, methodical materials which are written off from the "international" documents.

Let's provide their far incomplete list, including documents of the Organization for development of standards of the structured information — Organization for the Advancement of structured Information Standards (OASIS), Consortium of the World Wide Web - World Wide Web Consortium (W3C) which the developer of functional information systems and new services of exchange should consider:

• Hypertext transfer protocol, Hypertext Transfer Protocol (HTTP)
• Comments of engineering group of designers of an information communication network Internet, RFC (Request for Comments)
• Security of the Transport layer, TLS (Transport Layer Security)
• The protocol of the protected connections, SSL (Secure Socket Layer)
• A set of the protocols for ensuring data protection transferred under the internetwork protocol, IPsec (IP Security)
• Support system of namespace, DNS (Domain Name System)
• Specification of the universal description, search and integration of electronic services of version 2.0 (Universal Description Discovery and Integration, UDDI 2.0)
• The exchange protocol the structured messages, Simple Object Access Protocol, SOAP
• Language of the description of electronic services of version 1.1, Web Services Description Language, WSDL 1.1.
• Basic profile of interoperability of version 1.1, WS-I Basic Profile 1.1.
• Policy of usage of electronic services of version 1.2, Web Service Policy 1.2.
• Interoperability profile on transfer of binary data, WS-I Attachments Profile 1.0.
• The optimized mechanism of transfer of binary data in the structured messages of SOAP, Message Transmission Optimization Mechanism
• Profile of comparison of data of version 1.0, WS-I Simple SOAP Binding Profile 1.0.
• Specification of the universal description, search and integration of electronic services of version 3.0, Universal Description Discovery and Integration, UDDI 3.0.
• Rasshiryaemyyazykrazmetki of XML, Extensible Markup Language
• Expanded language of the description of data schemes versions not lower than 1.0, XML Schema 1.0, XML Schema 1.1.
• Expanded language of the description of stylesheets of version 1.1, Extensible Stylesheet Language, XSL v. 1.1.
• Rules of formatting and data translation of XSL Transformation, XSLT
• Language of the description of data schemes, XML Schema Definition, XSD
• and many others.

About what it is so numerous, verbose and is globally pathos?

Let's try to state in human language an essence well at least in relation to native SIEI.

All these documents contain the description of the general approaches and the principles to data exchange function implementation including: "formation, maintaining and updating of the unified register of Participants SIEI providing the regulated providing access to it; implementation of procedures for granting of electronic services to Consumers, including providing integration logic of electronic service and calls of necessary services of Suppliers in the required sequence set by interdepartmental administrative regulations of execution of public service (function); sale of mechanisms of the publication of electronic services of the Suppliers available to use by the SMEV electronic services; sale of mechanisms of receiving, processing and the guaranteed delivery of electronic messages within interdepartmental information exchange with ensuring fixing of time, with ensuring integrity, authenticity, authorship and possibility of providing the necessary certificates allowing to recover the course of events in the course of rendering the public and municipal services in electronic form and at interdepartmental information exchange; ensuring protection of the transmitted data against unauthorized access, distortion or blocking; maintaining the magazine of interdepartmental information exchange of Participants through SIEI; formation of the necessary reporting on process of information interdepartmental exchange" and many other things same quality.

Again it is difficult? And told is higher and higher regulates so far only the procedure of exchange of the following types of messages between really used functional information systems:

• the electronic message using which the Consumer announces SIEI the intention to receive electronic service;
• the electronic message using which SIEI returns to the Consumer the result of providing electronic service;
• the electronic message using which SIEI announces the Supplier need to provide electronic service;
• the electronic message using which the Supplier returns SIEI the information required or the result of accomplishment of action according to the type of service requested SIEI;
• different types of office electronic messages.

So attempts to standardize and regulate, to some extent, only mass construction of "electronic carts of exchange" become (without the main thing — contents!) by the coach box sizes, parameters of wheels, quality of lubricant, hinged engines, speeds, addressees, "electronic" signatures to the "transported" sendings, etc. Yes, it is possible to standardize a type of a mail envelope, but receivers and senders need another — sense of the letter.

And what in these binding documents in essence, to a subject, sense, semantics, functions, data, business processes, objects and management processes, real life (how still to cry out about the main thing?!) implementations of electronic interdepartmental interaction of functional information systems when ensuring electronic services? Anything! Words!

The effectiveness of the sales activity of the systems of interdepartmental electronic interaction using a SOA paradigm is estimated by the international community amount of requests for exchange, at the same time neither their sense, nor expediency, nor synchronization of transmitted data on time and quality is considered. Ministers and IT specialists vigorously and joyfully report — at us hundred thousand requests, one million requests, "квадраллион" requests come... Reminds nothing?

Boasting on a global scale: "... couriers, couriers, couriers... you can imagine, thirty five thousand some couriers!"

And at such SOA implementation of integration and interaction of information systems someone else hopes to receive the complete consistent uniform, synchronized on time, reliable information managerial space? Never!

I will repeat, the strategy of development for information technologies focused on SOA is the deadlock.

Is not present in SOA of basic solutions on implementation of high dynamics of structural change of informational and functional space. How should already functioning react to change of requirements it is distributed the developed separate services? Again to change them, to test, to finish iteratsionno and to be late constantly catastrophically, transferring to the consumer always a "stale" product, yesterday's relevance.

Use of SOA creates problems of formation both uniform information, and a function space as there are same problems of uncontrollable redundancy, inconsistency, incomparability, incompatibility, etc. of separately programmable functions, services.

There are also no conceptual solutions on problems of semantic integration of information systems of different producers which everyone in own way implemented the service-oriented architecture.

SOA — the excellent global development business project of IT for a new type of mastering of money of the customer — at first sold it many different modules of programs (promising the fairy tale), now suggest to buy, for implementation of the same fairy tale, for expensively to them a lot more SOA services...

So, we sum up a number of the main unsolvable problemv achievement of semantic interoperability of separate functional information systems, including using architecture of SOA:

• the repeated excess incomparable description in different functional information systems of the same objects and processes of data domain;
• different time of making changes in identical data in the different systems, basic impossibility requests and exchange transactions to synchronize all information space on time and data and consequently to provide reliability of the processed and transmitted data, a common information space;
• conceptual incompatibility, not integrity, inconsistency, etc. of the description and implementations of common parts of data domain: a data structure and methods of processing, as well as data in storages of the different systems;
• additional programming in a SOA paradigm on two and more accepting and transferring services for each departmental functional program (depending on quantity of external information systems with which it is necessary to implement exchange);
• at each change of requirements repeated rewriting, testing, input in trial and commercial operation of both functional program systems, and the accepting and transferring services;
• need of the nadsistemny description and further maintenance for current status of the generalized knowledge of data processing arbitrarily distributed between structure, methods and interfaces in the different integrated systems;
• existence in the systems of own data warehouses excludes a possibility of simple stream processing;
• the distributed independent parallel development of modules of the complex functional systems leads to the fact that development of the system of 1 one large part of data domain inevitably is in a conflict with simultaneous, but separate system development 2 other large parts of data domain that amplifies further subjective aspects of difference in coding of programs;
• ensuring interaction of systems among themselves becomes one more "type of activity" exceeding maintenance of operation and development of the systems on time and other resources;
• deceleration and restriction of speed of modification in response to the increasing growth of dynamics of changes of real objects and management processes, at increase in quantity of the integrated systems and increase in their complexity;
• problems of ensuring interoperability of software packages lead to significant falling of operability of information systems in general;
• absence and basic impossibility of implementation of an end-to-end system of security of fragmentary program systems and intersystem integration information space;
• low reliability of the difficult software packages requiring integration which is defined by the minimum level of reliability which is logging in it;
• high finance, temporary, personnel and other costs on development, upgrade, maintenance and operation;
• and many other problems.

So far the majority of efforts in researches is directed to creation of universal gateways and technologies of formation and maintenance of "communication environment" between incomparable programs.

Discovery of secretion of such universal "glue" for water, a stone, fire, gas, paper, acid, etc. is expected.

But attempts of integration of application programs at the level of creation of universal "interfaces of black boxes" preserve and aggravate a problem of creation of uniform reliable informational and functional space and effective adequate management even more.

New paradigm

The problem of ensuring effective semantic interoperability of three and more different dynamically changeable functional information management systems is essentially not solvable.

When implementing integration of information systems at the principles of message exchange synchronization of data of the distributed information storages in uniform time and space is not achievable.

Uniform reliable information space cannot be received in a separation from creation of a uniform function space.

It is offered not to solve problems of exchange at all, including messages. Pass from ensuring semantic interoperability to the main thing: create at once uniform complete adaptive informational and functional network-centric managerial space.

Therefore in GGG technology the paradigm of the solution of a SI problem of integration is changed — in its network-centric information GGG management systems just conceptually does not exist.

However, what to do with the legacy software? It is impossible to pass with everything to new network-centric G3aarkhitekturu together suddenly.

Therefore in the offered innovatsionnykhggg-technologies two problems were solved:

• Create "ideal" technology of the "seamless" Future;
• Create technology of Evolutionary Migration in the Future.

Are developed for the solution of these tasks and the following technologies are industrially used:

1. Creation of "ideal" technology of the "seamless" Future includes the following main GGG technologies:

• G3A — network-centric architecture of the global information management system,

• G3LC — "biological" two-stage lifecycle of information systems,

• G3L — visual language of the description of uniform "genesis" of network-centric information systems;

• G3EM — collective evolutionary creation of a uniform adaptive semantic model of our cumulative knowledge – "DNA" of projectible information systems;

• G3AP — machine programming of adaptive information network-centric management systems on the basis of design model (the hypergraph of classes of Khokhlova) described in unified virtual environment of evolutionary modeling;

2. Creation of technology of Evolutionary Migration in the Future — the system of transition to GGG technologies with gradual "painless" substitution of the present, including legacy, on the innovation future using G3I technology.

• The G3I — GGG technology performing evolutionary "projection" — the description of the external operating legacy information systems in a modern language of G3L using special classes of the hypergraph of Khokhlova in the network-centric G3EM environment. Machine programming of G3AP creates "the" new user interfaces to external systems, besides data of external systems are used "on reading" in different functions of processing.

• Gradual evolutionary substitution is implemented, i.e. "germination through" external systems, absorbing knowledge accumulated in them. At the same time substitution happens the quicker, than legacy systems integrate more and more dynamically there is a change of requirements to them.

Transition from primitive message exchange — to the main thing is performed: to the joint interconnected collective work.

Experience of use of the "absorbing" integration of G3I showed what terms and cost of integration decreases at increase in quantity of the integrated systems, i.e. the inversely proportional dependence is observed. Why?

In the integrated information systems catastrophic volumes of redundancy — repeated duplication of the discordant description of identical objects and processes of the real world are historically chaotically created.

G3I effectively eliminates this redundancy by analogy with optimal simplification bulky, at first frightening by the sizes, difficult algebraic expressions which all of us at school so dashingly led to an elementary type.

Over time, when using G3I, from each new integrated external information system occasionally you will gather nothing new, well there can be a number of properties, a method, a data set.

In the eyes the artificial complexity generated by fragmentary building information systems "thaws". The real complexity of the complete interconnected multidirect systems of management is shown, the look on the true, sharply demanded and not solved problems is focused.

Integration of G3I is forced temporary komponenty evolutionary "besshokovy" transition to a single new global network of Graph.

See Also

The book in web