Software Resiliency

Definition

Software Resiliency indicates programming best practices that make software bullet-proof, more robust and secure. This index is derived through technology-specific code analysis that searches for the presence of code patterns and bad programming practices that may comprise the reliability of the software at short term. Higher is the Software Resiliency, lower is the likelihood of defects occurring in production.

 

Thresholds

Thresholds used for Software Resiliency categories:

  • High (green): value > 84.0
  • Medium (orange): value >= 62.0
  • Low (red): value < 62.0

 

Code Insights

Find below some code insight examples which contribute to the Software Resiliency index.

The code contains too many queries leading to a high number of table columns
Read more
The code contains too many hard coded absolute file system paths in include directives
Read more
The Web Dynpro code contains too many direct calls to routines using “me–>”
Read more
A Program, User-Exit or Include contains too many Open SQL queries that access SAP standard tables in modification
Read more
The code contains too many SQL instructions with a missing where clause, or using “order by”, or using “not” operator or “is null” check in a where clause
Read more
The code contains too many empty functions, procedures, methods or modules
Read more
The code contains too many unchecked returns of functions calls
Read more
Avoid having too many conditions using variables without operators
Read more
Avoid having too many unused variables
Read more
Top Level Functions declaring Too Many Functions is a Risk
Read more
Spaces between function name and opening parenthesis cause bugs
Read more
Builtin instructions are inadvisable because of their risky nature
Read more
Deep functions are a Production Risk in JavaScript
Read more
Suspicious File Usage patterns can be risky
Read more
File Records with no COPY Clause can be risky
Read more
EVALUATE instructions without default treatment causes Production Risk
Read more
Standard SQL API increases Production Risk in JSP
Read more
TLD Headers can reduce Production Risks
Read more
Break Statements helps reduce production risk
Read more
Magic Numbers are a Production Risk
Read more