Using adapters to reduce interaction complexity in reusable component-based software development

Rine, David C.; Nada, Nader; Jaber, Khaled

doi:10.1145/303008.303018

Cited by 26 publications

(15 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Attribute adaptors are connectors that translate component interaction. An attribute adaptor can be used to convert an incompatible provided attribute so that it satisfies system [12].…”

Section: A Configurationmentioning

confidence: 99%

Re-configurable VoIP interactive response

Talevski

Chang

Dillon

2008

2008 2nd IEEE International Conference on Digital Ecosystems and Technologies

View full text Add to dashboard Cite

“…Attribute adaptors are connectors that translate component interaction. An attribute adaptor can be used to convert an incompatible provided attribute so that it satisfies system [12].…”

Section: A Configurationmentioning

confidence: 99%

Re-configurable VoIP interactive response

Talevski

Chang

Dillon

2008

2008 2nd IEEE International Conference on Digital Ecosystems and Technologies

View full text Add to dashboard Cite

“…When we consider only technical interoperability, that is the connectivity, communication and encoding related aspects, incompatibilities between languages, interfaces or operational environments can be solved quite efficiently. Methods and techniques like interface description languages [22,27], adaptors [34,46], wrappers [26], middleware [28,41] and middleware bridges [10] have quite success- Fig. 1.…”

Section: A Taxonomy Of Service Interoperabilitymentioning

confidence: 99%

Interoperability in Service-Based Communities

Ruokolainen

Kutvonen

2006

Business Process Management Workshops

View full text Add to dashboard Cite

Abstract. Interoperability is a multifaceted problem caused by issues surpassing those of technological incompatibilities. The real interoperability challenges are stemming from various sources, such as organisational incompatibilities buried deeply into the structures of collaborating enterprises, architectural mismatches and defective assumptions about business application behaviour, or from the inherent properties of business collaboration models.To achieve interoperability in enterprise computing environments, the aspects of interoperability must be identified and their properties analysed. This paper studies interoperability issues in enterprise computing environments. Enterprise computing environments under analysis are based on Service Oriented Computing paradigm and enhanced with necessary infrastructure facilities. Several classes of causes for interoperability problems are identified and the mechanisms for overcoming the problems in these classes are briefly discussed.

show abstract

“…All communication with the current system was to be through the OMF COM. Adapters are very useful when a new component is to used in parallel with an existing one [17]. This solution makes it easy to remove the old OMF and replace it with COM in small steps over time.…”

Section: Replacing Omf With Dcommentioning

confidence: 99%

A case study: demands on component-based development

Crnkovic¹,

Larsson²

Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium

View full text Add to dashboard Cite

Building software systems with reusable components brings many advantages. The development becomes more efficient, the reliability of the products is enhanced, and the maintenance requirement is significantly reduced. Designing, developing and maintaining components for reuse is, however, a very complex process which places high requirements not only for the component functionality and flexibility, but also for the development organization. In this paper we discuss the different levels of component reuse, and certain aspects of component development, such as component generality and efficiency, compatibility problems, the demands on development environment, maintenance, etc. The evolution of requirements for products generates new requirements for components, if components are not enough general and mature. This dynamism determines the component life cycle where the component first reaches its stability and later degenerates in an asset that is difficult to use, difficult to adapt and maintain. When reaching this stage, the component becomes an obstacle for efficient reuse and should be replaced. Questions related to use of standard and de-facto standard components are addressed specifically. As an illustration of reuse issues, we present a successful implementation of a component-based system which is widely used for industrial process control.

show abstract

Using adapters to reduce interaction complexity in reusable component-based software development

Cited by 26 publications

References 16 publications

Re-configurable VoIP interactive response

Re-configurable VoIP interactive response

Interoperability in Service-Based Communities

A case study: demands on component-based development

Contact Info

Product

Resources

About