Tips and Strategies for Systems Integrators | channel talk
Products that offer integration at the factory
n a perfect world, there are no uncer- process to go smoothly. However, it is im- likely to be under the user’s platform.
tainties. We completely understand portant to understand the validation goal This is where the level of uncertainty
and account for all variability. at this level is gearing towards functional rises dramatically. For example, let us as-
Our real life experiences and expecta- compatibility between the hardware and sume the supplier’s portfolio of platform
tions are different. Integrating systems, software. products include a small catalog of 10
even those designed to work together, An effective way to improve proper products that can be integrated togeth-
can pose some unique challenges during meshing is to rely on a standard hardware er. Simple permutation tells us these 10
the installation process. speciﬁcation for device pin-out and trig- products can go together in over 3 mil-
To understand some of the systemic gers and a common software speciﬁcation lion ways. It is physically impossible to test
issues related to integration, we need to for the driver. An example of an industry out every single combination of hardware
look at the structure of the various com- standard that deﬁnes both a hardware and software from a typical catalog of
ponents that integrate into a system. and software speciﬁcation is the PXI stan- products.
Consider the interconnectivity between dards (www.pxisa.org). So the Validation and Veriﬁcation (V&V)
the hardware components and a user ap- process involves educated estimates on
plication in a “typical system.” It is clear the most likely causes of failures and
that if different vendors supply various Hardware design
requirement tests for these scenarios. The V&V test-
components of the system, there is a ing validates interoperability under these
potential failure point at each interface. Prototype
scenarios using the versions of hardware
Integrators can minimize this effect three board
and software tested.
ways: However, by the time the product in-
1. Industry standards for bus architecture Manufacturing tegrates into a customer system, other
2. Industry standards for hardware design combinations may come out, or the ver-
and software interoperability sions of tested combinations may have
3. System level integration changed.
The V&V testing is unlikely to be the
catch all incompatibilities. It is primarily a