Dears,, I want full answers to these questions please: Q2: Give examples of ways

Question

Dears,,

I want full answers to these questions please:

Q2:

Give examples of ways that coordinated windows can help users multitask.

Q3:

Describe how rolecentered design might improve a user’s efficiency.

Q4:

Describe the characteristics of a wellwritten error message.

Q5:

Explain the disadvantages associated with anthropomorphic design. Describe the guidelines for avoiding anthropomorphism.

Q6:

What are the guidelines for creating usable abbreviations for a command set?

Describe color choices that enhance user satisfaction            and performance when designing an            interface. What color pitfalls should be avoided?

Explanation / Answer

2. Coordinated windows are windows that appear, change contents, and close as a direct result of user actions in the task domain.
example: Medical insurance claims-processing application, when the agent retrieves information about a client, such as the client’s address, telephone number, and membership number should be automatically filled in on the display. Simultaneously, and with no additional commands, the client’s medical history might appear in a second
window, and the record of previous claims might appear in a third window. A fourth window might contain a form for the agent to complete to indicate payment or exceptions. Scrolling the medical-history window might produce a synchronized scroll of the previous-claims window to show related information. When the claim is completed, all window contents should be saved and all the windows should be closed with one action.

3. Users get information and interface choices tailored the tasks they need to perform for a specific role. This could improve performance and reduce distraction while the user is working in a given role and could facilitate shifting of attention from one role to another.
The personal role manager could simplify and accelerate the performance of common coordination tasks, in the same way that graphical user interfaces simplify file-management tasks.

4.
   Be as specific and precise as possible.
   Be constructive. Indicate what the user needs to do.
   Use a positive tone. Avoid condemnation. Be courteous.
   Choose user-centered phrasing.
   State the problem, cause, and solution.
   Consider multiple levels of messages.
   State brief, sufficient information to assist with the corrective action.  
   Maintain consistent grammatical forms, terminology, and abbreviations.
   Maintain consistent visual format and placement.

5. Attributions of intelligence, autonomy, free will, or knowledge to computers are appealing to some people, but to others such characterizations may be seen as deceptive, confusing, and misleading. The suggestion that computers can think, know, or understand may give users an erroneous model of how computers work and what the machines’ capacities are. Ultimately, the deception becomes apparent, and users may feel poorly treated.
Guidelines to avoid:
   Be cautious in presenting computers as people, either with synthesized or cartoon characters.
   Design comprehensible, predictable, and user-controlled interfaces.
   Use appropriate humans for audio or video introductions or guides.
   Use cartoon characters in games or children’s software, but avoid them elsewhere.
   Provide user-centered overviews for orientation and closure.
   Do not use “I” when the computer responds to human actions. Use “you” to guide users, or just state facts.

6.
   Use color conservatively. limit the numer of colors.
   Ensure that color-coding supports the task. Be aware that using color as a coding technique can inhibit performance of tasks that go against the grain of the coding scheme.
   Place color-coding under user control.
   Design for monochrome first.
   Consider the needs of color-deficient users.
   Use color to help in formatting such as similar colors can be used to group related items. Use the same color-coding rules throughout the system.
   Be alert to common expectations about color codes.
   Be alert to problems with color pairings (red/blue, yellow/purple, magenta/green) and lack of contrast (brown on black, yellow on white),
   Use color changes to indicate status changes.
   Use color in graphic displays for greater information density.

Pitfalls to be avoided
   Color pairings may cause problems.
   Color fidelity may degrade on other hardware.
   Printing or conversion to other media may be a problem.
   Users with color vision problems might miss key information or might not be able to user the interface at all.

Related Questions

Navigate

• Browse (All)
• Browse D
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.