<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="18990" 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/18990?output=omeka-xml" accessDate="2026-05-21T11:57:29+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="161494">
              <text>Automated Single Responsibility Principle Enforcement: A Step Toward Reusable and Maintainable Code</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="161495">
              <text>Code smells; Cyclometric complexity; Halstead volume; Interface analysis; Single responsibility principle</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="161496">
              <text>In this study, we delve into the sphere of automated code scrutiny, specifically concentrating on compliance with the single responsibility principle (SRP), a key principle in software architecture. The SRP proposes that a class should have a singular reason for modification, thereby enhancing code cohesion and facilitating its maintenance and reusability. The study presents a pioneering system that utilizes a holistic strategy to ascertain SRP compliance within code. This system rigorously inspects code interfaces, the interaction points among various software components. Through this process, we extract critical insights into the codes maintainability and reusability. An optimally designed interface can significantly improve code management and foster its reuse, leading to superior software design efficiency. Beyond interface inspection, our system also explores complexity metrics such as cyclomatic complexity and hassel volume. Cyclomatic complexity offers a numerical indicator of the count of linearly independent paths traversing a programs source code, serving as a measure of code complexity. Hassel volume is an additional metric that can quantify code complexity. Moreover, our system employs code smell detection methodologies to identify instances of high interdependence between classes, often a sign of SRP breaches. High interdependence, or tight coupling, complicates code modification and maintenance. The system integrates the conclusions from these varied analyses to determine SRP compliance. The outcomes of this investigation highlight a hopeful trajectory toward automated SRP detection. This could provide developers with tools that proactively foster the development of well-organized and maintainable code, thereby enhancing software design quality.  The Author(s), under exclusive license to Springer Nature Singapore Pte Ltd. 2024.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="161497">
              <text>Jacob B.A.; Manohar M.; Roy G.</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="161498">
              <text>Lecture Notes in Networks and Systems, Vol-1112 LNNS, pp. 343-353.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="161499">
              <text>Springer Science and Business Media Deutschland GmbH</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="161500">
              <text>2024-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="161501">
              <text>&lt;a href="https://doi.org/10.1007/978-981-97-6684-0_28" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-981-97-6684-0_28&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85215655517&amp;amp;doi=10.1007%2F978-981-97-6684-0_28&amp;amp;partnerID=40&amp;amp;md5=7ac1173f69be0421e06c009b900c3c26" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85215655517&amp;amp;doi=10.1007%2f978-981-97-6684-0_28&amp;amp;partnerID=40&amp;amp;md5=7ac1173f69be0421e06c009b900c3c26&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="161502">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="161503">
              <text>ISSN: 23673370; ISBN: 978-981976683-3</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="161504">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="161505">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="161506">
              <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="161507">
              <text>Jacob B.A., Department of Computer Science and Engineering, School of Engineering and Technology, CHRIST (Deemed to Be University), Karnataka, Bangalore, 560074, India; Manohar M., Department of Computer Science and Engineering, School of Engineering and Technology, CHRIST (Deemed to Be University), Karnataka, Bangalore, 560074, India; Roy G., Department of Computer Science and Engineering, School of Engineering and Technology, CHRIST (Deemed to Be University), Karnataka, Bangalore, 560074, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
