With rapidly changing test requirements and shortening tester project development cycles, it is even more critical that you and your team gain the most reuse possible from existing test software and measurement libraries. So why aren’t more test engineers reusing software more often? Here are the responses we hear most from test groups:
- There is legacy software developed by someone that is no longer in the group or in the company; and it is working, so there is significant risk and expense in changing the unknown.
- There are tool and language personal preferences or group standardization across test and validation engineering teams; therefore, it is difficult to reuse code modules because the tools or software to use for a past project don’t translate to what we are using today.
- There is a need to maximize software reuse and build abstraction layers or frameworks, but this is expensive and time-consuming. With short-term project demands, the focus on how to enable reuse standards and best practices is continuously being deferred.
The challenges of balancing longer term standardization benefits with existing code and software skills or preference is real. To help address this difficult balance, LabVIEW NXG as an open platform was designed to help you integrate all your test hardware and software systems together.
In LabVIEW NXG, you can combine multiple programming approaches alongside graphical data flow (G) in a single application. Use this flexibility to select your tool of choice for creating device under test (DUT) control, configuration, or measurement libraries. LabVIEW NXG integrates multiple languages, like C, into your application and interoperates with other software running locally or on the network to reduce your team’s time to success.