Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB-CTFL Exam - Topic 2 Question 53 Discussion

Actual exam question for ISTQB's ISTQB-CTFL exam
Question #: 53
Topic #: 2
[All ISTQB-CTFL Questions]

You are responsible for applying the correct technique for a review of the requirements document for a project to develop a new software application. You identify the reviewers and the required roles, including the meeting leader, who is the requirements document author, and a separate role for a scribe. Additionally, you decide to take a relatively informal approach to the requirements review. The goal of the review is to find defects in the requirements document, such as omissions, Inconsistencies, and duplications. Another goal of the review is to improve the software application's usability and accessibility by considering the various stakeholders' viewpoints.

Which of the following statements BEST describes this scenario?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Raymon
1 day ago
Wait, are we sure it's not a checklist-based review?
upvoted 0 times
...
Kerry
6 days ago
Definitely perspective-based, right?
upvoted 0 times
...
Moon
11 days ago
I think it's more of a pair review type.
upvoted 0 times
...
Aileen
17 days ago
Sounds like a walkthrough review to me.
upvoted 0 times
...
Joaquin
22 days ago
C is the way to go. Walkthrough and perspective-based, just like the question says. Easy peasy!
upvoted 0 times
...
Laine
27 days ago
Haha, I bet the requirements author is sweating bullets right now. Gotta love those perspective-based reviews!
upvoted 0 times
...
Ena
2 months ago
Hmm, I'm not sure. The mention of finding defects like omissions and inconsistencies makes me think a checklist-based review might be more appropriate.
upvoted 0 times
...
Benton
2 months ago
I agree, C is the correct answer. The scenario mentions a relatively informal approach, which aligns with a walkthrough review type.
upvoted 0 times
...
Isaac
2 months ago
C) This scenario is using a walkthrough review type and a perspective-based review technique. Seems like the most accurate description.
upvoted 0 times
...
Bulah
2 months ago
I’m confused about the difference between pair reviews and walkthroughs. I feel like this scenario is more about collaboration, so maybe it's a walkthrough?
upvoted 0 times
...
Valentine
2 months ago
I’m leaning towards option C because it talks about improving usability and considering different viewpoints, which sounds like a perspective-based approach.
upvoted 0 times
...
Teresita
2 months ago
I'm not entirely sure, but I remember practicing a question about perspective-based reviews. This seems to fit that idea, especially with the focus on stakeholders.
upvoted 0 times
...
Sena
3 months ago
I think this might be a walkthrough review since it mentions a meeting and discussing the document together.
upvoted 0 times
...
Laura
3 months ago
This is a tricky one. The informal approach makes me hesitant about the walkthrough, but the goals of the review do seem to fit that type. And considering different perspectives is definitely a perspective-based technique. I'll go with option C, but I'm not totally certain.
upvoted 0 times
...
Leila
3 months ago
I'm pretty confident this is a walkthrough review type, since the requirements author is leading it. And the focus on different stakeholder viewpoints suggests a perspective-based approach, so I think option C is the best answer.
upvoted 0 times
...
Micaela
3 months ago
Okay, let me think this through. The informal approach and considering different stakeholder perspectives points to a perspective-based review. But the goal of finding defects seems to align better with a checklist-based approach. I'm leaning towards option C, but I'm not 100% sure.
upvoted 0 times
...
Heike
3 months ago
Hmm, I'm a bit confused. The question mentions an informal approach, which makes me think it's not a formal walkthrough. And the goal of finding defects like omissions and inconsistencies sounds more like a checklist-based review to me.
upvoted 0 times
...
Effie
3 months ago
I think this is a walkthrough review type, since the requirements author is leading the review. And it sounds like they're using a perspective-based approach to consider different stakeholder viewpoints.
upvoted 0 times
...

Save Cancel