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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ISTQB CTAL-TTA Exam - Topic 1 Question 45 Discussion

Actual exam question for ISTQB's CTAL-TTA exam
Question #: 45
Topic #: 1
[All CTAL-TTA Questions]

The following user story has been written for a new application being developed to pre-book a space at a National Car Park.

As a vehicle driver

i want to be able to pre-book a car parking space online, selecting a disabled driver's space if needed

So that l can pay in advance and receive confirmation of my parking space number.

The following acceptance criteria have also been written:

* Payment can be made via PayPal, Debit or Credit Card

* Confirmation of payment and car parking details should be sent after the booking process is completed

* Driver information is stored in the reservation database

The database has been built and tested in a previous sprint, but the interface to the different payment methods have yet to be developed

As a tester in an agile team, you have been asked to review the user story You have detected some issues with this story:

1. it needs to cater for different user groups: a driver or disabled driver

2. it needs to cater for different vehicle types: a car. 4x4. van or motorbike

3. There are no acceptance criteria relating to how quick the booking process should be

4. How confirmation is to be sent for payment and space number, and other important details, have not been specified

5. A stub will be needed to test the payment method

Which pair of requirements engineering techniques are you MOST LIKELY to have used to uncover these issues'

SELECT ONE OPTION

Show Suggested Answer Hide Answer
Suggested Answer: D

The most likely pair of requirements engineering techniques used to uncover the issues mentioned with the user story would be 'Storyboards and Personas.' This approach allows for a visual and persona-based exploration of how different users (such as drivers of different vehicle types and disabled drivers) would interact with the system. This technique helps in uncovering varied user needs and ensuring that all critical user interactions are considered during the development process.


by Cecilia at Jan 26, 2026, 01:54 PM

Limited Time Offer

25%

Off

Get Premium CTAL-TTA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Sabra
1 day ago
Yep, those are some good points the tester raised. Gotta nail down those requirements.
upvoted 0 times
...
Lenna
6 days ago
Haha, a stub for the payment method? Sounds like a fun challenge for the dev team!
upvoted 0 times
...
Maurine
12 days ago
Agreed, the user story is a bit vague. Gotta make sure it covers all the bases.
upvoted 0 times
...
Stephaine
17 days ago
The user story could definitely use some more details. Glad the tester caught those issues!
upvoted 0 times
...
Claudio
22 days ago
Oof, this is a lot to unpack. I'm feeling a bit overwhelmed, to be honest. I think I'll start by reviewing the user story and acceptance criteria carefully, and then try to break it down into smaller, more manageable pieces. Maybe I'll even sketch out a few user flow diagrams to help me visualize the different scenarios. Gotta take it one step at a time, right?
upvoted 0 times
...
Makeda
27 days ago
This is a tricky one, but I feel pretty confident I can handle it. The key is to really dig into the user story and acceptance criteria, and then use a mix of techniques like interviews, workshops, and prototyping to get a clear understanding of all the requirements. Once I've got that, I can start mapping out a test plan to cover all the bases.
upvoted 0 times
...
Elza
2 months ago
Okay, I think I've got a strategy here. I'd start by reviewing the user story and acceptance criteria in more depth, and then use a combination of use case analysis and requirements elicitation techniques to uncover any missing or unclear requirements. That should help me identify the key issues and come up with a solid plan for addressing them.
upvoted 0 times
...
Veronika
2 months ago
Hmm, I'm a bit confused about how to approach this. There are a lot of different requirements to consider, and I'm not sure where to start. Maybe I should try to break it down into smaller pieces and tackle them one by one.
upvoted 0 times
...
Earnestine
2 months ago
This looks like a pretty comprehensive user story, but I can see a few areas that could use some more detail. The acceptance criteria don't seem to cover all the different user and vehicle types, and the confirmation process could use some more specifics.
upvoted 0 times
...
Jestine
2 months ago
I feel like we might have covered requirements workshops too, but I can’t recall if that was specifically for acceptance criteria.
upvoted 0 times
...
Gary
2 months ago
I think we practiced using scenarios and use cases in our last session, which might relate to identifying vehicle types and the booking process speed.
upvoted 0 times
...
Lajuana
3 months ago
I’m a bit unsure about the techniques we learned. Was it brainstorming and user stories that we used to uncover issues like these?
upvoted 0 times
...
Vilma
3 months ago
I remember we discussed user personas in class, which could help identify different user groups like disabled drivers.
upvoted 0 times
...

Save Cancel