HMI Viva QB
HMI Viva QB
Examination
1. Define HMI
Human–machine interaction (HMI) refers to the communication
and interaction between a human and a machine via a user interface.
2. What are different components of HMI
HMI Components: Hardware, Software and Operating Environments
Hardware:
Essential part of any computing device
Used to work with software and interface
Generally selected as per as user’s requirements
Software:
Tool to create an effective user interface
Based on requirements and hardware we need to choose software
Fulfill user level acceptance test and can provide modification
Operating Environments:
Friends, family members, colleagues are not representatives of target users.
User requirements should be understood by a team and not by an individual.
Goal should be to minimize user difficulties.
The hardware and the software balance should be managed properly.
3. What is human-centred design
Human-centred designing considers all the aspects of destined user, such as
interest, behaviors, needs, likes, dislikes, skills, experience, challenges, etc.
and products that will be easily operable for users.
User satisfaction is the main goal of such system design.
Creativity of the designer lies in figuring out this knowledge about user and
incorporate it to design best possible interface. Example: Locker
Conceptual model is the mental image a human has built about a system. It
defines good design as the communication between designer and user.
8. What is interaction?
Communication or direct conversion or involvement with someone or something
9. What are phases of execution-evaluation cycle
Establishing the goal
Forming the interaction
Specifying the action sequence
Executing the action
Perceiving the system state
Interpreting the system state
Evaluating the system state with respect to the goals and intentions
13. What are common mistakes performed by people while designing computer
system
Developers expect people to think like computers.
Developers ask users to perform difficult operations which may be easy for
developers, but not so much for the users.
The resultant software design will have poor behaviour as users are not taken
into consideration while designing the system.
14. What are different types of responses to poor design
Psychological
Confusion: Since the framework and complex operations couldn’t be understood
by normal users.
Annoyance/Frustration: Inconsistence in design, slow computer reaction times,
difficulties in quickly finding information and unexpected computer responses.
Panic or Stress: unexpectedly long delays times of severe or unusual pressure
may introduce panic or stress.
Boredom: Slow response time or long download time.
Physical
Abandonment of the system: The system is rejected, and other information
sources are relied upon.
Partial use of the system: only a portion of the system capabilities are used.
Indirect use of the system: the intermediary is placed between the would-be user
and computer.
Modification of the task: task is change to match the capability of system.
Misuse of the system: rules are bent to shortcut operational difficulties.
Direct programming: The system is reprogrammed by its user to specific needs.
Requirements- What is wanted: The firs step is establishing what exactly needed.
Example how do people currently watch movies? What sort of personal
applications do they currently use?
Analysis: The results of observation and interview need to be ordered in some way
to bring out key issues and communicate with later stages of design.
Design: There is a central stage when you move from what you want, to how to do
it.
Iteration and prototyping: Humans are complex and cannot expect to get designs
right first time. So, it need to evaluate a design to see how well it is working.
Implementation and deployment: Finally, when we are happy with our design, we
need to create it and deploy it. Writing documentation and manuals.
19. What is software life cycle
Requirement Specification: Designer & customer try to capture a description of
what the eventual system will be expected to provide.
It involves customer work environment, domain, final product functions.
Architectural Design: How the system provides the services expected from it.
Details Design: Those components that are not already available for immediate
integration, the designer must provide a sufficiently detailed description so that
they may be implemented in some programming language.
Coding and Unit testing: Coding component can be tested to verify that it
performs correctly, according to some test criteria that were determined in earlier
activities.
Integration and testing: Once enough components have been implemented and
individually tested, they must be integrated as described in the architectural
design. Further testing is done to ensure correct behavior and acceptable use of
any shared resource.
Maintenance: After product release, all work on the system is considered under
the category of maintenance, until such time a new version of product demands a
total redesign, or the product is phased out entirely.
31. What are different ways to order screen data and contents
32. What are different ways for information retrieval on web
Reading on web
1. Initial focus of attention
2. Page perusal: Focusing on the page’s content, some studies show that the user’s
eyes are first drawn to the page’s text, particularly headings, captions, summaries,
and notes.
Scanning guidelines:
• Organize content in a logical, systematic and obvious way.
• Highlight and emphasize important information.
• Use clear, well-located headings and subheadings.
• Use short phrases and sentences.
• Use small readable paragraphs.
• Include bulleted and numbered lists.
• Array information in tables.
B. Browsing
1. Facilitate scanning
2. Provide multiple layers of structure
• Make navigation easy.
• Freely use links
3. Respect the user’s desire to leave
• Upon returning, help the users reorient themselves
C. Searching
Problems with search facilities:
1. Not understanding the users
2. Difficulties in formulating the search
3. Many users make many mistakes
4. Overly literal search engines
5. Page titles with low search engine visibility.
6. Difficulties in presenting meaningful results