What is Incident Management and Incident Lifecycle in Software Testing ? Risk Analysis, Management.

Incident Management

Any event that occurs during testing that requires subsequent investigation or correction.

Actual results do not match expected results possible causes :
  1. Software fault
  2. Test was not performed correctly
  3. Expected results incorrect
  • May be used to monitor and improve testing.
  • Should be logged.
  • Should be tracked through stages, e.g.:
Initial recording , analysis (s/w fault, test fault, enhancement, etc.), assignment to fix (if fault), fixed not tested, fixed and tested OK, closed.

Incident Lifecycle 

Tester Tasks

  1. Steps to reproduce a fault.
  2. Test fault or system fault.
  3. External factors that influence the symptoms.
  4. Is the fault fixed ?
Developer Tasks
  1. Root cause of the problem.
  2. How to repair (without introducing new problems).
  3. Changes debugged and properly component tested.

   Risk Analysis

What is Risk ?

  • Risk is a potential that a chosen action or activity will lead to a loss or undesirable outcome.
  • Risk is a potential problem. It might happen or might not.
Example : There is a possibility that I might meet with an accident if I drive.
                  There is no possibility of an accident, if I do not drive at all.

Risk Analysis:

  • Risk analysis and Management are a series of steps that help software team to understand and manage uncertainly.
  • Risk analysis is " Combination of likelihood and the impact that it could have on the user ".
What Risk Analysis Can Do ?

Help in 
  • Forecasting any unwanted situation.
  • Estimating damages of such situation.
  • Decision making to control such situation.
  • Evaluating effectiveness of control measures.

How the risks can be ranked ?

Risk Probability : Probability of an adverse event occurring.
E.g. system crashes, airplane crash.

Impact : Consequence of an adverse event occurring.
E.g. lives lost, cost of an airplane etc.

Exposure : Is the measure of importance of the risk.
Exposure = Probability*Impact

Risk Management

Software Risks :
  1. Risk identification : It is a systematic attempt to specify threats to the project by identifying known and predictable risk.
  2. Risk analysis : The process of assessing identified risks to estimate their impact and probability of occurrence (likelihood).
  3. Risk planning :  Draw up plans to avoid or minimize the effects of the risk.
  4. Risk monitoring : Monitor the risks throughout the project.

Risk Mitigation

The activity of mitigation and avoiding risks is based on information gained from the previous activities of identifying, planning and assessing the risks.
Avoids risks and minimize their impact.

Example :-
Man goes to an ATM machine
Quadrate 1 : Forgets his ATM card in the ATM machine. HIGH probability that his card will be stolen and money swiped.

Quadrant 2 : The man uses wrong PIN in the ATM. HIGH Probability that his transaction will fail. Low impact as he will not loose any money even through he will not get any money either.

Quadrant 3 : The ATM machine does not give printed receipt of money withdrawn. No money is lost but the customer does not get receipt of transaction.

Quadrant 4 : The man uses his card to withdraw money from ATM. The ATM hands over fake notes. Very low probability but HIGH impact. 
   

Comments

Popular posts from this blog

What are the different levels of Testing in Software Testing? Unit Testing, Integration Testing, System Testing, User Acceptance Testing.

What is Software Testing and Why Testing is necessary ?Principles, STLC , SDLC-Model, Agile-Model, V-Shaped Model, CMMI-Levels.

What is Digital Marketing and How to learn Digital Marketing ? Modules, Blog, Domain, Hosting, SEO.