Now let's briefly consider some aspects of
designing the actual version of the applied ontology
of various typical IES architectures, the main purpose
and purpose of which is to take into account and
reflect at different levels of the ontology the features
and logical relationships of the architecture model of
the projected IES, as well as the specification of
methods and algorithms implemented in the
corresponding RUC.
It should be noted here that the architecture model
of the prototype of the IES, represented in the form of
a hierarchy of extended data flow diagrams (EDFD)
(Rybina, 2008), is one of the important components
of the process of prototyping of the IES, due to the
fact that its order has a strong effect on the prototype
of the IES and its capabilities for the implementation
of a specific class of tasks to be solved. The
emergence of architectural elements at different
levels of nesting due to the implementation of multi-
level integration processes reproduced in the EDFD
hierarchy required the use of different non-trivial
approaches and solutions, including a set of plural
information and operational RUCs included in
various software tools of the AT-TECHNOLOGY
workbench.
Therefore, the general structure and basic levels
of the considered applied ontology are given in
(Rybina, 2021), as well as connection (relation) types
presented in that research and at Figure 1 above.
Taking into account these conceptual and
functional features of IES prototyping (Rybina
2008), (Rybina, 2019), all algorithms and procedures
for designing, storing and maintaining the considered
in main title applied ontology as an significant section
of the technological KB were developed in such a
way as to make the possibility of access and
comprehensive customization the appropriate RUC to
perform all planned tasks with the help of an
intelligent planner, depending on the features of the
model the architecture of the designed IES (at the
same time, a knowledge engineer can perform some
tasks independently or jointly with an expert).
For automated support of the processes of
designing an applied ontology of typical IES
architectures, modified tools were used that function
as part of the basic tools of the AT-TECHNOLOGY
workbench and allow to fully implement the
necessary functionality, as well as for modeling
interaction with an intelligent planner (Rybina, 2019)
developed tools for managing interaction with
technological KB were involved.
3 APPLIED ONTOLOGY OF
TYPICAL IES
ARCHITECTURES
FRAGMENT’S EXAMPLE (SDP
"DESIGNING TUTORING IES
AND WEB-IES")
As an example, we will give a fragment of the applied
ontology of typical IES architectures, which shows
the conceptual (logical) and program relationship
between the set of standard processes for tutoring IES
related to displaying the current student model, built
as a result of web testing, on the ontology of a specific
course/discipline and the formation of an individual
strategy (plan) depending on the results obtained
tutoring type (Rybina, 2008), (Rybina, 2017).
As noted above, the overall management of these
and other processes in the two basic modes of
operation of tutoring IES (DesignTime and RunTime)
(Rybina, 2008), (Rybina, 2019), (Rybina, 2017) is
supported by an intelligent planner, the SDP
"Designing tutoring IES and web-IES" and a set of
RUC implemented using a significant amount of
various software and information tools registered in
different years in the AT-TECHNOLOGY
workbench and included in the subsystem of support
for the design of tutoring IES.
Therefore, issues related to preliminary analysis,
structural and functional identification and formal
representation of all software tools and components
in accordance with the basic RUC model are of great
importance for designing an applied ontology of
typical IES architectures (Rybina 2008). Below are
the formal descriptions (concretizations) of two
conceptually related RUC implementing the
functionality mentioned above.
Specification of the RUC "Mapping the current
student model to the ontology of the
course/discipline" in accordance with the basic model
of the RUC <N, Arg, F, PINT, FN> (Rybina, 2008) is
defined as:
N - the name of the registered component
"Mapping the current model of the student on the
ontology of the course/discipline";
Arg = <Arg1, Arg2>, where Arg1 is the
course/discipline ontology, (previously built in
DesignTime mode (Rybina, 2008), (Rybina, 2017));
Arg2 - current student model (M1cur);
F: Arg1 х Arg2 → R - method for evaluating the
results of testing students, where R = {rj}, (j = 1÷m)
- a set of "problem areas" of a particular student
(Rybina, 2008), (Rybina, 2017);