Human Machine Interface

Why do great products often have a weak HMI? Can I change HMI without a full platform migration? Will HMI requirements change faster than other feature requirements and therefore dictate special architectural approaches. These are some of the questions asked when dealing with HMI development.

HMI as a Separate Layer

After years of experience in embedded devices design and implementations we see the HMI as a separate layer within the target device which requires special design and development skills. The approach to HMI is a combination of graphical design and great software implementation of the design.

Advantages of using HERMES SoftLab's HMI building block

• Platform Independent
• Fast Adoption to Requirements Change
• GUI Expertise
• High HMI Reusability
• Style Change Support
• Usability Awareness
• One Approach, Many Targets
• Low Resources Consumption

     Figure 1: HERMES SoftLab’s Process of Creation of HMI Component

HERMES SoftLab offers HMI software development and testing services for both embedded and non-embedded devices. Our strategy is usually to decouple HMI from the application logics. Advantages with that approach are:

• Allows application improvement while keeping the same HMI and reusing HMI across all products from the same product family
• A common technique in IT paradigms
• It often attempted in embedded architectures, but often the results are less effective.
• HERMES SoftLab has experience with both and understands the common traps and trade-offs with various embedded approaches.
• We are able to quickly recognize how your architecture approaches HMI and code in a style compatible with this approach.