Peter Blume is the founder and president of Bloomy Controls, Inc., a National Instruments Select Integration Partner that specializes in LabVIEW-based systems development. Since LabVIEW Version 2.5, Blume and his staff of engineers have solved more than a thousand industrial applications for customers throughout the northeastern United States. To promote consistent quality among multiple developers in multiple offices, Blume established and evolved the company’s LabVIEW development practices.
Blume has written and presented multiple LabVIEW style-related presentations, including Bloomy Controls’ Professional LabVIEW Development Guidelines at NIWeek 2002 and Five Techniques for Better LabVIEW Code at NIWeek 2003. He also has published technical articles in various trade publications, including Test & Measurement World, Evaluation Engineering, Electronic Design, and Desktop Engineering.
Blume holds a Bachelor of Science degree in electrical engineering from the University of Connecticut. He is a National Instruments Certified LabVIEW Developer and Certified Professional Instructor. The company has offices in Connecticut, Massachusetts, and New Jersey. For more information, visit www.bloomy.com.
Readers who want to contact Blume regarding style-related suggestions, questions, or comments may do so at the following email address: lvstyle@bloomy.com . Readers interested in contracting Bloomy Controls for a LabVIEW development project should call us directly or contact us through our website at www.bloomy.com/quote.
PrefaceThe LabVIEW Style Book is a comprehensive reference on recommended LabVIEW development practices. It contains guidelines designed to optimize the ease-of-use, efficiency, readability, maintainability, robustness, simplicity, and performance of LabVIEW applications. The book provides thorough explanations of each guideline, including examples and illustrations. The material leverages the work of the early pioneers of the LabVIEW community1, has evolved from many years of use by Bloomy Controls2, and has been reviewed by esteemed representatives of the LabVIEW community3. I invite you to learn from the experiences of myself and the staff at Bloomy Controls, Inc., by reading The LabVIEW Style Book. I hope you enjoy reading it as much as I enjoyed writing it!
Intended Reader
Intended readers include developers, managers, and organizations that develop or use LabVIEW applications. Developers that have learned and successfully applied the fundamentals of LabVIEW can use this material to learn LabVIEW best practices. Experienced beginners can use this book to form good programming habits early in their LabVIEW careers. You must have a working knowledge of fundamental LabVIEW principles and terminology, as instructed in a LabVIEW Basics I and II hands-on course4, and experience developing and deploying applications. Intermediate developers, who have mastered the fundamentals and are ready to take their skills to the next level, will learn the most from this material. No doubt you have experienced the power and flexibility of LabVIEW and are ready to concentrate on style. Advanced developers will strongly identify with the contents, reinforce their knowledge and experience, and have a useful reference to share with colleagues. You might use The LabVIEW Style Book to help reduce the training and support burden you might have within your organization, to focus on your primary responsibilities. Managers and Organizations that employ multiple developers and users can gain maximum benefit by standardizing on these guidelines across the organization. Specifically, an organization might adopt the recommended guidelines and reference as its standard and require that all applications, whether received from internal or remote developers, consultants, or third-party systems integrators, conform to these guidelines. This approach ensures quality and consistency throughout an organization and helps satisfy industry quality standards.
Organization
The chapters of The LabVIEW Style Book present guidelines and examples organized by topic. Chapter 1, "Introduction," discusses the significance of style, including its relationship to ease of use, efficiency, readability, maintainability, robustness, simplicity, and the performance of the completed application. Chapter 2, "Prepare for Good Style," presents considerations that influence style before you begin programming, including specifications, configuration of the LabVIEW environment, and project and file organization. Additionally, it presents a specialized standard for LabVIEW project specifications. Chapter 3, "Front Panel Style," Chapter 4, "Block Diagram," and Chapter 5, "Icon and Connector," present the basics for VI layout and development. Chapter 3 provides guidelines for layout, text, color, and navigation. It distinguishes separate guidelines for the front panels of GUI VIs and subVIs, where appropriate. Chapter 4 presents guidelines for layout, wiring, and data flow, along with techniques for optimizing data flow. Chapter 5 discusses good icon development practices and editing shortcuts, and covers standard connector terminal patterns, assignments, and conventions.
Chapter 6, "Data Structures," provides guidelines on data type selection and array and cluster development. A methodology is integrated with several useful reference tables for simplifying data type selection and configuration. Guidelines and examples for optimizing VIs involving complex data structures also are presented in this chapter. Chapter 7, "Error Handling," Chapter 8, "Design Patterns," and Chapter 9, "Documentation," expand upon the basics. Chapter 7 presents comprehensive guidelines for thorough error handling, along with special considerations for error handling within subVIs. Chapter 8 discusses common VI architectures that promote good style, beginning with simple subVI design patterns and progressing to single and multiple loop design patterns. It also describes several variations of the LabVIEW state machine. Additionally, Chapter 8 presents three complex application frameworks, including a dynamic framework that uses plug-ins, a multiple-loop framework, and a modular multiple-loop framework that uses loop-subVIs. Chapter 9 provides a summary of guidelines to facilitate source code documentation. Chapter 10, "Code Reviews," presents manual and automated methods of reviewing source code and enforcing style rules. The LabVIEW VI Analyzer Toolkit, an add-on tool that integrates with the LabVIEW environment for analyzing VIs, is discussed. An analysis task is configured and an application is evaluated using the VI Analyzer.
Appendixes include a glossary, a style rules summary, and a bibliography. Appendix A, "Glossary," provides a list of terms and definitions; many LabVIEW and software industry terms are evolutionary and context sensitive. Any term that seems specialized or ambiguous is defined where it first appears within the book and used consistently in successive chapters. The definitions are repeated in the glossary for ease of reference. Appendix B, "Style Rules Summary," lists the style guidelines presented in each chapter. Finally, additional references are noted throughout the book where they apply to the material, and each is described in Appendix C, "Bibliography." These include online documents and downloadable materials, books, and resources.
- See the "Acknowledgments" section for a list of reviewers, contributors, and people who have helped advance the science of LabVIEW Style.
- Bloomy Controls is a National Instruments Select Integration Partner with offices in Windsor, Connecticut; Milford, Massachusetts; and Fort Lee, New Jersey. Information is available at http://www.bloomy.com.
- LabVIEW Basics I and II is a one-week hands-on course offered by NI Certified Training Centers. More information is available from http://sine.ni.com/nips/cds/view/p/lang/en/nid/2236.
© Copyright Pearson Education. All rights reserved.
