This lens is about the adoption of Service-Oriented Architecture (SOA).
Barriers to SOA Adoption?
Please vote for the inhibitors you think most significant. Or submit additional inhibitors.
The Organization Itself
says CBDI1 point
IT Department
says Zapthink0 points
XML Skills
says Perficient0 points
Lack of Business Justification
says BEA0 points
Vision, People, Management & Resources
says InfoSys0 points
Lack of awareness and familiarity with SOA
says Vinita Gupta, journalist0 points
Complexity
says BEA0 points
IT Integration and Flexibility
says IBM0 points
Detangling the web of applications and old systems
says NSW Police0 points
Lack of discretionary spending in IT
says Interarbor Solutions0 points
The Desktop
says ZDNet0 points
Resistance to Change
says IDC0 points
Available material
Resources on SOA adoption
- Roadmap - PGFSOA Wiki
- A Roadmap for SOA adoption - from the Practical Guide to Federal SOA (PGFSOA)
- CBDi Web Services Roadmap
- CBDI Web Services Roadmap - Guiding the Transition to Web Service and SOA
- Richard Veryard on SOA Adoption
- Selected posts from Richard Veryard's SOAPbox blog.
Reader Feedback
submit
-
Reply
- Todd Biske Todd Biske May 11, 2007 @ 8:08 am
- While resistance to change and the organization itself are somewhat the same thing, my instinct is that it's the broader organization that is typically the barrier, and it's usually that the entire org is resistant to change.
Explore related pages
Service Oriented Architecture (SOA)- A common language for expression of ideas between IT and Business have been long...
SOA Security- SOA is often thought to introduce new challenges for security. But at the same t...
