Discuss ISQI CTAL-ATT Exam Topic 3 Question 24

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

ADiagrams and Story Mapping

BStory Mapping and use Cases

CPersonas and Diagrams

DStoryboards and Personas

Suggested Answer: A

Get Premium CTAL-ATT Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

35 comments · newest first

Rolande 11 months ago

I think story mapping would help clarify these issues.

Salley 11 months ago

Good point about the disabled spaces, they should be more specific!

Marcelle 11 months ago

Wait, how are they going to handle payment confirmations? Seems vague.

Sylvia 11 months ago

I agree, especially about the different vehicle types.

Virgina 11 months ago

Sounds like a solid user story, but it definitely needs more detail!

Domonique 12 months ago

I think diagrams might be useful, but I'm leaning towards story mapping since it helps break down user journeys effectively.

Nancey 12 months ago

I feel like we practiced a similar question where we had to identify user needs. Maybe use cases would be relevant here too?

Rhea 1 year ago

I'm not entirely sure, but I think story mapping could help visualize the booking process and highlight missing acceptance criteria.

Tegan 1 year ago

I remember we discussed using personas to identify different user groups, like drivers and disabled drivers, in our last class.

Lachelle 1 year ago

Okay, let's see. I think using a combination of diagrams and story mapping will be key here. We need to map out the different user journeys and scenarios, and then use diagrams to visualize the system and identify any gaps or edge cases. And of course, we'll need to validate everything with the stakeholders.

Jillian 1 year ago

Hmm, this is a tricky one. I can see a few potential issues right off the bat - the lack of specifics around confirmation and the need for a payment method stub. I'll need to think carefully about the best requirements engineering techniques to uncover all the hidden requirements here.

Shoshana 1 year ago

This user story seems pretty straightforward, but I think we'll need to dig deeper to really understand all the requirements. The acceptance criteria are a good start, but we'll need to explore things like different user groups and vehicle types to make sure we cover all the bases.

Eulah 1 year ago

This user story seems pretty comprehensive, but I can see a few areas that need some more attention. The different user groups and vehicle types are definitely something we'll need to explore further. And the lack of specifics around confirmation and timing is a bit concerning. I think a mix of personas and diagrams will be the way to go here.

Refugia 1 year ago

I'm leaning towards "drop out frequency" as the most relevant metric here. That seems like it would directly point to potential network issues causing connections to be dropped.

Lucy 1 year ago

I'm a little confused by the wording of the options. They all seem to be talking about different aspects of the design process. I'm not totally sure which one is the best match for the "identify improvement opportunities" part. I might have to go with my best guess on this one.

Benedict 1 year ago

Hmm, I'm not sure about this one. I'll have to think it through carefully. Spark is supposed to be fault-tolerant, right?

Lonna 1 year ago

Ah, the joys of software development. I bet the team could use a car park pre-booking app just to find a spot for their daily meetings!

Laurel 1 year ago

↳ replying to Lonna

I think the pair of requirements engineering techniques used would be Personas and Diagrams.

Ressie 1 year ago

↳ replying to Lonna

I think the user story needs to cater for different user groups and vehicle types.

Cary 1 year ago

↳ replying to Lonna

I agree, it would make finding a parking spot much easier.

Ammie 1 year ago

↳ replying to Lonna

We definitely need that app for our team meetings!

Ria 1 year ago

Diagrams and personas would have helped uncover these issues. Storyboarding could also be useful to visualize the different scenarios.

Walker 1 year ago

↳ replying to Ria

Yes, storyboarding can also help us visualize the different scenarios and identify potential gaps in the requirements.

Thersa 1 year ago

↳ replying to Ria

Diagrams and personas are definitely important for uncovering issues in user stories.

Tonette 1 year ago

↳ replying to Ria

Storyboarding could also be useful to visualize the different scenarios.

Donette 1 year ago

↳ replying to Ria

Diagrams and personas would have helped uncover these issues.

Ilene 2 years ago

I agree, the user story needs to be more specific. The confirmation process and payment methods should be clearly defined as well.

Jennifer 2 years ago

The user story is lacking in detail, especially around different user groups and vehicle types. The acceptance criteria also need to be more comprehensive.

Delisa 1 year ago

↳ replying to Jennifer

That sounds like a good idea, we can ensure all aspects are covered.

Merilyn 1 year ago

↳ replying to Jennifer

I think we should use Personas and Diagrams to uncover these issues.

Paris 1 year ago

↳ replying to Jennifer

I agree, the acceptance criteria should be more detailed.

Celeste 1 year ago

↳ replying to Jennifer

We need to make sure the user story covers different user groups and vehicle types.

Ettie 2 years ago

I believe we may have used Story Mapping and Use Cases to uncover these issues.

Alline 2 years ago

I agree, the acceptance criteria should specify how quick the booking process should be.

Ettie 2 years ago

I think the user story needs to cater for different user groups and vehicle types.

iSQI CTAL-ATT Exam - Topic 3 Question 24 Discussion