Software architecture in practice
Software architecture in practice
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
Managing variability in software architectures
SSR '01 Proceedings of the 2001 symposium on Software reusability: putting software reuse in context
Building systems from commerical components
Building systems from commerical components
Variability Issues in Software Product Lines
PFE '01 Revised Papers from the 4th International Workshop on Software Product-Family Engineering
Considering Variabilities during Component Selection in Product Family Development
PFE '01 Revised Papers from the 4th International Workshop on Software Product-Family Engineering
On the Notion of Variability in Software Product Lines
WICSA '01 Proceedings of the Working IEEE/IFIP Conference on Software Architecture
A Software Development Process for COTS-based Information System Infrastructure
SAST '97 Proceedings of the 5th International Symposium on Assessment of Software Tools (SAST '97)
A Procurement-centric Model for Engineering Component-based Software Systems
SAST '97 Proceedings of the 5th International Symposium on Assessment of Software Tools (SAST '97)
A comprehensive reuse model for cots software products
A comprehensive reuse model for cots software products
| Hi-index | 0.00 |
COTS (commercial off-the-shelf) component designers and developers often envision different usage contexts for their component and, therefore, provide it with adaptation possibilities. These adaptation possibilities are especially important when considering system families. System family engineering is currently an emerging discipline. Variability is a core property of system families which allows deriving different customer-specific applications from a core artifact base. A system family's core artifact base may also be populated with COTS components. These COTS components then need to support the system family's variability, i.e. they have to offer the possibility to adapt them to different customer-specific applications. Through their adaptation possibilities COTS components are able to meet this requirement. During COTS evaluation, a system family's requirements and architecture need to be taken into account. Variability is inherent in both. That is, the question is how to evaluate COTS with regard to variable features. In this paper, we describe variability in architecture in more detail and point out how this variability needs to be reflected in COTS evaluation criteria. The contribution is an extension of ‘traditional' COTS evaluation criteria in order to consider a system family's variability.