| Deailed Lessons Learned Data |
| Type |
Good practice |
| Lesson Learned Statement |
Choosing an appropriate vendor is important to success. |
| Issue/Risk factor |
Not taking vendor characteristics into account (in addition to product characteristics) could result in vendor relationship problems later. |
| Impact on cost |
unknown |
| Impact on quality |
unknown |
| Impact on schedule |
unknown |
| Type of data |
qualitative |
| Recommended action |
Consider the characteristics of the vendor as part of the acquisition. COTS software should be obtained from vendors who view the software as one of their products. |
| Comments/Story |
see text |
| Life-cycle Phase |
Acquisition |
| Recommended audience |
Project manager |
| Aspect |
Business |
| Object |
Vendor |
| Type of system |
transportation |
| Type of company |
diverse |
| Number of COTS per project |
one to many |
| Type of COTS |
diverse |
| Date Created |
7/2/2003 |
| Date added |
12/10/2003 |
| Name |
Tricia Oberndorf |
| Organization |
SEI |
| e-mail |
po@sei.cmu.edu |
| Reference |
"COTS-Based Systems Lessons Learned Web Pages" (http://www.sei.cmu.edu/cbs/lessons/) |
| Link |
docs/Procurement.doc |
|
|