Current Options
1. Avoid COTS altogether. Write your own
2. Depend on: (1) laws to sue COTS publishers, and/or (2) insurance policies for protection if your business suffers after acquired software fails
3. Ask for independent, (3rd) party product certification (as opposed to personnel accreditation or process certification)
4. Perform system-level testing with the COTS software embedded
5. Determine the robustness of your system if the COTS functionality were to fail
- a. Demand warranties from the COTS publisher that certain failure modes are not possible
- b. Build your own wrappers