Software Resiliency

8 March 2016

Indicators & Methodology, Software Health

Definition

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

Thresholds

Thresholds used for Software Resiliency categories:

Low/Red: below 65.0
Medium/Orange: from 65.0 to 87.0
High/Green: above 87.0

Code Insights

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

Use of ‘return’ statement is not recommended

Do not compare to null

phpinfo() should not be used in production

The code contains too many PHP4 deprecated constructor naming.

The code contains too many final artifacts in final classes

The code contains too many classes that declare get() without declaring set()

Force casts should not be used

Avoid abstract classes without abstract or concrete methods

Variables should be declared with ‘let’ or ‘const’

Multiline string literals should not be used

Logical OR should not be used in switch cases

Avoid caching selector for long time

URIs (URL & path) should not be hardcoded for testability purpose

try! should not be used

Avoid generic catch

Avoid undefined type on data or routines declaration

Avoid to update static fields from instance methods

Avoid Public finalize() methods

Avoid confusing initialization for variables declared on the same line

The code contains too many unnecessary COMPUTE