Code Decay Measurements for ABAP Coding

Former Member — Sat, 21 Jul 2012 23:21:49 GMT

Hi,

With pc development languages eg. Java / MS C# etc, various Code Decay Indices (CDIs) exist to allow for measurement of code deterioration.

The CDIs use things like number of non-commented lines, experience of the developer, complexity etc.

Formulas have been defined using the CDIs so that (ultimately) a 'measured' approach can be used by a developer to decide when code may need to be re-developed, or aid with work estimation. This could be after continual maintenance has eroded the code to such an extent that it takes longer to fix than it should, maybe longer than re-develoment itself. My investigations are part of an OU course.

Does anyone know if SAP use CDIs? Do they have their own? Do they use the generic CDIs? Or don't they use them at all?

I appreciate that for most developers it's a gut feel as to whether to re-develop or not, but for my project I need to have something more formal.

Please can anyone help me?

Thank you,

Ian Lawrence

Re: Code Decay Measurements for ABAP Coding

HermannGahm — Wed, 08 Aug 2012 09:54:07 GMT

Hi Ian,

have you had a look at the SAP Code Inspector (transaction SCI / SCII) metrics?

not exactly what you want but a start i guess... the i button offers some help about the checks.

Kind regards,

Hermann

topic Re: Code Decay Measurements for ABAP Coding in Application Development and Automation Discussions

Code Decay Measurements for ABAP Coding

Re: Code Decay Measurements for ABAP Coding