iTranslated by AI
The content below is an AI-generated translation. This is an experimental feature, and may contain errors. View original article
🌊
Authorized Translation: Practical Risk-Based Testing - The PRISMA Method
Practical Risk-Based Testing -The PRISMA Method-
Written by: Drs. Erik P.W.M. van Veenendaal CISA / Translated by: Fumikazu Fujiwara
It is common for activities preceding the system test phase—such as development, unit testing, and integration testing—to be delayed.
As a result, the burden often falls on the system test phase, which must then be executed under significant pressure.
However, you cannot simply stop testing, delay it further, or, worse yet, perform a superficial test.
So, how will you navigate this situation?
Table of Contents
- 1. Introduction
- 2. Product Risk Management
- 3. Good Enough Testing
- 4. The Testing Challenge
- 5. Finding the Most Important Parts of the Product
- 6. Finding the Worst Areas of the Product
- 7. The PRISMA Process
- 8. Practical Experiences with PRISMA
- 9. References
- 10. Biography
This translation is published under an agreement with the original author of Practical Risk-Based Testing - Product RISk MAnagement: the PRISMA.
Discussion