Okay, you now have some pretty powerful patterns to help develop quality and consistent data models that can be used for many purposes. Some of these purposes, such as using them for enterprise-wide models in enterprise data management, enterprise data warehousing, data governance, and master data management, deal with enterprise-wide data integration. To be successful at enterprise-wide data integration, you need to gain buy-in and get people to move in the same direction. Likewise, if the patterns are used at more of a specific application level, you still need to gain buy-in so that these patterns can be adopted and used on specific projects. The patterns are useful tools to help you build your data models and data architecture. However, after you've made the decision to understand and use patterns, you still need to address some important questions about socializing the patterns in your enterprise; questions such as the following:
What is an appropriate balance between requiring adherence to the patterns and allowing them to be used completely optionally and used if and when they are helpful to the modeler/designer?
How do you get your enterprise and various people in the enterprise to adopt these patterns? For example, how can you show the value of these patterns to your senior management or how do you show their value to project managers who are constrained by tight deadlines?
What types of policies or principles regarding use of the patterns ...