<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The concept of a software complex for interdisciplinary problems solving based on self-organization principle</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Matrosov Institute for System Dynamics and Control Theory of Siberian Branch of Russian Academy of Sciences</institution>
          ,
          <addr-line>Irkutsk, Lermontova, 134, Russia idstu.irk.ru</addr-line>
        </aff>
      </contrib-group>
      <fpage>0000</fpage>
      <lpage>0001</lpage>
      <abstract>
        <p>The paper presents the concept of a software complex for solving interdisciplinary problems based on self-organization features. In particular, the basic principles and stages of self-organization process during solving an interdisciplinary problems of designing complex technical systems, as well as the architecture of proposed software along with some details of implementation are considered. The architecture of the software complex includes subject and problem ontologies, data and knowledge bases, set of "solvers" as well as intelligent scheduler. The intelligent scheduler implements the self-organization algorithm and provides creation the computing environment for solving considered problem using "solvers" as a buildings blocks. The implementation of selforganizing algorithm base on combination of knowledge representation as an ontologies, group decision-making, component and model-oriented approaches. Self-organization features in context of designing complex technical systems task are implemented on the stages of defining the design methodology, determining the source data, solving the problem, and training the system. The intelligent scheduler can analyze the state of current task with set of indicators and manage it through a set of local rules. This paper presents examples of local rules for each stage. The stages specifications in the form of technological diagrams that contains components used ("solvers"), their connections along with the results of their work describe the self-organization process features related to each stage. The software implementation are based on the capabilities of the used platform for creating knowledge-based systems developed by the authors and component approach applied to specialized component development.</p>
      </abstract>
      <kwd-group>
        <kwd>Interdisciplinarity</kwd>
        <kwd>Complex Technical System</kwd>
        <kwd>Design</kwd>
        <kwd>Information Technology</kwd>
        <kwd>Subject Ontology</kwd>
        <kwd>Problem Ontology</kwd>
        <kwd>Self-Organization</kwd>
        <kwd>Local Rules Of Self-Organization</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The task of designing complex technical systems is an interdisciplinary one, which
requires processing huge amounts of data and knowledge of various scientific,
technical and scientific-technical disciplines. At the stage of creating technical systems,
Copyright © 2020 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).
there is always some uncertainty of strength, resource and structural reliability and
safety due to imperfection and violation of methods and means of creating objects, the
inability to adequately test elements and components of complex unique technical
systems, which leads to their sudden failures. Due to incompleteness of some sets of
data and knowledge belonging to different disciplines, the relationships between them
can not be completely defined, which makes it difficult to formulate both disciplinary
and interdisciplinary goals and may be one of the reasons of incorrectly
interdisciplinary tasks formulation.</p>
      <p>These problems determine the relevance of the task of creating the technology and
the appropriate software complex ensuring the teamwork of a specialists (experts)
from various disciplines for solving interdisciplinary problems related to the design of
complex technical systems. The software complex should meet the following
requirements:
• common space for information exchange including mathematical, methodological
and software areas;
• interaction between specialists from the various disciplines;
• formulation of the one cooperative view point for the multiple of the expert groups;
• processing of heterogeneous information, along with data of unknown or uncertain
at design time structure model;
• the possibility of using heterogeneous software (open source code, third-party
programs, own programs, hybrid systems, etc.);
• the user requirements for skills in programming and knowledge representation
languages are limited to interaction with the software complex interface in domain
terms;
• decision support at all stages of problem solving;
• high level of the automation during implementation of the new problem solving
methods and adaptation of existing ones to any changes in the initial data.
• Implementation of these requirements is based on the following approaches:
• common space for information exchange by ontological modeling,
• interaction between specialists from the various disciplines by the methods of
group decision-making,
• use of heterogeneous information and software by the separation of data
representation and processing methods according to model-oriented and component-based
software development approaches,
• decision making support by applying knowledge processing methods (for example,
expert systems),
• high level of the automation by applying self-organizing algorithms.</p>
      <p>
        Currently, there are methods and models of artificial self-organization for the
formation of coordinated solutions and control of complex objects [
        <xref ref-type="bibr" rid="ref1 ref2 ref3">1, 2, 3</xref>
        ]. As follows
from works [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ], a system can be considered self-organizing if it acquires some
spatial, temporal or functional structure without specific external influence. So the
artificial self-organization can be represented as a process of the automatic
modification (adaptation) of the action plan (decision-making algorithm) when changing the
properties of the controlled object, the control goal, or environmental parameters are
meet.
      </p>
      <p>
        It is proposed to acquire the solution of the interdisciplinary problem as the schema
of interaction between "solvers" of disciplinary and interdisciplinary problems of
different competence and specialization by application of the self-organizing
algorithm [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The mechanism of self-organization provides organization the available
"solvers" into computational structure according to the parameters of the problem
model and object to study like the object properties, influencing factors, etc.
      </p>
      <p>The obtained computational structure can be automatically reorganized in case of
any changes in initial states.</p>
      <p>The purpose of this paper is to present the concept of a software for solving
interdisciplinary problems of designing complex technical systems.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Architecture of the software complex</title>
      <p>The conceptual architecture of a software complex for creating and supporting the
self-organizing systems for solving interdisciplinary tasks is defined:
,
(1)
where IS – software complex, E – experts, the Dt – database, Knl – knowledge base,
Ont – the ontology of domain and problem areas, P – tasks,
– task hierarchy, Slv – "solvers", RIS – the relationships between components IS, in
particular, between experts and tasks, between tasks, between tasks and
"coordinators", between tasks and "solvers", Crd – "coordinators" of the task, Ind – state
indicators IS,</p>
      <p>a set of indicators to display of the current state of
task execution process, Pln – an intelligent scheduler that implements a
selforganizing algorithm SAlg for solving an interdisciplinary task based on local rules
LRule, UI a user interface.</p>
      <p>
        The "solvers" of software complex can be divided to the basic ones and user ones
. The basic "solvers" provides the set of build-in data and
knowledge processing operations [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]: data control – SlvDt, ontological modeling –
SlvOnt, rule-based reasoning – SlvKnl, organization of two-way data exchange – SlvCom,
dialog interaction with the user – SlvUI, specification of operations based on visual
workflow notation – SlvOp.
      </p>
      <p>SlvOnt provides the creation of an ontological (conceptual) model for the selected
domain with a specified level of detail.</p>
      <p>SlvKnl provides creation of knowledge bases by visual construction of rules and
formation of initial conditions using obtained domain ontology as initial data. In
current implementation Drools system is used as rule-based reasoning engine so the code
generation function results are in format of Drools knowledge representation
language.</p>
      <p>The SlvCom use WebSocket protocol to provide the ability to fast, asynchronous
data exchange between users and/or "solvers" of the complex, as well as the server to
client interaction with a server as initiator.</p>
      <p>SlvUI provides automatic creation of user interface based on meta descriptions
using graphical controls to display the data in a simple and/or nested tables, semantic
networks and elements for selection one/multiple values from the list, and the
standard set of elements for simple data types (one/many-lines input fields, the date, time,
datetime controls, checkbox for Boolean type, etc.).</p>
      <p>SlvOp has two main functions: the creation formal specification of actions plan for
solving a certain domain problem using visual workflow notation, and the second is
the implementation of the obtained specification using the other "solvers" of software
complex and functionality of the available external systems.</p>
      <p>
        Pln [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] provides an actions plan of the solving domain task process as the
interaction schema between "solvers" that displays both the control flow and data flow
according to model of the task. During the task execution process Pln monitors the state
of the task and in case of necessity adjusts actions plan by results of applying a local
rules to the current state according to the values of the indicators.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Stages of self-organization algorithm</title>
      <p>Let's consider the stages of the proposed algorithm for self-organization of the
software for solving an interdisciplinary problems of designing technical systems. The
algorithm has four main stages:
1. Self-organization at the stage of creating a software system (see Fig. 1).</p>
      <p>
        This stage implements the following:
─ Definition of the design methodology. By defining the methodology, we mean
describing the stages and tasks of the design process for an object or a certain class
of objects. Design stages and tasks are formalized in the task ontology as a
hierarchy of conceptual tasks [
        <xref ref-type="bibr" rid="ref6 ref7 ref8">6-8</xref>
        ], where the hierarchy shows the part-whole
relationships. The actions plan of abstract kind is formed using visual workflow notation
based on the obtained task hierarchy.
─ Detailed formulation of tasks [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], according to the design methodology. At this
stage, the conceptual tasks defined in the previous stage are being specified. Such
type of specification consists of related domain concepts and rules along with
descriptions of the methods available for considered tasks. The obtained specification
would considered by the related group of experts (domain specialists) to retrieve
the common view.
─ Definition of methods for solving tasks. The algorithms of methods for solving
tasks that been described in the task ontology [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] are defined using visual
workflow notation. A mandatory part of this stage is the description of actions in the
case of obtaining unsatisfactory result for one or several subtasks. Moreover, the
alternative algorithms that based on other implementations or provides a different
accuracy, and so on can be added to the method description. The method definition
is also have be adjusted to the common opinion by the group of experts.
Domain
ontologyconcepts of the
design process
Problem ontology
– tasks of the
design methodology
Specification of
the methodology
model
проектиро
      </p>
      <p>вания
Specification of
self-organization
defining of the
methodology
Specification of
self-organization
of the learning
process</p>
      <sec id="sec-3-1">
        <title>Defining the design methodology</title>
        <p>Formulation of
concepts
методологии
проектиро</p>
        <p>Formulation of
tasks according to
the design
method</p>
        <p>ology
Defining methods
algorithms for
solving tasks
The creation of</p>
        <p>
          «solvers»
Approval of
elements of the
methodology with a
group of experts
Design system learning
─ Creating "solvers" - software components that implement the proposed methods for
solving tasks. This stage is important in case of the methods for processing weakly
structured information based on artificial intelligence methods, such as expert
systems [
          <xref ref-type="bibr" rid="ref10 ref11 ref9">9, 10, 11</xref>
          ].
        </p>
        <p>
          Within the first stage, the model of the design methodology is formed while the
self-organization algorithm is utilized for user support during the describing concepts,
tasks, methods, “solvers” and adjusting of descriptions [
          <xref ref-type="bibr" rid="ref12 ref13 ref14">12, 13, 14</xref>
          ].
2. Self-organization at the stage of setting up a software system (see Fig. 2). This
stage includes:
        </p>
        <p>Domain ontology –
concepts of the
design object
Problem ontology –
tasks of a specified
design methodology</p>
        <p>Specification of a
model of a specified
design methodology
Specification for
selforganization of initial</p>
        <p>data definition
Specification of
selforganization of the
approval process
Specification of
selforganization of the
learning process</p>
      </sec>
      <sec id="sec-3-2">
        <title>Defining the initial data of the design process</title>
        <p>Defining the
structure and
properties of an</p>
        <p>object
The formation of
the task structure
of the design</p>
        <p>object
Specification of
design tasks</p>
        <p>объекта
Defining of
initial data for
design tasks
Choosing
methods for
solving tasks
Approval of task
elements with a
group of experts
Design system
learning
─ Input of initial data, including a description of the structure and properties of the
object under design.
─ Defining the specific structure of tasks / subtasks according to the specified
structure and properties of the object under design. Self-organization at this stage is the
user support during analysis of the description of the object structure in the
ontology and the formation of a sequence of tasks for each element of the hierarchy
according to structure of the object under design and the description of the
methodology.
─ The obtained task structure are expanding by concrete data (instances of the
domain ontology concepts) about the object under design. Also the correspondence
between the domain concepts and the concepts from the task description is
established.
─ Determination the runnable methods of solving tasks and most effective ones from
them based on the available initial data. The intelligent scheduler is used to check
whether the initial data is available to evaluate whether the method can be launch,
and whether the methods are runnable with the current input parameters. For
example, with the domain ontology, knowledge bases for expert systems are
formulated, methods are ranked by efficiency and accuracy, and the selection of the
runnable methods is performed.</p>
        <p>As a result of this stage, a models of the specific tasks is formed for a given object.
3. Self-organization at the stage of exploitation of the software system (see Fig. 3).</p>
        <p>This stage includes:
─ Adjustment of task statements based on the results of their executions and expert
suggestions,
─ Changing methods for solving tasks based on the results of the executions and
expert suggestions: reducing performance requirements, addition a new method or
a new algorithm for implementing the method.
─ Adjusting the actions plan for task solving based on the results of the executions
and expert suggestions.</p>
        <p>
          The process is controlled with set of indicators: the progress indicator, risk
indicator, the indicator formulation of the task etc. [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
        </p>
        <p>The result of this stage is the adjusted model for solving the specific task.
4. Self-organization during the learning phase of a software system:
─ Learning of the system as a result of analysis, extraction and accumulation of
information (rules, precedents) at each stage of the software system operation.
─ Use of knowledge at all stages of self-organization to improve efficiency.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Knowledge structure of the scheduler</title>
      <p>The main component of the software complex that implements self-organization
algorithms is the intelligent scheduler. Self-organization is based on the analysis the states
of set of indicators and the local rules.</p>
      <p>The structure of knowledge base containing the local rules corresponds to the
stages of self-organization, in particular, consists of following parts:</p>
      <p>Specification of</p>
      <p>a model of a
specified design</p>
      <p>methodology
Domain
ontology – concepts of
the design
ob</p>
      <p>ject
Problem
ontology – tasks of a
specified design</p>
      <p>methodology
Specification of
self-organization
of analysis of
results of task</p>
      <p>solving
Specification of
self-organization
of the approval</p>
      <p>process
Specification of
self-organization
of the learning
process</p>
      <p>Solving design tasks
Creating a task-solving</p>
      <p>sequence
Performing a
tasksolving sequence
Analysis of the results</p>
      <p>of solving tasks
Adjusting the task</p>
      <p>statement
Approval of task
elements with a
group of experts</p>
      <p>Design system
learning</p>
      <p>Scheduler
self-organization
of the task-solving
process
• self-organization in the process of determining the design methodology,
• self-organization in the process of defining the initial data,
• self-organization in the process of description the task solving algorithm,
• self-organization in the process of knowledge adjustment by expert and group of
experts,
• self-organization in the process of the system learning.</p>
      <p>Here are examples of local rules.</p>
      <p>Rules for self-organization of the process of determining the design methodology:
IF the stages of the methodology are not defined, THEN
start the procedure for defining the stages;
IF the task of the methodology stage is not defined, THEN
start the task definition procedure;
IF the requirements for the object under design are not
defined, THEN launch the requirements definition
procedure;
and others.</p>
      <p>Rules for self-organizing the initial data definition process:
IF the initial data is not defined, THEN start the
initial data definition procedure;
IF the result of the procedure for determining the
initial data is not feasible, THEN start the procedure for
changing the model of the methodology;
and others.</p>
      <p>
        Rules for self-organization of the problem solving process [
        <xref ref-type="bibr" rid="ref15 ref3">3,15</xref>
        ].
      </p>
      <p>IF the formulation of the methodology tasks is complete
AND the definition of the initial data is complete, THEN
the procedure for solving the design problem is started;
IF the result of solving the task is unsatisfactory (for
example, it does not meet the risk criteria), THEN launch
a procedure to identify the reasons for unsatisfactory
solution of the task;
and others.</p>
      <p>
        Rules for self-organization of the knowledge adjustment process [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]:
IF there is an incompleteness of the task formulation,
THEN launch a procedure to reduce (resolve) the
identified incompleteness, depending on the type of incomplete
information;
IF there is an incompleteness of the source data of the
task, THEN launch the procedure to agree on the opinions
of experts on the new source data;
IF there is an incompleteness of knowledge (templates,
rules, precedents and etc.) of the task, THEN launch a
procedure to agree on the opinions of experts on new
knowledge (templates, rules, precedents and etc.) of the
problem;
IF there is an incompleteness of data on the methods of
the problem, THEN launch a procedure to agree on the
opinions of experts on new methods of the task;
and others.
      </p>
      <p>Rules for self-organization of the learning process:
IF a new task formulation is being created, THEN the
procedure for collecting expert opinions on the reasons for
creating a new task formulation is launched AND the
casebased knowledge base of task formulations is updated;
IF you are forming a new sequence of methods of solving
the task, THEN start the procedure of collecting expert
opinions on the reasons for the creation of a new
algorithm for solving the task AND funding the
caseknowledge-base algorithms (methods) of solving the task;
and others.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Features of software implementation</title>
      <p>
        The software implementation of the software complex is proposed to be performed
using the capabilities of the platform for creating knowledge-based systems [
        <xref ref-type="bibr" rid="ref11 ref5">5, 11</xref>
        ].
      </p>
      <p>
        This software platform is developed as a web application using the "thin" client
technology, in which the components [
        <xref ref-type="bibr" rid="ref16 ref17">16, 17</xref>
        ] ("solvers") of the complex are placed
on the server, and a standard browser program acts as a user terminal.
      </p>
      <p>In the process of organizing interaction between the software complex components
along with internal client-server links of them for calling methods and receiving
(sending) data, it is suggested to limit the use of the following set of protocols: HTTP,
SOAP, and WebSocket. This set provides the ability to use a significant part of
existing software systems and libraries.</p>
      <p>To implement the components user interface, are used a well-established approach
for creating interactive web pages using HTML, CSS, JavaScript, and popular
libraries (jQuery, jQueryUI, jQueryGrid, and jsPlumb). The data exchange process is
organized both on the basis of client-initiated requests over the HTTPS Protocol, and
using bidirectional channels of the WebSocket Protocol. Currently, the server part
includes two HTTP servers: Apache-based and Node.js, which are together with the
WSS Node.js server form the external part of the server.</p>
      <p>The HTTP-Apache server provides access to the functionality of the basic
"solvers": SlvDt, SlvOnt, and partially to the functionality of SlvKln (knowledge base design
and code generation). HTTP Node server.js provides a solution to the problems of
authentication of the customer SlvCom and WSS server Node.js provides Slavcom with
the ability to organize bidirectional data exchange, in which each client is able to
interact with others in any order.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>The article discusses the basic approaches, conceptual stages of self-organization of
the process of solving an interdisciplinary task of designing complex technical
systems, as well as the architecture of the software complex and features of its
implementation. The proposed approach include a combination of ontological knowledge
representation, group decision-making, component and model-oriented approaches
that ensure the implementation of a self-organizing algorithm. The stages of
selforganization include the stage of defining the design methodology, determining the
initial data, description the task solving algorithm, and the system learning.
Selforganization of the system is based on analyzing the state of set of indicators through
a system of local rules. The chosen approach to software implementation is based on
the use of modern tools and data exchange protocols and provides the tool under
development with the ability to add a new one, including by integrating software from
third parties, as well as adapting existing functionality in accordance with changes in
the requirements of the domain.</p>
      <p>In the future, it is planned to implement proposed software complex and utilize it
to solve the tasks of designing unique mechanical and technical systems operated at
hazardous industrial facilities.
7</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>The research was supported by the Program of the Fundamental Research of the
Siberian Branch of the Russian Academy of Sciences, project no. IV.38.1.2 (reg. no.
АААА-А17-117032210079-1). Results are achieved using the Centre of collective
usage «Integrated information network of Irkutsk scientific educational complex».</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Kaljaev</surname>
            ,
            <given-names>I.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kaljaev</surname>
            ,
            <given-names>A.I.</given-names>
          </string-name>
          , Korovin, Ja.S.:
          <article-title>Principles of organization and functioning of deserted robotic production</article-title>
          . Mechatronics, automation, control, vol.
          <volume>17</volume>
          ,
          <issue>11</issue>
          ,
          <fpage>741</fpage>
          -
          <lpage>749</lpage>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Kolesnikov</surname>
            ,
            <given-names>A.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kirikov</surname>
            ,
            <given-names>I.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Listopad</surname>
            ,
            <given-names>S.V.</given-names>
          </string-name>
          :
          <article-title>Hybrid Intelligent Systems with SelfOrganization: Coordination</article-title>
          , Consistency, Dispute,
          <volume>189</volume>
          p. Moscow, IPI RAN Publ (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Berman</surname>
            ,
            <given-names>A.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikolajchuk</surname>
            ,
            <given-names>O.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pavlov</surname>
            ,
            <given-names>A.I.</given-names>
          </string-name>
          :
          <article-title>Self-organizing solution formation algorithm to ensure the required technical condition of complex hazardous objects</article-title>
          .
          <source>In: Proceedings of the conference "System Analysis and Information Technologies"</source>
          , vol.
          <volume>1</volume>
          , pp.
          <fpage>377</fpage>
          -
          <lpage>384</lpage>
          . Moscow, ISA RAN Publ (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Haken</surname>
          </string-name>
          , G.:
          <article-title>Information and self-organization: a macroscopic approach to complex systems</article-title>
          , Moscow, URSS: LENAND Publ.
          <article-title>(</article-title>
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Nikolaychuk</surname>
            ,
            <given-names>O.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pavlov</surname>
            ,
            <given-names>A.I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stolbov</surname>
            ,
            <given-names>A.B.</given-names>
          </string-name>
          :
          <article-title>The software platform architecture for the component-oriented development of knowledge-based systems</article-title>
          .
          <source>In: Proceedings of the 41st International Convention on Information and Communication Technology, Electronics and Microelectronics (MIPRO)</source>
          , pp.
          <fpage>1234</fpage>
          -
          <lpage>1239</lpage>
          , Opatija, Croatia (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Gavrilova</surname>
            ,
            <given-names>T.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kudrjavcev</surname>
            ,
            <given-names>D.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Muromcev</surname>
            ,
            <given-names>D.I. Knowledge</given-names>
          </string-name>
          <string-name>
            <surname>Engineering</surname>
          </string-name>
          .
          <article-title>Models and methods</article-title>
          . Spb., «Lan'» Publ (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Chandrasekaran</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Josephson</surname>
            ,
            <given-names>J.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Benjamins</surname>
            ,
            <given-names>V.R.</given-names>
          </string-name>
          :
          <source>Ontology of Tasks and Methods. IEEE Intelligent Systems</source>
          ,
          <volume>14</volume>
          (
          <issue>1</issue>
          ),
          <fpage>20</fpage>
          -
          <lpage>26</lpage>
          (
          <year>1998</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Berman</surname>
            ,
            <given-names>A.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikolaychuk</surname>
            ,
            <given-names>O.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pavlov</surname>
            ,
            <given-names>A.I.</given-names>
          </string-name>
          :
          <article-title>The Ontology Model for Automating the Solution of Multidisciplinary Research Tasks</article-title>
          . In: Proc. the V Intern. Workshop Critical Infrastructures:
          <article-title>Contingency Management, Intelligent, Agent-Based, Cloud Computing and Cyber Security (IWCI</article-title>
          <year>2018</year>
          ), vol.
          <volume>158</volume>
          . pp.
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Cretu</surname>
            ,
            <given-names>L. G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Florin</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Model-Driven Engineering</surname>
          </string-name>
          of Information Systems: Principles, Techniques, and
          <string-name>
            <surname>Practice</surname>
          </string-name>
          . Apple Academic Press (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Yurin</surname>
            ,
            <given-names>A.Yu.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dorodnykh</surname>
            ,
            <given-names>N.O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikolaychuk</surname>
            ,
            <given-names>O.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grishenko</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>Designing rulebased expert systems with the aid of the model-driven development approach</article-title>
          .
          <source>Expert Systems</source>
          , vol.
          <volume>35</volume>
          ,
          <issue>5</issue>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Dorodnykh</surname>
            ,
            <given-names>N.O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yurin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Yu</surname>
          </string-name>
          .:
          <article-title>Technology for creating rule-based expert systems using the model transformations</article-title>
          .
          <source>SB RAS</source>
          ,
          <string-name>
            <surname>Novosibirsk</surname>
          </string-name>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Gubanov</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Korgin</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Novikov</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Raikov</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          : E-Expertise:
          <article-title>Modern Collective Intelligence</article-title>
          .
          <source>Series: Studies in Computational Intelligence</source>
          , vol.
          <volume>558</volume>
          , pp.
          <fpage>112</fpage>
          . Springer International Publishing (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Berman</surname>
            ,
            <given-names>A.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikolajchuk</surname>
            ,
            <given-names>O.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pavlov</surname>
            ,
            <given-names>A.I.</given-names>
          </string-name>
          :
          <article-title>Method of acquiring multidisciplinary knowledge based on ontology</article-title>
          .
          <source>In: Proceedings of the conference "System Analysis and Information Technologies"</source>
          , vol.
          <volume>1</volume>
          , pp.
          <fpage>295</fpage>
          -
          <lpage>302</lpage>
          . Moscow, ISA RAN Publ (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Berman</surname>
            ,
            <given-names>A.А.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikolaychuk</surname>
            ,
            <given-names>O.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maltigueva</surname>
            ,
            <given-names>G.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yurin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Yu</surname>
          </string-name>
          .
          <article-title>: A Method of Experts' Knowledge Approval for Industrial Safety Expertise Task</article-title>
          .
          <source>In: Series:Advances in Intelligent Systems Research. Proceedings of the VIth International Workshop «Critical Infrastructures: Contingency Management, Intelligent, Agent-Based, Cloud Computing and Cyber Security» (IWCI</source>
          <year>2019</year>
          ), vol.
          <volume>169</volume>
          , pp.
          <fpage>102</fpage>
          -
          <lpage>107</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Mahutov</surname>
            ,
            <given-names>N.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berman</surname>
            ,
            <given-names>A.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikolajchuk</surname>
            ,
            <given-names>O.A.:</given-names>
          </string-name>
          <article-title>Some principles of self-organization to manage the risk of man-made disasters</article-title>
          .
          <source>Risk analysis problems</source>
          , vol.
          <volume>12</volume>
          ,
          <issue>4</issue>
          ,
          <fpage>34</fpage>
          -
          <lpage>45</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Nikolajchuk</surname>
            ,
            <given-names>O.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pavlov</surname>
            ,
            <given-names>A.I.</given-names>
          </string-name>
          :
          <article-title>Using the component approach to create a research automation system</article-title>
          .
          <source>Vestnik of Computer and Information Technologies</source>
          ,
          <volume>4</volume>
          (
          <issue>70</issue>
          ),
          <fpage>23</fpage>
          -
          <lpage>32</lpage>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>George</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Heineman</surname>
          </string-name>
          , William, T.:
          <article-title>Councill. Component-Based Software Engineering: Putting the Pieces Together</article-title>
          .
          <string-name>
            <surname>Addison-Wesley</surname>
            <given-names>Professional</given-names>
          </string-name>
          , Reading (
          <year>2001</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>