Final answer:
The correct statement about static testing is that it helps find coding defects early in the development process that might not be found through dynamic testing alone. Static testing contributes to better software quality and cost-effective defect management.
Step-by-step explanation:
The statement that correctly reflects the value of static testing is: Since we started using static analysis, we find coding defects that might have not been found by performing only dynamic testing. Static testing is a key part of the software development process that involves checking code, requirements, and design documents to uncover errors early on, without executing the code (hence 'static'). Finding defects early through reviews, static analysis tools, or inspections can save time and money by preventing more complex problems down the line. Moreover, static testing improves the overall quality of the software and contributes to the reduction of the cost of defect management.
It is also worth noting that while static testing can increase the quality of specifications and improve the communication between testers and developers, it does not necessarily increase the time required for development and testing if implemented effectively. This refutes statement A. How static testing impacts defect detection later in the lifecycle is nuanced; it aims to make defect detection earlier and cheaper, which is at odds with statement B. Finally, improved communication and reduced missed requirements, as stated in option C, can be a result of many practices, including but not limited to static testing.