The place where BPM and SOA meet is one where two ideologies must work together: those of business people and those
of developers. The effectiveness of these two mindsets to communicate requirements is essential to the success of a SOA and BPM implementation.
In a panel at a recent SearchSOA virtual trade show, several experts spoke up on issues in this area. One thing all agreed upon was the need for an integrated and educated team.
Sandy Kemsley, an analyst and systems architect with Kemsley Design, said she often sees a team of business experts thinking in purely business terms and a team of developers thinking only in terms of what code they'll need to write. But SOA is not the sort of architecture that one builds by throwing code at it. It is, at its core, very conceptual.
Peter WoodhullPrincipalModus 21
"We have found that the biggest hurdle is invariably organizational and you have to start with training," said Peter Woodhull, principal at Modus 21. "IT realizes the burden is not on them anymore. The business has to be the responsible party."
A large degree of preparation goes into readying an enterprise for BPM through SOA, but the benefits can be great. Where processes often once lived in silos and did not make use of reusable components, a SOA-backed BPM is far easier to modify and connect with new processes down the road.
Woodhull said that SOA may actually give smaller companies a competitive advantage. In larger organizations, there is often a mentality of implementing SOA for compliance purposes, he said. The smaller an organization is, the more fully it can adopt SOA principles from the offset. And thus, the more effective its BPM practices might turn out to be.
"Using BPM and SOA together really pays off as your timeline increases," said Marc Smith, director of technology marketing at Lombardi. "It's when you start looking at the long term goals and execution that using SOA techniques in conjunction with your process improvement tools really starts to pay off."
The panel generally agreed that it is of utmost importance for the business and IT side of a BPM implementation to work together to define exactly what the business objects are and what operations need to be performed on them.
SOA, of course, is intended to address the issue of disorganized code and systems, often referred to as 'spaghetti.' But without a business objective, even SOA can lead to such mangled systems. Said Lombardi's Smith: "Unless you use SOA in the context of what you're trying to do with the business, you can end up with just the new spaghetti to replace the old spaghetti."
BPM, SOA and steps toward better application building
Podcast: Forrester analysts talk SOA and BPM
Co-evolution of BPMN and BPEL drives BPM in SOA settings