The "Exit Criteria" in test planning defines the specific conditions or metrics that need to be achieved before the software can be released. It ensures that the product has reached a certain quality standard before it's deemed fit for production.

Although Exploratory Testing can be freestyle, many testers use "Test Charters" to guide their exploration. Test Charters help in providing a clear context, scope, and purpose of the exploration while allowing testers to document and manage their findings efficiently.

System testing is conducted on an integrated software to evaluate its complete and end-to-end behavior. It ensures that the entire software functions according to specified requirements. This phase tests the entire software as a single entity.

Change Control in Configuration Management involves a systematic approach to manage changes by evaluating, approving, or disapproving changes, ensuring that changes are documented, and ensuring that configuration items maintain their integrity throughout the lifecycle.

The primary difference between test planning and test strategy is their purpose and scope. While test planning is a document that outlines the specifics of the testing process for a particular project, test strategy provides an overarching approach to testing across multiple projects or for an entire organization.

A Code Review is a systematic examination of the application's source code. It's conducted to find vulnerabilities or bugs before the app is deployed. While tools like Selenium and JUnit focus on functional testing, and Wireshark on network analysis, only a thorough code review provides insights into code vulnerabilities.

Path testing is a white-box testing technique that ensures every path through the program is tested at least once. It is particularly focused on evaluating the program's internal logic paths to ensure all code branches and potential execution paths are tested.

The "risk matrix" is a tool that visualizes risks in a matrix format, based on their likelihood (or probability) on one axis and their impact on another. By categorizing risks in this manner, teams can easily prioritize which risks need immediate attention and which can be addressed later or monitored.

Configuration Management ensures consistency across various attributes of a product. One of these attributes is the 'physical' aspect, which relates to the tangible characteristics, components, and structure of the product. This is vital for ensuring the product meets the expected standards and requirements.

Big Bang Integration Testing involves integrating all the modules or components at once after they are fully developed. This can sometimes lead to challenges in identifying defects as all components are integrated in one go without any incremental checks.