Abstract
Virtual Instrument (VI) based test program development systems, as exemplified by National Instruments' LabVIEW, provide very powerful design capture fools that allow the test program set (TPS) developer to rapidly prototype test strategies. As usual, in great power lies danger. In this case the danger is the ease of which VIs are reused. While code reuse is a desired feature, unintentional modifications to common VIs, name clashes, and library corruption are all potential headaches resulting from uncontrolled changes to VIs stored in shared libraries. Undetected Spontaneous Upgrades to library components can ruin a maintainer's day when the program loads with broken wires. Developing quality software requires software quality. This paper provides recommended practices to address the Key Practice Areas (KPAs) defined in the Software Engineering Institute's (SEI) Capability Maturity Model (CMM) in the context of TPS development in LabVIEW. Repository management procedures such as check-in check-out and change tracking and documentation are described.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
