A COTS architectural component specification stencil for selection and reasoning

Authors:
Jing Dong;Sheng Yang;Lawrence Chung;Paulo Alencar;Donald Cowan
Affiliations:
University of Texas at Dallas, Richardson, TX;University of Texas at Dallas, Richardson, TX;University of Texas at Dallas, Richardson, TX;University of Waterloo, Waterloo, Ontario, Canada;University of Waterloo, Waterloo, Ontario, Canada
Venue:
MPEC '05 Proceedings of the second international workshop on Models and processes for the evaluation of off-the-shelf components
Year:
2005

Citing 5
Cited 0

Dealing with non-functional requirements: three experimental studies of a process-oriented approach

Proceedings of the 17th international conference on Software engineering
Architectural mismatch or why it's hard to build systems out of existing parts

Proceedings of the 17th international conference on Software engineering
Pattern-based reverse-engineering of design components

Proceedings of the 21st international conference on Software engineering
Certifying Off-the-Shelf Software Components

Computer
Experience Report: Correcting System Failure in a COTS Information System

ICSM '98 Proceedings of the International Conference on Software Maintenance

Quantified Score

Hi-index	0.00

Visualization

Abstract

Reusing commercial-off-the-shelf (COTS) components may reduce cost and time-to-market. It may significantly improve software productivity. However, the selection and assessment of COTS components are still a challenge task. It is hard to find the right components that exactly fit into the requirements. The selection processes are in general ad-hoc. Wrong choice of COTS components may compromise the benefits from reusing these components since the chosen component may mismatch with other components and the environment. In this position paper, we advocate a more detailed architectural specification stencil which may help on the component selection and mismatch detection. The architectural specification of a COTS component is encoded in XML so that searching components can be automated. In addition, inconsistencies and mismatches among components can be detected.