|
|
|
•Many applications that I’ve seen, contort or
duplicate information about a Party.
|
|
•For example, applications may evolve where
there is a discovery for the need of a Contact and not just a Customer. Or, a
Credit Card Main Owner and Credit Card child owners. The application is
amended to take care of these, by adding new tables or sometime flags, to
accommodate the requirement.
|
|
•Even worse, I’ve seen projects that
“re-designed” the application for a new technology that completely replicated
there VIEW about these relationships.
|
|
•Of course, these applications result in poor
structures that provide un-trusted information that is not synchronized and
requires significant scrubbing and reconciliation.
|
|
•Also, the applications are brittle and break
easily when the slightest changes are made. Again, the problems are circular.
|
