Session:Components--Paper Preview
From WICSA Conference Wiki
Service-Oriented Architecture for Deploying and Integrating Enterprise Applications
Michael Jiang - Motorola
Allan Willey - Motorola
Service-Oriented Architectures (SOA) offer a flexible solution to the integration of systems, applications, protocols, data sources, and processes into a cohesive system to support critical business operations. A major challenge in these service-based systems is how to ensure the availability and reliability of web services upon which user applications and services are built. This paper describes a high-availability SOA platform for deploying and integrating enterprise applications. This SOA platform has been used to deploy and integrate multiple large enterprise applications that are used throughout Motorola for the past few years.
Architectural Concerns When Selecting an In-House Integration Strategy – Experiences from Industry
Rikard Land - Mälardalen University
Laurens Blankers - Eindhoven University of Technology
Stig Larsson - Mälardalen University
Ivica Crnkovic - Mälardalen University
Consider the scenario where two or more software systems have been developed in-house, for different purposes. Over time, the systems have been evolved to contain more functionality, until a point where there is some overlap in functionality and purpose. The same situation occurs, only more drastically, as a result of company acquisitions and mergers. A new system combining the functionality of the existing systems would improve the situation both from an economical and maintenance point of view, and from the point of view of users, marketing and customers.
To investigate this problem of in-house integration, we carried out a multiple case study, consisting of nine integration projects in six organizations from different domains (here labelled A-F). For details on methodology, a presentation of the data sources, and the complete copied out interviews, see [3]. Elsewhere we have analyzed the case study data from a process point of view [4], and discussed the possibilities for reuse in this context [2]; the present paper investigates issues of importance to an industrial architect [5] and focuses on how to select a high-level integration strategy."
Adaptor synthesis for protocol-enhanced component based architectures
Massimo Tivoli - University of L'Aquila
David Garlan - Carnegie Mellon University
Correct assembly of software components is an important issue in Component Based Software Engineering. Composing a system from reusable components often introduces a set of problems related to communication and compatibility. In particular, one of the main problems in component assembly is that components may have incompatible interaction behavior. In this paper, we address this problem using an architecture-based approach that can detect integration mismatches, and semi-automatically synthesize a suitable adaptor, or glue code, to bridge them.
Software Component Services for Embedded Real-Time Systems
Frank Lüders - Mälardalen University
Daniel Flemström - Mälardalen University
Anders Wall - ABB Corporate Research
The use of software component models has become popular during the last decade, in particular in the development of software for desktop applications and distributed information systems. Such models have not been as popular in the domain of embedded real-time systems, presumably because of the special requirements such systems have to meet. There is a considerable amount of research on component models for embedded real-time systems, or even narrower application domains, which focuses on source code components and statically configured systems. This paper explores an alternative approach by laying the groundwork for a component model based on binary components and targeting the broader domain of embedded real-time systems. The work is inspired by component models for the desktop and information systems domain in the sense that a basic component model is extended with a set of services for the targeted application domain.
Establishing Connectors as Integration Services
M. Hepner - University of Tulsa
R. Gamble - University of Tulsa
One distinction of service-oriented architectures (SOAs) from component-based architectures is that processing relies on services, such as web services, that avoid dependencies on other components and expect interoperability. SOAs have become so popular that many commercial and government organizations have initiatives to base their business processing solely on web services. This is due to the loosely coupled framework of a SOA and the use of many open standards. Often organizations cannot make the investment to transition entirely to web services and must rely on some existing components. This reliance leads to an architecture that must support both styles, service oriented and component-based. Within this mix, interoperability is no longer guaranteed. In this paper, we examine the representation of connectors as integration services in the architecture design. We describe why they are needed, how they interact with web service coordination specifications, and factors that influence their formation and position within the SOA.
