This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
The Challenges of Using COTS Software in Component-Based Development
June 1998 (vol. 31 no. 6)
pp. 44-45
An increasing number of organizations are using software applications of larger applications. In this new role, acquired software must integrate with other software functionality. In the introduction to the cover features, the author describes why the industry is moving toward a software design paradigm in which many of the needed software functions already exist. The developer's task, then, becomes one of accurately selecting functions and integrating them into a system. The problem is that commercial, off-the- shelf (COTS) software is almost always delivered in a black box with restrictions that keep developers from looking inside. Therefore, most forms of software analysis that would help developers decide if the software is going to perform safely, securely, and reliably are not available. Developers are thus at the mercy of the software vendor in many ways. The author argues that to achieve the goal of widespread component-based engineering, the industry must overcome challenges related to safety, reliability, and security. If the industry cannot adequately address these problems, the goal may remain unmet.
Citation:
Jeffrey M. Voas, "The Challenges of Using COTS Software in Component-Based Development," Computer, vol. 31, no. 6, pp. 44-45, June 1998, doi:10.1109/MC.1998.683006
Usage of this product signifies your acceptance of the Terms of Use.