[bobnews]

A major Army intelligence system has a problem since the system is too complex for the operators that need to work on the system. There is a continuous problem whenever they have to train new operators.

The problem is that the User Interface is still based upon the features and ideas of the 1980’s. The ideas of the 1980’s were based upon simple programs that performed minimal functions and not complex systems that would perform numerous functions.

When is the government going to stop following the ideas of private corporation and recognize that government computer systems are far more complex than computer systems of private corporations.

The computer systems of corporations can get along with the ideas of the 1980’s, but the computer systems of corporations of government are complex and can not get along with the ideas of the 1980’s. Corporations do not have operators that have to work on complex computer systems that protect the United States.

Currently the only concern of Microsoft, Apple, and organizations like Java is to add new features that will make their GUI’s prettier. There is no thought about adding features that would aid in developing a User Interface that would aid individuals that need to deal with a complex computer system.

Topic

[jreade]

What features of a UI would make that UI easier to work with a complex system versus a simple system? Can you give some examples or point to some resources that would explain features that could be added or removed to make a UI more user-friendly when working with a complex system?

[bobnews]

What features of a UI would make that UI easier to work with a complex system versus a simple system?

The GUI widget menu would have a scroll bar. This would allow menus to have more choices without creating the problem that a menu is too large. The scroll bar would have a height limit that would indicate how many lines should be displayed.

Cascade menus would have features to indicate whether the menu for the cascade is to appear above, below, or centered in regard to the the position of the cascade. This would make it better for users when they have to work with menu buttons or short cut popups.

The idea that buttons that activate a button has to only go on the first line of a window will be abandoned, and buttons that activate menus would appear not only on the first line. This allows for more buttons with menus. I do not use menu buttons. Instead I create a button that will activate a menu.

Users would have choices on the font used for the program button. This is important for readability and the fact that operators might be working on different screen sizes.

Users will also have choices on the back ground colors. The color white creates glare. Operators need better readability and not glare.

Icons will not be used since they do size to changes in the font. Operators are under pressure and should not have to remember what a icon stands for. Text should be used on buttons.

The windows will be designed to hold as many single action buttons as possible since these are the most useful for someone who is performing work on a computer system.

The other idea I have and use for removing complexity are proprietary at this point.

[bobnews]

What features of a UI would make that UI easier to work with a complex system versus a simple system?
Part 2

A better method for operators obtaining help information regarding the computer system. Proprietary

Multiple tasks windows with easy navigation to the main window, and all other tasks windows. This means that all the functions of the system do not have to be jammed into one computer window, and also allows for better organization of the functions.

Be ready to understand that the ideas of the 1980’s are out of date and that it is necessary to start to think about new ideas in creating a computer product.

Imagine if automobiles today were still totally built on the 1980’s. I am always amazed how it is not recognized that new computer programs are still created totally on the ideas of the 1980’s, and that this is serious problem since it means no advancement in software development.

[odeon2000]

I found this post so interesting, I had to reply. The problem statement: “A major Army intelligence system … is too complex for the operators that need to work on the system.” was correct, but follow-on discussions (even in the root of the thread) is illogical. “Why?” you may ask? Well, as a practitioner of Software Engineering, the correct solution is found after the root cause is understood. Here we have a bunch of folks, albeit with good intention, stabbing at solutions. Let follow the problem statement with the following relevant facts: 1) the system was “quickly” developed such that the applications were not tightly coupled, 2) the infrastructure is not tightly coupled, 3) most of applications (>70%) are Commercially available! WRT “features of a UI….?” it turns out that these are all subjective, and the best we can do as purchasers is to ask a set of standard question of the vendors. Those questions are kinda analogous to what BOB is saying. That is not as important as suggesting that root cause analysis should be a common practice to members of a Software Engineering group. (I say this, this way since I don’t know what a constitutes a “Software Intensive” system. ) For example, my simple formal root cause analysis does not reveal that making college loans easier, is a viable solution to the problem of extremely high cost of college tuition, maybe the 3- 24 million $ salary of major college football coaches have to change? ETC……

[bobnews]

“Well, as a practitioner of Software Engineering, the correct solution is found after the root cause is understood.”
…………………………………………………
The root cause of the problem is that the User Interface is still based upon the features and ideas of the 1980’s.

No sense in trying to figure out what is the root cause of shoddy work when a carpenter is using a rock instead of a hammer. Software developers are using UI ideas that are out of date and are like using a rock instead of using a hammer. This is why users have so many problems in working with computer programs.

[bobnews]

(I say this, this way since I don’t know what a constitutes a “Software Intensive” system. )
…………………………………………….
FBCB2 Post Production Software Support
Solicitation Number: SSESNG-16-R-2060

Take a look at the above solicitation for FBCB2 and you will have an idea of “what a constitutes a “Software Intensive” system”.

[Author]

Replies