The overall risk score, commonly referred to as the "Risk Exposure," is determined by multiplying a risk's likelihood (or probability) with its impact. This provides a quantitative measure that aids in understanding the potential severity of the risk, allowing for more informed decision-making.

Usability Testing is a technique used to evaluate a product by testing it on users. In this phase, real users interact with prototypes of the design to uncover potential usability flaws. This helps ensure that the end product is user-friendly and offers a good user experience before finalizing the design.

Beta Testing is a phase where the software is exposed to the real-world potential users before the final release. It's a type of User Acceptance Testing (UAT) where actual users use the software and provide direct feedback. This feedback can be related to functionality, usability, performance, or any other aspect of the software.

Usability Testing not only evaluates the ease of use of a product but also examines its overall user interface, ensuring there's consistency in design, clear error messaging, and providing meaningful feedback. This ensures a seamless, user-friendly experience for the end-user.

While automated tests can efficiently handle repetitive tasks, manual testing is indispensable for exploratory testing (where testers actively explore the application to identify issues) and usability checks to ensure a user-friendly experience.

The "Assigned" bug status signifies that the bug has been assigned to a developer and is currently being addressed. "Open" means the bug has been recognized but might not be attended to yet. "Closed" denotes that the bug has been resolved. "Verified" signifies that the tester has verified the fix.

Cyclomatic complexity, introduced by Thomas McCabe, quantifies the complexity of a program by calculating the number of linearly independent paths through the source code. A higher cyclomatic value indicates a complex program with many branches, which may require more extensive testing to ensure each path is evaluated. It aids testers in assessing risks associated with the intricate logic of the code.

Automated test suites, which consist of a collection of test scripts, test data, and execution sequences, require effective management to ensure organized execution and reporting. Test Management tools offer capabilities to define, organize, and execute tests, as well as to report defects and generate metrics, streamlining the automation workflow.

The Test Manager oversees the entire testing process and ensures that all testing activities align with the project timelines and budget. They coordinate between stakeholders and the testing team, ensuring that the testing phase progresses smoothly.

Git is a widely-used Configuration Management tool. It helps developers track and control changes in the software, allowing multiple developers to collaborate on a project simultaneously without interfering with each other's changes, and helps maintain version history.