Just had some requirements through for a query that a customer has specified.
“Set the value to 1 if the Outcome is not Complete or Cancelled or NULL”
This could be variously interpreted as:
“if the Outcome is NOT Complete and NOT Cancelled and NOT NULL”
Or “if the Outcome is NOT Complete, and NOT Cancelled, or IS NULL”
Or perhaps even “if the Outcome is NOT ‘Complete or Cancelled’ or IS NULL”
Obviously I’ll go back to them for clarity, but it’s a wonder why so often “bugs” arise based on interpretation of specifications.
Technical requirements are often ambiguous when written as free text, the way someone would speak them, because as you have discovered the free text fails to capture where the linguistic stress would be that disambiguates in speech.
Instead, I suggest using a format that is more suited to text.
I would recommend a table. Email the customer back with your current interpretation of the requirements, with a column for outcome and a column for value. Ask them to check and sign off on the table, or to correct the table where it is wrong.
Example:
There are edge-cases with if outcome can be "Complete or Cncelled
Cheers yeah, that is standard usually. I was just having a whinge rather than asking for a solution. In this case the customer was trying to preempt having to complete a change request form (similar to what you’ve described) and get the relevant sign off etc, and had emailed over a “minor alteration” to an existing request, for which they should know better at this stage of the project.
Even using bullet points can help a lot in these situations (I use them quite often in emails with non-technical recipients).