| Deailed Lessons Learned Data |
| Type |
Hypothesis |
| Lesson Learned Statement |
Time-driven programs present different issues than requirements-driven ones. |
| Issue/Risk factor |
A sense of urgency will sometimes lead to hasty choices of COTS components without considering all relevant factors |
| Impact on cost |
high |
| Impact on quality |
unknown |
| Impact on schedule |
high |
| Type of data |
qualitative |
| Recommended action |
Do not rush evaluation and selection or, if it is necessary to rush it, be prepared for problems due to bad functional fit to arise later |
| Comments/Story |
see text |
| Life-cycle Phase |
COTS evaluation and selection |
| Recommended audience |
Project manager |
| Aspect |
Managerial |
| Object |
Process |
| Type of system |
diverse |
| Type of company |
defense |
| Number of COTS per project |
few 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/Programmatics.doc |
|
|