Redesigning Enterprise Processes for E-Business
Redesigning Enterprise Processes for E-Business
Lean Six SIGMA: Combining Six SIGMA Quality with Lean Speed
Lean Six SIGMA: Combining Six SIGMA Quality with Lean Speed
Service-Oriented Architecture Compass: Business Value, Planning, and Enterprise Roadmap
Service-Oriented Architecture Compass: Business Value, Planning, and Enterprise Roadmap
Impact of service orientation at the business level
IBM Systems Journal
Models for semantic interoperability in service-oriented architectures
IBM Systems Journal
The World Is Flat [Updated and Expanded]: A Brief History of the Twenty-first Century
The World Is Flat [Updated and Expanded]: A Brief History of the Twenty-first Century
SOA for the Business Developer: Concepts, BPEL, and SCA (Business Developers series)
SOA for the Business Developer: Concepts, BPEL, and SCA (Business Developers series)
Service-oriented design and development methodology
International Journal of Web Engineering and Technology
IBM business transformation enabled by service-oriented architecture
IBM Systems Journal
Designing environmental software applications based upon an open sensor service architecture
Environmental Modelling & Software
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Towards an architectural viewpoint for systems of software intensive systems
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Application integration patterns based on open resource-based integrated process platform
ICICA'11 Proceedings of the Second international conference on Information Computing and Applications
Hi-index | 0.00 |
The primary objective of service-oriented architecture (SOA) is to use information technology to address the key goals of business today: innovation, agility, and market value. Agility in SOA is achieved by use of the principles of encapsulation, modularity, and loose coupling, which facilitates a cleaner separation of concerns. While loose coupling enables customers to rapidly reuse services in new applications, strong coherency must be maintained to achieve the primary business objectives of the application. When applications are composed of loosely coupled services that are independent (owned by different parts of the organization, based on disparate technology assumptions, and evolving on independent schedules and with diverse priorities) the coherency of the composite application can be undermined. In this paper, we examine how coherency can be created and maintained in loosely coupled applications. We examine, in this context, various techniques and design approaches, such as service management, the use of service buses, the role of industry models and semantic ontologies, and governance, to achieve and maintain coherency of composite applications using SOA.