What is the term for the analysis of software development artifacts without executing them?

The term for the analysis of software development artifacts without executing them is static analysis. This method involves reviewing and examining the code, documentation, or other development artifacts to identify potential issues, bugs, or improvements, all without the need to run the software.

Static analysis is typically performed by tools or techniques that evaluate the code for specific standards, best practices, and potential vulnerabilities. This form of analysis can be very effective in the early stages of development, as it allows teams to catch issues that could lead to more significant problems later in the software lifecycle, all while saving resources that would otherwise be spent on time-consuming debugging during execution.

In contrast, some terms refer to either the execution of the code or broader aspects of the software development process. Dynamic analysis, for example, requires executing the software to evaluate its behavior during runtime, while quality assurance encompasses various processes and practices to ensure high-quality deliverables, but is not limited to the examination of artifacts without execution.