Objectives:	Explore relationships between EDM / SOA, and how strategies for either will fail if not coordinated Show how coordinating EDM / SOA strategies will optimize enterprise data value and gain IT economies Introduce a flexible C-SODA framework that coordinates EDM / SOA strategies for described benefits
Abstract:	Strategies for EDM and SOA are often pursued as separate programs and initiatives within organizations. There are key overlapping components, roles, processes, and checkpoints for which coordination provides business and IT benefits in making either strategy more successful. Utilizing common Oracle data and SOA tools and related best practices will facilitate such a coordinated enterprise IT strategy around your data and SOA components. Consider these EDM / SOA touchpoints that should be taken into account when forming strategies for either in order to assure mutual success:  Master Data and SOA Enterprise Service Bus transactional data  Data Governance and SOA Governance roles, processes, and checkpoints  Enterprise Data Architecture and SOA release mgmt  Enterprise Architecture release mgmt, including EDA and SOA ESB  Program Mgmt Office (PMO) prioritization, decision criteria, and reporting for EDM / SOA initiatives
Audiernce Focus:	Managers
Expertise:	Advanced
Track:	Architecture
Date:	Wednesday, April 16, 2008
Time:	11:00 AM - 12:00 PM