QuestionQ19

Requirements Engineering Techniques

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

As a vehicle driver—

I want to pre-book a car parking space online, choosing a disabled driver's space if required,

so that I can pay in advance and receive confirmation of my parking space number.

The following acceptance criteria have also been written:

  • Payment may be made through PayPal, Debit or Credit Card.
  • Confirmation of payment and car parking details should be sent once the booking process is complete.
  • Driver information is stored in the reservation database.

The database was built and tested in a previous sprint, but the interfaces to the different payment methods have not yet been developed.

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

  • It must cater for different user groups: a driver or disabled driver.
  • It must cater for different vehicle types: a car, 4x4, van or motorbike.
  • There are no acceptance criteria concerning how fast the booking process should be.
  • The method for sending confirmation of payment and space number, and other important details, has not been specified.
  • A stub will be needed to test the payment method.

Which pair of requirements engineering techniques are you MOST LIKELY to have used to identify these issues?

Explanation

Personas reveal missing or inconsistent needs across user groups, such as drivers with disabilities. Storyboards visualize the functional flow, helping expose gaps in booking steps and acceptance criteria, and helping identify required test doubles for undeveloped payment interfaces. ISTQB Advanced Agile Technical Tester Syllabus

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!