4 ms·
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 makin
by oscillonoscope 3y ago
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
- BaseballPhysics 3y agoIt's a suggestion for a tool to create that matrix. i.e., you propose these "anti-requirements" as a way to surface attributes that have no direct relationship. Feels a bit kitschy to me, but with the right audience, or with an inexperienced BA, perhaps it has merit.
- oscillonoscope 3y agoBut why not just create it directly? To use the article's example, you can just directly fill in or ask questions about the upper triangle of the matrix below. Adding in the anti-requirements just adds the possibility of missing a combination. Name Desc Price Qty Name Desc Price Qty
- BaseballPhysics 3y ago> To use the article's example, you can just directly fill in or ask questions about the upper triangle of the matrix below. 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.