Topic 11, Scenario 11 "Incident Management"
The following is the current incident handling process in used at the company.
Step 1: Incident is documented in the incident Tile with the following information:
-Software module or area where the fault occurred
-Who has reported the fault
-Hardware configuration used for the test that found the fault
-The sequential incident number (1 greater than the last one recorded)
Step 2: Developer assigned to fix the fault
Step 3: Developer fixes the fault
Step 4: Developer signs off the incident as closed, and it is then removed from the incident file

Topic 2
2, Scenario 2 "Reviews"
A software development organization wants to introduce some specific improvements to its test process. Currently, most of their testing resources are focussedon system testing. They are developing embedded software, and do not have a simulation environment to enable them to execute software modules on the development host. They have been advised that introducing inspections and reviews could be the most appropriate step forward.

Topic 17, Scenario 10, V2 "Online Application"
While waiting for the responses, the test manager has been asked to prepare test plans to validate the software application delivered by the successful bidder.

Explanation/Reference:
Explanation:
Incident management is the collection and processing of incidents raised when errors and defects are discovered. Test monitoring identifies the status of the testing activity on a continuous basis. Risk management identifies, analyses and mitigates risks to the project and the product. Configuration management is concerned with the management of changes to software components and their associated documentation and testware.