Code Analysis for SAP: What was Learned at ASUG NJ

CAST recently sponsored the ASUG NJ Summer Chapter meeting, held on June 12th. ASUG is a renowned organization across US and Canada for SAP professionals and organizations working in the field of SAP. The conference was attended by more than 100 professionals from companies across various industries. The full day event featured many interesting presentations including a presentation of the latest CRASH report on SAP.

"The rules most consistently violated by ABAP developers affect performance or maintainability of SAP applications."

“The rules most consistently violated by ABAP developers affect performance or maintainability of SAP applications.”

The key points discussed during presentations were:

  1. Developers complied only one third of the instances of the most frequently violated rules.
  2. Some ABAP programs are big compared to other major languages such as Java, C# etc.
  3. Poorly written ABAP code typically affects all most Health Factors of an application such as Performance, Robustness, Security, Changeability and Transferability.
  4. ABAP programs have higher failure risk than other languages.
  5. ABAP developers struggle with info retrieval, and structuring for agility.

In the SAP CRASH report, Bill Curtis, SVP and Chief Scientist at CAST, states: “Structural quality is often sacrificed for speed to deployment. Yet structural weaknesses are root causes of security breaches, outages, and other business risks. Businesses can improve their competitive agility and reduce costs by managing the quality of their SAP customizations”.

Traditional SDLC (Software development Life Cycle) allows poor programing practices to slip away from the testing phases since Software Testing does not touch all parts of the codebase. On top of that, bugs reported in traditional SDLC approach does not attach business values with the reported issues such as whether the issue reported is related to performance, or it’s related to security etc. With such limited information, development teams often just try to fix the immediate issue and in the process they break other functionalities of the system by mistake. This problem is not related to the efficiency of the development teams or their knowledge gaps in technology but rather is related to the narrow approach taken by the teams to resolve just the immediate issue without taking into consideration the possible impacted areas due to the modified code.

Download a copy of the SAP CRASH Benchmark Report now!

CAST is a proud sponsor of ASUG, be sure to check out our events page to find out which chapter we’ll be visiting next.

Get Your Free White Paper & Learn How Software Analytics Can Help Your Business

Learn why you need to build security into your applications and how it will help improve and protect your business. Click the button below to get our FREE copy today.

Your Information will be kept private and secure.

Comments

comments