Domain-Specific Software Component Models

Abstract

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.

A catalogue of component connectors to support development with reuse

“…For future work, we plan to consider the issues of domain specificity (Lau and Taweel, 2009) and non-functional properties for components and connector definitions. In Section 8.4, we mentioned that we are convinced that our connectors are good for developing certain types of control systems.…”

An Analysis Of Life Cycle Models For CBSD

“…It consists of two phases: component design and component deployment, and is set in the context of a problem domain. In the design phase, components are designed and constructed according to the domain requirements or knowledge, and deposited into a repository [7]. Repository components are domain-specific but not system-specific.…”

The W Model for Component-Based Software Development

“…It consists of two phases: component design and component deployment, and is set in the context of a problem domain. In the design phase, components are (identified and) designed and constructed according to the domain requirements or knowledge [16], and deposited into a repository. Repository components are domain-specific but not system-specific.…”