<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Code review tools &amp; procedures in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117384#M1363255</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;use code inspector: TCode: SCI and SCII.&lt;/P&gt;&lt;P&gt;you can also trigger code inspector from any program from SE38-&amp;gt;program-&amp;gt;check-&amp;gt;code inspector.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this will check the code as per standard check variant. you can also use own variants by using SCI tcode&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;most checks described above can be done by code inspector&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Sep 2009 09:55:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-09-17T09:55:00Z</dc:date>
    <item>
      <title>Code review tools &amp; procedures</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117382#M1363253</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we've decided to go through a code review process in order to gain/maintain better code (e.g.,, standard, efficient,..). after a  short search we've got a list of provided tools &amp;amp; transactions (e.g., code inspector, ST05). now, i need  to set a procedure (for our abap developers) to ensure developed code standards quality. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what tools should i use? at what order? at what development phase? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;looking forward for your comments. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Uri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 09:32:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117382#M1363253</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T09:32:36Z</dc:date>
    </item>
    <item>
      <title>Re: Code review tools &amp; procedures</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117383#M1363254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;You can search in SCN for related articles and blogs.&lt;/P&gt;&lt;P&gt;ST05 and SE30 are tools which you can use for performance improvement. Use the tips and tricks in SE30.&lt;/P&gt;&lt;P&gt;Code Inspector and Extended Program Check will help you in efficient programing.&lt;/P&gt;&lt;P&gt;There are several other things which you need to follow as follows:-&lt;/P&gt;&lt;P&gt;1.  Proper Naming Convention of variables for better code understanding.&lt;/P&gt;&lt;P&gt;2.  Avoid nested selects.&lt;/P&gt;&lt;P&gt;3.  Avoid nested loops whenever possible.&lt;/P&gt;&lt;P&gt;4.  Use of SORT and BINARY SEARCH in READ statements wherever possible.&lt;/P&gt;&lt;P&gt;5.  SY-SUBRC checks wherever needed.&lt;/P&gt;&lt;P&gt;6.  Avoid ZERO DIVIDE errors.&lt;/P&gt;&lt;P&gt;7.  Use of FOR ALL ENTRIES as needed.&lt;/P&gt;&lt;P&gt;8.  Better handling of messages and exception.&lt;/P&gt;&lt;P&gt;9.  Avoiding endless looping.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are some points. You can add more as per your knowlegde.&lt;/P&gt;&lt;P&gt;Create a code review checklist document and ask your developers to follow the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can share a template if you need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ankur Parab&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Ankur Parab on Sep 17, 2009 3:20 PM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Ankur Parab on Sep 17, 2009 3:34 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 09:49:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117383#M1363254</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T09:49:10Z</dc:date>
    </item>
    <item>
      <title>Re: Code review tools &amp; procedures</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117384#M1363255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;use code inspector: TCode: SCI and SCII.&lt;/P&gt;&lt;P&gt;you can also trigger code inspector from any program from SE38-&amp;gt;program-&amp;gt;check-&amp;gt;code inspector.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this will check the code as per standard check variant. you can also use own variants by using SCI tcode&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;most checks described above can be done by code inspector&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 09:55:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117384#M1363255</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T09:55:00Z</dc:date>
    </item>
    <item>
      <title>Re: Code review tools &amp; procedures</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117385#M1363256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adding to Ankur's list,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should take care of the following of the code:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Remove the dead code&lt;/P&gt;&lt;P&gt;2.Remove the redundant codes.These 2 are for better readability.&lt;/P&gt;&lt;P&gt;3.Avoid Nested-loops&lt;/P&gt;&lt;P&gt;4.Avoid using select * and use select &amp;lt;fields required&amp;gt;&lt;/P&gt;&lt;P&gt;5.Avoid the use of INTO CORRESPONDING command in the select query&lt;/P&gt;&lt;P&gt;6.Avoid using hashed/sorted internal table types if the data volume is large.&lt;/P&gt;&lt;P&gt;7.Use comments as and when required.&lt;/P&gt;&lt;P&gt;8.Keep a track of changes in the history of the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mostly it is in the stlye of the coding you follow. It is always a best practice to have a checklist given to both the programmer and reviewer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;Swetha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 09:59:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117385#M1363256</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T09:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: Code review tools &amp; procedures</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117386#M1363257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ankur, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sharing your template would be great,  pleas do. it will be helpful. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10x &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Uri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 10:54:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117386#M1363257</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T10:54:03Z</dc:date>
    </item>
    <item>
      <title>Re: Code review tools &amp; procedures</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117387#M1363258</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;uri,&lt;/P&gt;&lt;P&gt;code inspector result will any ways create a result set for you which you can take as code review checklist.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 11:08:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/code-review-tools-procedures/m-p/6117387#M1363258</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T11:08:02Z</dc:date>
    </item>
  </channel>
</rss>

