IOTSDM Workshop, ICCBSS, February 2006, Orlando, Florida, USA
Updates are a major part of the maintenance of every COTS-based application. Security flaws, bugs or missing functionalities can cause a vendor to reissue a new version and when major new functionality is added to the COTS component, vendors usually release a new major version. Every update - minor or major - is a potential risk for the existing functionality of the COTS-based application. This makes updating a difficult choice when a new version is available: will the new features and bug fixes be worth all the potential work to ensure existing functionality will not be broken? This paper presents a process and a risk scale factor that aims to evaluate the risk of updating of one COTS component in an application.