Analysing the product risks


Testing itself can never ensure that the damage when the system is taken into production is reduced. Based on the test results, defects and therefore potential damage are demonstrated. Based on this, it is determined to either make changes to the test object that eliminate or reduce the damage when it is taken into production, or not.

Testing is a measure to provide insight into the quality and the related product risks of a system or package when it is taken into production by an organisation.(2) Since there will never be an unlimited quantity of resources and time, it is important to determine in advance which system parts and characteristics require additional or less test effort. Well-justifi ed choices have to be made in this context. One instrument to determine areas of concern for the test is executing a product risk analysis ( PRA).


The stakeholders and test manager achieve a joint view of what the more and less risky parts and characteristics of the system are.


  • Determining participants
  • Determining the PRA approach
  • Preparing session/interviews
  • Collecting and analysing product risks
  • Completeness check

Exit Criteria

check-TMap_4.gif The risk tables with the test goals and possible object parts with risk indications for each characteristic, managed separately and optionally laid down in the master test plan. The PRA total overview with characteristics/object parts with risk class, defined in the master test plan.


  • Product risk analysis (chapter 9)
  • Explanation of quality characteristics (chapter 10).

Last edited Nov 6, 2009 at 7:06 PM by ClemensReijnen, version 4


No comments yet.