Independently of the graphics design, software engineers can work on business logic to assign behavior to the graphic elements. The two elements can then be imported into the tool and verified together accordingly. If at a later stage, the look and feel needs to be changed, all that needs to be done is to re-import the new graphics assets without affecting the business logic part.
Convenient host and target environment
Microsoft Windows is undoubtedly the most common OS for both work and personal use. Having a tool based on this OS allows implementing and testing user interfaces in a convenient environment.
In addition to that, the HMI tool should allow continuous and trouble free integration on target platform. There should be as few steps as possible in going from the host to the target. One way to achieve that is by having the same execution environment engine that runs the graphics application on host and target.
HMI tool needs not only UI (User Interface) data, such as graphics assets (bit map files, 2D/3D models, asset properties, etc.), but also code that defines the application behavior. The code embodies business logic and could possibly be generated by a state machine tool or hand coded.
In the latter case, the tool should allow the standard programming languages within the software community. The HMI tool should be structured in a way that UI data is strictly separated from the code portion.
The resulting advantage is the ease of changing the look and feel of graphics without touching the code or the need to rebuild it. The old UI data in the tool output is simply replaced with the new one without rebuilding the entire application.
It's also desirable that the tool is capable of