Labview applications management 2010

Labview applications management 2010

Reference: 10 AT 005
Edited by: Adeo Turatsinze
Revision: 001
Date: October 05, 2010

1 of 3
Author: Adeo Turatsinze
Labview applications management 2010.doc
Reference: 10 AT 005
Labview applications management 2010

Introduction

Purpose
The labview application management aims to identify the applications created
and used in laboratory.

Application identity
Each application is identified by an abbreviation. It can be a set of numbers, a
set of letters or a set of numbers and letters.
The application identification contains
• The identifier = serial number
• The name = description
• The purpose = main function
• The destination = where the application is used, who is the user.
• The application archive = where the source and the exec are stored.

N. ID Name (description) Purpose Destination Archive (link)

1

See Attachment A0: Labview Software Identity.

Application Components
Each application achieves the user requirements. This section want to identify
the different components used to build the unique application. Does the
application manages the power supply, the network (CAN, LIN, LAN…), the
acquisition? Each application is located in a specific environment.
See attachment A1: Labview Software Components

Application Interfaces
Each application is interfaced with the environment. In this section we want to
focus our attention on the inputs, the outputs and the NI hardware used.
See Attachment A2I: Labview Software Input interfaces
See Attachment A2O: Labview Software Output interfaces.

2 of 3
Author: Adeo Turatsinze
Labview applications management 2010.doc
Reference: 10 AT 005
Labview applications management 2010

Application architecture
The labview application is structured basically in the main program and the
subVIs. In this section our purpose is to describe the architecture. The first
step consists to identify the main program and its subVIs. The second step we
will focus us on the subVI and their subsubVIs. At the end we will take view on
the local variables and the global variables. The goal of this effort remains to
define the application key parameters.
See Attachment A3: Labview Software Architecture
See Attachment A4: Labview Software SubVI
See Attachment A5: Labview Software Key parameters.

Application traceability
The labview application has been modified in the time. It is important to
manage the configuration and the modifications. In this section we will dress
the traceability of each application. To achieve this goal we need to build a
table of modifications.
See Attachment A6: Labview Software Traceability.

3 of 3
Author: Adeo Turatsinze
Labview applications management 2010.doc
Reference: 10 AT 005