Of late, SOA initiatives have more often crisscrossed with BPM projects. That has only intensified the interest in MDM.
"MDM is heavily tied into what I would call SOA development and business user empowerment," says Malcom Ross, director of product management at BPM vendor Appian Corp.
"When you think of building an enterprise SOA, you think of everything as consumable objects. That's been done with object components like JavaBeans, but data management of this type has been pretty difficult," he says. "It is hard to have a SOA approach without making your data a top-level service."
Gartner Inc. analyst Michael Blechar has discussed the role master data management plays in creating reusable, sharable data services for BPM and SOA. In a blog entry, Blechar writes that ensuring that the architecture and analysis efforts of BPM, SOA and MDM projects are coordinated "should be of extreme importance to business and IT management.''
Some of this should happen as part of an organization's MDM effort to address the governance of data services. But collaboration across enterprise groups is key, as there is much to be learned from the data structures, workflows and services coming out of SOA and BPM projects, according to Blechar.
Meanwhile, BPM mashups and business rules engines, coupled with MDM, may change the tenor of data integration.
SOA and MDM: GIGO 2.0?A five part special report
Part 1: SOA with MDM prevents messaging confusion
Part 2: SOA and MDM: New techniques address old problems
Part 3: Data architecture project practices with SOA and MDM
Part 4: MDM brings SOA and BPM closer together
Part 5: With MDM and BPEL, business users become data stewards