Create more robust, more flexible LabVIEW applications—through software design principles!

Writing LabVIEW software to perform a complex task is never easy—especially when those last-minute feature requests cause a complexity explosion in your system, forcing you to rework much of your code! Jon Conway and Steve Watts offer a better solution: LCOD-LabVIEW Component Oriented Design—which, for the first time, applies the theories and principles of software design to LabVIEW programming. The material is presented in a lighthearted, engaging manner that makes learning enjoyable, even if you're not a computer scientist.

• LCOD software engineering techniques make your software more robust and better able to handle complexity—by making it simpler! Even large, industrial-grade applications become manageable.

• Design to embrace flexibility first, making changes and bug fixes much less painful

• Pragmatic discussion of the authors' tried and tested techniques, written by—and for—working programmers

• Covers design principles; LCOD overview, implementation, and complementary techniques; engineering essentials; style issues; and more

• Complete with practical advice on requirements gathering, prototyping, user interface design, and rich with examples

• Work through an example LCOD project (all code included on companion Web site) to tie the lessons together

This book is intended for test engineers, system integrators, electronics engineers, software engineers, and other intermediate to advanced LabVIEW programmers. None of the methods discussed are complex, so users can benefit as soon as they are proficient with the syntax of LabVIEW.Go to the companion Web site located at http://author.phptr.com/watts/ for full source code and book updates.

Amazon.com® Reader Reviews (Ranked by Helpfulness)

Average Amazon.com® Rating:  Based on 11 Ratings

figures are bad, but everything is also online! - 2006-03-08
Reviewer Rating:
This book was a quick read, rather short. About half of the book goes over actual programming concepts, and the other half goes over a long design example scenario. The book is written in a fun engaging way, but in my mind the book costs a little too much for such a short read.

Coming in, I was an intermediate Labview user, and the book has opened my eyes to some better ways to program.

For those of you complaining about the quality of the figures, visit the website at authors.phptr.com/watts. Note that there is a typo in the URL on the back cover!

Great Resource for LabVIEW Programmers - 2009-06-08
Reviewer Rating:
I'm not sure what is the cause of the bad reviews over picture quality. The pictures look great in the edition I have - if there was a problem, it's fixed now. The content of the book is great and gives LabVIEW programmers (both new and old) a quality approach to engineering good code.

I would definitely get this one to add to the reference library if you are or are interested in becoming a LabVIEW programmer.

Poor Figures - 2007-01-10
Reviewer Rating:
The text content of this book is informative, succinct and useful. However the figures are all very blurry and it is almost impossible to get much out of them. This is too bad since it seems that the authors intended to convey a lot of information through the many figures. Until this is fixed, I wouldn't recommend wasting good money on the book.

Good book for design concepts - 2006-06-30
Reviewer Rating:
It is agood book to know the design concepts.Although the print is not clear but the website provides most of the Block diagrams.
Recommended reading for anyone developing and designing using LabVIEW.

great content, bad printing quality - 2006-03-16
Reviewer Rating:
The content is very helpfull for the design of professional application. The software design approach kills finally the idea that Labview is just a nice and funny toy ! This request a rigorus approach to the programming as in all the others languages and allow to produce efficient and reusable code.
Unfortunately the printing quality is very bad, the figures are unreadable and you need the source code to understand something.
It is really a pitty !

Browse Similar Topics

Top Level Categories:
Software Engineering

Sub-Categories:
Software Engineering > Requirements and Specifications