| Service Oriented Architecture is the hot | | | | needs to be well managed, controlled, clean, etc? |
| movement in IT right now, and rightly so. It | | | | Well... yes. |
| leverages code in a way that makes it flexible | | | | Metadata will level set everyone in the |
| and reusable, integrates legacy and one-off | | | | organization as to what the data actually means. |
| systems, and solves just about every other | | | | Hopefully you have an enterprise data dictionary, |
| problem in the world. | | | | but if you don't, write that down as task #1. |
| So, if you're bringing this to your organization, | | | | Data Governance will provide the proactive and |
| good for you. A key piece to your SOA roadmap | | | | reactive management needed to ensure |
| should be an effective Data Management plan. | | | | everyone agrees on what a field is to be used |
| Your Data Management plan should include Data | | | | for. The results of this end up in the metadata |
| Quality, Metadata, and Data Governance. | | | | repository mentioned above. |
| Lets face it, SOA will integrate all your systems | | | | Data Quality checks for data anomalies and |
| and allow for sharing across many lines of | | | | procedures should kick-out any outliers to be |
| business and systems. But, what is shared? The | | | | manually or systematically corrected based on |
| Data. Let me reiterate that... The reason for SOA | | | | business rules. |
| is so that data and information are processed | | | | So, be sure to integrate an effective Data |
| more efficiently and effectively. | | | | Management plan in your SOA roadmap, |
| So, doesn't it then make sense that your data | | | | otherwise it will be a bumpy road at best. |