<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.1 20151215//EN" "http://jats.nlm.nih.gov/publishing/1.1/JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xml:lang="en" article-type="research-article" dtd-version="1.1">
<front>
<journal-meta>
<journal-id journal-id-type="pmc">CMC</journal-id>
<journal-id journal-id-type="nlm-ta">CMC</journal-id>
<journal-id journal-id-type="publisher-id">CMC</journal-id>
<journal-title-group>
<journal-title>Computers, Materials &#x0026; Continua</journal-title>
</journal-title-group>
<issn pub-type="epub">1546-2226</issn>
<issn pub-type="ppub">1546-2218</issn>
<publisher>
<publisher-name>Tech Science Press</publisher-name>
<publisher-loc>USA</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">57359</article-id>
<article-id pub-id-type="doi">10.32604/cmc.2025.057359</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>X-OODM: Leveraging Explainable Object-Oriented Design Methodology for Multi-Domain Sentiment Analysis</article-title>
<alt-title alt-title-type="left-running-head">X-OODM: Leveraging Explainable Object-Oriented Design Methodology for Multi-Domain Sentiment Analysis</alt-title>
<alt-title alt-title-type="right-running-head">X-OODM: Leveraging Explainable Object-Oriented Design Methodology for Multi-Domain Sentiment Analysis</alt-title>
</title-group>
<contrib-group>
<contrib id="author-1" contrib-type="author">
<name name-style="western"><surname>Javed</surname><given-names>Abqa</given-names></name><xref ref-type="aff" rid="aff-1">1</xref></contrib>
<contrib id="author-2" contrib-type="author" corresp="yes">
<name name-style="western"><surname>Shoaib</surname><given-names>Muhammad</given-names></name><xref ref-type="aff" rid="aff-1">1</xref><email>shoaib@uet.edu.pk</email></contrib>
<contrib id="author-3" contrib-type="author">
<name name-style="western"><surname>Jaleel</surname><given-names>Abdul</given-names></name><xref ref-type="aff" rid="aff-2">2</xref></contrib>
<contrib id="author-4" contrib-type="author">
<name name-style="western"><surname>Deriche</surname><given-names>Mohamed</given-names></name><xref ref-type="aff" rid="aff-3">3</xref></contrib>
<contrib id="author-5" contrib-type="author">
<name name-style="western"><surname>Nawaz</surname><given-names>Sharjeel</given-names></name><xref ref-type="aff" rid="aff-4">4</xref></contrib>
<aff id="aff-1"><label>1</label><institution>Department of Computer Science, University of Engineering and Technology</institution>, <addr-line>Lahore, 54890</addr-line>, <country>Pakistan</country></aff>
<aff id="aff-2"><label>2</label><institution>Department of Computer Science (RCET Campus, GRW), University of Engineering and Technology</institution>, <addr-line>Lahore, 52250</addr-line>, <country>Pakistan</country></aff>
<aff id="aff-3"><label>3</label><institution>Artificial Intelligence Centre (AIRC), Ajman University</institution>, <addr-line>Ajman, 346</addr-line>, <country>United Arab Emirates</country></aff>
<aff id="aff-4"><label>4</label><institution>Smith School of Business, University of Maryland</institution>, <addr-line>College Park, MD 20742-5151</addr-line>, <country>USA</country></aff>
</contrib-group>
<author-notes>
<corresp id="cor1"><label>&#x002A;</label>Corresponding Author: Muhammad Shoaib. Email: <email>shoaib@uet.edu.pk</email></corresp>
</author-notes>
<pub-date date-type="collection" publication-format="electronic">
<year>2025</year>
</pub-date>
<pub-date date-type="pub" publication-format="electronic">
<day>06</day><month>03</month><year>2025</year>
</pub-date>
<volume>82</volume>
<issue>3</issue>
<fpage>4977</fpage>
<lpage>4994</lpage>
<history>
<date date-type="received">
<day>15</day>
<month>8</month>
<year>2024</year>
</date>
<date date-type="accepted">
<day>22</day>
<month>10</month>
<year>2024</year>
</date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2025 The Authors.</copyright-statement>
<copyright-year>2025</copyright-year>
<copyright-holder>Published by Tech Science Press.</copyright-holder>
<license xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This work is licensed under a <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</ext-link>, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="TSP_CMC_57359.pdf"></self-uri>
<abstract>
<p>Incorporation of explainability features in the decision-making web-based systems is considered a primary concern to enhance accountability, transparency, and trust in the community. Multi-domain Sentiment Analysis is a significant web-based system where the explainability feature is essential for achieving user satisfaction. Conventional design methodologies such as object-oriented design methodology (OODM) have been proposed for web-based application development, which facilitates code reuse, quantification, and security at the design level. However, OODM did not provide the feature of explainability in web-based decision-making systems. X-OODM modifies the OODM with added explainable models to introduce the explainability feature for such systems. This research introduces an explainable model leveraging X-OODM for designing transparent applications for multidomain sentiment analysis. The proposed design is evaluated using the design quality metrics defined for the evaluation of the X-OODM explainable model under user context. The design quality metrics, transferability, simulatability, informativeness, and decomposability were introduced one after another over time to the evaluation of the X-OODM user context. Auxiliary metrics of accessibility and algorithmic transparency were added to increase the degree of explainability for the design. The study results reveal that introducing such explainability parameters with X-OODM appropriately increases system transparency, trustworthiness, and user understanding. The experimental results validate the enhancement of decision-making for multi-domain sentiment analysis with integration at the design level of explainability. Future work can be built in this direction by extending this work to apply the proposed X-OODM framework over different datasets and sentiment analysis applications to further scrutinize its effectiveness in real-world scenarios.</p>
</abstract>
<kwd-group kwd-group-type="author">
<kwd>Measurable</kwd>
<kwd>explainable</kwd>
<kwd>web-based application</kwd>
<kwd>object-oriented design</kwd>
<kwd>sentiment analysis</kwd>
<kwd>multi-domain</kwd>
</kwd-group>
<funding-group>
<award-group id="awg1">
<funding-source>Deanship of Research and Graduate Studies at Ajman University</funding-source>
<award-id>2024-IRG-ENiT-36 and 2024-IRG-ENIT-29</award-id>
</award-group>
</funding-group>
</article-meta>
</front>
<body>
<sec id="s1">
<label>1</label>
<title>Introduction</title>
<p>Web-based applications are critically important in the modern digital landscape because they provide organizations with a means of attracting and retaining valued customers. For instance, these include constructs for user recommendations [<xref ref-type="bibr" rid="ref-1">1</xref>], tools to help improve users&#x2019; decisions and levels of engagement and satisfaction [<xref ref-type="bibr" rid="ref-2">2</xref>], and agents that could mine online reviews to extract valuable knowledge from user-generated content [<xref ref-type="bibr" rid="ref-3">3</xref>]. Explainability in such web-based decision-making systems can help explain the system&#x2019;s generated recommendations [<xref ref-type="bibr" rid="ref-4">4</xref>]. In the last few years, explanations have come into evidence in recommender systems to enable better user comprehension, trust, and effective decision-making [<xref ref-type="bibr" rid="ref-5">5</xref>]. The explanations provide a reason behind the recommendations, thus helping users evaluate suggestions in domains such as e-commerce and social networking [<xref ref-type="bibr" rid="ref-6">6</xref>,<xref ref-type="bibr" rid="ref-7">7</xref>].</p>
<p>Explainability in web-based sentiment analysis systems includes high computation costs [<xref ref-type="bibr" rid="ref-8">8</xref>], sophisticated model interpretation [<xref ref-type="bibr" rid="ref-9">9</xref>], problems of scalability, and design variations for individual users [<xref ref-type="bibr" rid="ref-10">10</xref>&#x2013;<xref ref-type="bibr" rid="ref-12">12</xref>]. The rapid increase of web applications led to the increased demand for systems that could analyze and interpret user sentiment across various domains. Most present systems for sentiment analysis emphasize correctness and performance, while ignoring the importance of explainability [<xref ref-type="bibr" rid="ref-13">13</xref>,<xref ref-type="bibr" rid="ref-14">14</xref>]. This deficiency results in systems that are effective but not readily interpretable by end-users, thereby limiting their practical utility in decision-making processes.</p>
<p>Traditional object-orientated design methods (OODM), which include OODM [<xref ref-type="bibr" rid="ref-15">15</xref>], semantic web (SW)-OODM [<xref ref-type="bibr" rid="ref-16">16</xref>], reverse (R)-OODM [<xref ref-type="bibr" rid="ref-17">17</xref>], and Secure (S)-OODM [<xref ref-type="bibr" rid="ref-18">18</xref>], have provided strong base design for the construction of object-oriented based systems. Requirements of an object-oriented design are given in [<xref ref-type="bibr" rid="ref-19">19</xref>]. In the existing literature, various studies [<xref ref-type="bibr" rid="ref-20">20</xref>&#x2013;<xref ref-type="bibr" rid="ref-23">23</xref>] provided guidelines for implementing the object-oriented design methodology in different domains, e.g., healthcare [<xref ref-type="bibr" rid="ref-24">24</xref>,<xref ref-type="bibr" rid="ref-25">25</xref>], university administrative information system [<xref ref-type="bibr" rid="ref-26">26</xref>]. The studies [<xref ref-type="bibr" rid="ref-27">27</xref>&#x2013;<xref ref-type="bibr" rid="ref-30">30</xref>] integrated explainability, while metrics for object-oriented designs are discussed in [<xref ref-type="bibr" rid="ref-31">31</xref>,<xref ref-type="bibr" rid="ref-32">32</xref>]. However, existing studies lack the features of explainability in object-oriented design methodology for a web-based multi-domain sentiment analysis application. Hence, there is a need to propose an explainable framework that provides the interpretations in web-based multi-domain sentiment analysis.</p>
<p>The Explainable Object-Oriented Design Methodology (X-OODM) [<xref ref-type="bibr" rid="ref-33">33</xref>] presented the constructs for incorporating explainability features in web-based systems at the design level. This research extends X-OODM for multi-domain sentiment analysis incorporation in web-based object-oriented designs. This X-OODM for multi-domain sentiment analysis bridges the gap of X-OODM by providing models and components of sentiment analysis that guarantee system transparency and directly impact user experience and decision-making. The multi-domain sentiment analysis X-OODM provides reasons why a certain sentiment classification has been made to make the system more trustworthy. The study uses a suite of design quality metrics developed for the explainable model to evaluate the incorporation of X-OODM for multi-domain sentiment analysis. These metrics are validated using a web-based application of multi-domain sentiment analysis, which increases and quantifies the system&#x2019;s explain ability. The findings show that including these metrics early in the design process leads to applications that are transparent, trustworthy, functionally robust, and user-friendly. Our X-OODM for multi-domain sentiment analysis improves the design of web-based applications by incorporating components like transparency, reliability, trustworthiness, and fairness. This makes decision-making processes more rational, understandable, and optimal for better results. This framework with explainability characteristics establishes a new benchmark for future web-based multi-domain sentiment application development.</p>
<p>The paper is organized as follows: the next section discusses related work, <xref ref-type="sec" rid="s3">Section 3</xref> covers the proposed work and the metrics of the explainable model. <xref ref-type="sec" rid="s4">Section 4</xref> presents the results and discussion, and <xref ref-type="sec" rid="s5">Section 5</xref> concludes the paper.</p>
</sec>
<sec id="s2">
<label>2</label>
<title>Related Work</title>
<p>Object-oriented design methodologies (OODMs) have emerged as effective ways of developing web-based applications, like e-commerce or social networking sites. OODMS provides a systematic structure for designing large-scale, dynamic web applications that combine the complexity of navigation patterns with sophisticated computational behavior. The Object-Oriented Hypermedia Design Method is one of the most famous approaches, which describes a structured procedure comprising the phases of conceptual design, navigational design, abstract interface design, and implementation [<xref ref-type="bibr" rid="ref-34">34</xref>]. Rossi et al. [<xref ref-type="bibr" rid="ref-35">35</xref>] treat web applications as views of conceptual models, applying abstraction primitives to design conceptual and navigational structures. The application of OODMs allows developers to construct web applications that scale, reuse, and are modular, and to properly manage the complex data structures necessary for large applications.</p>
<sec id="s2_1">
<label>2.1</label>
<title>Object-Oriented Design Methodology</title>
<p>Liang et al. [<xref ref-type="bibr" rid="ref-21">21</xref>] introduced the Design with Objects (DwO) method to enhance the computability, reusability, and interchangeability of the same data of objects in modules. This method deals with electronic assemblies and their problems regarding components. Abad Shah [<xref ref-type="bibr" rid="ref-15">15</xref>] created Object-Oriented Design Methodology OODM for web applications; this is a combination of the waterfall software development lifecycle and the activities of the web. OODM, however, did not apply all steps of the software development lifecycle. Ghani et al. [<xref ref-type="bibr" rid="ref-17">17</xref>] proposed the Reverse Object-Oriented Design Methodology R-OODM whereby designs of web applications are obtained using OODM design phase models and mapping XML schemas to object databases, represented as graphs.</p>
</sec>
<sec id="s2_2">
<label>2.2</label>
<title>Secure Metrics of Object-Oriented Design Methodology</title>
<p>Kiewkanya et al. [<xref ref-type="bibr" rid="ref-22">22</xref>] emphasized a maintainability model in object-oriented design that focuses on modifiability and understandability as the two desirable states of maintenance. They used metrics and discriminant techniques to discern how maintainability correlates with structural complexity, which they translated into scores using weighted sum and predicted level techniques. Arshad et al. [<xref ref-type="bibr" rid="ref-18">18</xref>] have enhanced the OODM by the integration of security principles in the design, which incorporates the design phase because there are no such concerns in the existing methodologies of OODM in web application development. S-OODM is proposed and is tested at the design level, which is a secure object-oriented design methodology. Similarly, Kadam et al. [<xref ref-type="bibr" rid="ref-23">23</xref>] adopted the security adoption for measuring and reducing risks of numerous vulnerabilities; security guidelines were adopted at design time for improving security through security metrics. Jangra et al. [<xref ref-type="bibr" rid="ref-24">24</xref>] provided the use of object-oriented databases in the attributes of health case management systems, including re-design of structure for data and schema views, temporal data, and multimedia data management. Mohapatra et al. [<xref ref-type="bibr" rid="ref-25">25</xref>] implemented an object-oriented methodology in a cloud healthcare system to secure sensitive information, which increased modularity and flexibility. This methodology results in greater collaboration and communication between the components of the system due to the enhanced behavioral aspects. Nwokoro et al. [<xref ref-type="bibr" rid="ref-26">26</xref>] depicted the description of the object-oriented analysis and design methodology applied for a university management system, citing that object relationship increase efficiency in data retrieval with the functioning of the system.</p>
</sec>
<sec id="s2_3">
<label>2.3</label>
<title>Neural Representation Using Object-Oriented Design Methodology</title>
<p>Arulprakash et al. [<xref ref-type="bibr" rid="ref-27">27</xref>] conducted research on neural representation in explainable Artificial Intelligence (AI) using scientific methods within object-oriented approaches; instead, teaching approaches based on feature importance made it possible to reveal dependencies between weight and the distribution of loss. They offered the main parameter with the possibility of extension to business parameters such as the function of loss distribution computation. Geyer et al. [<xref ref-type="bibr" rid="ref-28">28</xref>], on the other hand, proposed a structural view in designing the components of custom methods of machine learning based on explanations provided by the systems. To deal with the black-box nature of these models, they carried out a component-based approach with the help of systems engineering where the explanation of the models was evaluated qualitatively and quantitatively relative to the component-based models.</p>
<p>Furthermore, these works demonstrate the versatility and applicability of object-oriented approaches in different areas, including web and cloud-based healthcare systems, explainable AI, or the systems of university management that note enhancement of systems maintainability, security, and data well management. Real-time studies or an application of these methodologies to bigger data sets and crowder more complex applications are potential future work.</p>
</sec>
</sec>
<sec id="s3">
<label>3</label>
<title>Proposed Work</title>
<p>In the proposed work, the OODM framework is modified by introducing the explainability features at the design level for web-based multidomain sentiment analysis applications. The proposed X-OODM for multidomain sentiment analysis design is given in subsection below followed by the proposed metrics at the design level.</p>
<sec id="s3_1">
<label>3.1</label>
<title>X-OODM for Multi-Domain Sentiment Analysis</title>
<p>X-OODM [<xref ref-type="bibr" rid="ref-33">33</xref>] extends OODM [<xref ref-type="bibr" rid="ref-16">16</xref>] and enhances web-based applications by emphasizing explainability throughout the analysis and design phases, which leads to better decision-making. This affects existing design approach models, such as the informational, navigational, operational, user interface, and component models as shown in <xref ref-type="fig" rid="fig-1">Fig. 1</xref>. Application of this integration improves the interpretation of the system by the user towards the knowledge about web applications.</p>
<fig id="fig-1">
<label>Figure 1</label>
<caption>
<title>X-OODM framework for multidomain sentiment analysis</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_57359-fig-1.tif"/>
</fig>
<p>It encompasses explainability in the various models in the system as can be elucidated by the multi-domain sentiment analysis, which is depicted in <xref ref-type="fig" rid="fig-2">Fig. 2</xref>. Various studies [<xref ref-type="bibr" rid="ref-27">27</xref>&#x2013;<xref ref-type="bibr" rid="ref-30">30</xref>] reflect on the explainability importance in compliance aspects with legal provisions which provide internal working of the application related to regulations.</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption>
<title>Design parameters for building explainable model for user context with proposed X-OODM multi-domain sentiment analysis</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_57359-fig-2.tif"/>
</fig>
</sec>
<sec id="s3_2">
<label>3.2</label>
<title>X-OODM Design Quality Metrics for Multidomain Sentiment Analysis</title>
<p>We employed X-OODM to integrate the concept of explainability into web-based multi-domain sentiment analysis applications by combining different components in user requirements. The important components of a user-interactive model are operations, including transferability, informativeness, and accessibility, whereas, for a transparent model, there is simulatability, decomposability, and algorithmic transparency. All these models pass on every combined input into the explainable model so that every aspect of the application is transparent.</p>
</sec>
<sec id="s3_3">
<label>3.3</label>
<title>Schema Representation of the Explainable Model of User Context for Multidomain Sentiment Analysis</title>
<p>Abstract graph of the explainable schema for building an explainable model of user context is defined in <xref ref-type="fig" rid="fig-3">Fig. 3</xref> and the following terms are used in each layer of the model:</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption>
<title>Abstract graph for components building of explainable model for multidomain sentiment analysis</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_57359-fig-3.tif"/>
</fig>
<p><inline-formula id="ieqn-1"><mml:math id="mml-ieqn-1"><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mi>d</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>: Lower Level <inline-formula id="ieqn-2"><mml:math id="mml-ieqn-2"><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>b</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>: Component Based Level</p>
<p><inline-formula id="ieqn-3"><mml:math id="mml-ieqn-3"><mml:msub><mml:mi>N</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>: Base Model Level <inline-formula id="ieqn-4"><mml:math id="mml-ieqn-4"><mml:msub><mml:mi>O</mml:mi><mml:mrow><mml:mi>p</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>: Upper Model Level</p>
<p><inline-formula id="ieqn-5"><mml:math id="mml-ieqn-5"><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mi>c</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>: Application Based Level <inline-formula id="ieqn-6"><mml:math id="mml-ieqn-6"><mml:msub><mml:mi>Q</mml:mi><mml:mrow><mml:mi>r</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>: User Based Level</p>
<p>The numbers including d, b, s, p, c, and r present the model and components that provide explainability in web-based applications at the design level for building an explainable model of user context. Interaction Graph &#x2018;R&#x2019; is used to define the measurements related to the design quality of explainable. This graph further denotes its vertices E(R), defined in <xref ref-type="disp-formula" rid="eqn-1">Eq. (1)</xref>.
<disp-formula id="eqn-1"><label>(1)</label><mml:math id="mml-eqn-1" display="block"><mml:mi>E</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>R</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mi>U</mml:mi><mml:mrow><mml:mi>e</mml:mi></mml:mrow></mml:msub><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mi>V</mml:mi><mml:mrow><mml:mi>f</mml:mi></mml:mrow></mml:msub><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mi>W</mml:mi><mml:mrow><mml:mi>g</mml:mi></mml:mrow></mml:msub><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mi>X</mml:mi><mml:mrow><mml:mi>h</mml:mi></mml:mrow></mml:msub><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mi>Y</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mi>Z</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo fence="false" stretchy="false">}</mml:mo></mml:math></disp-formula></p>
<p>Here, 1 &#x2264; <inline-formula id="ieqn-7"><mml:math id="mml-ieqn-7"><mml:mi>e</mml:mi></mml:math></inline-formula> &#x2264; d, 1 &#x2264; <inline-formula id="ieqn-8"><mml:math id="mml-ieqn-8"><mml:mi>f</mml:mi></mml:math></inline-formula> &#x2264; b, 1 &#x2264; <inline-formula id="ieqn-9"><mml:math id="mml-ieqn-9"><mml:mi>g</mml:mi></mml:math></inline-formula> &#x2264; s, 1 &#x2264; <inline-formula id="ieqn-10"><mml:math id="mml-ieqn-10"><mml:mi>h</mml:mi></mml:math></inline-formula> &#x2264; p, and 1 &#x2264; <inline-formula id="ieqn-11"><mml:math id="mml-ieqn-11"><mml:mi>i</mml:mi></mml:math></inline-formula> &#x2264; c the terms <italic>e</italic>, <italic>f</italic>, <italic>g</italic>, <italic>i</italic>, and <italic>j</italic> are integer numbers to denote the Lower Level, Component-Based Level, Base Model Level, Upper Model Level, Application-Based Level, and User-Based Level.</p>
<p><xref ref-type="table" rid="table-1">Table 1</xref> depicts the bidirectional edges denoting more than one edge from the single vertex. Therefore, different vertices are assigned to the edges using a unique symbol. Here, 1 &#x2264; <inline-formula id="ieqn-12"><mml:math id="mml-ieqn-12"><mml:mi>e</mml:mi></mml:math></inline-formula> &#x2264; d, 1 &#x2264; <inline-formula id="ieqn-13"><mml:math id="mml-ieqn-13"><mml:mi>f</mml:mi></mml:math></inline-formula> &#x2264; b, 1 &#x2264; <inline-formula id="ieqn-14"><mml:math id="mml-ieqn-14"><mml:mi>g</mml:mi></mml:math></inline-formula> &#x2264; s, 1 &#x2264; <inline-formula id="ieqn-15"><mml:math id="mml-ieqn-15"><mml:mi>h</mml:mi></mml:math></inline-formula> &#x2264; p, and 1 &#x2264; <inline-formula id="ieqn-16"><mml:math id="mml-ieqn-16"><mml:mi>i</mml:mi></mml:math></inline-formula> &#x2264; c. The integers <italic>v</italic>, <italic>w</italic>, <italic>x</italic>, <italic>y</italic>, and <italic>z</italic> are the subscript of the edges which denoting the vertex number of the respective edge such as <inline-formula id="ieqn-17"><mml:math id="mml-ieqn-17"><mml:mi>&#x03B1;</mml:mi></mml:math></inline-formula>, <inline-formula id="ieqn-18"><mml:math id="mml-ieqn-18"><mml:mi>&#x03B2;</mml:mi><mml:mo>,</mml:mo><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mtext>&#xA0;and&#xA0;</mml:mtext></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow></mml:math></inline-formula>, where 1 &#x2264; <inline-formula id="ieqn-19"><mml:math id="mml-ieqn-19"><mml:mi>v</mml:mi></mml:math></inline-formula> &#x2264; d, 1 &#x2264; <inline-formula id="ieqn-20"><mml:math id="mml-ieqn-20"><mml:mi>w</mml:mi></mml:math></inline-formula> &#x2264; n, 1 &#x2264; <inline-formula id="ieqn-21"><mml:math id="mml-ieqn-21"><mml:mi>x</mml:mi></mml:math></inline-formula> &#x2264; o, 1 &#x2264; <inline-formula id="ieqn-22"><mml:math id="mml-ieqn-22"><mml:mi>y</mml:mi></mml:math></inline-formula> &#x2264; p, and 1 &#x2264; <inline-formula id="ieqn-23"><mml:math id="mml-ieqn-23"><mml:mi>z</mml:mi></mml:math></inline-formula> &#x2264; q. Whereas the edge number of each vertex <inline-formula id="ieqn-24"><mml:math id="mml-ieqn-24"><mml:msub><mml:mi>F</mml:mi><mml:mrow><mml:mi>m</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>, <inline-formula id="ieqn-25"><mml:math id="mml-ieqn-25"><mml:msub><mml:mi>G</mml:mi><mml:mrow><mml:mi>n</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>, <inline-formula id="ieqn-26"><mml:math id="mml-ieqn-26"><mml:msub><mml:mi>H</mml:mi><mml:mrow><mml:mi>o</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>, <inline-formula id="ieqn-27"><mml:math id="mml-ieqn-27"><mml:msub><mml:mi>I</mml:mi><mml:mrow><mml:mi>p</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>, and <inline-formula id="ieqn-28"><mml:math id="mml-ieqn-28"><mml:msub><mml:mi>J</mml:mi><mml:mrow><mml:mi>q</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> used the subscript integers such as <inline-formula id="ieqn-29"><mml:math id="mml-ieqn-29"><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>w</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>x</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>, <inline-formula id="ieqn-30"><mml:math id="mml-ieqn-30"><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>y</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> and <inline-formula id="ieqn-31"><mml:math id="mml-ieqn-31"><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>z</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>, which acts as a counter of the multiple edges.</p>
<table-wrap id="table-1">
<label>Table 1</label>
<caption>
<title>Bidirectional edges having more than one edge from the single vertex</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Edge titles</th>
<th>Starting node</th>
<th>Edge level</th>
</tr>
</thead>
<tbody>
<tr>
<td><inline-formula id="ieqn-32"><mml:math id="mml-ieqn-32"><mml:msubsup><mml:mi mathvariant="bold-italic">&#x03B1;</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">v</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">v</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>Component based level <inline-formula id="ieqn-33"><mml:math id="mml-ieqn-33"><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>b</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>)</td>
<td>Low level</td>
</tr>
<tr>
<td><inline-formula id="ieqn-34"><mml:math id="mml-ieqn-34"><mml:msubsup><mml:mi mathvariant="bold-italic">&#x03B2;</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">w</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">w</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>Base model level <inline-formula id="ieqn-35"><mml:math id="mml-ieqn-35"><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>N</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>)</td>
<td>Component based level</td>
</tr>
<tr>
<td><inline-formula id="ieqn-36"><mml:math id="mml-ieqn-36"><mml:msubsup><mml:mrow><mml:mrow><mml:mtext>&#x03B4;</mml:mtext></mml:mrow></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">x</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">x</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>Upper model level <inline-formula id="ieqn-37"><mml:math id="mml-ieqn-37"><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>O</mml:mi><mml:mrow><mml:mi>p</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>)</td>
<td>Base model level</td>
</tr>
<tr>
<td><inline-formula id="ieqn-38"><mml:math id="mml-ieqn-38"><mml:msubsup><mml:mrow><mml:mrow><mml:mtext>&#x03B5;</mml:mtext></mml:mrow></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">y</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">y</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>Application based level <inline-formula id="ieqn-39"><mml:math id="mml-ieqn-39"><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mi>c</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>)</td>
<td>Upper model level</td>
</tr>
<tr>
<td><inline-formula id="ieqn-40"><mml:math id="mml-ieqn-40"><mml:msubsup><mml:mrow><mml:mrow><mml:mtext>&#x03BB;</mml:mtext></mml:mrow></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">z</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">z</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>User based level <inline-formula id="ieqn-41"><mml:math id="mml-ieqn-41"><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>Q</mml:mi><mml:mrow><mml:mi>r</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>)</td>
<td>Application based level</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The defined edges are revolved in the following order:
<disp-formula id="ueqn-2"><mml:math id="mml-ueqn-2" display="block"><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mtext>&#x00A0;</mml:mtext><mml:mo>&#x003A;</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:mo>,</mml:mo><mml:mo stretchy="false">&#x2192;</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup></mml:math></disp-formula></p>
<p>In terms of interaction edges between the distinct vertices of the abstract graph, explainable components, is described as follows:
<disp-formula id="eqn-2"><label>(2)</label><mml:math id="mml-eqn-2" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd><mml:msub><mml:mi>E</mml:mi><mml:mrow><mml:mi>x</mml:mi></mml:mrow></mml:msub></mml:mtd><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:mi>E</mml:mi><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2286;</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>j</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:mi>E</mml:mi><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2286;</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mi>w</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>w</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mi>k</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>k</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:mi>E</mml:mi><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2286;</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mi>k</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>k</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mi>l</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>l</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:mi>E</mml:mi><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2286;</mml:mo></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mspace width="1em" /><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mi>l</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>l</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mo>&#x222A;</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mi>m</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>m</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:mi>E</mml:mi><mml:mi>x</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x2286;</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mi>m</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>m</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
<p>The defined explainable models are used to enhance the trust of user on the web-based applications which further categorized into the subcomponents that are represented in <xref ref-type="fig" rid="fig-2">Fig. 2</xref>.</p>
</sec>
<sec id="s3_4">
<label>3.4</label>
<title>Explainable User Interactivity Modulation for Multidomain Sentiment Analysis</title>
<p>User Interactive Model develops as a fundamental method that includes transferability, informativeness, and accessibility. This model integrates individuals into the sentiment analysis process by implementing domain-specific information and context through interactive interfaces and feedback mechanisms. Using visualization tools and explanation interfaces, users may get explicit explanations for sentiment predictions, which helps them grasp the analytic results.</p>
<sec id="s3_4_1">
<label>3.4.1</label>
<title>Transferability</title>
<p>Transferability enhances the ability of the system to communicate information. It integrates the attributes to provide domain-specific information for users to improve the model. The <xref ref-type="disp-formula" rid="eqn-3">Eq. (3)</xref> presents the transferability metrics, and the average impact of the transferability is achieved in <xref ref-type="disp-formula" rid="eqn-4">Eq. (4)</xref>.
<disp-formula id="ueqn-4"><mml:math id="mml-ueqn-4" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Previous Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>&#x03C3;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mtext>&#x00A0;</mml:mtext><mml:mrow><mml:mtext>Target Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:mspace width="thinmathspace" /><mml:msub><mml:mo>&#x221D;</mml:mo><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-3"><label>(3)</label><mml:math id="mml-eqn-3" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Transferability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mrow><mml:mo>(</mml:mo><mml:mfrac><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>&#x03C3;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mo>&#x221D;</mml:mo><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow><mml:msub><mml:mi>&#x03C3;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mfrac><mml:mo>&#x2217;</mml:mo><mml:mn>100</mml:mn><mml:mo>)</mml:mo></mml:mrow><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-4"><label>(4)</label><mml:math id="mml-eqn-4" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Average Transferability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo>[</mml:mo><mml:munderover><mml:mo>&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:munderover><mml:mrow><mml:mo>(</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mfrac><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>&#x03C3;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mo>&#x221D;</mml:mo><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow><mml:msub><mml:mi>&#x03C3;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mfrac></mml:mstyle><mml:mo>&#x2217;</mml:mo><mml:mn>100</mml:mn><mml:mo>)</mml:mo></mml:mrow><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
</sec>
<sec id="s3_4_2">
<label>3.4.2</label>
<title>Informativeness</title>
<p>Informativeness provides the interface that successfully delivers information through application in relevant, clear, and efficient ways. It increases the users&#x2019; understanding, confidence, and trust in the system&#x2019;s operations. The metrics are defined in the <xref ref-type="disp-formula" rid="eqn-5">Eq. (5)</xref> and average ratio in <xref ref-type="disp-formula" rid="eqn-6">Eq. (6)</xref>.
<disp-formula id="ueqn-7"><mml:math id="mml-ueqn-7" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Clarity of Modules Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mtext>&#xA0;</mml:mtext><mml:msub><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mspace width="2em" /><mml:mrow><mml:mtext>Relevance of Modules Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>&#x03D1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="ueqn-8"><mml:math id="mml-ueqn-8" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Completeness Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>&#x03C9;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mspace width="2em" /><mml:mrow><mml:mtext>Timeliness Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="ueqn-9"><mml:math id="mml-ueqn-9" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Interactivity Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>&#x03C6;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-5"><label>(5)</label><mml:math id="mml-eqn-5" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Informativeness Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03D1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C9;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C6;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-6"><label>(6)</label><mml:math id="mml-eqn-6" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Average Informativeness Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo>[</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:munderover><mml:mo>&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:munderover><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03D1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C9;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C6;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup></mml:mstyle><mml:mo>]</mml:mo></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
</sec>
<sec id="s3_4_3">
<label>3.4.3</label>
<title>Accessibility</title>
<p>Accessibility presents the data to users more clear and understandable manner irrespective of data analysis. It is achieved by implementing simple language and removing any advanced terminologies that are difficult to understand.
<disp-formula id="ueqn-12"><mml:math id="mml-ueqn-12" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Linguistic Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mspace width="2em" /><mml:mrow><mml:mtext>Visuality Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>V</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mspace width="2em" /><mml:mrow><mml:mtext>Formative Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mmultiscripts><mml:mrow><mml:mi mathvariant="normal">F</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:none/><mml:mprescripts/><mml:none/><mml:mrow><mml:mo>&#x2218;</mml:mo></mml:mrow></mml:mmultiscripts></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-7"><label>(7)</label><mml:math id="mml-eqn-7" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Accessibility Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>V</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:msup><mml:mo>+</mml:mo><mml:mo>&#x2218;</mml:mo></mml:msup><mml:msub><mml:mrow><mml:mi mathvariant="normal">F</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
<p>The <xref ref-type="disp-formula" rid="eqn-7">Eq. (7)</xref> gives the complete accessibility metrics, and the average ratio of the accessibility metrics is defined in <xref ref-type="disp-formula" rid="eqn-8">Eq. (8)</xref>.
<disp-formula id="eqn-8"><label>(8)</label><mml:math id="mml-eqn-8" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Average Accessibility Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo>[</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>V</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:msup><mml:mo>+</mml:mo><mml:mo>&#x2218;</mml:mo></mml:msup><mml:msub><mml:mrow><mml:mi mathvariant="normal">F</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup></mml:mstyle><mml:mo>]</mml:mo></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
<p>Various components are used to measure the user interactive model. The metrics of <xref ref-type="disp-formula" rid="eqn-3">Eqs. (3)</xref>, <xref ref-type="disp-formula" rid="eqn-5">(5)</xref>, and <xref ref-type="disp-formula" rid="eqn-7">(7)</xref> are added up in <xref ref-type="disp-formula" rid="eqn-9">Eq. (9)</xref> to measure the overall impact on the model.
<disp-formula id="eqn-9"><label>(9)</label><mml:math id="mml-eqn-9" display="block"><mml:mrow><mml:mtext>XUIM</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mrow><mml:mo>(</mml:mo><mml:mfrac><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>&#x03C3;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mo>&#x221D;</mml:mo><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow><mml:msub><mml:mi>&#x03C3;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mfrac><mml:mo>&#x2217;</mml:mo><mml:mn>100</mml:mn><mml:mo>)</mml:mo></mml:mrow><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03D1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C9;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03C6;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>V</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:msup><mml:mo>+</mml:mo><mml:mo>&#x2218;</mml:mo></mml:msup><mml:msub><mml:mrow><mml:mi mathvariant="normal">F</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>XUIM is measured in <xref ref-type="disp-formula" rid="eqn-10">Eq. (10)</xref> and <xref ref-type="disp-formula" rid="eqn-11">Eq. (11)</xref> shows the average impact of the model.
<disp-formula id="eqn-10"><label>(10)</label><mml:math id="mml-eqn-10" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Overall Impact of the XUIM</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mi>X</mml:mi><mml:mi>U</mml:mi><mml:mi>I</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-11"><label>(11)</label><mml:math id="mml-eqn-11" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Average Impact of the XUIM</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mfrac><mml:mrow><mml:mi>X</mml:mi><mml:mi>U</mml:mi><mml:mi>I</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
</sec>
</sec>
<sec id="s3_5">
<label>3.5</label>
<title>Explainable Transparency Modulation for Multidomain Sentiment Analysis</title>
<p>Transparency is the major gain of trust for the users in the sentient analysis application. It provides the details and a clear decision process to the users. Various methodologies are implemented to gain a transparent system for applications. These methodologies allow the users to understand and observe the output of the model in the multidomain sentiment analysis applications.</p>
<sec id="s3_5_1">
<label>3.5.1</label>
<title>Simulatability</title>
<p>Simulatability in a transparent model allow the users to replicate and grasp the model&#x2019;s decision-making process. It also enhances the user confidence in the model&#x2019;s output by enhancing the accuracy and fairness of the prediction.
<disp-formula id="eqn-12"><label>(12)</label><mml:math id="mml-eqn-12" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Simplicity Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mspace width="2em" /><mml:mrow><mml:mtext>Usability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>U</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mspace width="2em" /><mml:mrow><mml:mtext>Complexity Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Simulatability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>U</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
<p>Various components such as usability, simplicity, and model&#x2019;s complexity are measured in the simulatability presented in <xref ref-type="disp-formula" rid="eqn-12">Eq. (12)</xref> and average ratio in <xref ref-type="disp-formula" rid="eqn-13">Eq. (13)</xref>.
<disp-formula id="eqn-13"><label>(13)</label><mml:math id="mml-eqn-13" display="block"><mml:mrow><mml:mtext>Average ratio of Simulatability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo stretchy="false">[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>U</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo stretchy="false">]</mml:mo></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:math></disp-formula></p>
</sec>
<sec id="s3_5_2">
<label>3.5.2</label>
<title>Decomposability</title>
<p>Decomposability provides the conversion of the large problem into smaller components that help the users to easily grasp the knowledge. Users can enhance the model&#x2019;s prediction by integrating the specifications, characteristics, and decision rules. These components are merged back in a way that can easily be managed by the users.
<disp-formula id="ueqn-2242"><mml:math id="mml-ueqn-2242" display="block"><mml:mrow><mml:mtext>Edges Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2203;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mspace width="2em" /><mml:mrow><mml:mtext>Nodes Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2202;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mrow><mml:mtext>Connected Components</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mmultiscripts><mml:mrow><mml:mi mathvariant="normal">C</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:none/><mml:mprescripts/><mml:none/><mml:mrow><mml:mo>&#x2218;</mml:mo></mml:mrow></mml:mmultiscripts></mml:math></disp-formula>
<disp-formula id="ueqn-21"><mml:math id="mml-ueqn-21" display="block"><mml:mrow><mml:mtext>Cyclometric Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2203;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2212;</mml:mo><mml:mo>&#x2229;</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2202;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msup><mml:mn>2</mml:mn><mml:mo>&#x2218;</mml:mo></mml:msup><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></disp-formula>
<disp-formula id="eqn-14"><label>(14)</label><mml:math id="mml-eqn-14" display="block"><mml:mrow><mml:mtext>Decomposability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2203;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2212;</mml:mo><mml:mo>&#x2229;</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2202;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msup><mml:mn>2</mml:mn><mml:mo>&#x2218;</mml:mo></mml:msup><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup></mml:mstyle><mml:mo>]</mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>Decomposability metrics are calculated by implementing in <xref ref-type="disp-formula" rid="eqn-14">Eq. (14)</xref> and <xref ref-type="disp-formula" rid="eqn-15">Eq. (15)</xref> describes the average ratio.
<disp-formula id="eqn-15"><label>(15)</label><mml:math id="mml-eqn-15" display="block"><mml:mrow><mml:mtext>Average Decomposability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo>[</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2203;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2212;</mml:mo><mml:mo>&#x2229;</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2202;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msup><mml:mn>2</mml:mn><mml:mo>&#x2218;</mml:mo></mml:msup><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup></mml:mstyle><mml:mo>]</mml:mo></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:math></disp-formula></p>
</sec>
<sec id="s3_5_3">
<label>3.5.3</label>
<title>Algorithmic Transparency</title>
<p>Transparency of the algorithm in an explainable model is critical for building trust in its predictions. This refers to making the algorithm&#x2019;s inner workings and decision-making processes transparent and accessible to users. Explainable models can boost their usability and efficiency across a wide range of applications, allowing users to make more informed decisions based on a better understanding of the model&#x2019;s behavior via algorithmic transparency, which is estimated in <xref ref-type="disp-formula" rid="eqn-16">Eq. (16)</xref>.
<disp-formula id="ueqn-44"><mml:math id="mml-ueqn-44" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Robustness Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>&#x03BC;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mrow><mml:mtext>Bias Detection Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Data Accountability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2200;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="2em" /><mml:mrow><mml:mtext>Traceability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mi>&#x03C4;</mml:mi><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Sustainability Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:msub><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-16"><label>(16)</label><mml:math id="mml-eqn-16" display="block"><mml:mrow><mml:mtext>Algorithmic Transparency</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>&#x03BC;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2200;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mi>&#x03C4;</mml:mi><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:msub><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup></mml:mstyle><mml:mo>]</mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>The average ratio has the impact on the overall transparent model defined in <xref ref-type="disp-formula" rid="eqn-17">Eq. (17)</xref>.
<disp-formula id="eqn-17"><label>(17)</label><mml:math id="mml-eqn-17" display="block"><mml:mrow><mml:mtext>Average Algorithmic Transparency</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo>[</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>&#x03BC;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2200;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mi>&#x03C4;</mml:mi><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:msub><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup></mml:mstyle><mml:mo>]</mml:mo></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:math></disp-formula></p>
<p>The above-mentioned metrics of XTPM are used to measure transparency in explainability. The overall design metrics are combined in <xref ref-type="disp-formula" rid="eqn-18">Eq. (18)</xref>.
<disp-formula id="eqn-18"><label>(18)</label><mml:math id="mml-eqn-18" display="block"><mml:mrow><mml:mtext>XTPM</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>U</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2203;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2212;</mml:mo><mml:mo>&#x2229;</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2202;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msup><mml:mn>2</mml:mn><mml:mo>&#x2218;</mml:mo></mml:msup><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>&#x03BC;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi mathvariant="normal">&#x2200;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mi>&#x03C4;</mml:mi><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:msub><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo>]</mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>The overall impact of the XTPM is measured in <xref ref-type="disp-formula" rid="eqn-19">Eq. (19)</xref> and average impact in <xref ref-type="disp-formula" rid="eqn-20">Eq. (20)</xref>.
<disp-formula id="eqn-19"><label>(19)</label><mml:math id="mml-eqn-19" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Overall Impact of XTPM</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mi>X</mml:mi><mml:mi>T</mml:mi><mml:mi>P</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-20"><label>(20)</label><mml:math id="mml-eqn-20" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Average Impact of the XTPM Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mfrac><mml:mrow><mml:mi>X</mml:mi><mml:mi>T</mml:mi><mml:mi>P</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
<p>We define the metrics of individual components of explainable model and merge them into respective model. Given defined models such as User Interactive model and Transparent model have directly impact on the explainability of the web-based application as shown in <xref ref-type="disp-formula" rid="eqn-21">Eq. (21)</xref> and average impact is defined in <xref ref-type="disp-formula" rid="eqn-22">Eq. (22)</xref>.
<disp-formula id="ueqn-29"><mml:math id="mml-ueqn-29" display="block"><mml:mrow><mml:mtext>User Interactive Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mi>X</mml:mi><mml:mi>U</mml:mi><mml:mi>I</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mspace width="1em" /><mml:mspace width="1em" /><mml:mrow><mml:mtext>Transparent Metrics</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mi>X</mml:mi><mml:mi>T</mml:mi><mml:mi>P</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></disp-formula>
<disp-formula id="eqn-21"><label>(21)</label><mml:math id="mml-eqn-21" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Overall Impact of Explainable Model Metrics</mml:mtext></mml:mrow><mml:mrow><mml:mo>(</mml:mo><mml:mi>X</mml:mi><mml:mi>D</mml:mi><mml:mi>C</mml:mi><mml:mi>U</mml:mi><mml:mi>I</mml:mi><mml:mi>T</mml:mi><mml:mi>M</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:mi>X</mml:mi><mml:mi>U</mml:mi><mml:mi>I</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mi>X</mml:mi><mml:mi>T</mml:mi><mml:mi>P</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<disp-formula id="eqn-22"><label>(22)</label><mml:math id="mml-eqn-22" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd /><mml:mtd><mml:mrow><mml:mtext>Average Impact of Explainable Model Metrics&#xA0;</mml:mtext></mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>X</mml:mi><mml:mi>D</mml:mi><mml:mi>C</mml:mi><mml:mi>U</mml:mi><mml:mi>I</mml:mi><mml:mi>T</mml:mi><mml:mi>M</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo stretchy="false">[</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>0</mml:mn></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msubsup><mml:mo stretchy="false">(</mml:mo><mml:mi>X</mml:mi><mml:mi>U</mml:mi><mml:mi>I</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mi>X</mml:mi><mml:mi>T</mml:mi><mml:mi>P</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mi>&#x03F5;</mml:mi><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:msup><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo stretchy="false">]</mml:mo></mml:mrow><mml:mi>n</mml:mi></mml:mfrac></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
<p>The value of the overall metrics presents that the explainable model is implemented successfully. The average acceptance scale to introduce the explainability for the end users in the web-based applications is based on the [<xref ref-type="bibr" rid="ref-26">26</xref>] and by using the web content accessibility guidelines. The following defined is the range of the metrics values:</p>
<p>Low (&#x003C;10), Medium (10 to 20), High (&#x003E;20)</p>
<p>The highest value of the metric measured indicates that the model is implemented perfectly and achieves explainability in all aspects.</p>
</sec>
</sec>
<sec id="s3_6">
<label>3.6</label>
<title>Explainable Design Complexity Calculation for Multidomain Sentiment Analysis</title>
<p>Various components of explainable model are implemented in the web-based application which define the Explainable Design Quality Complexity Metric given as follows:
<disp-formula id="eqn-23"><label>(23)</label><mml:math id="mml-eqn-23" display="block"><mml:mrow><mml:mtext>EDCM</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>v</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>m</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>m</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>v</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>w</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>w</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>n</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>n</mml:mi><mml:mrow><mml:mi>w</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mi>w</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>w</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>x</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>x</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>o</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>o</mml:mi><mml:mrow><mml:mi>x</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>x</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>y</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>y</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>p</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>p</mml:mi><mml:mrow><mml:mi>y</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mi>y</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>y</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>z</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>z</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>q</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>q</mml:mi><mml:mrow><mml:mi>z</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mi>z</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi>i</mml:mi><mml:mrow><mml:mi>z</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msubsup></mml:math></disp-formula></p>
<p>The unique value is assigned to each relation of edge as a weight value. The average design complexity of explainable web-based application is calculated as
<disp-formula id="eqn-24"><label>(24)</label><mml:math id="mml-eqn-24" display="block"><mml:mrow><mml:mtext>Average Design Complexity</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mtext>Total Number of Relations</mml:mtext></mml:mrow><mml:mrow><mml:mtext>Total Number of Components</mml:mtext></mml:mrow></mml:mfrac></mml:math></disp-formula></p>
<p>This metric defines the overall complexity of the web-based application by introducing the explainability and interaction of its various components.</p>
</sec>
</sec>
<sec id="s4">
<label>4</label>
<title>Results and Discussions</title>
<p>The web-based multidomain sentiment analysis application is considered as a case study to evaluate the design quality metrics of explainable model defined in this work. In this web-based application for multidomain sentiment analysis various explainable models are introduced to provide the detail web-based application at the user end. In the multidomain sentiment analysis, users are interacting with the application and give input as a sentence of specific domain and get the output as a positive, negative, or neutral sentiment. We consider the web-based application for multidomain sentiment analysis which provides the explainability using various parameters illustrated in <xref ref-type="fig" rid="fig-4">Fig. 4</xref>.</p>
<fig id="fig-4">
<label>Figure 4</label>
<caption>
<title>UML for multidomain sentiment analysis design with explainable model building</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_57359-fig-4.tif"/>
</fig>
<p>Various numbers of users are interacted with the application and the defined parameters ensure the explainability to implement numerous factors in the application. The factors include relevancy, completeness, timeliness, language relevancy, edges, and nodes. These factors provide the information to the respective component which further transfers to each related model.</p>
<p>This information enables the explainable model which helps to enhance the performance of the system and provide the secure, transparent, interpretable, and interactive system to the user. The systems explainability can be checked through these parameters. Moreover, these parameters can be incorporated according to the requirements of the users.</p>
<p>For the evaluation of the defined metrics, we consider the different scenarios of the case study. The low-level parameters and their working are defined in <xref ref-type="table" rid="table-2">Table 2</xref>.</p>
<table-wrap id="table-2">
<label>Table 2</label>
<caption>
<title>End-level parameters and their working in web-based applications</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Factors (Bottom stage)</th>
<th>Factors description</th>
</tr>
</thead>
<tbody>
<tr>
<td>Transferability to Next Module Score (TNMS)</td>
<td>Transition performance from previous to current module</td>
</tr>
<tr>
<td>Relevancy (RL)</td>
<td>Provide related information</td>
</tr>
<tr>
<td>Completeness (CT)</td>
<td>Cover all aspects of the information</td>
</tr>
<tr>
<td>Timeliness (TL)</td>
<td>Provide time sensitive information</td>
</tr>
<tr>
<td>Language Relevancy (LR)</td>
<td>User understandable language</td>
</tr>
<tr>
<td>Effectiveness of Visualization (EV)</td>
<td>Provide detailed and clear visualization</td>
</tr>
<tr>
<td>Transparency Score (TC)</td>
<td>Provide transparency of the system</td>
</tr>
<tr>
<td>Complexity Score (CS)</td>
<td>Provide simple interface to user</td>
</tr>
<tr>
<td>Edges (E)</td>
<td>Number of edges in the control graph</td>
</tr>
<tr>
<td>Nodes (N)</td>
<td>Number of nodes in the control graph</td>
</tr>
<tr>
<td>Connected Components (CP)</td>
<td>Number of connected components in control graph</td>
</tr>
<tr>
<td>Bias Detection Score (BDS)</td>
<td>Bias exists in system</td>
</tr>
<tr>
<td>User control Score (UCS)</td>
<td>System is controlled by user</td>
</tr>
<tr>
<td>Traceability Score (TC)</td>
<td>Trace the flow of data</td>
</tr>
<tr>
<td>Sustainability Score (SS)</td>
<td>Transparency maintained over time</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>These parameters help to implement the explainability in the overall application for the user and transfer data from the databases to the user interface. The user gets the details of each module in the web-based application through the implemented parameters which helps to deal with the transparent system.</p>
<sec id="s4_1">
<label>4.1</label>
<title>Scenario 1: Explainable Transparency Using XUIMM and XTPM</title>
<p>In the user-interactive model, the aim is to make the system explainable at the user interface. To introduce this explainability, we implement three parameters in this model. Therefore, the complexity of the user-interactive model is calculated using three scenarios. <xref ref-type="fig" rid="fig-5">Fig. 5</xref> depicts Scenario 1 where the green line is moved from the XUIMM to the transferability parameter and simulatability parameter from the XTPMM.</p>
<fig id="fig-5">
<label>Figure 5</label>
<caption>
<title>Spiral Graph showing the comparative evaluations for Scenario 1 (Green), Scenario 2 (Blue) and Scenario 3 (Red) of web-based application for multi-domain sentiment analysis</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_57359-fig-5.tif"/>
</fig>
<p>The total number of edges is the complexity of this parameter. The complexity of the transferability parameter to introduce explainability is calculated using <xref ref-type="disp-formula" rid="eqn-25">Eq. (25)</xref> which is 5 units.
<disp-formula id="eqn-25"><label>(25)</label><mml:math id="mml-eqn-25" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mtext>XUIMM</mml:mtext></mml:mrow></mml:mtd><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>=</mml:mo><mml:mn>5</mml:mn><mml:mspace width="thinmathspace" /><mml:mrow><mml:mtext>units</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
<p><xref ref-type="disp-formula" rid="eqn-26">Eq. (26)</xref> provides the complexity of simulatability factors of XTPMM which is 6 units.
<disp-formula id="eqn-26"><label>(26)</label><mml:math id="mml-eqn-26" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mtext>XTPMM</mml:mtext></mml:mrow></mml:mtd><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>=</mml:mo><mml:mn>6</mml:mn><mml:mspace width="thinmathspace" /><mml:mrow><mml:mtext>units</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
</sec>
<sec id="s4_2">
<label>4.2</label>
<title>Scenario 2: Transferability and Informativeness Using XUIMM and XTPM</title>
<p>In Scenario 2 for user-interactive model, the transferability and informativeness parameters are implemented. In <xref ref-type="fig" rid="fig-5">Fig. 5</xref>, the green and blue lines are used to calculate the complexity of the defined parameters. The <xref ref-type="disp-formula" rid="eqn-27">Eq. (27)</xref> describes that the complexity is 9 units to implement this model.
<disp-formula id="eqn-27"><label>(27)</label><mml:math id="mml-eqn-27" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mtext>XUIMM</mml:mtext></mml:mrow></mml:mtd><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>=</mml:mo><mml:mn>9</mml:mn><mml:mspace width="thinmathspace" /><mml:mrow><mml:mtext>units</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>

<p>We consider two parameters of XTPMM such as simulatability and decomposability to evaluate the complexity of this model in explainable model. The 10 units are used to define the complexity of this scenario mentioned in <xref ref-type="disp-formula" rid="eqn-28">Eq. (28)</xref> by using the lines green and blue presents in <xref ref-type="fig" rid="fig-5">Fig. 5</xref>.
<disp-formula id="eqn-28"><label>(28)</label><mml:math id="mml-eqn-28" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mtext>XTPMM</mml:mtext></mml:mrow></mml:mtd><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>5</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>=</mml:mo><mml:mn>10</mml:mn><mml:mspace width="thinmathspace" /><mml:mrow><mml:mtext>units</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>

</sec>
<sec id="s4_3">
<label>4.3</label>
<title>Scenario 3: Algorithmic Transparency Using XUIMM and XTPM</title>
<p>Explainability of the web-based application can extend by incorporating one more parameter in XUIMM and XTPMM which is accessibility and algorithmic transparency. In Scenario 3, we incorporate all the three defined models which enhance the explainability of the system. <xref ref-type="fig" rid="fig-5">Fig. 5</xref> depicts the green, blue, and red lines intersecting each level. Therefore, we select all the edges of the XUIMM to calculate its complexity which is 12 units defined in <xref ref-type="disp-formula" rid="eqn-29">Eq. (29)</xref>.
<disp-formula id="eqn-29"><label>(29)</label><mml:math id="mml-eqn-29" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mtext>XUIMM</mml:mtext></mml:mrow></mml:mtd><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>5</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>6</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>=</mml:mo><mml:mn>12</mml:mn><mml:mspace width="thinmathspace" /><mml:mrow><mml:mtext>&#xA0;units</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>

<p>The three parameters are defined in XTPMM including simulatability, decomposability, and algorithmic transparency. In Scenario 3, all these parameters are used to measure the complexity of the model. The major emphasizes of the complexity described in <xref ref-type="disp-formula" rid="eqn-30">Eq. (30)</xref> is the factors that are defined in this model such as TC, CS, E, N, CP, UCS, BDS, TC, and SS.
<disp-formula id="eqn-30"><label>(30)</label><mml:math id="mml-eqn-30" display="block"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mtext>XTPMM</mml:mtext></mml:mrow></mml:mtd><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>5</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>6</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>7</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>8</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>9</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mtd></mml:mtr><mml:mtr><mml:mtd /><mml:mtd><mml:mi></mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>=</mml:mo><mml:mn>15</mml:mn><mml:mspace width="thinmathspace" /><mml:mrow><mml:mtext>&#xA0;units</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></p>
<p>The average complexity to implement all the parameters of XUIMM is calculated with defined factors such as TNMS, RL, CT, TL, LR, and EV. All the scenarios are considered to get the average complexity of the user-interactive model which is (5 &#x002B; 9 &#x002B; 12)/3 &#x003D; (26)/3 &#x003D; 8 units. The Average explainable complexity of the transparent model is calculated to be (6 &#x002B; 10 &#x002B; 15)/3 &#x003D; (31)/3 &#x003D; 10 units, which is acceptable for this model.</p>
</sec>
<sec id="s4_4">
<label>4.4</label>
<title>Explainable Design Complexity Modulation</title>
<p>The design complexity metrics determine the overall complexity of the web-based application to introduce the explainable model. Different scenarios are considered to measure the complexity with various parameters of defined models. Green, blue, and red lines in <xref ref-type="fig" rid="fig-5">Fig. 5</xref> depict the complete scenarios to calculate complexity by providing details of each model. The design complexity of this web-based application is measured with the XDCM metrics by evaluating the unit cost of each factor and parameters involved in the model.
<disp-formula id="ueqn-40"><mml:math id="mml-ueqn-40" display="block"><mml:mrow><mml:mtext>XDCM</mml:mtext></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>5</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>6</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>5</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>6</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>7</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>8</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>9</mml:mn></mml:mrow></mml:msubsup></mml:math></disp-formula>
<disp-formula id="ueqn-41"><mml:math id="mml-ueqn-41" display="block"><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msubsup></mml:math></disp-formula>
<disp-formula id="ueqn-42"><mml:math id="mml-ueqn-42" display="block"><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03B5;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>+</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="normal">&#x03BB;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>=</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mn>15</mml:mn><mml:mo>+</mml:mo><mml:mn>6</mml:mn><mml:mo>+</mml:mo><mml:mn>2</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mn>1</mml:mn><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mn>25</mml:mn></mml:math></disp-formula></p>

<p>The average design complexity is 10 to 20 units in this case study of a web-based multidomain sentiment analysis application which is calculated as (25/26). It is the perfect case as it is less than the total number of components. Therefore, our design-level explainable model is an extremely simple system for web-based applications.</p>
</sec>
<sec id="s4_5">
<label>4.5</label>
<title>Discussion</title>
<p>In this proposed work, design quality metrics of the explainable model for web-based applications are evaluated for multi-domain sentiment analysis. An abstract graph is utilized to implement the explainable model on web-based applications. Design models are defined to develop design quality metrics, including Explainable User-Interactive Model Metrics, Explainable Transparent Model Metrics, and Explainable Design Complexity Metrics. The defined metrics are evaluated using a case study of a web-based multi-domain sentiment analysis application, and results are compared with the assigned work range in this study. The X-OODM can be integrated into existing methodologies as a learning curve by facilitating developers with object-oriented design and explainability principles. System developers map the components of explainability, including transferability, fairness, and transparency, into the multi-domain sentiment analysis application, which is then implemented through various tools and libraries to ensure the explainable design level. These explained elements such as transferability, fairness, and transparency are mapped to the multi-domain sentiment analysis application developed by the system developers for the purpose of implementation using different tools and libraries to ensure an appropriate explainable design level.</p>
<p>In <xref ref-type="table" rid="table-3">Table 3</xref>, we present the results of every overall scenario and, after that, benchmark it to the realistic result. The results of the defined metrics are validated against benchmark values obtained from experts in web-based applications. Defined metrics yield accurate values that are consistent with the predicted parameters. Parameters such as completeness, timeliness, and interaction time with other modules are employed to measure scalability at the design level. The values of these parameters are utilized to assess the scalability of the system when large data is input to the application. The optimal model is the one that provides higher explainability in the web-based application, which corresponds to the defined metrics with the maximum values.</p>
<table-wrap id="table-3">
<label>Table 3</label>
<caption>
<title>Explainable path of design for web-based application</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
<col/>
<col align="center"/>
<col/>
</colgroup>
<thead>
<tr>
<th>Evaluation scenario</th>
<th>Nodes</th>
<th>Edges</th>
<th align="center">Explainable design path</th>
<th>Weights of paths</th>
</tr>
</thead>
<tbody>
<tr>
<td><bold>Scenario 1:</bold></td>
<td>Low-end</td>
<td><inline-formula id="ieqn-42"><mml:math id="mml-ieqn-42"><mml:mi>&#x03B1;</mml:mi></mml:math></inline-formula></td>
<td>Max (<inline-formula id="ieqn-43"><mml:math id="mml-ieqn-43"><mml:mi>&#x03B1;</mml:mi></mml:math></inline-formula>)</td>
<td>3</td>
</tr>
<tr>
<td rowspan="4"><bold><italic>Explainable Transparency Using XUIMM and XTPM</italic></bold>)</td>
<td>Component level</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Basic model level</td>
<td><inline-formula id="ieqn-44"><mml:math id="mml-ieqn-44"><mml:mi>&#x03B2;</mml:mi></mml:math></inline-formula></td>
<td>Max <inline-formula id="ieqn-45"><mml:math id="mml-ieqn-45"><mml:mo>&#x2211;</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:mi>y</mml:mi></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>2</td>
</tr>
<tr>
<td>Upper model level</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>User level</td>
<td><inline-formula id="ieqn-46"><mml:math id="mml-ieqn-46"><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow></mml:math></inline-formula></td>
<td>Max (<inline-formula id="ieqn-47"><mml:math id="mml-ieqn-47"><mml:mi>&#x03B2;</mml:mi></mml:math></inline-formula>)</td>
<td>2</td>
</tr>
<tr>
<td><bold>Scenario 2:</bold></td>
<td>Low-end</td>
<td><inline-formula id="ieqn-48"><mml:math id="mml-ieqn-48"><mml:mi>&#x03B1;</mml:mi></mml:math></inline-formula></td>
<td>Max (<inline-formula id="ieqn-49"><mml:math id="mml-ieqn-49"><mml:mi>&#x03B1;</mml:mi></mml:math></inline-formula>)</td>
<td>9</td>
</tr>
<tr>
<td rowspan="4"><bold><italic>Transferability and Informativeness Using XUIMM and XTPM</italic></bold></td>
<td>Component level</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Basic model level</td>
<td><inline-formula id="ieqn-50"><mml:math id="mml-ieqn-50"><mml:mi>&#x03B2;</mml:mi></mml:math></inline-formula></td>
<td>Max <inline-formula id="ieqn-51"><mml:math id="mml-ieqn-51"><mml:mo>&#x2211;</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:mi>y</mml:mi></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>4</td>
</tr>
<tr>
<td>Upper model level</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>User level</td>
<td><inline-formula id="ieqn-52"><mml:math id="mml-ieqn-52"><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow></mml:math></inline-formula></td>
<td>Max (<inline-formula id="ieqn-53"><mml:math id="mml-ieqn-53"><mml:mi>&#x03B2;</mml:mi></mml:math></inline-formula>)</td>
<td>2</td>
</tr>
<tr>
<td><bold>Scenario 3:</bold></td>
<td>Low-end</td>
<td><inline-formula id="ieqn-54"><mml:math id="mml-ieqn-54"><mml:mi>&#x03B1;</mml:mi></mml:math></inline-formula></td>
<td>Max (<inline-formula id="ieqn-55"><mml:math id="mml-ieqn-55"><mml:mi>&#x03B1;</mml:mi></mml:math></inline-formula>)</td>
<td>15</td>
</tr>
<tr>
<td rowspan="4"><bold><italic>Algorithmic Transparency Using XUIMM and XTPM</italic></bold></td>
<td>Component level</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Basic model level</td>
<td><inline-formula id="ieqn-56"><mml:math id="mml-ieqn-56"><mml:mi>&#x03B2;</mml:mi></mml:math></inline-formula></td>
<td>Max <inline-formula id="ieqn-57"><mml:math id="mml-ieqn-57"><mml:mo>&#x2211;</mml:mo><mml:msubsup><mml:mi>&#x03B1;</mml:mi><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:mi>y</mml:mi></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>6</td>
</tr>
<tr>
<td>Upper model level</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>User level</td>
<td><inline-formula id="ieqn-58"><mml:math id="mml-ieqn-58"><mml:mrow><mml:mi mathvariant="normal">&#x03B4;</mml:mi></mml:mrow></mml:math></inline-formula></td>
<td>Max (<inline-formula id="ieqn-59"><mml:math id="mml-ieqn-59"><mml:mi>&#x03B2;</mml:mi></mml:math></inline-formula>)</td>
<td>2</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec id="s5">
<label>5</label>
<title>Conclusion</title>
<p>This research highlights that X-OODM serves as an important contribution to developing multi-domain sentiment analysis systems by enriching the traditional OODM with explainability attributes. It fills up the critical gap of transparency and interpretability that so far existed without explanations inside web-based applications of sentiment analysis. The proposed methodology makes all the design elements, from data structure to user interfaces, more transparent with better user trust and decision-making. Thus, the experiments prove that explainability should be introduced early in the design process to result in sturdy, user-friendly, and trustworthy systems. This contribution thus marks a new benchmark for future work on sentiment analysis systems, such that systems are not only highly accurate but also understandable and reliable when presented to end-users. The paper further introduces design quality metrics such as Explainable User-Interactive Model Metrics, Explainable Transparent Model Metrics, and Explainable Design Complexity Metrics which are fundamental in assessing the explainability of multi-domain sentiment analysis systems. Using these metrics, the research reveals that the deployment of X-OODM based sentiment analysis systems increases the transparency of the system while holding its design complexity at manageable levels to make applications of the system more efficient and interpretive.</p>
</sec>
</body>
<back>
<ack>
<p>The authors sincerely acknowledge the support from collaborators for this research.</p>
</ack>
<sec>
<title>Funding Statement</title>
<p>The authors acknowledge the support of the Deanship of Research and Graduate Studies at Ajman University under Projects 2024-IRG-ENiT-36 and 2024-IRG-ENIT-29.</p>
</sec>
<sec>
<title>Author Contributions</title>
<p>Conceptualization, proposed framework and developing the methodology for writing the original work were led by Abqa Javed. Abdul Jaleel, M. Shoaib and M. Deriche supervised the algorithm implementation, data analysis and results, developed by Abqa Javed. Sharjeel Nawaz contributed in validation, investigation, resources, data curation and original draft preparation. M. Shoaib leaded the final writing whereas M. Deriche worked on review, edition, validation and funding acquisition. All authors reviewed the results and approved the final version of the manuscript.</p>
</sec>
<sec sec-type="data-availability">
<title>Availability of Data and Materials</title>
<p>Data used in this research are available on request.</p>
</sec>
<sec>
<title>Ethics Approval</title>
<p>Not applicable.</p>
</sec>
<sec sec-type="COI-statement">
<title>Conflicts of Interest</title>
<p>The authors declare no conflicts of interest to report regarding the present study.</p>
</sec>
<ref-list content-type="authoryear">
<title>References</title>
<ref id="ref-1"><label>[1]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Swacha</surname> <given-names>J</given-names></string-name>, <string-name><surname>Kulpa</surname> <given-names>A</given-names></string-name></person-group>. <article-title>Evolution of popularity and multiaspectual comparison of widely used web development frameworks</article-title>. <source>Electronics</source>. <year>2023</year>;<volume>12</volume>(<issue>17</issue>):<fpage>3563</fpage>. doi:<pub-id pub-id-type="doi">10.3390/electronics12173563</pub-id>.</mixed-citation></ref>
<ref id="ref-2"><label>[2]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Bektemyssova</surname> <given-names>G</given-names></string-name>, <string-name><surname>Guldana</surname> <given-names>S</given-names></string-name>, <string-name><surname>Yerassyl</surname> <given-names>A</given-names></string-name></person-group>. <article-title>Application of recommended systems for E-commerce</article-title>. <source>Procedia Comput Sci</source>. <year>2024</year>;<volume>231</volume>:<fpage>329</fpage>&#x2013;<lpage>34</lpage>. doi:<pub-id pub-id-type="doi">10.1016/j.procs.2023.12.212</pub-id>.</mixed-citation></ref>
<ref id="ref-3"><label>[3]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Abdessamad</surname> <given-names>B</given-names></string-name>, <string-name><surname>Boumhidi</surname> <given-names>A</given-names></string-name>, <string-name><surname>Nfaoui</surname> <given-names>EH</given-names></string-name></person-group>. <article-title>Mining online reviews to support customers&#x2019; decision-making process in E-commerce platforms: a narrative literature review</article-title>. <source>J Organ Comput Electron Commerce</source>. <year>2022</year>;<volume>32</volume>(<issue>1</issue>):<fpage>69</fpage>&#x2013;<lpage>97</lpage>. doi:<pub-id pub-id-type="doi">10.1080/10919392.2022.2053454</pub-id>.</mixed-citation></ref>
<ref id="ref-4"><label>[4]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Georgios</surname> <given-names>K</given-names></string-name>, <string-name><surname>Davrazos</surname> <given-names>G</given-names></string-name>, <string-name><surname>Kotsiantis</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Explainable artificial intelligence-based decision support systems: a recent review</article-title>. <source>Electronics</source>. <year>2024</year>;<volume>13</volume>(<issue>14</issue>):<fpage>2842</fpage>. doi:<pub-id pub-id-type="doi">10.3390/electronics13142842</pub-id>.</mixed-citation></ref>
<ref id="ref-5"><label>[5]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Alexandra</surname> <given-names>VA</given-names></string-name>, <string-name><surname>B&#x0103;dic&#x0103;</surname> <given-names>C</given-names></string-name></person-group>. <article-title>Recommender systems: an explainable AI perspective</article-title>. In: <conf-name>2021 International Conference on Innovations in Intelligent Systems and Applications (INISTA)</conf-name>; <year>2021</year>; <publisher-loc>Kocaeli, Turkey</publisher-loc>: <publisher-name>IEEE</publisher-name>. p. <fpage>1</fpage>&#x2013;<lpage>6</lpage>.</mixed-citation></ref>
<ref id="ref-6"><label>[6]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Rajesh</surname> <given-names>S</given-names></string-name>, <string-name><surname>Ray</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Explanations in recommender systems: an overview</article-title>. <source>Int J Bus Inf Syst</source>. <year>2016</year>;<volume>23</volume>(<issue>2</issue>):<fpage>248</fpage>&#x2013;<lpage>62</lpage>. doi:<pub-id pub-id-type="doi">10.1504/IJBIS.2016.078909</pub-id>.</mixed-citation></ref>
<ref id="ref-7"><label>[7]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Fabian</surname> <given-names>G</given-names></string-name>, <string-name><surname>Tomitza</surname> <given-names>C</given-names></string-name>, <string-name><surname>Winkelmann</surname> <given-names>A</given-names></string-name></person-group>. <article-title>Comparing expert systems and their explainability through similarity</article-title>. <source>Decis Support Syst</source>. <year>2024</year>;<volume>182</volume>(<issue>1</issue>):<fpage>114248</fpage>. doi:<pub-id pub-id-type="doi">10.1016/j.dss.2024.114248</pub-id>.</mixed-citation></ref>
<ref id="ref-8"><label>[8]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Guanghao</surname> <given-names>X</given-names></string-name>, <string-name><surname>Yan</surname> <given-names>K</given-names></string-name>, <string-name><surname>Zhou</surname> <given-names>X</given-names></string-name></person-group>. <article-title>A distributed learning-based sentiment analysis methods with web applications</article-title>. <source>World Wide Web</source>. <year>2022</year>;<volume>25</volume>(<issue>5</issue>):<fpage>1905</fpage>&#x2013;<lpage>22</lpage>. doi:<pub-id pub-id-type="doi">10.1007/s11280-021-00994-0</pub-id>.</mixed-citation></ref>
<ref id="ref-9"><label>[9]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Phan</surname> <given-names>HT</given-names></string-name>, <string-name><surname>Nguyen</surname> <given-names>NT</given-names></string-name>, <string-name><surname>Tran</surname> <given-names>VC</given-names></string-name>, <string-name><surname>Hwang</surname> <given-names>D</given-names></string-name></person-group>. <article-title>A sentiment analysis method of objects by integrating sentiments from tweets</article-title>. <source>J Intell Fuzzy Syst</source>. <year>2019</year>;<volume>37</volume>(<issue>6</issue>):<fpage>7251</fpage>&#x2013;<lpage>63</lpage>. doi:<pub-id pub-id-type="doi">10.3233/JIFS-179336</pub-id>.</mixed-citation></ref>
<ref id="ref-10"><label>[10]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Ribana</surname> <given-names>R</given-names></string-name>, <string-name><surname>Bohn</surname> <given-names>B</given-names></string-name>, <string-name><surname>Duarte</surname> <given-names>MF</given-names></string-name>, <string-name><surname>Garcke</surname> <given-names>J</given-names></string-name></person-group>. <article-title>Explainable machine learning for scientific insights and discoveries</article-title>. <source>IEEE Access</source>. <year>2020</year>;<volume>8</volume>:<fpage>42200</fpage>&#x2013;<lpage>16</lpage>. doi:<pub-id pub-id-type="doi">10.1109/ACCESS.2020.2976199</pub-id>.</mixed-citation></ref>
<ref id="ref-11"><label>[11]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>David</surname> <given-names>G</given-names></string-name>, <string-name><surname>Stefik</surname> <given-names>M</given-names></string-name>, <string-name><surname>Choi</surname> <given-names>J</given-names></string-name>, <string-name><surname>Miller</surname> <given-names>T</given-names></string-name>, <string-name><surname>Stumpf</surname> <given-names>S</given-names></string-name>, <string-name><surname>Yang</surname> <given-names>GZ</given-names></string-name></person-group>. <article-title>XAI&#x2014;explainable artificial intelligence</article-title>. <source>Sci Robot</source>. <year>2019</year>;<volume>4</volume>(<issue>37</issue>):<fpage>eaay7120</fpage>. doi:<pub-id pub-id-type="doi">10.1126/scirobotics.aay7120</pub-id>; <pub-id pub-id-type="pmid">33137719</pub-id></mixed-citation></ref>
<ref id="ref-12"><label>[12]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Vera</surname> <given-names>LQ</given-names></string-name>, <string-name><surname>Gruen</surname> <given-names>D</given-names></string-name>, <string-name><surname>Miller</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Questioning the AI: informing design practices for explainable AI user experiences</article-title>. In: <conf-name>Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems</conf-name>; <year>2020</year>; <publisher-loc>Honolulu, HI, USA</publisher-loc>. p. <fpage>1</fpage>&#x2013;<lpage>15</lpage>.</mixed-citation></ref>
<ref id="ref-13"><label>[13]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Federico</surname> <given-names>N</given-names></string-name>, <string-name><surname>Aliprandi</surname> <given-names>C</given-names></string-name>, <string-name><surname>Capeci</surname> <given-names>F</given-names></string-name>, <string-name><surname>Cuadros</surname> <given-names>M</given-names></string-name></person-group>. <article-title>Sentiment analysis on social media</article-title>. In: <conf-name>2012 IEEE/ACM International Conference on Advances in Social Networks Analysis and Mining</conf-name>; <year>2012</year>; <publisher-loc>USA</publisher-loc>: <publisher-name>IEEE</publisher-name>. p. <fpage>919</fpage>&#x2013;<lpage>26</lpage>.</mixed-citation></ref>
<ref id="ref-14"><label>[14]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Rudresh</surname> <given-names>D</given-names></string-name>, <string-name><surname>Dave</surname> <given-names>D</given-names></string-name>, <string-name><surname>Naik</surname> <given-names>H</given-names></string-name>, <string-name><surname>Singhal</surname> <given-names>S</given-names></string-name>, <string-name><surname>Omer</surname> <given-names>R</given-names></string-name>, <string-name><surname>Patel</surname> <given-names>P</given-names></string-name>, <etal>et al.</etal></person-group> <article-title>Explainable AI (XAI): core ideas, techniques, and solutions</article-title>. <source>ACM Comput Surv</source>. <year>2023</year>;<volume>55</volume>(<issue>9</issue>):<fpage>1</fpage>&#x2013;<lpage>33</lpage>. doi:<pub-id pub-id-type="doi">10.1145/3561048</pub-id>.</mixed-citation></ref>
<ref id="ref-15"><label>[15]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Shah</surname> <given-names>A</given-names></string-name></person-group>. <chapter-title>OODM: an object-oriented design methodology for development of web applications</chapter-title>. In: <source>Information modeling for internet applications</source>. <publisher-loc>Nijmegen, The Netherlands</publisher-loc>: <publisher-name>IGI Global</publisher-name>; <year>2003</year>. p. <fpage>189</fpage>&#x2013;<lpage>229</lpage>.</mixed-citation></ref>
<ref id="ref-16"><label>[16]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Farooq</surname> <given-names>A</given-names></string-name>, <string-name><surname>Ahsan</surname> <given-names>S</given-names></string-name>, <string-name><surname>Shah</surname> <given-names>A</given-names></string-name></person-group>. <article-title>Engineering semantic web applications by using object-oriented paradigm</article-title>. <comment>arXiv:1006.4562. 2010</comment>.</mixed-citation></ref>
<ref id="ref-17"><label>[17]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Ghani</surname> <given-names>MU</given-names></string-name>, <string-name><surname>Zafar</surname> <given-names>M</given-names></string-name>, <string-name><surname>Arshad</surname> <given-names>MJ</given-names></string-name>, <string-name><surname>Asif</surname> <given-names>KH</given-names></string-name>, <string-name><surname>Shah</surname> <given-names>AA</given-names></string-name></person-group>. <article-title>Reverse object-oriented design methodology (R-OODM)</article-title>. <source>J Facu Eng Technol</source>. <year>2014</year>;<volume>21</volume>(<issue>2</issue>):<fpage>60</fpage>&#x2013;<lpage>81</lpage>.</mixed-citation></ref>
<ref id="ref-18"><label>[18]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Arshad</surname> <given-names>S</given-names></string-name></person-group>. <article-title>S-OODM: a secure object-oriented design methodology</article-title>. <source>Pak J Sci</source>. <year>2010</year>;<volume>62</volume>(<issue>1</issue>).</mixed-citation></ref>
<ref id="ref-19"><label>[19]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Walker</surname> <given-names>IJ</given-names></string-name></person-group>. <article-title>Requirements of an object-oriented design method</article-title>. <source>Softw Eng J</source>. <year>1992</year>;<volume>7</volume>(<issue>2</issue>):<fpage>102</fpage>&#x2013;<lpage>13</lpage>. doi:<pub-id pub-id-type="doi">10.1049/sej.1992.0011</pub-id>.</mixed-citation></ref>
<ref id="ref-20"><label>[20]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Marinescu</surname> <given-names>R</given-names></string-name></person-group>. <article-title>Measurement and quality in object-oriented design</article-title>. In: <conf-name>21st IEEE International Conference on Software Maintenance (ICSM&#x2019;05)</conf-name>; <year>2005</year>; <publisher-loc>Budapest, Hungary</publisher-loc>: <publisher-name>IEEE</publisher-name>. p. <fpage>701</fpage>&#x2013;<lpage>4</lpage>.</mixed-citation></ref>
<ref id="ref-21"><label>[21]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Liang</surname> <given-names>WY</given-names></string-name>, <string-name><surname>O&#x2019;Grady</surname> <given-names>P</given-names></string-name></person-group>. <article-title>Design with objects: an approach to object-oriented design</article-title>. <source>Comput-Aid Des</source>. <year>1998</year>;<volume>30</volume>(<issue>12</issue>):<fpage>943</fpage>&#x2013;<lpage>56</lpage>. doi:<pub-id pub-id-type="doi">10.1016/S0010-4485(98)00050-5</pub-id>.</mixed-citation></ref>
<ref id="ref-22"><label>[22]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Kiewkanya</surname> <given-names>M</given-names></string-name>, <string-name><surname>Jindasawat</surname> <given-names>N</given-names></string-name>, <string-name><surname>Muenchaisri</surname> <given-names>P</given-names></string-name></person-group>. <article-title>A methodology for constructing maintainability model of object-oriented design</article-title>. vol. <volume>6</volume>, In: <conf-name>In: Proceedings of the Fourth International Conference on Quality Software (QSIC); 2004</conf-name>; <publisher-loc>Braunschweig, Germany</publisher-loc>: <publisher-name>IEEE</publisher-name>. p. <fpage>206</fpage>&#x2013;<lpage>13</lpage>.</mixed-citation></ref>
<ref id="ref-23"><label>[23]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Kadam</surname> <given-names>SP</given-names></string-name>, <string-name><surname>Joshi</surname> <given-names>S</given-names></string-name></person-group>. <article-title>Secure by design approach to improve security of object-oriented software</article-title>. In: <conf-name>2015 2nd International Conference on Computing for Sustainable Global Development (INDIACom)</conf-name>; <year>2015</year>; <publisher-loc>New Delhi, India</publisher-loc>: <publisher-name>IEEE</publisher-name>. p. <fpage>24</fpage>&#x2013;<lpage>30</lpage>.</mixed-citation></ref>
<ref id="ref-24"><label>[24]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Jangra</surname> <given-names>K</given-names></string-name>, <string-name><surname>Dua</surname> <given-names>K</given-names></string-name></person-group>. <article-title>Healthcare management information systems with object-oriented methodology</article-title>. <source>Int J Inform Technol</source>. <year>2012</year>;<volume>5</volume>(<issue>1</issue>):<fpage>234</fpage>&#x2013;<lpage>9</lpage>.</mixed-citation></ref>
<ref id="ref-25"><label>[25]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Mohapatra</surname> <given-names>S</given-names></string-name>, <string-name><surname>Paul</surname> <given-names>K</given-names></string-name>, <string-name><surname>Roy</surname> <given-names>A</given-names></string-name></person-group>. <article-title>Object-oriented modeling of cloud healthcare system through connected environment</article-title>. In: <conf-name>Applications of Internet of Things: Proceedings of ICCCIOT 2020</conf-name>; <year>2021</year>; <publisher-loc>Singapore</publisher-loc>: <publisher-name>Springer Singapore</publisher-name>. p. <fpage>151</fpage>&#x2013;<lpage>64</lpage>.</mixed-citation></ref>
<ref id="ref-26"><label>[26]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Nwokoro</surname> <given-names>I</given-names></string-name>, <string-name><surname>Nwatu</surname> <given-names>AN</given-names></string-name></person-group>. <article-title>Application of object-oriented analysis and design methodology in modeling of university administrative information system</article-title>. <source>Acad Lett</source>. <year>2021</year>. doi:<pub-id pub-id-type="doi">10.20935/AL3853</pub-id>.</mixed-citation></ref>
<ref id="ref-27"><label>[27]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Arulprakash</surname> <given-names>E</given-names></string-name>, <string-name><surname>Martin</surname> <given-names>A</given-names></string-name></person-group>. <article-title>An object-oriented neural representation and its implication towards explainable AI</article-title>. <source>Int J Inform Technol</source>. <year>2024</year>;<volume>16</volume>(<issue>3</issue>):<fpage>1303</fpage>&#x2013;<lpage>18</lpage>. doi:<pub-id pub-id-type="doi">10.1007/s41870-023-01432-2</pub-id>.</mixed-citation></ref>
<ref id="ref-28"><label>[28]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Geyer</surname> <given-names>P</given-names></string-name>, <string-name><surname>Singh</surname> <given-names>MM</given-names></string-name>, <string-name><surname>Chen</surname> <given-names>X</given-names></string-name></person-group>. <article-title>Explainable AI for engineering design: a unified approach of systems engineering and component-based deep learning</article-title>. <comment>arXiv:2108.13836. 2021</comment>.</mixed-citation></ref>
<ref id="ref-29"><label>[29]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Arrieta</surname> <given-names>AB</given-names></string-name>, <string-name><surname>Rodr&#x00ED;guez</surname> <given-names>ND</given-names></string-name>, <string-name><surname>Ser</surname> <given-names>JD</given-names></string-name>, <string-name><surname>Bennetot</surname> <given-names>A</given-names></string-name>, <string-name><surname>Tabik</surname> <given-names>S</given-names></string-name>, <string-name><surname>Barbado</surname> <given-names>A</given-names></string-name>, <etal>et al</etal></person-group>. <article-title>Explainable Artificial Intelligence (XAI): concepts, taxonomies, opportunities and challenges toward responsible AI</article-title>. <source>Inf Fusion</source>. <year>2020</year>;<volume>58</volume>(<issue>3</issue>):<fpage>82</fpage>&#x2013;<lpage>115</lpage>. doi:<pub-id pub-id-type="doi">10.1016/j.inffus.2019.12.012</pub-id>.</mixed-citation></ref>
<ref id="ref-30"><label>[30]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Huynh</surname> <given-names>TD</given-names></string-name>, <string-name><surname>Tsakalakis</surname> <given-names>N</given-names></string-name>, <string-name><surname>Helal</surname> <given-names>A</given-names></string-name>, <string-name><surname>Stalla-Bourdillon</surname> <given-names>S</given-names></string-name>, <string-name><surname>Moreau</surname> <given-names>L</given-names></string-name></person-group>. <article-title>A methodology and software architecture to support explainability-by-design</article-title>. <comment>arXiv:2206.06251. 2022</comment>.</mixed-citation></ref>
<ref id="ref-31"><label>[31]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Hsiao</surname> <given-names>JHW</given-names></string-name>, <string-name><surname>Ngai</surname> <given-names>HHT</given-names></string-name>, <string-name><surname>Qiu</surname> <given-names>L</given-names></string-name>, <string-name><surname>Yang</surname> <given-names>Y</given-names></string-name>, <string-name><surname>Cao</surname> <given-names>CC</given-names></string-name></person-group>. <article-title>Roadmap of designing cognitive metrics for explainable artificial intelligence (XAI)</article-title>. <comment>arXiv:2108.01737. 2021</comment>.</mixed-citation></ref>
<ref id="ref-32"><label>[32]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>McCabe</surname> <given-names>TJ</given-names></string-name>, <string-name><surname>Butler</surname> <given-names>CW</given-names></string-name></person-group>. <article-title>Design complexity measurement and testing</article-title>. <source>Commun ACM</source>. <year>1989</year>;<volume>32</volume>(<issue>12</issue>):<fpage>1415</fpage>&#x2013;<lpage>25</lpage>. doi:<pub-id pub-id-type="doi">10.1145/76380.76382</pub-id>.</mixed-citation></ref>
<ref id="ref-33"><label>[33]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Javed</surname> <given-names>A</given-names></string-name>, <string-name><surname>Shoaib</surname> <given-names>M</given-names></string-name>, <string-name><surname>Jaleel</surname> <given-names>A</given-names></string-name></person-group>. <article-title>X-OODM: explainable object-oriented design methodology</article-title>. <source>IEEE Access</source>. <year>2024</year>;<volume>12</volume>(<issue>2</issue>):<fpage>150807</fpage>&#x2013;<lpage>23</lpage>. doi:<pub-id pub-id-type="doi">10.1109/ACCESS.2024.3477553</pub-id>.</mixed-citation></ref>
<ref id="ref-34"><label>[34]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Schwabe</surname> <given-names>D</given-names></string-name>, <string-name><surname>Rossi</surname> <given-names>G</given-names></string-name></person-group>. <article-title>An object-oriented approach to web-based applications design</article-title>. <source>Theory Pract Object Syst</source>. <year>1998</year>;<volume>4</volume>(<issue>4</issue>):<fpage>207</fpage>&#x2013;<lpage>25</lpage>. doi:<pub-id pub-id-type="doi">10.1002/(ISSN)1096-9942</pub-id>.</mixed-citation></ref>
<ref id="ref-35"><label>[35]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><surname>Rossi</surname> <given-names>G</given-names></string-name>, <string-name><surname>Schwabe</surname> <given-names>D</given-names></string-name>, <string-name><surname>Lyardet</surname> <given-names>F</given-names></string-name></person-group>. <article-title>Web application models are more than conceptual models</article-title>. In: <conf-name>Advances in Conceptual Modeling: ER&#x2019;99 Workshops on Evolution and Change in Data Management, Reverse Engineering in Information Systems, and the World Wide Web and Conceptual Modeling</conf-name>; <comment>1999 Nov 15&#x2013;18</comment>; <publisher-loc>Paris, France. Berlin/Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>; <year>1999</year>. p. <fpage>239</fpage>&#x2013;<lpage>52</lpage>.</mixed-citation></ref>
</ref-list>
</back></article>