Abstract
The use of handy acronyms, such as COTS, can be a convenience, but it can also lead to confusion and misunderstanding. Instead of trying further to reach an absolute definition, a mechanism that lets one to characterize software products and components in a reasonably specific manner is proposed. This mechanism is easy to use, its sole constraint is a willingness to avoid applying simple labels.
| Original language | English |
|---|---|
| Pages (from-to) | 83-86 |
| Number of pages | 4 |
| Journal | IEEE Software |
| Volume | 17 |
| Issue number | 2 |
| DOIs | |
| Publication status | Published - Mar 2000 |