Testability of Software Components
IEEE Transactions on Software Engineering
Dealing with non-functional requirements: three experimental studies of a process-oriented approach
Proceedings of the 17th international conference on Software engineering
What Do You Mean by COTS? Finally, a Useful Answer
IEEE Software
Collaboration between a COTS Integrator and Vendors
ECSQ '02 Proceedings of the 7th International Conference on Software Quality
On Building Testable Software Components
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
Definition and Classification of COTS: A Proposal
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
A Process for COTS Software Product Evaluation
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
Testing Concurrency and Communication in Distributed Objects
HIPC '98 Proceedings of the Fifth International Conference on High Performance Computing
Assets and liabilities of organizational trust: COTS software adoption in government projects
ICCBSS'05 Proceedings of the 4th international conference on COTS-Based Software Systems
| Hi-index | 0.00 |
Increased use of COTS software components means increased demand for trust in these artifacts. The problem lies in the fact that trust is mainly a philosophical concept. We all deal with trust issues in our daily life yet it is hard for us to identify the attributes of trust. In the context of software components certain aspects and features can be classified as trust attributes. In this paper we attempt to identify these attributes and describe a mechanism to effectively use these in the selection and integration of COTS components. We also emphasize the important connection between the production and procurement processes and discuss how it can help us establish better trust in software components.