Adapting COTS products

2010 IEEE International Conference on Software Maintenance Pub Date : 2010-09-12 DOI:10.1109/ICSM.2010.5609658

D. Wile, R. Balzer, N. Goldman, Marcelo Tallis, Alexander Egyed, T. Hollebeek

{"title":"Adapting COTS products","authors":"D. Wile, R. Balzer, N. Goldman, Marcelo Tallis, Alexander Egyed, T. Hollebeek","doi":"10.1109/ICSM.2010.5609658","DOIUrl":null,"url":null,"abstract":"COTS products can play various architectural roles in software systems: as interfaces to problem-specific functionality, as components that provide such functionality itself, and as intermediary connectors and components in more complex systems. In doing so, COTS products impose their own, unique constraints on organization and functionality. Over the last ten years, we have gained considerable experience with adopting, adapting, and living with the limitations of COTS products. Our goal was to adapt the COTS product to make it fit the application rather than adapting the application needs to make them fit the COTS product - thus, in essence, adapting the COTS product without access to its source code or documentation (a unique form of maintenance). We report on a large set of experiences involving eight COTS products and a wide range of COTS-Based Software Systems - most of which were done with and for industrial partners or government agencies. This experience report attempts to both give a feeling for how applications can be augmented with such COTS interfaces and also tries to tease out the specific architectural issues that anyone adapting COTS products is certain to face.","PeriodicalId":101801,"journal":{"name":"2010 IEEE International Conference on Software Maintenance","volume":"9 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2010-09-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"6","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2010 IEEE International Conference on Software Maintenance","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICSM.2010.5609658","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 6

Abstract

COTS products can play various architectural roles in software systems: as interfaces to problem-specific functionality, as components that provide such functionality itself, and as intermediary connectors and components in more complex systems. In doing so, COTS products impose their own, unique constraints on organization and functionality. Over the last ten years, we have gained considerable experience with adopting, adapting, and living with the limitations of COTS products. Our goal was to adapt the COTS product to make it fit the application rather than adapting the application needs to make them fit the COTS product - thus, in essence, adapting the COTS product without access to its source code or documentation (a unique form of maintenance). We report on a large set of experiences involving eight COTS products and a wide range of COTS-Based Software Systems - most of which were done with and for industrial partners or government agencies. This experience report attempts to both give a feeling for how applications can be augmented with such COTS interfaces and also tries to tease out the specific architectural issues that anyone adapting COTS products is certain to face.

查看原文本刊更多论文

适应COTS产品

COTS产品可以在软件系统中扮演各种架构角色:作为特定问题功能的接口，作为提供此类功能本身的组件，以及作为更复杂系统中的中间连接器和组件。在这样做的过程中，COTS产品对组织和功能施加了它们自己的、独特的约束。在过去的十年中，我们在采用、适应和适应COTS产品的局限性方面获得了相当多的经验。我们的目标是调整COTS产品使其适合应用程序，而不是调整应用程序需求使其适合COTS产品——因此，本质上，调整COTS产品而不访问其源代码或文档(一种独特的维护形式)。我们报告了涉及8种COTS产品和广泛的基于COTS的软件系统的大量经验—其中大多数是与工业伙伴或政府机构一起完成的。这份经验报告试图给出一种感觉，即如何使用这样的COTS接口来增强应用程序，同时也试图梳理出任何采用COTS产品的人肯定会面临的特定架构问题。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文求助全文

来源期刊

2010 IEEE International Conference on Software Maintenance

自引率

0.00%

发文量