Ah, the coding phase. Now that you have finished slaving over all those requirements, designs, prototypes, and standards documents, you may begin this most enjoyable phase of LabVIEW development. Good code is written by someone who has been trained in the language, has practical experience, understands the elements of good style, and cares about writing a high-quality product. With these personal traits and the appropriate software engineering tools, you can?t miss.
LabVIEW Style Guides
All projects, and especially large multideveloper projects, will benefit from a standardized LabVIEW style guide. Whether you use one of the existing documents or create your own custom version, each developer on your team should review the style guide before coding begins. If your company has special requirements and practices, they should be added to the document. Such reference documents are required in ISO 9000-under Implementation.
The classic style guide, LabVIEW with Style, is included on the CD-ROM as an editable document for your convenience. This style guide contains recommended practices for LabVIEW development and addresses areas such as front panel design, elements of good data flow programming, program design, and debugging techniques. A detailed checklist for front panels, diagrams, and other VI attributes is readily incorporated into any QA plan. Feel free to modify the style guide to suit your purposes.
A condensed version of the classic style guide appears in the manual for the Professional G Developers Toolkit. Another style guide, entitled LabVIEW Application Programming and Style Guide Standards for...
Copyright The McGraw-Hill Companies, Inc. 1998 under license agreement with Books24x7