Page 1 of 1

Implemented in the application

Posted: Tue Feb 11, 2025 6:52 am
by asimd23
The DMBoK doesn’t recognize data fitness as a specific knowledge area but mentions it as part of data profiling:

Assessing the fitness of the data for a particular use requires documenting business rules and measuring how well the data meets those business rules. [DMBoK-2, 418; emphasis added]

But this sounds an awful lot like “data is of high quality to the vietnam whatsapp number data degree that it meets the expectations and needs of data consumers.” It seems like quality and fitness are being conflated.

As a friend recently commented, “We need quality for the definition of quality.”

Let’s go back to the data headwaters: the customer for whom the data was created in the first place. The needs and utilization context for that customer were:

Expressed in their requirements, epics, features, and/or user stories
Captured in the data definitions, expected content, and other quality dimensions
The needs of additional downstream consumers known a priori may also have been considered, but most of these uses and users emerge after the application is deployed.