| Deailed Lessons Learned Data |
| Type |
Hypothesis |
| Lesson Learned Statement |
The use of COTS products will likely require changes in the business processes for a system’s end users. |
| Issue/Risk factor |
COTS products have built-in models of use; they are created with the developer’s expectations of how they will be used. It is very likely that at least some aspects of these built-in models will not match what the current end users are accustomed to. |
| Impact on cost |
high |
| Impact on quality |
unknown |
| Impact on schedule |
high |
| Type of data |
qualitative |
| Recommended action |
Plan for business process migration |
| Comments/Story |
see text |
| Life-cycle Phase |
Throughout lifecycle |
| Recommended audience |
Project manager |
| Aspect |
Business |
| Object |
Process |
| Type of system |
resource planning |
| Type of company |
defense |
| Number of COTS per project |
several |
| 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/BusinessProcess.doc |
|
|