Suggest to improve the program interface

Question

User interface

There is one rather old program, the interface of which is not happy and people are just scared when they see it. However, all the elements and data in it are required. Please suggest what can be changed in the interface for easier assimilation.
The program itself:


PS The Win2000 operating system is WinXP, so no Metro interfaces. It is better to use a more classic look.

Answer 1

Well, replace at least “Yes / No” with checkboxes - save on a click on each field. Farther. When entering this amount of data, it is better to make a form that expands to full screen. Polish your form interaction with keyboard-only input - this type of input is usually faster than keyboard/mouse switching. This is offhand.

Answer 2

Split into "pages" and give out for filling in small groups and buttons < Back | Next >. When everything is filled in, activate the Done button. Similar to installers

Answer 3

before changing the interface, it is necessary to:
1. ask the wishes of users (write down as much as possible, even contradictory ones)
2. collect statistics on the use of fields (according to the database or insert hooks in the code)
a) determine how often people click the mouse and when they use the buttons (tab or else how)
b) analyze the time between each input
c) ideally add eye movement analysis (there is already such equipment, including software for high-quality webcams)
d) associate this data with users, dividing it into classes (new / old or experienced / novice or smart / stupid or male / female, etc.) it is also necessary to somehow define a set of typical business situations in which this form is opened
based on the data in item 2, identify plugs, frequently used fields and places that users are looking for, how the intervals differ from the type of users, and much more ... in general, the better you analyze the data, the more information you will have about what needs to be done
, then see what wishes fall on the correction of identified plugs
, only then you need to think about what to change

Answer 4

Judging by the signatures, we are talking about a certain technical process and work with equipment. In this case, most likely there are several procedures or tasks that the technician must perform and mark them in the database.
Hence the possible options:
1. Divide the accounting object into several components, namely, by tasks. For example, the results of the assembly of the device are entered on one tab, the results of disassembly - on the other, checking those. indicators - on the third. The idea is that the user can immediately see what exactly he needs to fill in at a given time. In principle, he will not even need to switch anywhere - it is enough to prepare several forms for specific tasks in advance, and the user will simply choose what he wants to do now. For example, a separate button of the form "Add weekly maintenance results" or "Put object for major repairs."
2. The second option, a workaround, if it is impossible to break the form structure into tasks - make several states of the object and, depending on them, visually highlight those blocks of data that the user must work with at the current time. Something like mandatory fields.

Answer 5

Beginners are afraid of it, because:
1. there are numbers (“770. Purity and ret. condens.”, “1. Clean”, “1. Yes”) - they spoil the view and eat up the place;
2. it is not clear what to enter (“Note: No comments”, “Oven No. 0” are clearly entered due to restrictions);
3. it is not obvious how the +/− buttons work;
4. There is a color coding that doesn't mean anything (or does it?).
Experienced users are afraid of it, because when you need to quickly find a field, there is no search at hand.

Answer 6

Can use accordion projects.developer.nokia.com/QMLTemplates/wiki/WikiStart#accordionlist