Inquiry - What is your Modularity Index?

[Graziano]

Hi Phillip,
  many thanks, but I get message that "Strip Path Extension__ogtk.vi" is missing, I'd fix it downloading openG tolkit (as mentioned above your post)?

  Thanks a lot!

graziano

[Wiebe@CARYA]

Ok. I devided the recurcive number of vi's by the vi's own number of nodes.
That seems unfair!

With the total number of nodes:

338/12221 *100 = 2.8

That seems more like it! Half the code is not mine, so now we have to
calculate who's vi is dragging down the avarage!

Regards,

Wiebe.

[Ben]

Well this question has pointed out something I had not stoped to think about.

I have not written a complte application myslef on about 4.5 years!

The modularity index I got on that app was just a hair under 3.

The applications were I have lead development average about 2.

If I were to take the recomendation that all of my apps should run about 4 then that means my average app should really consist of 800 and my biggy should have about 2000 VI's.

I also took a look at one of the abominations I have been contratcted to maintain (I did not develop!) at it scored about 1.

I have observed another way of evaluating the modularity and structure of an application that does not require any code analysis tools.

When you look at an applications hierachy (with no VI.llb showing) a well structured app will have an aspect ratio of about 3:4 when you view all of the VI's including typedef'd controls.

Applications that include a large dynamic content will be wider.

On top of that all of the icons can be seen and the VI help content can be viewed as well.

So for me the hierachy screen tells me a lot more than a modularity index.

Ben

[jrpe]

So when I first did this, I missed the part of the formula that multiplied by 100, so I got 0.0427 and was so ashamed of my index that I resolved to re-read the labview style guide! Instead I re-read the formula and magically improved my index to 4.27!

[Graziano]

Hi Ben!
   I cannot hide: I was waiting your opinion!

   I think that MI and Hierarchy are two different tools.  The tell you different aspects.  For example, if you build a top vi, with (below in hierarchy), 1000 VI, you can have a similar MI than if you struct code with a better nesting technique.  Si, in this case, MI tells few.  While, of course, if you have a MI of 1, probably your application is not maintainable!!

   About Hierarcy, I confess that I'm using it more and more, and 3:4 rule is quite interesting, even if I think that a good Hierarchy should resemble a diamond (or rhomb-like).

   Anyway,at this point it will be interesting to take a look at one of your Hierarchy... can you post even a reduced version?

   Have a nice day!

graziano

[parthabe]

A paltry 0.63. But inherited project, NOT self-developed.

[Ben]

Graziano wrote;

"Anyway,at this point it will be interesting to take a look at one of your Hierarchy... can you post even a reduced version?"

Here is a reduced verions of that LV 6.1 app.

This shows the structure of two of the 6 plug-ins that were used in that app.

I hope this helps,

Ben

Message Edited by Ben on 10-12-2007 08:19 AM

[Ben]

FYI

The design of that app can be found here !

Ben

[Wiebe@CARYA]

Ben,

This is way off topic, but at the moment I'm working on a Quizix pump
driver.

The problem is the don't give the direct protocol, and I need the control to
be done on a Fieldpoint controller. Our solution for now is to put a
seperate fanless pc next to it, and install pumpworks on it, and lett the FP
control the software over the serial port.

I see you use the DDE interface, have you ever come up with a better
solution? Or is the DDE interface working for you?

Regards,

Wiebe.

[Ben]

Re: "Quizix and DDE"

Its been running for 4.5 years and the customer has never mentioned any issues. I seem to remember resorting to a DOS command to get it started but after that, it just worked. I can't say it was a no-brainer soultion since my customer is one of those PHD's that thinks faster than he can talk. He reconfigures his lab so often that he pruchased a welder to save money on fittings. So he is not adverse to doing the config work required to move or change.

Ben