
Silverston c06.tex V2 - 11/21/2008 3:09am Page 294
294 Chapter 6 ■ Status: The States of Data
of this pattern allows an enterprise to explicitly define the behavior
between the status types. If the intention of the enterprise is to maintain
information about statuses in data structures as opposed to putting them
within applications, this pattern allows you to build intelligence into the
data and better manage status data.
For more mature data enterprises that are committed to making an
investment in data management. A certain amount of discipline is
needed to use this pattern. This pattern is intended for enterprises that
have a strong intention and commitment to be data-driven.
What Are the Weaknesses of the Pattern?
The weaknesses of this p attern are as follows:
This pattern is complex. It is easy even for experienced data profes-
sionals to have difficulty understanding this pattern. The implemen-
tation and use of this pattern should ideally be within the context of
a broader data management program. It requires training and under-
standing for programmers and application architects to use this pattern,
and commitment from the enterprise to invest in an integrated data
management strategy. That said, once this pattern is understood and
utilized, it is a very powerful tool for management of statuses.
Rules may be already maintained in a metadata repository or rules
engine. If your enterprise is