<!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>A Feature-wise Comparative Assessment of the CBR-based Methodologies FLEA and SEASALT</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Viktor Eisenstadt</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jessica Bielski</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christoph Langenhan</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Klaus-Dieter Althof</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andreas Dengel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>DFKI (German Research Center for Artificial Intelligence)</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Technical University of Munich</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Hildesheim</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper presents a feature-wise comparison of the capabilities of two methodologies developed for design and implementation of distributed artificial intelligence (AI) systems that utilize case-based reasoning (CBR) as the main computational method. The evaluated methodologies are SEASALT (Sharing Experience using an Agent-based System Architecture Layout), an established approach for organization of multi-agent CBR in several coherent system layers, and FLEA (Find, Learn, Explain, Adapt), a novel AI-based methodology for combining CBR and deep learning (DL) in flexible dependency graphs. SEASALT was conceptualized for use in diferent application domains at its outset, while FLEA was developed for the DL-based support of the architectural design process and then generalized for other domains. The comparative assessment aims to investigate the structural, relational, and technological capabilities of the methodologies, seeking for shallow as well as deeply hidden diferences. As an overall conclusion, the evaluation has revealed that SEASALT provides a more restrictive feature set that enables for more stability for the systems that utilize this methodology, while FLEA leaves more room for selection of applicable computational methods and ofers an integrated support for explanation of decisions made by the system. Furthermore, it has been shown that a SEASALT-based approach can be turned into a FLEA-based process, without loss of functionality. The work presented in this paper is part of a PhD thesis written in the context of the research project Metis-II funded by the German Research Foundation (DFG).</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;artificial intelligence</kwd>
        <kwd>methodology</kwd>
        <kwd>case-based reasoning</kwd>
        <kwd>deep learning</kwd>
        <kwd>multi-agent-systems</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>In modern research and industry, many complex systems that utilize artificial intelligence
(AI) as the main computational technique make use of a specific methodology to provide the
underlying approach with a coherent and comprehensible structure. Such methodologies
usually help to organize the system by utilizing specific components and interconnections
that control the execution processes and data flow cycles within the system.</p>
      <p>
        In the previous research, diferent methodologies were proposed to accomplish these
tasks. In the field of case-based reasoning (CBR) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], AI-based research and development
discipline for making informed decisions based on experiences recorded in the past, such
methodologies are common and have been applied for diferent domains of engineering,
science, or creativity in order to structurally organize the corresponding systems.
      </p>
      <p>
        In this paper, an established and frequently used CBR-based methodology SEASALT
(Sharing Experience using an Agent-based System Architecture Layout) [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ] will be
evaluated against the new methodology FLEA (Find, Learn, Explain, Adapt) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] in
order to explore the capabilities of both approaches and investigate their corresponding
advantages. The main goal of research presented in this paper is to find out if certain
application cases exist in which one of the methodologies might be a superior choice, how
to recognize these cases, and what are the boundaries of both approaches. First, both
methodologies will be briefly described, after that their features will be compared using a
list of criteria. In conclusion, the findings of the comparison will be presented.
      </p>
      <p>A related research work [5] was published in 2023 by Schultheis et al., it contains a
feature-wise comparison of the currently existing CBR programming frameworks, such as
myCBR1, CloodCBR2, or jColibri 3. We consider the methodology comparison presented
in this paper a methodical supplementation of work [5]. Comparing CBR methodologies
provides a more complete picture on the currently available CBR development tools.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Methodology SEASALT</title>
      <p>
        The methodology SEASALT (see Fig. 1) is described by its authors as ‘an
applicationindependent architecture that features knowledge acquisition from a web-community,
knowledge modularisation and agent-based knowledge maintenance’ [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. It is based on the
approach CoMES (Collaborative Multi-Expert-Systems) [6] and can be considered a
universal distributed CBR methodology that can be utilized for any application domain,
without further specification. The distributed structure of SEASALT allows for processing
various application domain knowledge, consisting of five main components: Knowledge
Sources (case bases or expert knowledge collected from the internet), Knowledge
Formalisation (conversion of unstructured knowledge into the structured form), Knowledge
Representation (structured knowledge formats for processing by the knowledge containers
of CBR), Knowledge Provision (segmentation into discerning domain topics using, e.g.,
case factories [7] and knowledge lines [8]), and Individualised Knowledge (user interfaces).
      </p>
      <p>
        SEASALT can be considered one of the most frequently used methodologies in the
research field of distributed case-based reasoning. In the previously published research,
it has been shown that SEASALT can be utilized for diferent application domains,
such as travel medicine (research project docQuery [
        <xref ref-type="bibr" rid="ref3">3, 9</xref>
        ]), cyber security (network
intrusion detection system [10]), big data (adds new main component Knowledge Stream
Management [11]), or decision support for maintenance and diagnosis of aircraft [12].
1http://mycbr-project.org/ – Last access on 14th Sep. 2023
2https://cloodcbr.com/ – Last access on 14th Sep. 2023
3https://gaia.fdi.ucm.es/research/colibri/jcolibri/ – Last access on 14th Sep. 2023
      </p>
      <sec id="sec-2-1">
        <title>Knowledge</title>
      </sec>
      <sec id="sec-2-2">
        <title>Provision</title>
      </sec>
      <sec id="sec-2-3">
        <title>Knowledge</title>
      </sec>
      <sec id="sec-2-4">
        <title>Formalisation</title>
        <p>Case
Factory
Knowledge</p>
        <p>Line
Coordination</p>
        <p>Agent
Intelligent Interface
Knowledge
Engineer
Apprentice</p>
        <p>Agent</p>
      </sec>
      <sec id="sec-2-5">
        <title>Individualised Knowledge</title>
        <p>Interface
User question</p>
      </sec>
      <sec id="sec-2-6">
        <title>Knowledge</title>
      </sec>
      <sec id="sec-2-7">
        <title>Representation</title>
        <p>Ontologies
Taxonomies
Similarity
measures
Constraints
Vocabularies
Rules</p>
        <sec id="sec-2-7-1">
          <title>Find</title>
        </sec>
        <sec id="sec-2-7-2">
          <title>Explain</title>
        </sec>
        <sec id="sec-2-7-3">
          <title>Learn</title>
        </sec>
        <sec id="sec-2-7-4">
          <title>Adapt</title>
          <p>FLEA-CA</p>
        </sec>
      </sec>
      <sec id="sec-2-8">
        <title>Knowledge</title>
      </sec>
      <sec id="sec-2-9">
        <title>Sources</title>
        <p>Collector
Community of Experts</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Methodology FLEA</title>
      <p>
        The methodology FLEA (see Fig. 2) was originally developed to support the early phases
of the architectural design process with modern AI methods, such as CBR or deep learning
(DL). Using a dependency graph model that distributes design support tasks, such as
retrieval of similar floor plans (Find) or autocompletion of design steps (Learn), among
the components of the execution process, diferent design scenarios can be supported
(see published examples [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]). FLEA’s combination of CBR and DL methods helps to
accelerate architectural design process in its ideation phases, making it more eficient
and sustainable. Additionally, FLEA was generalized for use in domains other than
architecture via its derivatives FLEA-CBR, FLE-ACL, and FLEA-CA.
      </p>
      <p>FLEA-CBR [13] can be considered a do-it-yourself CBR execution cycle and an
alternative to the 4R cycle (Retrieve, Reuse, Revise, Retain) [14] for the domains that are
not able to use 4R. FLEA-CBR allows for flexibility of the execution order using extended
capabilities for mixing, sequencing, or repeating of CBR phases. FLEA-ACL [15] is an
improved agents communication language (ACL) for case-based agents in multi-agent
systems, replacing the established language FIPA-ACL for such agents by bringing more
precision and sparsity to their communication processes. Finally, FLEA for cognitive
architectures (CA) aims to provide an approach for an autonomous early design agent
that elaborates the most optimal design solution by learning and competing with the
user. FLEA-CA is under active development, it aims to provide a CBR-based CA for
architectural design, being related to other CAs, such as ACT-R [16] or SOAR [17].</p>
    </sec>
    <sec id="sec-4">
      <title>4. Assessment of Features</title>
      <p>
        In this section, the feature-wise comparative assessment of the methodologies FLEA and
SEASALT will be presented. A specific list of criteria was developed to evaluate the
capabilities of methodologies. The list is based on the foundations and goals of the project
Metis-II, such as CBR, multi-agent systems (MAS), or integration of explainability of AI
methods. For each feature, it will be elaborated how it is supported by the corresponding
methodology, if the support is suficient and what can be improved to increase it.
4.1. General Type
To start the assessment, it should be investigated if both methodologies can be considered
a general type, i.e., if they are universal for use in multiple domains. This was already
mentioned in this paper for SEASALT (see Sect. 2 with references to examples) and the
authors of SEASALT denote the methodology as independent of domain or application [
        <xref ref-type="bibr" rid="ref2 ref3">2,
3</xref>
        ]. The original FLEA was developed to support the design process in the domain of
architecture, via FLEA-CBR, FLEA-ACL, and FLEA-CA (see Sect. 3) it was generalized
for use in other domains and applications. For FLEA-CBR, a theoretical example for
use for library services optimization exists [13]. It can be concluded that SEASALT can
be currently considered a more established and superior methodology for this criterion.
FLEA and its derivatives require several diferent application domains to catch up.
4.2. Integration of Explainable AI
In order to make the decisions of the AI-based systems transparent for the user, the
paradigm of XAI (eXplainable AI) was initiated and gained a great grade of popularity
among the AI researchers and developers, being present in the contributions of the major
AI conferences and in specific monograph publications. Following this trend, FLEA and
its derivatives integrate the XAI features ‘out-of-the-box’ in the component Explain, it is
up to the developers of the implementation to decide which XAI solutions (for example,
explanation patterns [18]), or frameworks (for example, the XAI framework by Wang et al.
[19]) will be utilized (see also Sect. 4.5). SEASALT does not provide a direct integration
of an XAI component, however, similar to the addition of the new Knowledge Stream
Management [11] component, SEASALT can be extended with an XAI facility. FLEA
can be seen as a more advanced methodology regarding XAI, i.e., it can be currently
considered a superior choice if explainability of system’s processes is required.
4.3. CBR Knowledge Containers
The knowledge containers [20] of CBR consist of vocabulary (knowledge representation
type), similarity measure (a function to calculate similarity between cases), case base
(collection of previously recorded experiences for reasoning), and solution transformation
(a.k.a. adaptation knowledge, stands for methods for adaptation of the solutions from
similar cases to the current problem, e.g., using rules). Knowledge containers play a
crucial role for CBR, they provide essential foundations for its computational processes.
Both FLEA and SEASALT provide a full support for CBR knowledge containers, being
both based on CBR foundations. SEASALT covers the containers by implementing them
in its main component Knowledge Representation (but also Knowledge Sources ), while
FLEA implements them in multiple facilities of its respective components, e.g., case
bases and similarity measures in Find and Learn or transformation rules in Adapt. Both
methodologies can be considered equal regarding the support of knowledge containers,
their implementations should keep up with the current advances of the containers.
4.4. Special Features for Agents
Being conceptualized as distributed methodologies at the outset, both SEASALT and
FLEA can be used to form a multi-agent system, ofering the capability of task-sharing
between and within their corresponding components, which communicate with each
other in order to achieve their own local as well as the common global goals. While the
features of communication and collaboration are typical for every multi-agent system,
SEASALT and FLEA provide several specific additional MAS features. In order to
enhance the coordination process within SEASALT-based systems, the methodology
utilizes the previously mentioned concept of case factories [7], while FLEA, via
FLEAACL, ofers an improvement of the communication process between case-based agents.
Both methodologies can be considered equal regarding special agent-related features.
      </p>
      <sec id="sec-4-1">
        <title>Request</title>
        <p>Client Layer: User Interface</p>
      </sec>
      <sec id="sec-4-2">
        <title>Response</title>
        <p>Logic Layer: Communication and Application
Workflow</p>
        <p>Applic. Logic
Taxonomy</p>
        <p>Query Structure</p>
        <p>Plausibility</p>
      </sec>
      <sec id="sec-4-3">
        <title>CBR Engine</title>
        <p>Answer
Structure</p>
      </sec>
      <sec id="sec-4-4">
        <title>Country info, Description,</title>
      </sec>
      <sec id="sec-4-5">
        <title>Medicament... Guidelines...</title>
        <p>Data Layer: Knowledge Sources
Domain
Model</p>
        <p>Data
Access</p>
      </sec>
      <sec id="sec-4-6">
        <title>Profile</title>
        <p>Request (Destination, travel period, ...)
Transfer solutions
from similar cases
Find similar cases
from same class</p>
        <p>Response
(Travel leaflet)</p>
        <p>E</p>
        <p>Feedback
from user
Expert</p>
        <p>Feedback
from expert</p>
        <p>L</p>
        <p>A</p>
        <p>Classify query
with neural network</p>
        <p>A
C</p>
        <p>B</p>
        <p>D
Case bases</p>
        <p>Query
class</p>
        <p>L
F
4.5. Restrictiveness of Methods
Finally, both methodologies can be compared by the freedom or limit of method selection.
While FLEA and its derivatives provide no specifications on algorithms and data structures
for their corresponding implementations, SEASALT goes more in detail, describing which
methods and data representations can be applied. That is, FLEA leaves the choice of
methods to the researchers and developers involved in the implementation process, defining
only the overall abstract structure and general tasks of the components Find, Learn,
Explain, and Adapt. In contrast, SEASALT specifies the agent types (e.g., Coordinator),
approaches (e.g., knowledge lines or case factories), or data representations (taxonomies,
ontologies, vocabularies) – the persons involved can make more concrete choices.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion and Outlook</title>
      <p>
        To conclude the research presented in this paper and evaluate the methodology comparison
in a simple manner, it can be first summarized that both investigated CBR methodologies
are similar on the high level of abstraction: both FLEA and SEASALT make use of
the same foundations and are generally comparable in terms of the overall structural
relationships of their respective components. This can be further demonstrated by a
simple example in Fig. 3, where the first existing implementation of SEASALT for the
already mentioned project docQuery [
        <xref ref-type="bibr" rid="ref3">3, 9</xref>
        ] (distributed CBR-based support for travel
medicine information) is converted into a FLEA dependency graph. The FLEA graph
executes the same tasks as the original SEASALT implementation, adding new modern AI
methods to the process, such as artificial neural networks (ANN) for query classification.
      </p>
      <p>Overall, it can be concluded that the SEASALT methodology provides a more stable
structure with established CBR and MAS methods, while FLEA and its derivatives ofer
integration of the latest AI advances (XAI or the current ANN models). With more
FLEA domains, both approaches can be compared more comprehensively in the future.
[5] A. Schultheis, C. Zeyen, R. Bergmann, An Overview and Comparison of Case-Based</p>
      <p>Reasoning Frameworks, in: Conference Proceedings of ICCBR 2023, 2023.
[6] K.-D. Althof, K. Bach, J.-O. Deutsch, A. Hanft, J. Mänz, T. Müller, R. Newo,
M. Reichle, M. Schaaf, K.-H. Weis, Collaborative Multi-Expert-Systems – Realizing
Knowlegde-Product-Lines with Case Factories and Distributed Learning Systems, in:
3rd KESE @ KI, 2007.
[7] K.-D. Althof, A. Hanft, M. Schaaf, Case Factory – Maintaining Experience to
Learn, in: T. R. Roth-Berghofer, M. H. Göker, H. A. Güvenir (Eds.), Advances in
Case-Based Reasoning, 2006, pp. 429–442. doi:10.1007/11805816_32.
[8] K. Bach, M. Reichle, A. Reichle-Schmehl, K.-D. Althof, Implementing a coordination
agent for modularised case bases, in: 13th UKCBR Workshop Procs., 2008, pp. 1–12.
[9] M. Reichle, K. Bach, K.-D. Althof, The SEASALT Architecture and Its
Realization within the docQuery Project, in: B. Mertsching, M. Hund, Z. Aziz
(Eds.), KI 2009: Advances in Artificial Intelligence, 2009, pp. 556–563. doi: 10.1007/
978-3-642-04617-9_70.
[10] J. M. Schoenborn, K.-D. Althof, Multi-Agent Case-Based Reasoning: a Network
Intrusion Detection System, in: P. Reuss, V. Eisenstadt, J. M. Schoenborn, J. Schäfer
(Eds.), Proceedings of the LWDA 2022 Workshops: FGWM, FGKD, and FGDB,
2022, pp. 258–269.
[11] K. Amin, Building an Integrated CBR-Big Data Oriented Architecture for Case-Based</p>
      <p>Reasoning Systems, in: ICCBR (Workshops), 2017, pp. 189–193.
[12] P. Reuss, K.-D. Althof, W. Henkel, Case-Based Decision Support on Diagnosis and</p>
      <p>Maintenance in the Aircraft Domain, in: LWDA, 2016, pp. 249–256.
[13] V. Eisenstadt, C. Langenhan, K.-D. Althof, FLEA-CBR – A Flexible Alternative
to the Classic 4R Cycle of Case-Based Reasoning, in: K. Bach, C. Marling (Eds.),
Case-Based Reasoning Research and Development, 2019, pp. 49–63. doi:10.1007/
978-3-030-29249-2_4.
[14] A. Aamodt, E. Plaza, Case-Based Reasoning: Foundational Issues,
Methodological Variations, and System Approaches, AI comm. 7 (1994) 39–59. doi:10.3233/
AIC-1994-7104.
[15] V. Eisenstadt, K.-D. Althof, RALE-ACL—A Language for Information Exchange
between Case-Based Agents as Alternative to the FIPA-ACL-Based
Communication, in: R. Barták, E. Bell (Eds.), Proceedings of the 33rd International FLAIRS
Conference, 2020, pp. 185–188.
[16] F. E. Ritter, F. Tehranchi, J. D. Oury, ACT-R: A cognitive architecture for modeling
cognition, WIREs Cognitive Science 10 (2019) e1488. doi:10.1002/wcs.1488.
[17] J. E. Laird, The Soar Cognitive Architecture, reprint ed. ed., MIT Press, 2019.
[18] J. Cassens, A. Kofod-Petersen, Designing Explanation Aware Systems: The Quest
for Explanation Patterns, in: Explanation-Aware Computing (ExaCt), 2007, pp.
20–27.
[19] D. Wang, Q. Yang, A. Abdul, B. Y. Lim, Designing Theory-Driven User-Centric
Explainable AI, in: Proceedings of the 2019 CHI Conference on Human Factors in
Computing Systems, 2019, p. 1–15. doi:10.1145/3290605.3300831.
[20] M. Richter, Knowledge containers, Readings in case-based reasoning (2003).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Kolodner</surname>
          </string-name>
          ,
          <article-title>Case-Based Reasoning</article-title>
          , Morgan Kaufmann,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>K.</given-names>
            <surname>Bach</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Reichle</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.-D. Althof</surname>
            ,
            <given-names>A Domain</given-names>
          </string-name>
          <string-name>
            <surname>Independent</surname>
          </string-name>
          <article-title>System Architecture for Sharing Experience</article-title>
          , in: Lernen, Wissen, Adaption.
          <source>Workshop Proceedings</source>
          ,
          <year>2007</year>
          , pp.
          <fpage>296</fpage>
          -
          <lpage>303</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M.</given-names>
            <surname>Reichle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Bach</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.-D. Althof</surname>
          </string-name>
          ,
          <article-title>Knowledge engineering within the applicationindependent architecture SEASALT</article-title>
          ,
          <source>International Journal of Knowledge Engineering and Data Mining</source>
          <volume>1</volume>
          (
          <year>2011</year>
          )
          <fpage>202</fpage>
          -
          <lpage>215</lpage>
          . doi:
          <volume>10</volume>
          .1504/IJKEDM.
          <year>2011</year>
          .
          <volume>037643</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>V.</given-names>
            <surname>Eisenstadt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Langenhan</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.-D. Althof</surname>
          </string-name>
          ,
          <article-title>Supporting Architectural Design Process with FLEA. A Distributed AI Methodology for Retrieval, Suggestion, Adaptation, and Explanation of Room Configurations</article-title>
          , in: J.
          <string-name>
            <surname>-H. Lee</surname>
          </string-name>
          (Ed.), Computer-Aided Architectural Design. “Hello, Culture”,
          <year>2019</year>
          , pp.
          <fpage>58</fpage>
          -
          <lpage>73</lpage>
          . doi:
          <volume>10</volume>
          .1007/
          <fpage>978</fpage>
          -981-13-8410-
          <issue>3</issue>
          _
          <fpage>5</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>