Read the summary and the most important questions on ISQTB Technical test analyst

• 1 The Technical Test Analyst's Tasks in Risk-Based Testing

• 1.1 Introduction

• 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 risk that are inherent in a project, such risks as security, system reliability and 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:
  

  • developers, 
  • architects, 
  • 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

  This is a preview. There are 1 more flashcards available for chapter 1.2.2
  Show more cards here

• What's the role of the TTA within risk assessment?

  • 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 generic project risks.

  • Conflict between stakeholders regarding technical requirements
  • Communication problems resulting from the geographical distribution of the development organization
  • Tools and technology (including relevant skills)
  • Time, resource and management pressure
  • Lack of earlier quality assurance
  • High change rates of technical requirements

• 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.