GUI Complexity

[SteveTaylor]

Hi all,

I am attempting to come up with some metrics for evaluating how complex our GUIs are.

I thought about basing it on the amount of code in the GUI file but that does not seem correct. I mean lots of it could be trivial or even 'copy-paste-change a word' which means the code is not difficult.

I thought a more accurate heuristic would involve the number of controls on the screen something like:

Complexity = 3 X (number of buttons) + 2 X (number of controls where the value is code calculated) + (number of other controls)

But I seem to have hit a mental wall now.

Can anyone offer any advice or opinions on this for me, please?

[PeejAvery]

I am not exactly sure why you would want to do such a thing. No matter...

The best way would be to get a bunch of people from all levels of technology experience. Poll them and see what they think. If you plan to count objects, you will have to take into consideration spacing and orientation as well if you want accuracy.

[SuperKoko]

3 X (number of buttons)...
I think you should not count "standard" buttons such as [OK] and [CANCEL], or you should affect them a smaller value.

You may also deem that two buttons with the same name (e.g. [OK]) on the same dialog is confusing and adds complexity.

Another thing: Disabled controls (which are enabled when the user perform some action) may add complexity.

User-drawn controls and user defined controls are always more confusing than standard controls.

[SteveTaylor]

The GUIs are being redone in a different language and the managment want a calculation for how much work is involved.

The first step was to being trying to figure a calculation for how complicated the dialogs are as they stand.

Good point on not counting Ok and Cancel. Controls which are disabled ... they may still need to be counted if they contain functionality which will need to be ported over to the new application.

[SuperKoko]

Controls which are disabled ... they may still need to be counted if they contain functionality which will need to be ported over to the new application.
My point is that they should have a higher coefficient than normal controls.

For example, a user who see that [OK] is disabled until he select some option, may find that counter-intuitive.
On the other hand, if it's activated from the start, it may mean that there's a "default action", and so, it probably means that the dialog box is simplier.

That's very empirical and not accurate. That's just an idea.

[SuperKoko]

Another thing: static controls containing help text.

It's hard to say whether this is a factor of complexity or of simplicity...

An intuitive interface should not need many static control text.
But, an interface containing too few static control text is likely to be hard to understand.

So, I don't know how these should be counted.