Performing static code analysis

The purpose of static code analysis is to help you improve your overall architectural quality, code quality, and performance by doing the following:

• Visualizing software architecture and its software dependencies
• Enforcing the designated architectural rules regarding laying, subsystems, calling rules, and more
• Identifying code that has been cloned and modified using cut, copy, and paste
• Identifying dead code that can be removed
• Calculating various software metrics
• Performing code style checks and flagging violations

Many companies employ static code analysis as part of their Continuous Integration (CI) process. There are various stages at which problems can come to light. These stages are listed as follows:

• When compiling source code in the IDE
• When running unit tests and end-to-end system tests
• When pushing source code to version control and issuing a pull request
• When a pull request has been issued...