Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
DIPES '98 Proceedings of the IFIP WG10.3/WG10.5 international workshop on Distributed and parallel embedded systems
Programming Web services with SOAP
Programming Web services with SOAP
Patterns of Enterprise Application Architecture
Patterns of Enterprise Application Architecture
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
A compositional formalization of connector wrappers
Proceedings of the 25th International Conference on Software Engineering
Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
Integrating COTS Software into Systems through Instrumentation and Reasoning
Automated Software Engineering
Wrapper-based evolution of legacy information systems
ACM Transactions on Software Engineering and Methodology (TOSEM)
A Rich Services Approach to CoCoME
The Common Component Modeling Example
Requirements for service composition in ultra-large scale software-intensive systems
Monterey'08 Proceedings of the 15th Monterey conference on Foundations of Computer Software: future Trends and Techniques for Development
Hi-index | 0.00 |
The use of commercial off-the-shelf (COTS) software can greatly reduce the development cost and effort for complex software systems. Reusing software can also improve the general quality of a system by leveraging already proven implementations. One of the limiting factors in the adoption of COTS software is the complexity of integrating it with the rest of the system under development. Often, requirements do not entirely match the functionalities available in COTS components, increasing the complexity of the glue software that needs to be written. In this paper, we present the blueprint of a Service- Oriented Architecture that can guide the engineer both in specifying the functionalities of a complex software system and as a deployment architecture to seamlessly integrate COTS components implementing such functionalities. The COTS integration concern, typically a deployment issue, is addressed in the service architecture, and is treated as first-class citizen of the development process.