A Component Model for Field Devices

Component-Based Software Engineering

Taweel

2009

Abstract. We believe that for developing applications in a specific domain, the best kind of software component model to use is a domain-specific one. We also believe that current component models intended for specific domains are actually not domain-specific. In this paper we present an approach for deriving domain-specific component models from the domain model of a given domain, and show why such a component model is better than existing models that are not domain-specific.

Section: Discussionmentioning

confidence: 99%

“…By and large, this is not the case for current component models that are meant for special domains, e.g. Koala [22] for consumer electronics, PECOS [20] for field devices and SaveCCM [1] for vehicular systems. These models tend to be generic ADLs.…”

Section: Introductionmentioning

confidence: 99%

Domain-Specific Software Component Models

Component-Based Software Engineering

Taweel

2009

“…3 (b)). Besides ADLs, other software component models that adopt indirect message passing schemes are JavaBeans [27], Koala [30], SOFA [25], PECOS [22], PIN [14] and Fractal [8].…”

Section: Exogenous Connectorsmentioning

confidence: 99%

A Software Component Model and Its Preliminary Formalisation

Formal Methods for Components and Objects

Ornaghi

Wang

2006

Abstract. A software component model should define what components are, and how they can be composed. That is, it should define a theory of components and their composition. Current software component models tend to use objects or port-connector type architectural units as components, with method calls and port-to-port connections as composition mechanisms. However, these models do not provide a proper composition theory, in particular for key underlying concepts such as encapsulation and compositionality. In this paper, we outline our notion of these concepts, and give a preliminary formalisation of a software component model that embodies these concepts.

“…Instead, messages are placed on the bus and components linked to the bus must determine which messages are intended for them. Besides JavaBeans and ADLs, other software component models that adopt indirect message passing schemes are Koala [26], PIN [15] and PECOS [18].…”

Section: Connecting Components By Indirect Message Passingmentioning

confidence: 99%

Exogenous Connectors for Software Components

Component-Based Software Engineering

Velasco-Elizondo

Wang

2005

Abstract.In existing component models, control originates in components, and connectors are channels for passing on the control to other components. This provides a mechanism for message passing, which allows components to invoke one another's operations by method calls (or remote procedure calls) either directly or indirectly via a channel such as a bus. Thus components in these models mix computation with control, since in performing their computation they also initiate method calls and manage their returns, via connectors. Consequently, in terms of control, components are not loosely coupled. In this paper, we propose exogenous connectors, and demonstrate their use in a small example. In contrast to connectors in existing component models, exogenous connectors initiate calls and manage their returns, and are used to encapsulate control in a component model we are working on. In the example, we demonstrate the feasibility of exogenous connectors, and compare them with connectors in closely related architecture description languages.