<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-10-05T21:32:55Z</responseDate>
  <request identifier="28060" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:28060</identifier>
        <datestamp>2026-10-05T06:44:07Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>AI-Enabling Requirements: An Industrial Experience Report from a Data-Driven Recruitment System</dc:title>
          <dc:creator>Kopczyńska, Sylwia</dc:creator>
          <dc:creator>Ochodek, Mirosław</dc:creator>
          <dc:creator>Kosmala, Eryk</dc:creator>
          <dc:creator>Musiał, Jędrzej</dc:creator>
          <dc:creator>Mroziewski, Rafał</dc:creator>
          <dc:creator>Nitychoruk, Dominik</dc:creator>
          <dc:subject>requirements engineering</dc:subject>
          <dc:subject>AI-based systems</dc:subject>
          <dc:subject>AI-enabling requirements</dc:subject>
          <dc:subject>industry case study</dc:subject>
          <dc:subject>data-driven recruitment</dc:subject>
          <dc:description>Requirements Engineering commonly distinguishes between functional and non-functional requirements. In AI-based systems, an orthogonal perspective might also be worth considering: whether requirements concern AI components or not.&#13;
This paper reports on a 2.5-year R&amp;D project building MONEKTO, a holistic data-driven recruitment system for a Polish temporary employment agency. The system integrates three data streams: recruitment process events, candidate and job order profiles, and employment histories - to support both candidate-order matching and employee retention prediction. &#13;
Drawing on project logs covering June 2023 to January 2026, we identified three categories of requirements in AI-based systems: Non-AI-based requirements, AI-based requirements, and AI-enabling requirements. &#13;
We show how these categories differ in their lifecycle: while traditional requirements stabilize after implementation, AI-enabling requirements emerge incrementally and require continuous investment throughout the system lifetime. We report five observations on the emergent nature of AI-enabling requirements and derive seven practitioner lessons for RE in AI-based system projects.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Sylwia Kopczyńska and Mirosław Ochodek and Eryk Kosmala and Jędrzej Musiał and Rafał Mroziewski and Dominik Nitychoruk</dc:contributor>
          <dc:date>2026</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 394, 20th International Symposium on Empirical Software Engineering and Measurement (ESEM 2026)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.ESEM.2026.92</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-280604</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ESEM.2026.92</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
