46
Data Element Requirements
zOnly useful in a context, that is its use (usefulness) is in a process. (NOTE: A report is the result of a process.) zData elements are often discovered over time. However, experienced domain participants should know the basic structures (patterns). zThird party interfaces impose special data element considerations. Do not seek to integrate - seek to interface. Create adapters between applications and systems (internal* or external) z*That is, unless the applications are developed using the same kernel (which includes runtime and persistent artifacts).
Data is too broad a term. For this discussion I’m constraining this to data elements. Individual instances of facts that one requires.
Integrating third party applications is too costly and is not the right attitude. Shoe-horning apps has never worked. Avoid folks who promote these ideas. Even trying to integrate in-house applications can be problematic. You’re better off developing adapters to interface between applications than necessarily “pointing” to the same data element. The acquisition of a data element should be a service.