Lessons Learned Integrating COTS into Systems

Authors:
Thomas G. Baker
Affiliations:
-
Venue:
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
Year:
2002

Citing 0
Cited 5

The software customer/supplier relationship

Communications of the ACM - Information cities
Understanding solution architecture concerns

MPEC '05 Proceedings of the second international workshop on Models and processes for the evaluation of off-the-shelf components
Experience in using business scenarios to assess COTS components in integrated solutions

CASCON '05 Proceedings of the 2005 conference of the Centre for Advanced Studies on Collaborative research
On the evaluation of the impact of shared resources in multithreaded COTS processors in time-critical environments

ACM Transactions on Architecture and Code Optimization (TACO) - HIPEAC Papers
Modeling towards incremental early analyzability of networked avionics systems using virtual integration

ACM Transactions on Embedded Computing Systems (TECS)

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper presents lessons learned by the author over fifteen years of experience integrating COTS software into systems at The Boeing Company. One key lesson has been to distinguish development vs. customization vs. integration vs. configuration and understanding the corresponding impacts on tools, architectures, and even methodologies. Methodology impacts can destroy a project if they aren't recognized and mitigated in a timely manner. The paper walks through four COTS projects, discussing the challenges of each and how they were overcome. The COTS integration project involving a workflow engine provides an extreme example of methodology impact.