Summary of SSD4

Take the SSD4 exam immediately. Here, I will summarize it for your review.

There are four parts in the course list. We only focus on three of them.

1. Introduction to user-oriented design

Basics of user-oriented programming and testing:

Iterative Design, basic iterative design viewpoint, basic cognitive psychology

Tool used to construct the interface:

VB programming environment, written in VB, debugging code

Evaluation interface availability method:

Basic HE and TA views, how to compile UAR

2. Use VB to construct the interface

LABEL, BUTTON, CHECKBOX, RADIOBUTTON, LISTBOX, COMBOBOX, updown and scrollbar, TEXTBOX, GROUPBOX, tabbed page, menu controls;

3. THINK-ALOUD availability test

Vbprogramming is not described much. It is the specific attributes and usage of some controls. You will understand it after checking MSDN.

Heuristic Evaluation Method

1.
Heuristic evaluation(HE) is a tool for analyzing user interface availability in the early stages of development. Now he has developed into a discipline. (HE'sHeuristics, Or usability principles) UnderstandingHeuristics concept. HeuristicsIt has evolved from the experience of user interface design and evaluation over the past 30 years. Although we can understand it from the perspective of cognitive psychology, it does not originate from cognitive psychology. This section briefly describes these principles.

2.
Overview of Procedure for Using Heuristics, the execution process of heuristic evaluation methods is the use of several peopleHeuristics
To check the user interface design (the design can make the design, sketch, prototype, and final result at any stage of the design are both designed, the earlier the stage is usedHeuristicsAssessment, the smaller the loss. Generally, the more complex the interface is, the more people need to be evaluated.

3.
HeuristicsThe most useful thing is to use its concept during design, from early prevention.

Principles of Heuristic Evaluation

1.
Visibility of System Status "Visibility of the state of the computer, what the computer is doing, computer input, how the computer is processed", sound, images, and other methods to remind users.

2.
Match Between System and the Real World ." The practice of the real world, the way users complete tasks, the environment and the use of general rules"
These uses use the user long-term memory so that they can quickly familiarize themselves with the system.

3.
User Control and Freedom users must have sufficient "autonomy" to promptly recover errors and perform other processing.

4.
Consistency and Standards: the same information should be expressed in the same way, and different information should be expressed in different ways.

5.
Error Prevention, the most typical Error Prevention is "Use the optional action list instead of the user input operation command", this Error is particularly prone.

6.
Recognition Rather Than Recall: for issues such as page switching, users should be provided with as comprehensive information as possible for users to choose, Rather Than expecting users to remember some information.

7.
Flexibility and Efficiency of Use: for advanced users, quick and healthy settings and specific interface settings are necessary to accelerate human-computer interaction.

8.
Aesthetics and Minimalist Design

9.
Help Users Recognize, Diagnose, and Recover from Errors. When an error occurs, you should accurately inform the user of the error and how to Recover the error.

10.
Help and Documentation, users can understand how to use a function.

Keep these principles in mind and use them to test your design.

Basic Think-Aloud availability test plan

1. think-aloud usability testing (allows the right user to use your interface prototype in any way, to say that there is a problem there, you listen quietly or use a videotape, record these problems, and then solve them. Prototype usually refers to the establishment of a dynamic interface prototype, rather than the prototype on the paper) is developed through practical experience, it is the most effective method for user interface evaluation.

2. HE is the preventive measure used by the designer during design. However, after all, the designer is a designer and cannot fully stand in the user's perspective. Therefore, it must be used with THINK-ALOUD.

3. The psychological principle of this method is that the user speaks contents of their working memory as they work on a task. Working
Memory contains the Linguistic Cognition part, which is easily aloud. Non-verbal users generally do not go to aloud. In any case, the results obtained through this method can greatly benefit the designers.

How to Write a Usability Aspect Report (UAR) Availability evaluation Report

After you evaluate a user interface, record where it needs to be changed and retained. This type of report is called an availability report. The most important thing about an Availability Report is to pay attention to its readability.

The availability report consists of the following red topics.

1.
UAR Identifier: it must be a unique Identifier (it can be named by the Identifier, or it can be named by the identification type. For example: HE6 or TA89, CS1
Or2JK75), followed by Problem or Good Feature.

2.
Succinct Description of the Usability Aspect: UAR name. This name should be brief but should reflect the problem (not a solution-because the problem can be solved in a centralized manner) it is also partitioned. (EG:
Press-Me label too small)

3.
Evict for the Aspect: Examples of users who can understand the meaning of the report. For an HE report, this can be a screen and the heuristic principles HE violates or abides. A copy of think-aloud
Study: What is displayed on the screen, what is done by the user, what is reported on the screen, and how the user evaluates it.

4.
Explanation of the Aspect: the cause of the problem. Remember to analyze it, not evaluate it, for TA, it indicates why a phenomenon occurs ). (
System was in editing mode, but the user thought it was in run mode because there isn't a noticeable difference between the modes on the screen)

5.
Severity of the Problem or Benefit of the Good Feature: solves the Problem or retains the meaning of a certain aspect (these features are frequently used by users, will these features affect the use of new users)

6.
Possible Solutions and Potential Trade-offs: if this aspect is a problem, this one is used to solve the problem, and try to solve it as soon as the problem is raised. Another one should list potential design
Trade-offs.

(For instance, the problem might be that there are no keyboard shortcuts for items on a menu in a mail system and you propose CTRL-S for SEND. A design
Trade-off you shoshould record is that CTRL-S might already be used for another menu item (e.g., SAVE), so all too cut keys need to be examined before any design changes are made .)

7.
Relationship to Other Usability Aspects: each aspect in the user interface is associated. This part is used to indicate the Relationship between the user interface and Other parts.
Point. For example, if #1 and #30 are associated, it must be mentioned in the files of both parties.

IMPORTANT: Always Step Back and Try to See the Bigger Picture!
Records a very important part of user availability evaluation. Stepping back and looking for patterns in the usability problems.

Every time you complete an Availability Report, you should look back and see if there are some UAR associated with this. A single UAR does not see any problems. Generally, many useful ideas will be found together.

Address http://hi.baidu.com/%D0%D0%D7%DF%D4%DA%BF%D5%D6%D0/blog/item/4c0670226ba760f4d6cae262.html