What type of analysis checks for adherence to coding standards without executing the program?

The type of analysis that checks for adherence to coding standards without executing the program is known as static analysis. This process involves examining the source code or compiled code to identify potential errors, security vulnerabilities, or deviations from coding standards. Static analysis tools scan the codebase and provide feedback on various aspects such as code quality, maintainability, and compliance with defined standards.

Static analysis is crucial in the development lifecycle because it allows for early detection of issues that could lead to bugs or performance problems if left unchecked. It can also improve code consistency and help enforce best practices among development teams. Since this analysis does not require program execution, it can be performed before the code is run, enabling developers to address issues proactively.

In contrast, dynamic analysis involves executing the program during runtime to assess its behavior in a live environment. Regression analysis focuses on finding defects introduced during changes to the software, while performance analysis evaluates how well code performs under certain conditions, such as its speed and resource usage. These other types do not specifically target adherence to coding standards without execution like static analysis does.