"Use of tools to evaluate the structure, completeness, and correctness of a software component without actually executing the code. The tools may be simple (e.g., statistics on module size and comment density) or sophisticated (e.g., call trees, setting and use of variables, fan out metrics). Contrast with dynamic analysis. See also inspection, regression testing, stress testing." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)
"Analysis of a program carried out without executing the program [BCS SIGIST]. See also Dynamic analysis." (Lars Dittmann et al, "Automotive SPICE in Practice", 2008)
"The process of evaluating a system or component based on its form, structure, content, or documentation." (Mark S Merkow & Lakshmikanth Raghavan, "Secure and Resilient Software Development", 2010)
"Analysis of a document (e.g., requirements or code) carried out without executing it." (Tilo Linz et al, "Software Testing Foundations, 4th Ed", 2014)
"A debugging technique that is carried out by examining the code without executing the program, and therefore is carried out before the program is compiled." (Adam Gordon, "Official (ISC)2 Guide to the CISSP CBK" 4th Ed., 2015)
"Analysis of software development artifacts, e.g. requirements or code, carried out without execution of these software development artifacts. Static analysis is usually carried out by means of a supporting tool." (ISTQB)
No comments:
Post a Comment