Which term refers to the evaluation of software artifacts, like requirements or design, without executing them?

The term that refers to the evaluation of software artifacts, such as requirements or design documents, without executing them is static analysis. This process involves reviewing these artifacts to identify potential issues, inconsistencies, or adherence to standards and guidelines. Static analysis can be carried out using formal reviews, inspections, or the application of various automated tools that help detect problems early in the software development lifecycle before any code has been written or executed.

In contrast, dynamic testing involves executing the software itself to identify defects by observing its behavior during runtime. This is fundamentally different from static analysis, as it requires a working version of the software.

Exploratory testing focuses on the tester's experience and intuition to find defects without predefined test cases, promoting an adaptable and knowledgeable approach to testing software during runtime rather than analyzing artifacts before execution.

Regression testing is concerned with verifying that existing functionalities remain unaffected by recent code changes or enhancements. It is performance-based, requiring the execution of tests on the software itself after changes have been made.

Therefore, static analysis is the correct term for evaluating software artifacts without executing them.