A Software Engineering Approach to LabVIEW , by working programmers Jon Conway and Steve Watts, applies for the first time the techniques and principles of software design to LabVIEW programming. The LCOD technique designs flexibility into applications, making them more robust and much more easily adaptable to changes, even in large, industrial applications. Complete with examples and working code.
I love "A Software Engineering Approach to LabVIEW". It is a book intended for the intermediate to advanced LabVIEW programmer. It is a crash course on Software Design using LabVIEW as the tool. It introduces the concept of LabVIEW Component Oriented Design (LCOD) making the development of large applications manageable. LCOD is programming based on Action Engines ( a.k.a. functional global variables), but do not be discouraged by this, because the principles still apply to LVOOP and the ideas of planning/designing your application before laying the first wire still applies. It also has useful information on how to gather requirements, prototype and design the user interface.
The first copies of the book were excellent quality. However, some of them are not so good, making the images non-readable (have we mentioned that LabVIEW is a "graphical programming language"! ). The information is still great and you can follow up on updates that Steve Watts maintains through his blog "Random Ramblings on LabVIEW Design" available via National Instruments website.
This book was invaluable when I started doing LabVIEW consulting on my own. Unfortunately given that Prentice-Hall decided to move it to "on-demand" printing (hence you may end up getting a poor quality printout), I don't think the authors would be encouraged to write any updates anytime soon.
It would be 4 stars if it were not so out of date.
A decent look at LabVIEW, primarily the older design method of "component oriented design." COD shares several properties with object-oriented design (OOP), so it's not _that_ old. So much has changed that the more advanced methods to do things are out of date - but the design patterns are still very much in use.
Also, they do hit upon code management and style guidelines by the end - ideas which probably never go out of style.