A Software Engineering Approach to LabVIEW - page 2

˜  

 
     
 
   
A Software Engineering Approach to LabVIEW
By Jon  Conway, Steve  Watts
   
Publisher : Prentice Hall PTR
Pub Date : May 05, 2003
ISBN : 0-13-009365-3 Copyright
      Virtual Instrumentation Series
      Preface
        The Test Engineer's Perspective
        Acknowledgments
      About Prentice Hall Professional Technical Reference
      Chapter 1.   Introduction
        Section 1.1.   LabVIEW Sucks
        Section 1.2.   Don't Buy This Book
        Section 1.3.   The Soap Box
        Section 1.4.   What This Book Is
      Chapter 2.   LabVIEW Rocks
        Section 2.1.   Why Does LabVIEW Rock?
        Section 2.2.   What Advantages Does This Bring to the Developer?
        Section 2.3.   How Can Good Design Leverage These Advantages?
      Chapter 3.   Software Design Principles
        Section 3.1.   Why is Software Complex?
        Section 3.2.   Coupling and Cohesion
        Section 3.3.   Information Hiding and Encapsulation
        Section 3.4.   Examples of Coupling, Cohesion, and Information Hiding
        Section 3.5.   Abstraction
      Chapter 4.   LabVIEW Component Oriented Design (LCOD)
        Section 4.1.   Components
        Section 4.2.   Design
      Chapter 5.   LCOD Implementation
        Section 5.1.   Component Mechanisms
        Section 5.2.   Message Sending
        Section 5.3.   Persistent Local Storage
        Section 5.4.   The Basic Structure of a Component
      Chapter 6.   LCOD Complementary Techniques
        Section 6.1.   State Machines
        Section 6.2.   Graphical User Interface (GUI) Design and Prototyping (UI Controller>>Message Queue Pattern)
        Section 6.3.   Abstraction in the Code, Detail Outside the Code
        Section 6.4.   Error Handling
        Section 6.5.   Pre- and Postconditions: Check What Comes In and What Goes Out
        Section 6.6.   Reuse
      Chapter 7.   Software Engineering Essentials
        Fairy Tales
        Horror Stories
        Section 7.1.   The Usual Suspects
        Section 7.2.   Requirements Document
        Section 7.3.   Quote/Project Validation
        Section 7.4.   Target Specification
        Section 7.5.   Test Plan
        Section 7.6.   Software Architecture Document
        Section 7.7.   Software Construction ”Build
        Section 7.8.   Test ”Customer Acceptance
        Section 7.9.   Pictures Tell a Thousand Words
        Section 7.10.   Checklists
        Section 7.11.   Code Reviews
        Section 7.12.   The Project Is Dead, Time for a Postmortem
        Section 7.13.   Metrics
      Chapter 8.   It's All About Style
        Section 8.1.   Why Do We Need Standards Anyway?
        Section 8.2.   Block Diagram
        Section 8.3.   Front Panel
      Chapter 9.   The Journey
        Section 9.1.   Agreeing on the Destination (Requirements)
        Section 9.2.   Planning Your Route (Design)
        Section 9.3.   Build
        Section 9.4.   Uh-oh We've Been Given the Wrong Directions
        Section 9.5.   Conclusions
      Glossary

Top