I don't understand the benefit of anti-requirements. It seems trivial to put your attributes in a matrix and identify relationships between them. Randomly making up requirements doesn't seem effective
Feels a bit kitschy to me, but with the right audience, or with an inexperienced BA, perhaps it has merit.
Name Desc Price QtyDesc
Price
Qty
And how do you formulate those questions?
This article is proposing a method.
"Just ask," you might respond, but the point is that non-technical audiences might struggle if you just ask "Do we think Name and Price are related?" because that's very abstract.
Formulating it as a specific example of a potential rule or relationship creates something concrete and relatable that people can react to.
Again, I think it's a bit kitschy, but having worked with non-technical audiences who struggle to think in terms of abstract relationships between data elements, I can see some merit in the idea.