Frequently Asked Questions About LabVIEW Development
Print
|
Visit the Frequently Asked Questions About Large LabVIEW Development
|
Is LabVIEW a compiled programming language? Yes. LabVIEW has a sophisticated compiler that is always running as you develop your application. When the compiler finds a syntactical error the run arrow is broken to indicate that the application cannot run. Continuous investment in the LabVIEW compiler has enabled optimized application performance and, amongst other things, the ability to take full advantage of multicore technologies. |
|
|
|
How do I make use of external libraries in LabVIEW? LabVIEW can communicate with any application or development environment that provides standard interfaces. Similarly, LabVIEW applications provide standard interfaces for re-using VIs in other development environments. |
|
|
|
Can LabVIEW be integrated into existing software engineering practices? Yes. An increasing number of large, mission-critical LabVIEW applications have been developed in LabVIEW in accordance with software development standards set by regulatory agencies such as the DOD and FDA. The same practices that are applied to text based development can be applied to graphical code with the proper understanding of tools and practices. |
|
|
|
Do LabVIEW VIs work with source code control providers? Yes. LabVIEW allows you to connect to source code control providers from within the development environment, thereby enabling developers to communicate with generic source code control functionality without leaving LabVIEW. |
|
|
|
How do I track the history of revisions to my LabVIEW application? Integration with source code control provides automatic tracking of iterative development for LabVIEW VIs. Use the built-in VI History window to synchronize to any version stored in source code control and view comments entered by a user at the time it was edited. You can also use the built-in comparison tool to see a side-by-side view of VIs in order to determine what changes have been made between versions. |
|
|
|
Yes. LabVIEW 8.5 introduced graphical merge, which automates the process of combining changes made to separate VIs. You can perform this operation from within LabVIEW, or you can setup source code control applications to automatically run this routine when conflicting changes require merging. |
|
|
|
How can I determine what modifications were made to a VI? LabVIEW enables developers to perform side-by-side comparisons of code in order to compare modifications with other VIs. LabVIEW can also perform side-by-side comparisons with older versions stored in source code control. |
|
|
|
How do I validate a LabVIEW application? Certification of a LabVIEW application requires demonstration of the same development practices as with any programming language in order to ensure that any risk associated with the application has been adequately mitigated. |
|
|
|
Can I map requirements to LabVIEW code? Requirements specifications can be linked to LabVIEW code using NI Requirements Gateway. This application ensures traceability of requirements and aides in the process of impact analysis when modifications are required. This tool also provides insight into valuable metrics such as requirements coverage. |
|
|
|
How do I document graphical code? Code comments and descriptions can be provided with print-outs of code by selecting the 'VI Documentation' option in the LabVIEW print menu. For more sophisticated documentation, use NI Requirements Gateway to provide traceable links to specification documentation. |
|
|
|
How do I perform static code analysis on LabVIEW VIs? Static code analysis can be performed in LabVIEW in accordance with the NI Style Guide. The LabVIEW VI Analyzer Toolkit is also available to automate the process in order to detect improper coding techniques that may detract from an application's performance and maintainability. |
|
|
|
What assurance do I have that LabVIEW is a high-quality software product? National Instruments has operated under ISO standards since 1995. In 2004, Lloyd's Register Quality Assurance, Inc. approved National Instruments for certification to ISO 9001:2000, the latest standard for effective quality management practices. |
|
|
Related Documents
Large LabVIEW Application Development Resources
For general questions about LabVIEW, visit the LabVIEW FAQ
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).