<!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>Coding Smarter, Not Harder: Leveraging GPT-3.5 Turbo for Automated Code Solution Scoring</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Aniket Deroy</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Subhankar Maity</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>IIT Kharagpur</institution>
          ,
          <addr-line>Kharagpur</addr-line>
          ,
          <country country="IN">India</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Information retrieval (IR) in software engineering is a critical area that focuses on the efective extraction, organization, and utilization of information from diverse software artifacts, including source code, documentation, and issue tracking systems. As software systems grow in complexity and volume, traditional search methodologies struggle to meet the demands of developers and engineers seeking relevant information. The task is, given a prompt (which includes a problem definition along with an incomplete code snippet) and ten corresponding solutions for each problem, we need to assign a predicted likelihood score to each (problem, solution) pair to indicate how likely the solution is to efectively address the problem. This paper explores GPT-3.5 Turbo via prompting to assign scores to solutions for programming tasks describing how good the solution is wrt to the problem. We experiment by difering the temperature values. Submission 2 scores the highest amongst the three submission runs with local nDCG of 0.6615 and Global nDCG of 0.9109.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;GPT</kwd>
        <kwd>Software Engineering</kwd>
        <kwd>Likelihood</kwd>
        <kwd>Programming</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Information retrieval (IR) in software engineering has emerged as an essential discipline in addressing
the challenges posed by the vast and complex landscape of software artifacts [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. With the rapid
growth of software systems, developers and engineers are inundated with an overwhelming amount of
information, including source code, technical documentation, and issue tracking data [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The ability to
efectively extract, organize, and utilize this information is paramount for enhancing productivity and
fostering innovation in software development [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Traditional search methodologies often fall short in meeting the nuanced needs of software
professionals, who require not just relevant information, but also contextual understanding and evaluative insights
into potential solutions [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. This gap in capability highlights the necessity for more sophisticated IR
techniques that can provide a deeper analysis of programming tasks and solutions [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        In this paper, we explore the application of GPT-3.5 Turbo [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] as a powerful tool for improving
IR in software engineering. Specifically, we investigate how this advanced language model can be
prompted to assign scores to various programming solutions based on their relevance and efectiveness
concerning specific problems. By leveraging the model’s natural language processing capabilities, we
aim to enhance the retrieval process, enabling developers to quickly identify the most suitable solutions
and streamline their workflow. This research not only contributes to the ongoing discourse on IR
in software engineering but also proposes practical methodologies for integrating AI-driven insights
into everyday software development practices. We experiment by difering the temperature values.
Submission 2 scores the highest amongst the three submission runs with local nDCG of 0.6615 and
Global nDCG of 0.9109.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        The field of Information Retrieval (IR) in software engineering has gained significant traction as
researchers and practitioners strive to manage the increasing complexity and volume of software artifacts
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Various studies have highlighted the challenges developers face in navigating vast repositories
of source code, documentation, and issue tracking systems, underscoring the need for advanced IR
techniques tailored to the unique characteristics of software engineering [
        <xref ref-type="bibr" rid="ref10 ref8 ref9">8, 9, 10</xref>
        ].
      </p>
      <p>
        Traditional IR Techniques: Early approaches to IR in software engineering predominantly utilized
keyword-based search methodologies, akin to traditional text retrieval systems [
        <xref ref-type="bibr" rid="ref11 ref9">9, 11</xref>
        ]. These methods,
while straightforward, often fell short of addressing the nuanced queries posed by software developers.
The limitations of Boolean searches and keyword matching have been well-documented, with studies
showing that developers frequently struggle to find relevant information quickly, leading to decreased
productivity and increased cognitive load [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. As a response, researchers have advocated for
contextaware retrieval systems that leverage semantic understanding, such as those incorporating
domainspecific ontologies [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
      <p>Semantic and Contextual IR: Recent advances in semantic search techniques have sought to bridge
this gap by incorporating contextual information and understanding user intent [14]. For instance,
techniques leveraging formal representations of code, such as abstract syntax trees (ASTs) and program
dependence graphs, have been explored to enhance the retrieval process [15]. These methods facilitate
more precise querying capabilities, allowing for improved matching of developer needs with relevant
artifacts.</p>
      <p>Natural Language Processing in Software Engineering: The intersection of natural language
processing (NLP) and software engineering has garnered increasing attention, particularly with the
advent of deep learning models [16]. Research has demonstrated that NLP can enhance code
summarization, documentation generation, and even automated bug fixing [ 17, 18, 19, 20]. The application of
transformer-based models, such as BERT and GPT, has shown promising results in understanding code
semantics and providing contextualized retrieval solutions [21].</p>
      <p>AI-Driven Insights for Enhanced IR: As AI technologies continue to evolve, researchers have
begun to explore their potential in improving IR processes in software engineering [22]. Notably,
studies have shown how machine learning algorithms can learn from past developer interactions to
predict relevant solutions and provide personalized recommendations [23]. This trend aligns with
our exploration of GPT-3.5 Turbo, where we investigate its ability to score programming solutions
based on relevance and efectiveness, building on the foundational work of AI-assisted development
environments.</p>
      <p>Integrating AI in Development Workflows: The integration of AI-driven tools into software
development practices represents a significant shift towards enhancing developer productivity [ 24].
Tools such as Codex and other AI pair programmers have demonstrated the potential for real-time
assistance and contextual recommendations, addressing the challenges of information overload [25].
Our research seeks to expand on these capabilities by providing a structured approach to IR, enabling
developers to leverage AI insights in their decision-making processes efectively.</p>
      <p>In summary, while traditional IR methodologies have provided a foundation for information retrieval
in software engineering, the rapid advancement of AI and NLP technologies presents an opportunity to
redefine these approaches. By leveraging models like GPT-3.5 Turbo, this research aims to contribute
to the evolution of IR techniques that not only retrieve relevant information but also ofer actionable
insights, ultimately fostering innovation and eficiency in software development practices.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Dataset</title>
      <p>There are 164 queries in the test set along with 10 solutions corresponding to every query.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Task Definition</title>
      <p>The task is, given a prompt (which includes a problem definition along with an incomplete code snippet)
and ten corresponding solutions for each problem, we need to assign a predicted likelihood score to
each (problem, solution) pair to indicate how likely the solution is to efectively address the problem.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Methodology</title>
      <sec id="sec-5-1">
        <title>5.1. Why Prompting?</title>
        <p>Prompting [26] is used for the following reasons:
• Structured Context: By providing a clear problem definition and an incomplete code
snippet, prompting establishes a structured context that helps the model understand the specific
requirements and nuances of the task at hand [27].
• Guided Responses: Prompts help guide the model in generating relevant and focused responses,
ensuring that the solutions provided align closely with the problem described [28]. This helps
mitigate ambiguity and enhances the quality of the output.
• Eficiency: Efective prompting can streamline the information retrieval process by enabling
the model to quickly hone in on relevant solutions, reducing the time developers and engineers
spend searching for pertinent information [29].
• Assessment Framework: Prompting sets up a framework for evaluating solutions based on the
likelihood scores, making it easier to analyze how well each solution addresses the problem [30].
• Complexity Management: Given the increasing complexity of software systems, prompting
allows the model to better handle diverse artifacts and contexts by providing specific cues that
focus its attention on relevant aspects of the problem and potential solutions [31].
• Scalability: As software projects grow, the ability to use prompting to eficiently evaluate
multiple solutions against specific problems scales well, accommodating the demands of larger
teams and more complex systems [32].
• Enhanced Learning: Using prompts enables the model to draw on previous knowledge and
learning from similar problems, allowing for more nuanced scoring and better-informed predictions
[33].
• Flexibility: Prompts can be adapted to diferent types of programming tasks or domains, making
the approach versatile and applicable to a wide range of software engineering challenges [34].</p>
        <p>Overall, prompting enhances the efectiveness of information retrieval in software engineering by
providing clarity, structure, and guidance, ultimately improving the relevance and accuracy of the
solutions generated.</p>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Prompt Engineering-Based Approach</title>
        <p>We used the GPT-3.5 Turbo model via prompting to solve the code quality estimation problem in
Zero-shot mode. We now summarize the internal steps in the prompting approach of GPT-3.5 Turbo:
(i) Input Reception: The model receives a text input (the prompt) from the user.
(ii) Tokenization: The input text is broken down into smaller units called tokens. This process
involves converting words and punctuation into numerical representations that the model can
understand.
(iii) Context Encoding: The model takes the sequence of tokens and encodes them into a contextual
representation. This involves capturing the relationships and meanings between the tokens based
on the model’s training.
(iv) Attention Mechanism: Using an attention mechanism, the model weighs the importance of
diferent tokens relative to each other. This allows it to focus on relevant parts of the input when
generating a response.
(v) Decoding: The model generates a response by predicting the next token in the sequence, based
on the encoded input and its learned patterns. It continues to generate tokens until it reaches a
specified length or an end condition.
(vi) Detokenization: The generated tokens are converted back into human-readable text.
(vii) Output Delivery: The final text response is presented to the user.</p>
        <p>An overview of GPT-3.5 Turbo to generate likelihood scores in Figure 1.</p>
        <p>We used GPT-3.5 Turbo in zero-shot mode at temperatures 0.7,0.8, and 0.9 with the following prompt:
"Given the problem &lt;Problem&gt; and the solution &lt;Solution&gt; generate a likelihood score between 0 and 1
stating how relevant is the solution wrt the problem. Only state the score".</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Results</title>
      <p>Run
Submission 1
Submission 2
Submission 3
Local nDCG
Global nDCG
0.6595</p>
    </sec>
    <sec id="sec-7">
      <title>7. Conclusion</title>
      <p>This research highlights the critical role of advanced Information Retrieval (IR) techniques in software
engineering, addressing the increasing complexity and volume of software artifacts developers face
daily. Traditional search methods often lack the contextual depth required by software professionals,
underscoring the need for more refined IR solutions capable of delivering relevant, evaluative insights.
Our study demonstrates the potential of GPT-3.5 Turbo as a valuable tool in this domain, showcasing
how its language processing capabilities can be used to enhance the relevance and efectiveness of
retrieved programming solutions.</p>
      <p>By experimenting with diferent model parameters, such as temperature, we observed that Submission
2 consistently scored the highest, achieving a local nDCG of 0.6615 and a global nDCG of 0.9109.
These results suggest that leveraging AI-driven models like GPT-3.5 Turbo not only improves retrieval
accuracy but also supports software engineers in navigating complex development tasks more eficiently.
This research contributes practical methods for integrating AI into software development workflows,
enhancing productivity, and supporting innovation in the field.</p>
    </sec>
    <sec id="sec-8">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author(s) used ChatGPT in order to: Drafting content, Grammar
and spelling check, etc. After using this tool/service, the author(s) reviewed and edited the content as
needed and take(s) full responsibility for the publication’s content.
[14] M. Fernández, I. Cantador, V. López, D. Vallet, P. Castells, E. Motta, Semantically enhanced
information retrieval: An ontology-based approach, Journal of Web Semantics 9 (2011) 434–452.
[15] J. Zhang, X. Wang, H. Zhang, H. Sun, K. Wang, X. Liu, A novel neural source code representation
based on abstract syntax tree, in: 2019 IEEE/ACM 41st International Conference on Software
Engineering (ICSE), IEEE, 2019, pp. 783–794.
[16] C. Watson, N. Cooper, D. N. Palacio, K. Moran, D. Poshyvanyk, A systematic literature review
on the use of deep learning in software engineering research, ACM Transactions on Software
Engineering and Methodology (TOSEM) 31 (2022) 1–58.
[17] S. Panichella, A. Panichella, M. Beller, A. Zaidman, H. C. Gall, The impact of test case summaries
on bug fixing performance: An empirical investigation, in: Proceedings of the 38th international
conference on software engineering, 2016, pp. 547–558.
[18] S. Gupta, S. Gupta, Natural language processing in mining unstructured data from software
repositories: a review, Sa¯dhana¯ 44 (2019) 244.
[19] Y. Zhu, M. Pan, Automatic code summarization: A systematic literature review, arXiv preprint
arXiv:1909.04352 (2019).
[20] E. Dehaerne, B. Dey, S. Halder, S. De Gendt, W. Meert, Code generation using machine learning: A
systematic review, Ieee Access 10 (2022) 82434–82455.
[21] D. Drain, C. Wu, A. Svyatkovskiy, N. Sundaresan, Generating bug-fixes using pretrained
transformers, in: Proceedings of the 5th ACM SIGPLAN International Symposium on Machine Programming,
2021, pp. 1–8.
[22] M. Borg, Advancing trace recovery evaluation-applied information retrieval in a software
engineering context, arXiv preprint arXiv:1602.07633 (2016).
[23] Z. Batmaz, A. Yurekli, A. Bilge, C. Kaleli, A review on deep learning for recommender systems:
challenges and remedies, Artificial Intelligence Review 52 (2019) 1–37.
[24] S. Tatineni, K. Allam, Ai-driven continuous feedback mechanisms in devops for proactive
performance optimization and user experience enhancement in software development, Journal of AI in
Healthcare and Medicine 4 (2024) 114–151.
[25] M.-F. Wong, S. Guo, C.-N. Hang, S.-W. Ho, C.-W. Tan, Natural language generation and
understanding of big code for ai-assisted programming: A review, Entropy 25 (2023) 888.
[26] L. Wang, X. Chen, X. Deng, H. Wen, M. You, W. Liu, Q. Li, J. Li, Prompt engineering in consistency
and reliability with the evidence-based guideline for llms, npj Digital Medicine 7 (2024) 41.
[27] X. Hou, Y. Zhao, Y. Liu, Z. Yang, K. Wang, L. Li, X. Luo, D. Lo, J. Grundy, H. Wang, Large language
models for software engineering: A systematic literature review, ACM Transactions on Software
Engineering and Methodology (2023).
[28] E. A. Siverling, T. J. Moore, E. Suazo-Flores, C. A. Mathis, S. S. Guzey, What initiates evidence-based
reasoning?: Situations that prompt students to support their design ideas and decisions, Journal
of Engineering Education 110 (2021) 294–317.
[29] L. Belzner, T. Gabor, M. Wirsing, Large language model assisted software engineering: prospects,
challenges, and a case study, in: International Conference on Bridging the Gap between AI and
Reality, Springer, 2023, pp. 355–374.
[30] H. A. Diefes-Dux, J. S. Zawojewski, M. A. Hjalmarson, M. E. Cardella, A framework for analyzing
feedback in a formative assessment system for mathematical modeling problems, Journal of
Engineering Education 101 (2012) 375–406.
[31] B. Mirel, Interaction design for complex problem solving: Developing useful and usable software,</p>
      <p>Morgan Kaufmann, 2004.
[32] T. Stober, U. Hansmann, Best practices for large software development projects, Springer, 2010.
[33] L. Reynolds, K. McDonell, Prompt programming for large language models: Beyond the few-shot
paradigm, in: Extended abstracts of the 2021 CHI conference on human factors in computing
systems, 2021, pp. 1–7.
[34] A. Kleppe, Software language engineering: creating domain-specific languages using metamodels,
Pearson Education, 2008.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Cleland-Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O. C.</given-names>
            <surname>Gotel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. Hufman</given-names>
            <surname>Hayes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mäder</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Zisman</surname>
          </string-name>
          ,
          <article-title>Software traceability: trends and future directions</article-title>
          ,
          <source>in: Future of software engineering proceedings</source>
          ,
          <year>2014</year>
          , pp.
          <fpage>55</fpage>
          -
          <lpage>69</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>C. H.</given-names>
            <surname>David</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. S.</given-names>
            <surname>Famiglietti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.-L.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Habets</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. R.</given-names>
            <surname>Maidment</surname>
          </string-name>
          ,
          <article-title>A decade of rapid-reflections on the development of an open source geoscience code</article-title>
          ,
          <source>Earth and Space Science</source>
          <volume>3</volume>
          (
          <year>2016</year>
          )
          <fpage>226</fpage>
          -
          <lpage>244</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>S.</given-names>
            <surname>Nambisan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Agarwal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Tanniru</surname>
          </string-name>
          ,
          <article-title>Organizational mechanisms for enhancing user innovation in information technology</article-title>
          ,
          <source>MIS quarterly</source>
          (
          <year>1999</year>
          )
          <fpage>365</fpage>
          -
          <lpage>395</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M. L.</given-names>
            <surname>Drury-Grogan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Conboy</surname>
          </string-name>
          , T. Acton,
          <article-title>Examining decision characteristics &amp; challenges for agile software development</article-title>
          ,
          <source>Journal of Systems and Software</source>
          <volume>131</volume>
          (
          <year>2017</year>
          )
          <fpage>248</fpage>
          -
          <lpage>265</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Sadeghi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Bagheri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Garcia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Malek</surname>
          </string-name>
          ,
          <article-title>A taxonomy and qualitative comparison of program analysis techniques for security assessment of android software</article-title>
          ,
          <source>IEEE Transactions on Software Engineering</source>
          <volume>43</volume>
          (
          <year>2016</year>
          )
          <fpage>492</fpage>
          -
          <lpage>530</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>B.</given-names>
            <surname>Mann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Ryder</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Subbiah</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kaplan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Dhariwal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Neelakantan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Shyam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Sastry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Askell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Agarwal</surname>
          </string-name>
          , et al.,
          <article-title>Language models are few-shot learners</article-title>
          ,
          <source>arXiv preprint arXiv:2005.14165 1</source>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>V.</given-names>
            <surname>Garousi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Borg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Oivo</surname>
          </string-name>
          ,
          <article-title>Practical relevance of software engineering research: synthesizing the community's voice</article-title>
          ,
          <source>Empirical Software Engineering</source>
          <volume>25</volume>
          (
          <year>2020</year>
          )
          <fpage>1687</fpage>
          -
          <lpage>1754</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>W.</given-names>
            <surname>Scacchi</surname>
          </string-name>
          ,
          <article-title>Understanding the requirements for developing open source software systems</article-title>
          ,
          <source>IEE Proceedings-Software</source>
          <volume>149</volume>
          (
          <year>2002</year>
          )
          <fpage>24</fpage>
          -
          <lpage>39</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Sharafi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Soh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.-G.</given-names>
            <surname>Guéhéneuc</surname>
          </string-name>
          ,
          <article-title>A systematic literature review on the usage of eye-tracking in software engineering</article-title>
          ,
          <source>Information and Software Technology</source>
          <volume>67</volume>
          (
          <year>2015</year>
          )
          <fpage>79</fpage>
          -
          <lpage>107</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>X.</given-names>
            <surname>Hou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Lo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Grundy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <article-title>Large language models for software engineering: A systematic literature review</article-title>
          ,
          <source>ACM Transactions on Software Engineering and Methodology</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>D.</given-names>
            <surname>Binkley</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Lawrie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Laplante</surname>
          </string-name>
          ,
          <article-title>Applications of information retrieval to software development, Encyclopedia of Software Engineering (P</article-title>
          . Laplante, ed.),(to appear) (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>A.</given-names>
            <surname>Abogdera</surname>
          </string-name>
          ,
          <article-title>Exploring Information-Seeking Strategies College Students Use to Improve the Relevance of Retrieval from Online Information Retrieval Systems</article-title>
          ,
          <source>Ph.D. thesis</source>
          , Colorado Technical University,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>A. D. Dave</surname>
            ,
            <given-names>N. P.</given-names>
          </string-name>
          <string-name>
            <surname>Desai</surname>
          </string-name>
          ,
          <article-title>A comprehensive study of classification techniques for sarcasm detection on textual data</article-title>
          , in: 2016 International Conference on Electrical, Electronics, and
          <article-title>Optimization Techniques (ICEEOT)</article-title>
          , IEEE,
          <year>2016</year>
          , pp.
          <fpage>1985</fpage>
          -
          <lpage>1991</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>