Scribd Logo
Upload

Welcome to Scribd!

  • Gestisci Il Cambiamento Con La Programmazione Orientata Agli Oggetti Di LabVIEW

    Uploaded by

    National Instruments Italy
    21 views16 pages
    This document discusses using object oriented programming in LabVIEW to manage changes. It defines object orientation as structuring software using classes instead of VIs and describes how a class groups VIs with a common responsibility. The benefits of object orientation include easier modification and addition of functionality as well as change verification. These benefits increase as the system grows. A case study example of a production test system is presented to demonstrate how object orientation localizes changes and supports adding new features through classes.

    Original Description:

    Presentazione di Jan Klasson, Endevo

    Original Title

    Gestisci il cambiamento con la programmazione orientata agli oggetti di LabVIEW

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document discusses using object oriented programming in LabVIEW to manage changes. It defines object orientation as structuring software using classes instead of VIs and describes how a class groups VIs with a common responsibility. The benefits of object orientation include easier modification and addition of functionality as well as change verification. These benefits increase as the system grows. A case study example of a production test system is presented to demonstrate how object orientation localizes changes and supports adding new features through classes.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    21 views16 pages

    Gestisci Il Cambiamento Con La Programmazione Orientata Agli Oggetti Di LabVIEW

    Uploaded by

    National Instruments Italy
    This document discusses using object oriented programming in LabVIEW to manage changes. It defines object orientation as structuring software using classes instead of VIs and describes how a class groups VIs with a common responsibility. The benefits of object orientation include easier modification and addition of functionality as well as change verification. These benefits increase as the system grows. A case study example of a production test system is presented to demonstrate how object orientation localizes changes and supports adding new features through classes.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 16

    Managing Change Using Object Oriented

    Programming in LabVIEW
    Jan Klasson
    VP Products & Training
    Endevo
    Agenda
    • LabVIEW Object Oriented Programming
    • What is it?
    • What does it look like?
    • Why bother?
    Short about Object Orientation
    • It is a way of structuring software
    • Building block: Classes instead of VIs
    • A class:
    • ”A cluster + VIs”
    • Grouping VIs with a common
    responsibility
    Code Demo – The Counter
    Class
    Why Object Orientation?
    • Easier to modify existing functionality
    • Easier to add new functionality
    • Easier to verify changes
    • The benefits increase when the system
    grows
    • Supports sharing code between
    applications
    Case Study Example
    • An automated production test system
    • Configurable to store data in
    • Ini file and
    • Data base
    • Capable of simulating Device Under
    Test (DUT)
    Design Overview - using Unified
    Modeling Language
    Change 1: Bug fix in DB access

    Affected
    VIs
    Change 2: Adding XML
    Storage

    New Child
    Class + VIs
    Change 3: Updated DUT
    Protocol

    Affected
    VIs
    Change 4: New Test Station
    Information

    Add or modify VIs


    What Happens During
    Change?
    • Most changes localized to one class
    • Easier to change
    • Easier to verify
    • Change existing feature ->
    • Modify existing VI/Class
    • Add new feature ->
    • Add new class or VI
    • The structure is robust for changes
    Generate Design from Code
    All Classes from Project are
    included
    Created Class Diagram
    Questions?
    • Learn more about OO, UML and tools:
    • Visit Endevos booth: 19

    You might also like