By Topic

Software metrics for non-textual programming languages

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Pittman, D. ; Autom. Sci. Group Inc., CACI, San Antonio, TX, USA ; Miller, J.

Most software metrics and cost model tools are based upon the Line of Source Code unit measure of software. Lines of code have no equivalent in a diagrammatic-graphical programming paradigm. Programs developed in National Instrument's “G” or LabVIEW(R) development environment are represented as a hierarchy of Virtual Instruments. A virtual instrument (VI) consists of a virtual front panel window and a programmatic diagram window. The front panel provides the program interface and the diagram provides the implementation. This paper describes several features of the front panel and the diagram that influence program storage size, execution speed, memory requirements and maintainability. The VI Hierarchy is described along with the relationship of the hierarchy width and depth to code reuse and program complexity. The VI Profiler and LabVIEW(R) add-in products such as the “Professional G Developers Tool Kit” are examined, as is an adaptation of the McCabe Cyclomatic Complexity Metric

Published in:

AUTOTESTCON, 97. 1997 IEEE Autotestcon Proceedings

Date of Conference:

22-25 Sep 1997