<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="19757" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/19757?output=omeka-xml" accessDate="2026-04-29T10:33:42+00:00">
  <collection collectionId="16">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51377">
                <text>Conference Papers</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="28">
    <name>Conference Paper</name>
    <description>Faculty Publications- Conference Papers</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172200">
              <text>Enhancing Software Cost Estimation using COCOMO Cost Driver Features with Battle Royale Optimization and Quantum Ensemble Meta-Regression Technique</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172201">
              <text>Battle Royale Optimization; BRO; COCOMO model; cost drivers; cost estimation; machine learning; QEMRT; Quantum Ensemble Meta-Regression Technique; software</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172202">
              <text>This research suggests a unique method for improving software cost estimates by combining Battle Royale Optimisation (BRO) and Quantum Ensemble Meta-Regression Technique (QEMRT) with COCOMO cost driver characteristics. The strengths of these three strategies are combined in the suggested strategy to increase the accuracy of software cost estimation. The COCOMO model is a popular software cost-estimating methodology that considers several cost factors. BRO is a metaheuristic algorithm that mimics the process of the fittest people being selected naturally and was inspired by the Battle Royale video game. The benefits of quantum computing and ensemble learning are combined in the machine learning approach known as QEMRT. Using a correlation-based feature selection technique, we first identified the most important COCOMO cost drivers in our study. To get the best-fit model, we then used BRO to optimize the weights of these cost drivers. To further increase the estimation's accuracy, QEMRT was utilized to meta-regress the optimized model. The suggested method was tested on two datasets for software cost estimating that are available to the public, and the outcomes were compared with other cutting-edge approaches. The experimental findings demonstrated that our suggested strategy beat the other approaches in terms of accuracy, robustness, and stability. In conclusion, the suggested method offers a viable strategy for improving the accuracy of software cost estimation, which might help software development organizations by improving project planning and resource allocation.  2023 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172203">
              <text>Shoran P.; Sinha A.; Mahmood H.R.; Sharma V.; Jha P.; Kumar B.; Alkhayyat A.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="172204">
              <text>2023 14th International Conference on Computing Communication and Networking Technologies, ICCCNT 2023</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="172205">
              <text>Institute of Electrical and Electronics Engineers Inc.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172206">
              <text>2023-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="172207">
              <text>&lt;a href="https://doi.org/10.1109/ICCCNT56998.2023.10307113" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICCCNT56998.2023.10307113&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85179851350&amp;amp;doi=10.1109%2FICCCNT56998.2023.10307113&amp;amp;partnerID=40&amp;amp;md5=fe37e1fdafcf79f36c4c54068f74e349" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85179851350&amp;amp;doi=10.1109%2fICCCNT56998.2023.10307113&amp;amp;partnerID=40&amp;amp;md5=fe37e1fdafcf79f36c4c54068f74e349&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172208">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="172209">
              <text>ISBN: 979-835033509-5</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172210">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172211">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="172212">
              <text>Conference paper</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="172213">
              <text>Shoran P., Dr. Akhilesh das Gupta Institure of Technology and Management, India; Sinha A., Ignou, Department of Cs and It, New Delhi, India; Mahmood H.R., Fast Nuces Cfd Campus, Punjab, Pakistan; Sharma V., Christ University, Department of Computer Science, Delhi NCR, India; Jha P., Amity University Jhrakhand, Department of Computer Science An Engineering, Ranchi, India; Kumar B., Amity University Jhrakhand, Department of Computer Science An Engineering, Ranchi, India; Alkhayyat A., The Islamic University, College of Technical Engineering, Najaf, Iraq</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
