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…

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