<!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>Explainable MLOps: A Methodological Framework for the Development of Explainable AI in Practice</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Annemarie Jutte</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Saxion University of Applied Sciences</institution>
          ,
          <addr-line>Enschede</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Twente</institution>
          ,
          <addr-line>Enschede</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The field of explainable artificial intelligence (XAI) aims to increase the transparency of AI models by providing explanations for their reasoning processes. Valuable eforts have led to an increase in transparency. However, there are still blind spots in literature, specifically related to the use of XAI techniques in practice. To make the development of AI models truly explainable, transparency is required in each stage of the Machine Learning Operations (MLOps) workflow: data preparation, model development and model deployment. This research aims to mitigate issues in each stage, using case studies from the industry and health domains. The final objective is to provide an application-oriented methodological framework for the development of more transparent AI approaches.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;XAI</kwd>
        <kwd>MLOps</kwd>
        <kwd>data quality</kwd>
        <kwd>application-oriented</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Artificial intelligence (AI) models, like those used for scheduling maintenance work [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] or
diagnosing diseases [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], are taking on an increasingly significant role in critical decision-making
processes. These models are often complex and it can be dificult to get insight into their internal
workings [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The most complex of these models are referred to as ‘black-box’ models [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], where
given an input, the decision of the model is known, but the reasoning behind it is unclear.
      </p>
      <p>
        If model reasoning is not understood, the model may seem to perform well in a controlled
environment, but we cannot be sure if it performs well for the right reasons. Consequently, we
cannot be sure if it will perform well in the future. Due to the automation bias [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], users of said
models may put (misguided) trust into them. Due to this trust, users may not notice unexpected
behaviours. Eforts in the field of Explainable AI (XAI) have led to a wide range of available
techniques to introduce explainability into AI models [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. However, there are still blind spots
within literature, specifically regarding the use of these techniques in practice.
      </p>
      <p>
        Firstly, current XAI techniques generally do not take stakeholder needs into account. Instead,
the focus tends to be on algorithmic possibilities [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Generally, machine learning engineers
design techniques without considering other users [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], who may have limited to no knowledge
of machine learning. As a consequence, the techniques are suitable to be used by machine
learning engineers to get insight into their models during model development, but unsuitable for
end-users during model deployment.
      </p>
      <p>
        Secondly many issues within AI models come up due to issues within the data [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Following
the ‘garbage in, garbage out’ principle, we cannot expect to develop high-quality models from
low-quality data. To avoid investing resources into the training of models that are set up to fail, it
would be valuable to mitigate data issues before training. Additionally, by bringing transparency
into the data, stakeholders may recognize data issues without needing to understand complex
models. Therefore, besides following the current trend in literature, where the focus is on
making models transparent, this research will also consider transparency in data preparation.
      </p>
      <p>
        In this research, I argue, to make AI truly transparent, explainability should not be focused
only on model development, but also on data preparation and model deployment. These stages
relate to the MLOps (Machine Learning Operations) paradigm. MLOps leads to an iterative
workflow, see Figure 1, based on the DevOps paradigm [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] in the software engineering field.
The MLOps workflow consists of three stages: data preparation, model development and model
deployment. MLOps aims to mitigate issues in the practical development and deployment of AI
applications. It does so through rapid iterations where the diferent stages provide feedback to
each other.
      </p>
      <p>Currently, explainability is not explicitly part of the MLOps workflow. However, to develop
truly transparent and robust AI models, it is imperative to be able to explain decisions in each
MLOps stage. Therefore, this research aims to extend this workflow by bringing explainability
into each step of the process:
• Prepare data: providing transparency into the data allows for verification of the data
quality before training the model.
• Develop model: explanations allow machine learning engineers to detect issues with
model reasoning to improve the model before passing the model on to domain-experts.
• Deploy model: when domain-experts interact with the model in critical decision-making
processes, the model needs to justify the decisions it makes to prevent mistakes due to
unexpected model behaviour and gain user trust.</p>
      <p>
        The main objective of this research is to design a methodological framework that supports
the development of end-to-end XAI approaches with an emphasis on application. This is a
rather broad objective. Issues that may occur during practical AI development are in many
aspects related to the modality of the data. Therefore, the choice is made to focus specifically on
applications using sensor data. This choice is made since sensor data has been underrepresented
in literature [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Related work</title>
      <sec id="sec-2-1">
        <title>2.1. Explainable data preparation</title>
        <p>
          The quality of the data is crucial for the quality of models trained using this data, low-quality
data can introduce issues into AI models [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. In literature on XAI, the focus is generally on
explaining already developed AI models rather than first providing transparency for the data [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ].
        </p>
        <p>
          Literature that does directly address data issues, generally focuses on data issues related to
biases towards certain outcomes. This focus is due to examples of AI discriminating against
groups of people [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. However, depending on the use case, there are also other issues related
to data quality that have not been given much attention.
        </p>
        <p>
          Calders and Žliobaitė [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] give three examples of ways in which data problems can present:
biased sampling, incorrect labels and incomplete data. However, these issues can also be linked
to diferent issues. A tired annotator may have given a subset of the data incorrect labels
or the sensors in a dataset do not capture a phenomenon that is to be predicted. Black and
van Nederpelt [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] present a list of 127 dimensions that determine data quality, including for
example: consistency, precision, and reputation. This research will explore which dimensions
are important for stakeholders and how to quantify data quality along these dimensions.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Explainable model development</title>
        <p>
          In the model development stage, the data is used by machine learning engineers to develop AI
models. XAI techniques can be used to validate whether the model is working as desired. Many
techniques have been developed to uncover model reasoning [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ].
        </p>
        <p>
          Generally in development, a black-box model is initially developed with the aim of obtaining
maximum predictive performance. Afterwards, a technique for post-hoc explainability [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] is
added. However, there is often a trade-of between the predictive performance of the model
and the level of explainability that can be reached [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. More complex models often have a
higher predictive performance, but are more dificult to interpret. Depending on the application,
end users may accept some decrease in predictive performance, given the benefit of higher
explainability.
        </p>
        <p>
          Therefore, it could be beneficial to expand the current evaluation methods that focus on
predictive performance, with factors such as explainability and data quality. Nauta et al. [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]
presented evaluation methods for explainable models. Extending this evaluation with the
evaluation of other model properties, like its computational cost and the quality of the used
data, could give insight into the trade-of between model properties.
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. Explainable model deployment</title>
        <p>
          During model deployment, the developed model is put into operation such that end-users
can apply the model in their work. Most XAI approaches focus on extracting explanations
for machine learning engineers, without making this information also understandable and
informative for other users [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Therefore, many approaches are in fact not suitable for domain
experts. Eforts have been made to uncover what diferent users need from explanations [
          <xref ref-type="bibr" rid="ref15 ref6">6, 15</xref>
          ]
and techniques have been developed to provide more appropriate explanations [
          <xref ref-type="bibr" rid="ref16 ref17">16, 17</xref>
          ], but
there are still steps to be made. Specifically, the explaining of temporal data to end users
is underrepresented. Existing types of explanations are often not suitable for complex
highdimensional temporal data [18].
        </p>
      </sec>
      <sec id="sec-2-4">
        <title>2.4. Explainable MLOps</title>
        <p>The workflow in Figure 1 presents a general overview of the stages in MLOps. There are multiple
models making the workflow more specific, for example CD4ML [ 19] or CRISP-ML(Q) [20]. They
add stages such as business understanding and the development of front-end code. Depending
on the findings in this research such a model will be adopted or adapted for the framework that
will be the product of this research.</p>
        <p>Previous research has started using such frameworks to expand the scope of XAI towards
MLOps. For example, Dwivedi et al. [21] argue for both data explainability and model
explainability in diferent phases. Kolyshkina and Simof [22] presented a new workflow based on
the interpretability requirements from diferent stakeholders for each stage. Tchuente et al.
[23] present a six step approach to explainability.</p>
        <p>The focus in these papers is mainly on organising existing research into diferent stages of
the MLOps workflow. This research will instead work with use cases to tie the whole workflow
together and make it more useful in practice. The research will include novel findings that
mitigate existing gaps within each of the stages, as discussed previously in this section.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Research questions</title>
      <p>The overarching purpose of this research is to develop a methodology for incorporating XAI
into the MLOps workflow when working with sensor data. This leads to the following research
question:</p>
      <p>How can we design an application-oriented methodological framework that
introduces explainability into the entire MLOps workflow for sensor data?
In alignment with the respective stages in the MLOps workflow (see Figure 1), the following
sub-questions are defined:
• RQ 1 - Explainable data preparation: How can issues related to data quality be quantified
for more transparent decision-making?
• RQ 2 - Explainable model development: How to select AI models and explainability
techniques that best match user requirements?
• RQ 3 - Explainable model deployment: How can AI models for sensor data be made
explainable for domain experts?</p>
    </sec>
    <sec id="sec-4">
      <title>4. Methodology</title>
      <p>The research questions, discussed in the previous section, relate to four sub-studies, see Figure 2.
Following the MLOps workflow, the overall process will be iterative in nature. Each study builds
on the previous studies and new findings lead to updates of the previous studies.</p>
      <p>This research will base itself around case studies. Drawing from the design science
methodology [24], new artefacts (criteria, techniques or frameworks) will be designed based on findings
from literature and findings from explorative user studies. The designed artefacts will be
evaluated through user studies to evaluate their validity in a real world context. The goal is to
generalize the findings into new theories for the state-of-the-art.</p>
      <sec id="sec-4-1">
        <title>4.1. Case studies</title>
        <p>The case studies will be used to uncover issues and desires from the application domain. For
this research, the case studies will be from the industry and health domains. This research will
focus on use cases these domains have in common: the prediction of events from sensor data.</p>
        <p>In order to ensure case studies are suited for the purposes of this research, they will need to
conform to the following criteria:
1. Data: sensor data must be available, the collection of this data is out of the scope of this
project. Furthermore, data must be available from a variety of diferent sensors. The data
should be suficiently dificult to interpret, such that explainability is not inherent.
2. Technology readiness: an AI solution to the problem from the case study has been
presented in at least one peer-reviewed paper, and this solution has been evaluated on a
real-world dataset. The aim of this research is to design XAI methodologies, not to solve
issues regarding predictive performance.
3. Infrastructure: in-house computational power is available or the company/institution is
willing to run models in a secure cloud environment for deployment.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Limitations and threats</title>
      <p>In this section we identify a number of threats to the success of this research, namely: data
confidentiality, the maturity of evaluation techniques and bias in user studies.</p>
      <p>Firstly, this research relies on data from real-world use cases. This type of data is generally
subject to confidentiality, there might be restrictions to publishing research related to this data.
A mitigation to this issue would be to use the confidential data for exploratory research, to
uncover real-world problems, but replace the data with similar open data for publications.</p>
      <p>
        Secondly, the focus of Study 2, see Section 4, is on selection criteria for AI models and XAI
techniques. The goal is for these criteria to take multiple factors into account. However, the
evaluation of explainability by itself is still in its early stages [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Therefore, the research may
instead focus solely on evaluation methods for explainability.
      </p>
      <p>Finally, the evaluation of this research relies on user studies. This type of evaluation is
specifically sensitive to bias due to a small sample size. Therefore, the generalization of the
results may be limited. To maximize the generalizability use cases from diferent domains are
used, see Section 4.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>In this research, I aim to design a novel application-oriented methodological framework for
explainability in MLOps. To create this framework, each stage of the MLOps workflow will
be researched in a study: explainable data preparation, explainable model development, and
explainable model deployment. During these three studies, application-oriented issues will be
explored in case studies and evaluated through user studies.</p>
      <p>The first step in this research will be the study concerning explainable data preparation.
This research will focus on the quantification of issues related to data quality by providing
transparency into the data. The final step of this research will be to generalize the findings from
the three studies into an application-oriented methodological framework.</p>
      <p>The goal of this research is to support the development of transparent AI technologies
in practice. The General Data Protection Regulation (GDPR) [25] states that citizens in the
EU are entitled to a ‘right to explanation’ for algorithms that afect them.This research aims
to contribute to the development data-driven algorithms that meet the requirements of this
legislation.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>I want to thank Faizan Ahmed, Jeroen Linssen and Maurice van Keulen for supervising this
research. This publication is part of the project ZORRO with project number KICH1.ST02.21.003
of the research programme Key Enabling Technologies (KIC) which is partly financed by the
Dutch Research Council (NWO).
(2023) 1–35.
[18] E. Ates, B. Aksar, V. J. Leung, A. K. Coskun, Counterfactual explanations for multivariate
time series, in: 2021 international conference on applied artificial intelligence (ICAPAI),
IEEE, 2021, pp. 1–8.
[19] D. Sato, A. Wider, C. Windheuser, Continuous Delivery for Machine Learning, 2019. URL:
https://martinfowler.com/articles/cd4ml.html, date accessed: 21-03-2024.
[20] S. Studer, T. B. Bui, C. Drescher, A. Hanuschkin, L. Winkler, S. Peters, K.-R. Müller, Towards
CRISP-ML (Q): a machine learning process model with quality assurance methodology, in:
Machine learning and knowledge extraction, volume 3(2), MDPI, 2021, pp. 392–413.
[21] R. Dwivedi, D. Dave, H. Naik, S. Singhal, R. Omer, P. Patel, B. Qian, Z. Wen, T. Shah,
G. Morgan, et al., Explainable AI (XAI): Core ideas, techniques, and solutions, ACM
Computing Surveys 55 (2023) 1–33.
[22] I. Kolyshkina, S. Simof, Interpretability of machine learning solutions in industrial decision
engineering, in: Australasian Conference on Data Mining, Springer, 2019, pp. 156–170.
[23] D. Tchuente, J. Lonlac, B. Kamsu-Foguem, A methodological and theoretical framework for
implementing explainable artificial intelligence (XAI) in business applications, Computers
in Industry 155 (2024) 104044.
[24] A. R. Hevner, A three cycle view of design science research, Scandinavian journal of
information systems 19 (2007) 4.
[25] European Parliament, Council of the European Union, Regulation (EU) 2016/679 of the
European Parliament and of the Council of 27 April 2016 on the protection of natural
persons with regard to the processing of personal data and on the free movement of such
data, and repealing Directive 95/46/EC (General Data Protection Regulation), 2016.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>T. P.</given-names>
            <surname>Carvalho</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. A.</given-names>
            <surname>Soares</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Vita</surname>
          </string-name>
          , R. d. P. Francisco,
          <string-name>
            <given-names>J. P.</given-names>
            <surname>Basto</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. G.</given-names>
            <surname>Alcalá</surname>
          </string-name>
          ,
          <article-title>A systematic literature review of machine learning methods applied to predictive maintenance</article-title>
          ,
          <source>Computers &amp; Industrial Engineering</source>
          <volume>137</volume>
          (
          <year>2019</year>
          )
          <fpage>106024</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>M. D. A. C. Jayatilake</surname>
          </string-name>
          , G. U. Ganegoda,
          <article-title>Involvement of machine learning tools in healthcare decision making</article-title>
          ,
          <source>Journal of healthcare engineering</source>
          <year>2021</year>
          (
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Adadi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Berrada</surname>
          </string-name>
          ,
          <article-title>Peeking inside the black-box: a survey on explainable artificial intelligence (XAI)</article-title>
          ,
          <source>IEEE access 6</source>
          (
          <year>2018</year>
          )
          <fpage>52138</fpage>
          -
          <lpage>52160</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L. J.</given-names>
            <surname>Skitka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. L.</given-names>
            <surname>Mosier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Burdick</surname>
          </string-name>
          ,
          <article-title>Does automation bias decision-making?</article-title>
          ,
          <source>International Journal of Human-Computer Studies</source>
          <volume>51</volume>
          (
          <year>1999</year>
          )
          <fpage>991</fpage>
          -
          <lpage>1006</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>W.</given-names>
            <surname>Saeed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Omlin</surname>
          </string-name>
          ,
          <string-name>
            <surname>Explainable</surname>
            <given-names>AI</given-names>
          </string-name>
          (
          <article-title>XAI): A systematic meta-survey of current challenges and future opportunities</article-title>
          ,
          <source>Knowledge-Based Systems</source>
          <volume>263</volume>
          (
          <year>2023</year>
          )
          <fpage>110273</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Dhanorkar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. T.</given-names>
            <surname>Wolf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Qian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Popa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <article-title>Who needs to know what, when?: Broadening the Explainable AI (XAI) Design Space by Looking at Explanations Across the AI Lifecycle</article-title>
          ,
          <source>in: Proceedings of the 2021 ACM Designing Interactive Systems Conference</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>1591</fpage>
          -
          <lpage>1602</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>U.</given-names>
            <surname>Bhatt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Xiang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Sharma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Weller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Taly</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Jia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Puri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Moura</surname>
          </string-name>
          ,
          <string-name>
            <surname>P. Eckersley,</surname>
          </string-name>
          <article-title>Explainable machine learning in deployment</article-title>
          ,
          <source>in: Proceedings of the 2020 conference on fairness, accountability, and transparency</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>648</fpage>
          -
          <lpage>657</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>T.</given-names>
            <surname>Calders</surname>
          </string-name>
          ,
          <string-name>
            <surname>I.</surname>
          </string-name>
          <article-title>Žliobaitė, Why unbiased computational processes can lead to discriminative decision procedures, in: Discrimination and Privacy in the Information Society: Data mining and</article-title>
          profiling in large databases, Springer,
          <year>2013</year>
          , pp.
          <fpage>43</fpage>
          -
          <lpage>57</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>G.</given-names>
            <surname>Symeonidis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Nerantzis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kazakis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. A.</given-names>
            <surname>Papakostas</surname>
          </string-name>
          ,
          <article-title>MLOps-definitions, tools and challenges</article-title>
          ,
          <source>in: 2022 IEEE 12th Annual Computing and Communication Workshop and Conference (CCWC)</source>
          , IEEE,
          <year>2022</year>
          , pp.
          <fpage>0453</fpage>
          -
          <lpage>0460</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>C.</given-names>
            <surname>Ebert</surname>
          </string-name>
          , G. Gallardo,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hernantes</surname>
          </string-name>
          , N. Serrano, DevOps, IEEE software
          <volume>33</volume>
          (
          <year>2016</year>
          )
          <fpage>94</fpage>
          -
          <lpage>100</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>A.</given-names>
            <surname>Theissler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Spinnato</surname>
          </string-name>
          , U. Schlegel,
          <string-name>
            <given-names>R.</given-names>
            <surname>Guidotti</surname>
          </string-name>
          ,
          <article-title>Explainable AI for time series classification: a review, taxonomy and research directions</article-title>
          ,
          <source>IEEE Access 10</source>
          (
          <year>2022</year>
          )
          <fpage>100700</fpage>
          -
          <lpage>100724</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>J.</given-names>
            <surname>Zou</surname>
          </string-name>
          , L. Schiebinger,
          <article-title>AI can be sexist and racist-it's time to make it fair</article-title>
          ,
          <source>Nature</source>
          <volume>559</volume>
          (
          <year>2018</year>
          )
          <fpage>324</fpage>
          -
          <lpage>326</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>A.</given-names>
            <surname>Black</surname>
          </string-name>
          ,
          <string-name>
            <surname>P. van Nederpelt</surname>
          </string-name>
          ,
          <source>Dimensions of Data Quality (DDQ)</source>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>M.</given-names>
            <surname>Nauta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Trienes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pathak</surname>
          </string-name>
          , E. Nguyen,
          <string-name>
            <given-names>M.</given-names>
            <surname>Peters</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Schmitt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Schlötterer</surname>
          </string-name>
          , M. van
          <string-name>
            <surname>Keulen</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Seifert</surname>
          </string-name>
          ,
          <article-title>From anecdotal evidence to quantitative evaluation methods: A systematic review on evaluating explainable ai</article-title>
          ,
          <source>ACM Computing Surveys</source>
          <volume>55</volume>
          (
          <year>2023</year>
          )
          <fpage>1</fpage>
          -
          <lpage>42</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>M.</given-names>
            <surname>Langer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Oster</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Speith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Hermanns</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Kästner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sesing</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Baum</surname>
          </string-name>
          ,
          <article-title>What do we want from Explainable Artificial Intelligence (XAI)?-A stakeholder perspective on XAI and a conceptual model guiding interdisciplinary XAI research</article-title>
          ,
          <source>Artificial Intelligence</source>
          <volume>296</volume>
          (
          <year>2021</year>
          )
          <fpage>103473</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>C. J.</given-names>
            <surname>Cai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Jongejan</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. Holbrook,</surname>
          </string-name>
          <article-title>The efects of example-based explanations in a machine learning interface</article-title>
          ,
          <source>in: Proceedings of the 24th international conference on intelligent user interfaces</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>258</fpage>
          -
          <lpage>262</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>V.</given-names>
            <surname>Lai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q. V.</given-names>
            <surname>Liao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <article-title>Selective explanations: Leveraging human input to align explainable ai</article-title>
          ,
          <source>Proceedings of the ACM on Human-Computer Interaction 7</source>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>