Software Testing Risk Analysis

the basic policy of software Testing risk analysis:

develop software test plans and prioritize.

Risk analysis is the process of identifying, estimating and evaluating potential problems in software.

The purpose of the software risk analysis is to determine the test object, the test priority, and the test depth. Sometimes it also includes determining which test objects can be ignored. Through risk analysis, testers identify high-risk parts of the software and conduct rigorous and thorough testing, identifying potential hidden software artifacts and testing them. In developing a test plan, the results of the risk analysis can be used to determine the priority of the software test and the depth of the test.

Expert departments for Risk analysis: Project managers, developers, testers, users, customers, and sales people.

add a title to the test plan: a software Risk analysis table that lists risk issues in a quantifiable form:

The Software Risk Analysis table includes the following:

1 risk identification (ID)-Represents a unique identification of a risk event.

2 risk Issues-A brief overview of the problem-finding phenomenon.

3 probability of occurrence--probability value from 1~10 (Low ~ high).

4 Severity of impact--severity from 1~10.

5 Risk forecast-the product of the probability of occurrence and the severity of the impact.

6 Risk prioritization-the ranking of risk forecasts from high to low.

Software Risk Analysis Table

Identity	Risk issues	Possibility	Severity	Predicted value	Priority level	Test Cases
A	Illegal user access	6	8	48	2	Tc-1-1
B	Illegal data entry	7	10	70	1	......
C	Database update is not synchronized	4	10	40	4	......
D	Fewer concurrent users	5	9	45	3	......
E	User documentation not clear	9	1	9	5	......