A Software Engineering Approach to LabVIEW

Description

Book Description
Preface There are many ways of designing and implementing a system. We are not trying to say that you should immediately adopt the techniques presented in this book in place of how you currently design and write software. Specifically, what we are saying is that this is how we design and implement software in real-world applications. We want you, the reader, to draw your own conclusions.It’s important to note that the authors are working engineers who pay their mortgages by writing software, not by writing books. The Test Engineer’s Perspective Steve Watts writes– As a normally trained test engineer I’ve been programming test systems for years and using many different programming languages (HPBasic, UCLA Pascal, Turbo Pascal, Visual Basic, and QuickBasic). In many of the more complex systems I have had the same experience. Doing little design up front I would plow into the coding, by the 50% stage I would normally be ahead of the game, and at the 90% stage I would be 90% complete and patting myself on the back. And then it happened! I now use the term “the complexity explosion” small changes in the software would cause problems throughout the system. The customer would throw in “unplanned-for” changes. I could no longer picture the system clearly in my head. The last 10% of the project took another 90% of the time. I knew something was wrong but didn’t have the tools or training to explain what, why, or how. In the end I put it down to software being a pain. A few years ago when Jon came to the company he was touting a language called LabVIEW. This became the company standard, so I had to learn it. The first application that I wrote (in a very unpleasant style I hasten to add) was a small temperature logging effort. It became clear to me that something was still wrong. True, G gave huge productivity increases over Pascal and Visual Basic, which I was using at the time, but the complexity explosion was still there, lurking in the background. I went back to Jon and discussed it with him and he introduced me to LCOD. I had never thought that there was a discipline called Software Engineering (I thought by writing software I was a software engineer), or heard of Coupling, Cohesion, or Information Hiding. OOD, OOA, and structured software design had all passed me by. I’m the sort of person who needs to completely understand a process beyond the words, and since we were dealing with reasonably abstract concepts I struggled in the search for this comprehension. I took postgraduate courses in Software Engineering and Object Oriented Programming. I experimented with the projects I was working on, using structured software design, CASE tools, and OOA. The inherent complexity that academia applies to all things and the embracing of this complexity (out of elitism perhaps!) by the software community, led me to believe that this whole process was harder than I thought. BUT IT’S NOT! I began to see that by applying these techniques my programs were becoming manageable, they were not increasing in complexity near the end, and I could implement late changes without reducing system robustness. Maintenance was easier and faster, customers were happy and impressed, stress levels were reduced, illness and pestilence were driven from the land, neighbor loved neighbor, and there was peace in our time. Don’t get me wrong, none of this will make a complex problem any less complex, but at least by applying these techniques you won’t be making it more complex. As software engineers we should be striving for the following: Deliver what we say we are going to deliver Deliver it when we say we are going to deliver it Ensure that it operates predictably Ensure that changes and bug-fixes do not harm the stability of the program or break the bank to implement We should be in the business of managing complexity: Clever Software = BAD; Simple Software = GOOD One of our customers wrote the following testimonial (and we didn’t even pay him!): “LCOD has made a complex test system simple, flexible, and futureproof.” Using the analogy of a journey (as we do throughout the book), we feel we have taken enough steps forward to enable us to turn around and put up a few signposts. Hopefully, these signposts will help you in your journey. I have never regretted adding flexibility to my software, but I have always rued the times I have omitted flexibility. The techniques presented in this book are reasonably simple to understand. We feel that someone can only successfully apply something if they understand it. Our aim is to introduce and explore the concepts of software design using LabVIEW, and to do this in an understandable and applicable manner. A lot of techniques and methodologies get bogged down with computer science and forget about the design aspects; our intentions are to always concentrate on design and hopefully translate some of the computer science.

From the Inside Flap
Preface

There are many ways of designing and implementing a system. We are not trying to say that you should immediately adopt the techniques presented in this book in place of how you currently design and write software. Specifically, what we are saying is that this is how we design and implement software in real-world applications. We want you, the reader, to draw your own conclusions.It’s important to note that the authors are working engineers who pay their mortgages by writing software, not

http://rapidshare.de/files/20577424/phs.rar.html

password : www.xpressionsz.com

Disclaimer:
Contents of this page are indexed from the Internet. All actions are under your responsability. Email us to report illegal contents or external links and we'll remove them immediately.

Please check the description for download links if any or do a search to find alternative books.

Can't Download?
Please search mirrors if you can't find download links for "A Software Engineering Approach to LabVIEW" in "Description" and someone else may update the links. Check the comments when back to find any updates.

Search Mirrors
Maybe some mirror pages will be helpful, search this book at top of this page or click here to find more info.

1. Ebooks list page : 346
2. A Software Engineering Approach to LabVIEW
3. Software Radio: A Modern Approach to Radio Engineering (Prentice Hall Communications Engineering and Emerging Technologies Series)
4. Software Engineering: A Practitioner's Approach
5. Core C : A Software Engineering Approach
6. Software Specification and Design: An Engineering Approach
7. Software Engineering: A Practitioner’s Approach
8. Strategic Software Engineering: An Interdisciplinary Approach
9. Strategic Software Engineering: An Interdisciplinary Approach
10. Strategic Software Engineering: An Interdisciplinary Approach
11. Strategic Software Engineering: An Interdisciplinary Approach
12. Software Engineering For Students: A Programming Approach, 4th Edition
13. Software Engineering: A Practitioner's Approach, 5th edition, 2000-12
14. Core C : A Software Engineering Approach by Victor Shtern
15. Roger S. Pressman Software Engineering : A Practitioner's Approach
16. Software Verification and Validation: An Engineering and Scientific Approach