1 / 12

Definition of a COTS Integration Process

Definition of a COTS Integration Process. Steve Nelson Raytheon Presented to ASEE 5 March, 2002. Agenda. Introduction Why COTS? COTS Advantages The Problems SEI Lessons Learned The Solutions The Process Summary. API. DII COE. GOTS. COTS. CORBA. MOTS. NDI. OTS. COTS-Solution

waneta
Download Presentation

Definition of a COTS Integration Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Definition of a COTS Integration Process Steve Nelson Raytheon Presented to ASEE 5 March, 2002

  2. Agenda • Introduction • Why COTS? • COTS Advantages • The Problems • SEI Lessons Learned • The Solutions • The Process • Summary

  3. API DII COE GOTS COTS CORBA MOTS NDI OTS

  4. COTS-Solution Single vendor Pre-Integrated e.g. Payroll ‘Turn Key’ COTS-Integration Usually different vendors Multiple Components ‘Glue Code’ COTS-Based Systems

  5. Why COTS? • Single Customer Expense • Inflexible and unable to easily capitalize on technical advances • Historically – field 10-year old technology • Increased availability • ‘Silver Bullet’

  6. COTS Advantages • Reduced Costs • Availability • Shortened Schedule (no ‘development’ & test) • Reduced Risk • Improved Quality (more users ‘testing’) • Maintenance transferred to vendor updates

  7. The Problems • To gain benefits, COTS must be used ‘as is’ • Most COTS is not designed to work together • Lack of true integration experience & product expertise • Constant, asynchronous product updates • Problems Percolate • Market driven upgrades (no control) • COTS unique aspects (upgrades, licensing, etc.) • No development process • Attitudes (‘plug-n-play’, home computers)

  8. SEI Lessons Learned • COTS acquisition started after contract award • COTS source-code changed to meet customer requirements • I&T uncovered further business practice differences • COTS Schedule = Custom Development • COTS requirements & selection pre-contract award • No COTS modifications! • Requirements flexibility • Early customer and vendor involvement • Contracting officer won award!

  9. The Solutions • Vendor and customer cooperation EARLY! • COTS Evaluation/Domain Groups • Standards Gurus • Training Investment • Historical Data • COTS Product Database • COTS Procedures Database (install, config, & integration) • PROCESS

  10. See first page of ‘ProcessA0.doc’

  11. See second page of ‘ProcessA0.doc’

  12. SUMMARY • Process – early involvement, early COTS, iterative, emphasis on learning from previous • COTS Product Database • COTS Procedures Database • Support from Domain and Standards Gurus • Trained Engineers • It’s an investment in the future

More Related