Supporting a service-oriented architecture
Proceedings of the 2008 Spring simulation multiconference
BPM on top of SOA: experiences from the financial industry
BPM'07 Proceedings of the 5th international conference on Business process management
An SOA-based diseases notification system
ICICS'09 Proceedings of the 7th international conference on Information, communications and signal processing
A Newborn Screening System Based on Service-Oriented Architecture Embedded Support Vector Machine
Journal of Medical Systems
Implementing Service-Oriented Architecture in Organizations
Journal of Management Information Systems
Factors affecting the organizational adoption of service-oriented architecture (SOA)
Information Systems and e-Business Management
| Hi-index | 0.00 |
You don't have to look far to become aware of the effect that Service-Oriented Architecture (SOA) is having on software systems. Vendors are aggressively marketing hardware, software, tools, and services that support SOA implementation within organizations as diverse as the Department of Defense, banks, federal agencies, manufacturing companies, and health care providers. Even more significantly, customers are embracing SOA as a way to successfully achieve business agility and interoperability among systems. However, our experience from working with current and potential adopters of SOA is that they often have a variety of misconceptions that lead them to oversimplify the effort required to implement SOA. Chief among these misconceptions is the belief that simply by adopting an SOA strategy for the enterprise, an organization has established a well-crafted architecture that will help the organization achieve its many IT goals. In reality, SOA is not an architecture, but an architectural pattern from which an infinite number of architectures can be derived-both good and bad. In this experience report, we discuss at a high level this and several other misconceptions about SOA derived from our experiences.