Guest Editors' Introduction: Integrating COTS into the Development Process

Authors:
Alexander Egyed;Hausi A. Muller;Dewayne E. Perry
Affiliations:
Teknowledge Corp.;University of Victoria, Canada;The University of Texas at Austin
Venue:
IEEE Software
Year:
2005

Citing 2
Cited 2

No Silver Bullet Essence and Accidents of Software Engineering

Computer
Architectural mismatch or why it's hard to build systems out of existing parts

Proceedings of the 17th international conference on Software engineering

Integrating COTS Search Engines into Eclipse: Google Desktop Case Study

IWICSS '07 Proceedings of the Second International Workshop on Incorporating COTS Software into Software Systems: Tools and Techniques
A roadmap to domain specific programming languages for environmental modeling: key requirements and concepts

Proceedings of the 2013 ACM workshop on Domain-specific modeling

Quantified Score

Hi-index	0.00

Visualization

Abstract

Building and evolving software systems is an arduous, costly, lengthy, and complex task. The resulting systems are similarly complex. We're thus constantly searching for ways to reduce such costs, time, and complexity while increasing system functionality and quality. One strategy that originally seemed promising was the notion of "buy not build." Using COTS products is one way to implement this strategy, because software development then becomes the process of "simply" integrating COTS components. However, it turns out that dealing with COTS is a high-risk activity for a variety of reasons.