2 ms·
Uh oh. That's a new one for me. I was taught about the idea of anti-requirements at some intro class at my university, but it was presented differently. Instea
by TeMPOraL 3y ago
Uh oh. That's a new one for me. I was taught about the idea of anti-requirements at some intro class at my university, but it was presented differently.
Instead of trying to probe your stakeholders with nonsense questions, anti-requirements were something you'd naturally come up with, and which you would include in the initial spec/design (and later keep track of). Their point wasn't about DDD or any tactical-level thing - it was to channel the natural... creativity of people during initial project planning into fences around project scope. It allowed and encouraged responding to "what about..." questions with a firm "no, we explicitly don't care about this" - so that later, when your developers start making vague hints about designing the shopping cart as eventually-consistent distributed object, or something equally "reasonable" from their POV, you could politely remind them that this is way past the fence and far on the pasture of out of scope, not doing that.
Of course, we had an exercise of coming up with anti-requirements, which went about as well as the TFA with its examples. Only now it finally clicked for me that anti-requirements, in the sense I was taught, are about documenting denials to most obvious hare-brained ideas - so obvious that they're likely to be independently thought of by someone multiple times during the project, and could lead to unnecessary waste of time and resources if attempted.
- hinkley 3y agoI stopped asking anti-requirements because the people you're asking will give whatever answer they think will make you enthusiastic about the project. When they have to walk back what they said six months or a year later, they just see it as a new requirement on the system. They don't realize they've sabotaged the entire project by lying about their certainty that we will ever do whatever they said 'no' to.