Can the CI component survive the environment? Is it reliable? Can it satisfy special performance requirements such as fault tolerance, security, real time? Is there a built-in-test?
Integration difficulties—documentation is often poor or lacking due to its proprietary nature. • Extension difficulties—extensions outside the domain for which the CI component was designed may be difficult or impossible (e.g., security). • Supportability—lack of influence over the vendor, e.g., frequent configuration changes with little or no warning. CIs could add unreasonable burden to configuration management. RISKS MITIGATION: • Ensure that only CI components are used that comply to acceptable open systems standards. Testing for conformance to specific profiles of standards aid in mitigating risk of being captured by proprietary extensions to standards by a particular vendor. • Ensure that system components can be substituted with similar components from competitive sources. • Keep the interface as constant as possible over the life of the system (or at least backward compatible).
Related Questions
- Can the CI component survive the environment? Is it reliable? Can it satisfy special performance requirements such as fault tolerance, security, real time? Is there a built-in-test?
- Are there any special environment requirements for the area where practice will happen?
- HANDLING AND ENVIRONMENT Are there any special handling requirements?
