Risk management involves making compromises in testing.
Some compromises have to be made to keep costs under control while other
aspects of testing absolutely cannot be compromised.
Important questions to ask when evaluating the risks of whether or not
to test a software component or system are:
- Who will use our product?
- What and how will it be used?
- If there are errors within the product, could this result in the
loss of reputation/money for our company or our customers?
- How could inadequate testing affect human health or safety?
Effective risk management can only be done if a thorough risk
analysis is conducted. Some analysis parameters are:
- costs: how much does it cost to test a particular component of the
system. Will lack of adequate funds refrain us from conducting fundamental
tests?
- frequency of use: which part of our system will be used the most?
More testing effort may have to be focused on high-usage systems or
components
as hidden errors have a greater potential to surface as troublesome
faults.
- testing schedule: how much time has been allocated to testing the
various deliverables within the system? Is this enough time, or will
lack of
adequate time introduce an element of risk?
More Software Testing information:
top of page
|
