1. Question
Consider the following acceptance criteria for a user story written from the perspective of an online store owner.
Given that the user is logged in and on the homepage, When the user clicks on the "Add Item" button, Then the "Create Item" form should appear, And the user should be able to input a name and price for the new item.
In what format is this acceptance criteria written?
- a) Rule-oriented
- b) Scenario-oriented
- c) Product-oriented
- d) Process-oriented
✅ Correct Answer: b) Scenario-oriented
2. Why b) Is Correct
The acceptance criteria follow the Given / When / Then structure, which describes a specific user scenario in a step-by-step way. This style is known as **scenario-oriented acceptance criteria**.
제시된 인수 기준은 Given / When / Then 형식을 사용하고 있으며, 이는 사용 시나리오를 단계적으로 서술하는 **시나리오 기반(Scenario-oriented)** 형식입니다.
3. Why the Other Options Are Incorrect
a) Rule-oriented
❌ Not correct.
Rule-oriented AC uses bullet lists, rules, or input/output tables—not Given/When/Then scenarios.
룰 기반(규칙 기반) 형식은 체크리스트나 입력-출력 표 등 규칙을 나열하는 방식입니다.
c) Product-oriented
❌ Not correct.
There is no “product-oriented” AC format in ISTQB or Agile AC guidelines.
“Product-oriented”라는 AC 형식은 존재하지 않습니다.
d) Process-oriented
❌ Not correct.
There is no “process-oriented” AC format either.
“Process-oriented” 형식 역시 존재하지 않습니다.
4. Summary
- Given / When / Then = **Scenario-oriented acceptance criteria**
- Scenario format is common in Agile (Gherkin syntax)
- Rule-oriented is used for verification lists and decision rules
- Product-oriented / Process-oriented formats do not exist
- Correct answer: b)
Given/When/Then은 사용자 관점의 시나리오를 정의하는 가장 대표적인 시나리오 기반 AC 형식입니다. FL-4.5.2
Related: More ISTQB Posts | 다음 문제