<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02727nam a22001337a 4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">64613</subfield>
    <subfield code="d">64610</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Indher, Zahid </subfield>
    <subfield code="a">15MSIT15</subfield>
    <subfield code="a">Supervisor - Dr. Abdul Wahid Memon</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Persisting comments using custom annotation inside byte code</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Nawabshah:</subfield>
    <subfield code="b">Quest,</subfield>
    <subfield code="c">2018.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">42p.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">ABSTRACT

Developer comments assist newer programmers to understand the code rapidly, the main benefit being their importance during the maintenance phase of Software Development Life Cycle (SDLC). If high level code base is lost due to any reason and only the lower level code base is available, the code base can he converted to high level language by using the reverse engineering technique. There can be problems, if the software package is old or out dated and the programmer who wrote the initial code is either not onboard or not immediately accessible. I such a case, the new developer will inevitable face have a lot of problems and hindrances while trying to understand the source code and specific business terms. In addition, i f the code is recovered using any decompiler then it would be much more difficult for new programmer to fully understand the code within a short time. All of these issues will consequently lead to an increase in development cost to the new programmer. The absence of the comments inside recovered source code will also ad&lt;l to the heap of problems. This research proposes the comments recovery approach which helps recover the code along with the comments which were added by initial developer. This research mainly focuses on java program mining language, however java discards the comments when it compiles a high level code to byte code. "Custom annotations" feature of Java is used to pinpoint the comments as specific location. Comments and annotation both are types of Metadata. Java programming does not let the comments be the part of bytecode. These are only allowed to go with bytecode. Comments are converted to custom annotation and pinpointed at specific location in source code, as soon process finishes and compilation completes and then the class file is generated. The comments will be inside bytecode. Existing technique helps the decompiler recover the comments by extracting comments in separate file and code in class file and finally merge them when decompiled. Using existing technique will lend to  a dependency of compiler as well as decompiler to recover the developer comments.
This research purposes universal technique embedding the comments with improved file size,  correctness  of  code,  correctness  or comments  and  improved  conversion
</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Department of Information Technology</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://tinyurl.com/2d4y2wp5</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">THESIS</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">RESEARCH</subfield>
    <subfield code="b">RESEARCH</subfield>
    <subfield code="d">2019-02-27</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">MP/40-439</subfield>
    <subfield code="r">2019-02-27 00:00:00</subfield>
    <subfield code="y">THESIS</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">RESEARCH</subfield>
    <subfield code="b">RESEARCH</subfield>
    <subfield code="d">2024-05-06</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">MP/54-684</subfield>
    <subfield code="r">2024-05-06 00:00:00</subfield>
    <subfield code="w">2024-05-06</subfield>
    <subfield code="y">THESIS</subfield>
  </datafield>
</record>
