- This summary
- +380.000 other summaries
- A unique study tool
- A rehearsal system for this summary
- Studycoaching with videos
A snapshot of the summary - ISQTB Technical test analyst
1 The Technical Test Analyst's Tasks in Risk-Based Testing
Who's responsible for a risk-based testing stragegy?The testmanager with involvement of the Technical Test Analyst.
What is the contribution of the TTA within the risk_based testing framework?They contribute their knowledge of the technical product
riskthat are inherentin a project, such risks as security, system reliabilityand performance.
1.2 Risk-based Testing Tasks
What in which risk-based test tasks are TTA actively involved?
- Risk identification
- Risk assessment
- Risk mitigation
1.2.1 Risk Identification
What's the role of TTA within risk identification?Because Technical Test Analysts possess unique technical skills, they are particularly well-suited for conducting expert interviews, brainstorming with co-workers and also analyzing the current and past experiences to determine where the likely areas of product risk lie.
With whom does the TTA works together to determine technical risks?With other stakeholders such as:
- operations engineers,
- product owners,
- local support offices
- service desk technicians.
According to the ISO25010 which risks are mostly identified by the TTA?
- Performance efficiency (e.g., inability to achieve required response times under high load conditions)
- Security (e.g., disclosure of sensitive data through security attacks)
- Reliability (e.g., application unable to meet availability specified in the Service Level Agreement)
1.2.2 Risk Assessment
What's the role of the TTA within risk
- In finding and understanding the potential technical product risk
- and understanding the potential business impact of the problem should it occur.
- proposes an initial risk level according to the guidelines established by the Test Manager.
Name a few
- Conflict between
stakeholdersregarding technical requirements
- Communication problems
resultingfrom the geographicaldistribution of the development organization
- Tools and technology (including relevant skills)
resourceand management pressure
- Lack of earlier quality
- High change rates of technical requirements
- Conflict between
Name a few generic product risks.
- Complexity of technology
- Complexity of code structure
- Amount of re-use compared to new code
- Large number of defects found relating to technical quality characteristics (defect history)
- Technical interface and integration issues
Is it possible for an initial risk level proposal handed to the testmanager to be modified?Yes, when all stakeholders views have been considered.