This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Integrating COTS Software: Lessons from a Large Healthcare Organization
March/April 2010 (vol. 12 no. 2)
pp. 50-58

An organization that decides to acquire and implement a COTS product instead of developing a customized solution must fully understand the characteristics of COTS integration. In addition, the project team must manage and balance both business and IT needs throughout the effort.

1. US Office of Management and Budget, OMB Circular No. A-11, June 2005; www.whitehouse.gov/omb/circulars/a11/current_year a11_toc.html, 2008.
2. US Office of Management and Budget, OMB Circular No. A-130, Feb.8, 1996; www.whitehouse.gov/omb/circulars/a130a130.html#8 .
3. Software Eng. Inst., "COTS-Based Systems Lessons Learned Web Pages," www.sei.cmu.edu/cbs/lessonsindex.htm.
4. G.A. Thomas and S. Jajodia, "Commercial-off-the-Shelf Enterprise Resource Planning Software Implementations in the Public Sector: Practical Approaches for Improving Project Success." J. Government Financial Management, vol. 53, no. 2, 2004, pp. 12–19.
5. L.C. Briand, "COTS Evaluation and Selection," Proc. Int'l Conf. Software Maintenance, IEEE CS Press, 1998, p. 222.
6. Systems Eng. Process Office, "Commercial-Off-the-Shelf (COTS) Evaluation, Selection, and Qualification Process," PR-SPE-05 V1. 0, Code 212, Space and Naval Warfare Systems Center, 17 Oct. 2002; http://sepo.spawar.navy.milCOTS_Process.doc .

Index Terms:
COTS software
Citation:
C. Todd Couts, Patrick F. Gerdes, "Integrating COTS Software: Lessons from a Large Healthcare Organization," IT Professional, vol. 12, no. 2, pp. 50-58, March-April 2010, doi:10.1109/MITP.2010.59
Usage of this product signifies your acceptance of the Terms of Use.