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

The correct term for the analysis of software development artifacts without executing them is static analysis. Static analysis refers to the evaluation of code, documentation, and other artifacts in a non-runtime environment, allowing testers and developers to identify potential issues such as bugs, security vulnerabilities, and adherence to coding standards much earlier in the development process.

This type of analysis can be performed using automated tools that inspect the codebase for irregularities or can be done manually through code reviews. The primary benefit of static analysis is that it can detect problems before the software is compiled or executed, leading to reduced costs and efforts in fixing issues later in the development cycle.

The other choices refer to different concepts: dynamic analysis involves executing the code to assess its behavior during runtime, quality assurance encompasses a broader range of activities focused on ensuring the overall quality of the software, and static testing, while closely related, is more commonly used to describe methods of testing that do not entail execution but can also include techniques like reviews and inspections rather than solely focusing on code analysis. Static analysis is a more specific and focused term that best describes the activity defined in the question.