Resolving COTS System Assessment Clashes
暂无分享,去创建一个
COTS significantly complicates the IV&V process. The necessarily pessimistic culture of IV&V has a perspective on which COTS assessment attributes and techniques are relevant that differs greatly from developer's typically optimistic, success-oriented perspective. There is no basis to assume that the COTS assessments made by developers will ultimately be consistent with IV&V COTS assessments. The result frequently results in a “lose-lose” situation where either large re-work costs are incurred to replace existing COTS with IV&V approved COTS, or higher risk and uncertainty must be tolerated (from the IV&V perspective) to continue with the COTS the developers chose. This work seeks to remedy this “culture clash” of COTS assessment perspectives by integrating IV&V and developers system level COTS assessments that provides a result that is both consistent and cost-effective.
[1] Daniel Port,et al. Assessing COTS Assessment: How Much Is Enough? , 2004, ICCBSS.
[2] Chris Abts,et al. COCOTS: A COTS Software Integration Lifecycle Cost Model - Model Overview and Preliminary Data Collection Findings , 2000 .
[3] B. Boehm. Software risk management: principles and practices , 1991, IEEE Software.