ISTQB 연습문제 풀이 - Exam A : Q#17


1. Introduction

This question checks your ability to identify the correct review type based on the attributes of a review process. Understanding how walkthroughs, inspections, and technical reviews differ is essential for the ISTQB exam.

Note (EN/KR):
Pay attention to clues such as “author-led,” “scribe present,” and “purpose is to evaluate quality.”
“작성자 주도(author-led)”, “서기(scribe) 존재”, “품질 평가 목적” 등의 단서를 잘 파악해야 합니다.

2. Key Concepts

✔ Review Types at a Glance

  • Informal Review – No formal roles required; documentation optional.
    비공식 리뷰: 역할/문서화가 필요하지 않음.
  • Walkthrough – Led by the author; includes scribe; focuses on understanding and quality.
    워크스루: 작성자가 주도, 서기 포함, 품질 이해·평가 목적.
  • Technical Review – Led by a technical expert; author does not lead; focuses on alternative solutions.
    기술 리뷰: 기술 전문가가 주도, 작성자가 이끌지 않음.
  • Inspection – Very formal; strict roles; moderator required; author does not lead the meeting.
    인스펙션: 매우 형식적이며, 모더레이터 필요, 작성자가 이끌지 않음.

3. Practice Question

❓ Question

The reviews used in your organization have these attributes:

  • There is the role of a scribe
  • The main purpose is to evaluate quality
  • The meeting is led by the author
  • There is individual preparation
  • A review report is produced

Which review type is MOST likely being used?

  • a) Informal review
  • b) Walkthrough
  • c) Technical review
  • d) Inspection

✅ Correct Answer: b) Walkthrough

📘 Explanation (EN/KR)

  • Not informal review. The presence of roles (scribe), preparation, and a report indicates a structured process. 비공식 리뷰 아님. 서기·준비·보고서 등은 비공식 리뷰와 맞지 않습니다.
  • Walkthrough fits all attributes.
    – Author leads the meeting ✔ – Scribe records findings ✔ – Purpose includes evaluating quality ✔ – Individual preparation allowed ✔ – Review report possible ✔ 워크스루는 모든 특징에 부합: 작성자 주도, 서기 존재, 품질 평가 목적, 사전 준비 가능, 보고서 작성 가능.
  • Not inspection. Author does NOT lead in inspections; a moderator leads.
    인스펙션 아님. 인스펙션에서는 작성자가 회의를 이끌 수 없습니다.
  • Not technical review. Usually led by technical experts, not the author.
    기술 리뷰 아님. 기술 리뷰는 작성자가 아닌 전문가가 주도합니다.

✔ Therefore, the review type described is a walkthrough.
✔ 따라서 해당 리뷰 유형은 워크스루입니다.

📊 Summary Table

Attribute Walkthrough? Reason
Scribe present ✔ Yes 워크스루에서 서기 가능
Author leads meeting ✔ Yes 작성자가 회의 주도
Main purpose is quality evaluation ✔ Yes 품질 평가가 핵심 목적
Individual preparation ✔ Allowed 사전 준비 가능
Review report produced ✔ Allowed 보고서 작성 가능

4. Summary & Call to Action

Walkthroughs are semi-formal reviews led by the author and focused on understanding and evaluating quality. They differ from inspections and technical reviews due to their flexibility and author-led nature.

워크스루는 작성자 주도, 품질 평가 목적, 비교적 유연한 구조를 가진 반형식적 리뷰입니다. 인스펙션/기술 리뷰와 구분되는 특징을 잘 기억하세요.

refer to : FL-3.2.4


Related: More ISTQB Posts

다음 이전