A case study in applying a systematic method for COTS selection
Proceedings of the 18th international conference on Software engineering
Contemporary Application-Domain Taxonomies
IEEE Software
What Do You Mean by COTS? Finally, a Useful Answer
IEEE Software
Definition and Classification of COTS: A Proposal
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
METRICS '01 Proceedings of the 7th International Symposium on Software Metrics
COTS products characterization
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
Assessment of Reusable COTS Attributes
ICCBSS '03 Proceedings of the Second International Conference on COTS-Based Software Systems
| Hi-index | 0.00 |
Classes of COTS products can be derived by classification attributes, which define a Cartesian space. Examples of such attributes are the architectural level, the kind of the COTS product (is it a standard, or a service, or an executable component?), and the software life cycle phase in which the product is used (is it a development tool or an executable component?). COTS products belonging to the same class can be evaluated and compared by means of evaluation attributes, such as price or type of license. This work has been conceived mainly for learning purposes. Building a classification schema and filling it with products is a way for COTS product familiarization. In addition, the process of defining classes and filling them with COTS poses new research questions, like "why is this class empty?", or "which are the relationships between these two classes?". The result of classification and evaluation process cannot have general validity if it not customized for special organization goals. These customization issues are outside the scope of this work.