This is great! As a CTO, having live integrity checks would strongly increase my trust, versus our current unit tests that cover data integrity. Development is nice, but live systems are real.
back
1 comments
Strictly speaking, data integrity isn't part of your role. Properly implementing business-wide data governance policies is the domain of the CDO. Data integrity and validity is not a property of any single application, but should be formalized as part of the business requirements and processes. This includes:
- identifying data flows: which data travels across which systems?
- determining data authority: which application/data store is authoritative for which piece of data?
- assigning data stewardship roles: which manager is tasked with maintaining data integrity for which authoritative data?
- documenting data definitions: what are the exact semantics of certain data fields?
Once the business has formalized its requirements on its data, you can use those requirements in your technology strategy (both in purchasing decisions, in-house development and worker training). But in the end, these requirements are business-driven, not technology-driven.
You don't know a single thing about my organization. Why are you telling me what my responsibilities are?