Gift Guide

The LabVIEW Style Book [NOOK Book]


This is the eBook version of the print title. The illustrations are in color for this eBook version. 


Drawing on the experiences of a world-class LabVIEW development organization, The LabVIEW Style Book is the definitive guide to best practices in LabVIEW development.

Leading LabVIEW development manager Peter A. Blume presents practical guidelines or “rules” for optimizing every facet of your applications: ease of use, ...

See more details below
The LabVIEW Style Book

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK 7.0
  • Samsung Galaxy Tab 4 NOOK 10.1
  • NOOK HD Tablet
  • NOOK HD+ Tablet
  • NOOK eReaders
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac

Want a NOOK? Explore Now

NOOK Book (eBook)
$50.49 price
(Save 42%)$87.99 List Price


This is the eBook version of the print title. The illustrations are in color for this eBook version. 


Drawing on the experiences of a world-class LabVIEW development organization, The LabVIEW Style Book is the definitive guide to best practices in LabVIEW development.

Leading LabVIEW development manager Peter A. Blume presents practical guidelines or “rules” for optimizing every facet of your applications: ease of use, efficiency, readability, simplicity, performance, maintainability, and robustness. Blume explains each style rule thoroughly, presenting realistic examples and illustrations. He even presents “nonconforming” examples that show what not to do—and why not.  While the illustrations in the print book are in black and white, you can download  full-color versions from the publisher web site for free.



Read More Show Less

Product Details

  • ISBN-13: 9780132797276
  • Publisher: Pearson Education
  • Publication date: 3/13/2007
  • Sold by: Barnes & Noble
  • Format: eBook
  • Edition number: 1
  • Pages: 400
  • Sales rank: 542,484
  • File size: 58 MB
  • Note: This product may take a few minutes to download.

Meet the Author

Peter Blume is the founder and president of Bloomy, 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

Readers who want to contact Blume regarding style-related suggestions, questions, or comments may do so at the following email address: . Readers interested in contracting Bloomy for a LabVIEW development project should call us directly or contact us through our website at


Read More Show Less

Read an Excerpt


The 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 identifywith 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
  • LabVIEW Basics I and II is a one-week hands-on course offered by NI Certified Training Centers. More information is available from

© Copyright Pearson Education. All rights reserved.

Read More Show Less

Table of Contents

Foreword by Darren Nattinger  xv

Preface xvii

Acknowledgments  xx

About the Author  xxii


Chapter 1          The Significance of Style  1

Chapter 2          Prepare for Good Style  21

Chapter 3          Front Panel Style  47

Chapter 4          Block Diagram  87

Chapter 5          Icon and Connector  129

Chapter 6          Data Structures  157

Chapter 7          Error Handling  203

Chapter 8          Design Patterns  239

Chapter 9          Documentation  299

Chapter 10        Code Reviews  319

Appendix A       Glossary  339

Appendix B       Style Rules Summary  349

Index  357


Read More Show Less

Customer Reviews

Average Rating 5
( 2 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 2 Customer Reviews
  • Anonymous

    Posted March 23, 2007

    many recommendations apply to any GUI design

    Labview has grown so complex and powerful that the necessity has arisen for a book like this. Inevitable, I suppose. A lot of the recommedations by Blume are applicable to any GUI designer. Like minimising the text in labels. Few users want to or will read large paragraphs or long sentences pasted into labels. These act instead to clutter up the real estate of the display, and often will confuse the new user or irritate the experienced user, who does not need such a laborious elaboration. Another tip is to avoid string controls unless really required. The problem here is that the user then has many ways to enter a badly formatted string. Perhaps it should be a decimal integer. But she sticks a letter in it. In general, you should make the input widgets as robust as possible against faulty user input. Of course, many tips are specific to Labview. Try to have data flowing mostly in one direction in a circuit diagram. And not left to right, right to left, up and down. More generally, whenever you have wires, minimise the number of bends. Makes the overall picture much clearer for a user to grasp. All of which makes this book well worth it for a Labview designer.

    1 out of 1 people found this review helpful.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted April 10, 2009

    No text was provided for this review.

Sort by: Showing all of 2 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)