<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Integrating Fairness in AI Development: Technical Insights from the fAIr by design Framework</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mira Reisinger</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rania Wazir</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>leiwand.ai</institution>
          ,
          <addr-line>Vienna</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper discusses the necessity of integrating fairness into the development of trustworthy AI systems, focusing on methods and tools designed within the fAIr by design project - a collaborative approach to guide development teams towards the creation of non-discriminatory AI systems. Practical applications, challenges, and recommendations based on real-world use cases are shared from a data science and machine learning team perspective. The paper advocates for continuous learning, diverse team assembly, and ongoing monitoring to ensure AI systems remain fair and inclusive, encompassing the whole life cycle of AI systems.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Fairness in AI Development</kwd>
        <kwd>Assurance Case</kwd>
        <kwd>Use Cases</kwd>
        <kwd>Ethical decision-making</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Artificial Intelligence (AI) has become increasingly integrated into various aspects of society,
from communications to recruitment[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] to justice systems[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. However, there are serious
concerns regarding potential unwanted biases and discrimination embedded in AI systems. These
concerns are not unfounded, as numerous examples of biased and discriminatory applications
and their significant negative impacts on individuals and communities have been revealed [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ].
      </p>
      <p>
        The challenge begins with defining fairness — a concept that proves elusive across disciplines.
Drawing upon Mehrabi et al.[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], fairness in decision-making is ideally the absence of prejudice
or favoritism towards any individual or group based on inherent or acquired characteristics. The
evolving nature of fairness definitions highlights the challenge of addressing the intertwined
issues of bias, fairness, and discrimination. This requires stakeholders and developers to work
together to develop context-specific definitions of fairness and non-discrimination, which
include acceptable thresholds and measurable metrics. Verma and Rubin[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] ofer insights
into defining and measuring fairness, involving various metrics such as predictive outcomes,
similarity measures, or causal reasoning.
      </p>
      <p>Recognizing the dynamic nature of fairness, influenced by societal norms and technological
advancements, adds complexity to the efort of implementing fairness in AI systems but also
enables AI systems to be finely tuned to balance fairness with performance. This balanced
approach requires ongoing dialogue and adjustments between ethical principles and system
eficiency, ensuring continuous alignment through monitoring and iterative enhancements.</p>
      <p>
        The research consortium fAIr by design[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], funded by the Austrian National Foundation for
Research, Technology and Development (FFG)[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], has devised a framework aimed at aiding
organizations in incorporating fairness requirements into their development processes. This
paper reflects on the utilization of the tools and methods[
        <xref ref-type="bibr" rid="ref1 ref8">8, 1</xref>
        ] introduced to 3 AI system
development teams to ensure adherence to fairness and trustworthiness principles.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Leveraging Assurance Cases for Fairness in AI Systems</title>
      <p>
        This chapter delves into a strategy employed by the fAIr by design team to navigate the
challenges of developing algorithms with embedded fairness constraints. Drawing on the adapted
Assurance Case method [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], the strategy includes a comprehensive discussion about the purpose
and role of an AI system, the analysis and identification of potential fairness and discrimination
risks followed by thorough testing for those risks, and adoption of mitigation strategies.
      </p>
      <sec id="sec-2-1">
        <title>2.1. The Assurance Case method (AC)</title>
        <p>
          Originating from safety engineering, the Assurance Case method ofers a structured pathway for
translating high-level goals into specific, actionable, and verifiable technical specifications [
          <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
          ].
It is a collaborative approach fostering a holistic perspective on fairness in AI development,
promoting the creation of ethically sound and socially responsible systems. The AC facilitates
close cooperation among social science, data science, and start-up development teams in the
fAIr by design project, serving as a valuable tool for integrating fairness into AI systems.
        </p>
        <p>Components of the method include claims, sub-claims, evidence and reasoning, which enable
the project team to identify and systematically integrate a comprehensive understanding of the
AI system and fairness needs through the definition of sub-claims, each supported by (technical)
evidences. The overall process included developing evidences and tests, a thorough exploration
of model selections, fairness metrics, and the application of mitigation strategies.</p>
        <p>The AC emphasizes the crucial role of integrating "challengers" (technical or non-technical)
into the AI development process to identify and point out aspects that are not clear and can lead
to unfairness. Having a comprehensive understanding of each component of the AI system from
the outset is invaluable, and the involvement of "challengers" enhances this understanding by
ensuring that fairness considerations are addressed. The "challenger" can assist in clarifying data
needs, testing protocols, evaluation metrics, and mitigation strategies, laying the groundwork
for in-depth fairness testing. This also equips the team to manage potential future challenges.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Practical Applications and Use Cases</title>
      <p>This chapter reports on the application of the methodologies and tools found during fAIr by
design. The implementation of the AC was done together with social scientists and legal experts,
but learnings and recommendations center on technical application and data science perspective.</p>
      <sec id="sec-3-1">
        <title>3.1. Learnings and Recommendations</title>
        <p>At the onset of developing a fair AI system, it’s important from a technical and social-science
standpoint to engage in a series of critical inquiries and clarifications with the use case partner,
which include:
• The definition of fairness from the partner’s perspective.
• The characteristics that constitute a fair AI system for them.
• The (envisioned) structure of the AI system and it’s components.
• The risks identified and the sub-claims that can be substantiated with technical evidence.
• The feasible tests, along with a potential responsible person.
• The prerequisites for conducting these tests, including necessary data, knowledge, and
resources.
• The applicable metrics and thresholds for fairness.</p>
        <p>• The mitigation strategies to be employed should these thresholds not be met.</p>
        <sec id="sec-3-1-1">
          <title>3.1.1. Tools and Resources</title>
          <p>
            The use of methods and tools developed within the Assurance Case or those available as
open access resources[
            <xref ref-type="bibr" rid="ref11 ref12">11, 12</xref>
            ], such as the AI canvas and ethics checklists, are particularly
recommended. The Data Science Ethics Checklist from deon.org[
            <xref ref-type="bibr" rid="ref12">12</xref>
            ], applied as an iterative
process, has been shown to significantly support the technical progress. If well done it can
be part of the documentation requirements of high risk AI systems[
            <xref ref-type="bibr" rid="ref13">13</xref>
            ]. The checklist helps
clarifying the data science and machine learning maturity level of the partners, and aligns well
with the need for clarity and eficacy common in development teams[
            <xref ref-type="bibr" rid="ref1">1</xref>
            ].
          </p>
        </sec>
        <sec id="sec-3-1-2">
          <title>3.1.2. Assessing and Building Knowledge</title>
          <p>All steps of fairness testing require data quality and overall machine learning and data science
expertise (e.g. ablation studies, hyper-parameter optimization or inverse relation modeling).
Addressing biases in training and evaluation data is vital to prevent AI systems from replicating
or exacerbating existing inequities. For some companies it can be a challenge to build the
necessary knowledge around data quality, conducting systematic evaluations, and testing model
components, which should be addressed from the onset.</p>
        </sec>
        <sec id="sec-3-1-3">
          <title>3.1.3. Assemble a Diverse and Competent Team</title>
          <p>
            Building a proficient team that specializes in appropriate data science and machine learning
methods is essential to circumvent fairness testing pitfalls efectively. It requires a concerted
efort to integrate knowledge on fairness into AI, delineating clear responsibilities among senior
management and development teams. Fairness, much like other critical quality criteria, must be
integrated into a wide array of business processes, gaining prominence especially in high-risk
AI systems[
            <xref ref-type="bibr" rid="ref13">13</xref>
            ]. The establishment of interdisciplinary teams is key to facilitating in-depth
discussions and making informed decisions regarding fairness.
          </p>
        </sec>
        <sec id="sec-3-1-4">
          <title>3.1.4. Continuous Validation and Monitoring</title>
          <p>The establishment of regular auditing and accountability mechanisms is pivotal in upholding
non-discriminatory practices in AI. Continuous monitoring and evaluation of AI systems
enable organizations to proactively identify and address any potential biases or discriminatory
outcomes, thereby demonstrating their commitment to fairness and ethical AI development.</p>
        </sec>
        <sec id="sec-3-1-5">
          <title>3.1.5. You think you know what fairness means – until you ask others</title>
          <p>Another critical aspect of promoting non-discriminatory AI development is fostering
collaboration and transparency. Organizations should actively seek partnerships with diverse
stakeholders, including ethicists, community representatives, and regulatory bodies, to gain insights into
the potential biases and discriminatory risks in AI systems. By promoting transparency in AI
development processes, organizations can build trust and accountability with the public, while
ensuring that fairness remains an integral part of the AI life cycle. This is useful as a quality
assurance tool, ensuring that the product being developed actually satisfies market needs.</p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Challenges and Limitations</title>
        <p>Collaborative eforts with partners have provided valuable insights into the practical challenges
and strategies for developing non-discriminatory AI systems. These collaborative endeavors
shed light on the significance of data science and machine learning maturity, as well as the
willingness to invest time, efort, and resources into crafting fair, non-discriminatory, and
trustworthy AI systems. However, navigating fairness throughout the AI life cycle presents
challenges, including the dynamic nature of fairness definitions and the intricacies of measuring
fairness.</p>
        <p>The fAIr by design use cases, focusing on small companies (SMEs), start-ups and cultural
organizations/NGOs - each with distinct applications, domains, and developmental stages -
underscore the diverse landscape within which fairness considerations are embedded, emphasizing
the importance of contextual understanding and adaptability. However, we have not been able
to work with larger, more established organizations, with a more advanced data management
structure, but may face other challenges.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion</title>
      <p>The journey towards non-discriminatory AI development requires the concerted eforts of
organizations, policymakers, and society as a whole. fAIr by design, including the Assurance
Case, provides a structured approach to the development of fair AI systems. Recognizing the
contextual nature of fairness, the adoption of ethical AI principles should be accompanied by
continuous training for development teams, enabling them to incorporate ethical guidelines
into their day-to-day decision-making processes. In this project we have seen how beneficial it
is for social sciences, data sciences and use case partners working together. Moving forward,
the exploration of cross-industry collaborations and the proposition of structured frameworks
for engaging organizations in fairness discussions are promising directions for the advancement
of non-discriminatory AI. The potential to draw on diverse perspectives and expertise, could
ultimately lead to industry-wide standardized approaches, thus bringing us closer to a future
where ethical principles in AI are upheld across the board.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>S.</given-names>
            <surname>Cepeda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Kunze</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Leimüller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Müller-Kress</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Stöger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Wazir</surname>
          </string-name>
          ,
          <article-title>Requirements for developing fair ai systems</article-title>
          , https://www.fairbydesign.eu/publications,
          <year>2022</year>
          . [Accessed 29-
          <fpage>03</fpage>
          -2024].
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>N.</given-names>
            <surname>Mehrabi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Morstatter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Saxena</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lerman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Galstyan</surname>
          </string-name>
          ,
          <article-title>A survey on bias and fairness in machine learning</article-title>
          ,
          <source>ACM Comput. Surv</source>
          .
          <volume>54</volume>
          (
          <year>2021</year>
          ). URL: https://doi.org/10.1145/3457607. doi:
          <volume>10</volume>
          .1145/3457607.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>C. O'Neil</surname>
          </string-name>
          , Weapons of Math Destruction:
          <article-title>How Big Data Increases Inequality</article-title>
          and
          <string-name>
            <given-names>Threatens</given-names>
            <surname>Democracy</surname>
          </string-name>
          , Crown Publishing Group, New York, NY, USA,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>J.</given-names>
            <surname>Dressel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Farid</surname>
          </string-name>
          ,
          <article-title>The accuracy, fairness, and limits of predicting recidivism</article-title>
          ,
          <source>Science Advances</source>
          <volume>4</volume>
          (
          <year>2018</year>
          )
          <article-title>eaao5580</article-title>
          . doi:
          <volume>10</volume>
          .1126/sciadv.aao5580.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S.</given-names>
            <surname>Verma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Rubin</surname>
          </string-name>
          ,
          <article-title>Fairness definitions explained</article-title>
          ,
          <source>in: Proceedings of the International Workshop on Software Fairness</source>
          , FairWare '18,
          <string-name>
            <surname>Association</surname>
          </string-name>
          for Computing Machinery, New York, NY, USA,
          <year>2018</year>
          , p.
          <fpage>1</fpage>
          -
          <lpage>7</lpage>
          . doi:
          <volume>10</volume>
          .1145/3194770.3194776.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <article-title>[6] fair by design</article-title>
          , https://www.fairbydesign.eu,
          <year>2024</year>
          . [Accessed 29-
          <fpage>03</fpage>
          -2024].
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <article-title>[7] fAIr by design - Entwicklung eines neuen Prozessmodells für nichtdiskriminierende Künstlicher Intelligenz | FFG</article-title>
          , https://www.fg.at/content/ fair
          <article-title>-design-entwicklung-eines-neuen-prozessmodells-fuer-nicht-diskriminierende-</article-title>
          <string-name>
            <surname>kuenstlicher</surname>
          </string-name>
          ,
          <year>2021</year>
          . [Accessed 29-
          <fpage>03</fpage>
          -2024].
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>L.</given-names>
            <surname>Kunze</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Leimüller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Müller-Kress</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. P.</given-names>
            <surname>Hauer</surname>
          </string-name>
          ,
          <article-title>Method handbook: Assurance cases for fair ai systems</article-title>
          , https://www.fairbydesign.eu/publications,
          <year>2024</year>
          . [Accessed 29-
          <fpage>03</fpage>
          -2024].
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>M. P.</given-names>
            <surname>Hauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Müller-Kress</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Leimüller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Zweig</surname>
          </string-name>
          ,
          <article-title>Using assurance cases to assure the fulfillment of non-functional requirements of AI-based systems - lessons learned</article-title>
          ,
          <source>in: 2023 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW)</source>
          , IEEE,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M. P.</given-names>
            <surname>Hauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Adler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Zweig</surname>
          </string-name>
          ,
          <article-title>Assuring fairness of algorithmic decision making</article-title>
          ,
          <source>in: 2021 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW)</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>110</fpage>
          -
          <lpage>113</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICSTW52544.
          <year>2021</year>
          .
          <volume>00029</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>J.</given-names>
            <surname>Unadkat</surname>
          </string-name>
          ,
          <article-title>What is Test Driven Development (TDD)?</article-title>
          , https://www.browserstack.com/ guide/what-is
          <article-title>-test-driven-</article-title>
          <string-name>
            <surname>development</surname>
          </string-name>
          ,
          <year>2023</year>
          . [Accessed 29-
          <fpage>03</fpage>
          -2024].
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <article-title>[12] deon, Data science ethics checklist</article-title>
          , https://deon.drivendata.org/,
          <year>2019</year>
          . [Accessed 29-
          <fpage>03</fpage>
          - 2024].
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>European</given-names>
            <surname>Parliament</surname>
          </string-name>
          and
          <article-title>Council of European Union, Regulation (EU) no 2024/1689 Annex III. High-risk AI systems referred to in Article 6(2</article-title>
          ), https://eur-lex.europa.eu/eli/reg/2024/ 1689/oj,
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>