Since by its very definition the goal of CDI is to integrate data, many companies assume that they can overlay their standard system development lifecycle or their data warehouse implementation process onto a CDI effort. However, data warehouses are primarily geared toward analytics whereas CDI systems are functionally oriented. Thus the well-worn, requirements-driven business intelligence (BI) and data warehouse development methods won’t work for CDI. Indeed, too much emphasis on business requirements can jeopardize a CDI initiative. In many ways CDI development is more straightforward, because the business more clearly understands the end game: to deliver an authoritative customer record to other systems.
Hence, with more of a focus on functionality, CDI implementation steps reflect operational systems. Exhibit 5.4 illustrates a simple CDI implementation framework.
It’s critical that CDI, like all enterprise-class IT efforts, be done incrementally. This prevents the “big bang” approach that dooms large IT projects, and ensures a well-scoped effort. Incremental development also means that data security and privacy requirements can be considered in a more deliberate and well-bounded way.
Many companies have an overarching business need that warrants quick delivery of CDI. The two most common needs are compliance—“We need to recognize the account holder as an individual so we can accurately report his deposit activities”; and mergers and acquisitions—“We ...

Get Customer Data Integration: Reaching a Single Version of the Truth now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.