
Silverston c09.tex V2 - 11/21/2008 3:16am Page 548
548 Chapter 9 ■ Using the Patterns
choosing to use generalized patterns versus specific patterns. There are some
other considerations that we thought were worth mentioning regarding using
generalized patterns, such as
11
:
Generalized structures move the change process from the typical ‘data
architect to DBA to developer to tester’ process to a data change process,
and often organizations have no formal process for data change like they
have for application change. This can be addressed with organizational
commitment to flexible data modeling structures. In fact, we believe that
using generalized patterns is an important step in empowering users
to take control of their data. The typical data architect-DBA-developer-
tester process is often too cumbersome and slow for users’ needs. Gen-
eralized patterns force a paradigm shift away from this traditional devel-
opment process.
Data stewardship is important when using generalized data patterns
because new instances can have a large effect on the model. For example,
there may be new instances that could result in new roles, classifications,
statuses, contact mechanism types, or business rules. Data stewardship
is about assigning parties to be accountable for the data, and generalized
models require more management of the instances in the data model. An
advantage to using more generalized patterns in data ...