# A human-centred methodology applied to decision support system design and evaluation in a railway network context

Sophie Lepreux, Mourad Abed, Christophe Kolski

<figure><img src="image_1.png" /></figure>

## To cite this version:

Sophie Lepreux, Mourad Abed, Christophe Kolski. A human-centred methodology applied to decision support system design and evaluation in a railway network context. Cognition, Technology and Work, 2003, 5, pp.248-271. 10.1007/s10111-003-0128-9. hal-03279713

HAL Id: hal-03279713

https://uphf.hal.science/hal-03279713

Submitted on 21 Dec 2023

HAL is a multi-disciplinary open access archive for the deposit and dissemination of scientific research documents, whether they are published or not. The documents may come from teaching and research institutions in France or abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est destinée au dépôt et à la diffusion de documents scientifiques de niveau recherche, publiés ou non, émanant des établissements d'enseignement et de recherche français ou étrangers, des laboratoires publics ou privés.

<figure><img src="image_2.png" /></figure>

Distributed under a Creative Commons Attribution 4.0 International License
# STATE OF THE ART ON THE COGNITIVE WALKTHROUGH METHOD, ITS VARIANTS AND EVOLUTIONS

Thomas MAHATODY<fnref n="1" />,<fnref n="2" />,<fnref n="3" />, Mouldi SAGAR<fnref n="1" />,<fnref n="2" />,<fnref n="3" />, Christophe KOLSKI<fnref n="1" />,<fnref n="2" />,<fnref n="3" />

## ABSTRACT

This review paper discusses interactive system evaluation from the perspective of inspection methods, specifically the Cognitive Walkthrough (CW) method. The basic principles of CW are reviewed as proposed in the original version and the first two revisions. Then eleven significant extensions of CW are examined: Heuristic Walkthrough, The Norman Cognitive Walkthrough Method, Streamlined Cognitive Walkthrough, Cognitive Walkthrough for the Web, Groupware Walkthrough, Activity Walkthrough, Interaction Walkthrough, Cognitive Walkthrough with Users, Extended Cognitive Walkthrough, Distributed Cognitive Walkthrough and Enhanced Cognitive Walkthrough. Four summaries are proposed: the first one concerns the conceptual, methododological and technological aspects; the next two summaries deal with existing studies, first comparative and then non-comparative; and the last summary provides help for choosing a version or variant.

## CONTENTS

1. INTRODUCTION

2. EVOLUTION OF THE ORIGINAL CW VERSIONS

2.1. First version: CW1

2.2. Second version: CW2

2.3. Third version: CW3

3. VARIANTS OF THE ORIGINAL CW VERSIONS

3.1. Heuristic Walkthrough

3.2. Norman's Cognitive Walkthrough

3.3. Streamlined Cognitive Walkthrough

3.4. Cognitive Walkthrough for the Web

3.5. Groupware Walkthrough

3.6. Activity Walkthrough

3.7. Interaction Walkthrough

3.8. Cognitive Walkthrough with users

3.9. Extended Cognitive Walkthrough

3.10. Distributed Cognitive Walkthrough

3.11. Enhanced Cognitive Walkthrough

4. SUMMARIES

4.1. Summary of the conceptual, methodological and technological aspects

4.2. Summary of the comparative studies

4.3. Summary of non-comparative studies

4.4. Summary of the studies intended to help make the choice of a version or variant

5. CONCLUSIONS AND PERSPECTIVES

<footnote n="1">¹ Univ Lille Nord de France, F-59000 Lille, France</footnote>

<footnote n="2">² UVHC, LAMIH, F-59313 Valenciennes, France</footnote>

<footnote n="3">³ CNRS, UMR 8530, F-59313 Valenciennes, France</footnote>
# 1. INTRODUCTION

The development of an interactive system is an iterative process, and evaluation is an important component of this process. For this reason, over the years, evaluation has been the subject of numerous studies and much research in the scientific community concerned with Human-Machine Interaction (HCI). Today, many evaluation techniques and methods exist, and they have been reviewed and summarized to allow researchers an at-a-glance view of several methods (e.g., Dix, Finlay, Abowd and Beale (1993); Sweeney, Maguire and Shackel (1993); Grislin and Kolski (1996); Sears (2003)). Usability inspection is the generic name for a set of methods that inspect (i.e., evaluate) the usability of the user interface (Mack & Nielsen, 1994; Virzi, 1997; Cockton, Lavery & Woolrych, 2003; Bastien, 2004). According to Nielsen et Mack (1994, p. 3), "usability is a fairly broad concept that basically refers to how easy it is for users to learn a system, how efficiently they can use it once they have learned it, and how pleasant it is to use".

Cognitive Walkthrough (CW) is a usability inspection method that links the interface walkthrough to a cognitive model. The evaluator uses the interface to perform tasks that a typical interface user will need to accomplish. The actions and responses of the interface are evaluated according to the user's goals and knowledge through responses to questions related to the method's cognitive model, the differences between the user's expectations and the use reality (i.e., the steps really required by the interface). Like other common HCI evaluation methods, CW focuses on the basic principles of usability. However, unlike the other evaluation methods, CW also focuses on the cognitive activities of users, especially on their goals and knowledge when performing a specific task

CW was proposed by Lewis, Polson, Wharton and Rieman in 1990, but it has since evolved. Later versions and extensions by other authors have been proposed. The basic principle remains the same in all versions and extensions: the method simulates the cognitive behavior of the user by responding to questions related to the user's cognitive model. Based on previous papers (Mahatody, Sagar & Kolski, 2007a; 2007b), this article first describes the evolution of the CW method through its three versions: the first version proposed by Lewis, Polson, Wharton and Rieman in 1990, their second version in 1992 (Polson, Lewis, Wharton & Rieman, 1992), and finally the third version proposed two years later (Wharton, Rieman, Lewis & Polson, 1994). Then, it reviews the various significant extensions of CW, providing a summary of the concepts, methods and technology used in each: Heuristic Walkthrough (HW), The Norman Cognitive Walkthrough Method (NCW), Streamlined Cognitive Walkthrough (SCW), Cognitive Walkthrough for the Web (CWW), Groupware Walkthrough (GW), Activity Walkthrough (AW), Interaction Walkthrough (IW), Cognitive Walkthrough with Users (CWU), Extended Cognitive Walkthrough (Extended CW), Distributed Cognitive Walkthrough (DCW) and Enhanced Cognitive Walkthrough (Enhanced CW). Finally, four synthesis discussions are provided at the end of the article.

# 2. EVOLUTION OF THE ORIGINAL CW VERSIONS

## 2.1. First version: CW1

The original version of CW (Lewis, Polson, Wharton & Rieman, 1990) was designed to evaluate walk-up-and-use interfaces (i.e., interfaces that can be used with little or no training). It is based on the theory of exploratory learning CE + (Polson & Lewis, 1990). The CE + model was the first cognitive learning theory to use HCI. Design guidelines, called "Design Principles for Successful Guessing", were derived from this theory to support the design of interactive systems requiring little or even no user training. The CE + model has three main components: a learning component, a problem-solving component and an execution component. The model operates as follows: a system user chooses an action among several alternatives based on the similarity between his/her goals and expected consequence of the action; after carrying out the action selected, the user evaluates the system response using the heuristics proposed by Lewis (Lewis, 1986, 1988). In this way, users evaluate their progress towards their goals. If the goal is achieved, the learning that occurs is registered by inscribing the steps taken by the system (i.e., the evaluated response) in the rule-based representation of procedural knowledge proposed by Kieras (1985). Otherwise, the problem-solving
component is activated to discover appropriate action and so forth. The execution component consists of
triggering an applicable rule that matches the current context.

The first version of CW (called CW1 in this article) has two phases. In the preparation phase, first, the evaluator, or a group of evaluators, specifies a series of tasks to be assessed. These evaluators may be designers, users or usability inspection experts. Then, each task is broken down into action sequences. In the evaluation phase, each action is inspected by answering the questions that are generated by the simulation process of the CE+ model described above: selecting and performing the action and then evaluating the response of the system. Lewis, Polson, Wharton and Rieman (1990) noted that the method was promising but not yet satisfactory because only 50% of observed errors were identified.

## 2.2. Second version: CW2

To improve the first version of CW, a second version (called CW2 in this article) was proposed by the same authors in 1992 (Polson, Lewis, Rieman & Wharton, 1992). It is based on an extension of the model CE +. The new model of this version is related to the theory of action (Norman, 1986) and the construction-integration model (Kintsch, 1988):

- Norman's action theory holds that task execution involves seven stages: establishing a goal, formulating an intention, specifying a sequence of actions, executing those actions, perceiving and interpreting the system state and finally evaluating the system state in terms of the goal established in stage 1. CW2 also uses this cyclic cognitive mechanism.

- Kintsch's model provides a framework for building 2-phase connectionistic structures. In the first phase, called construction, all possible connections or relationships are built. During the second phase, called integration, inappropriate connections or relationships are eliminated based on the context of the field of study. In CW2, the Kintsch model is used to integrate the perceptual interface's representation of text or objects, taking the background and knowledge of the user into account.

In this second version of CW, the characteristics of the user, the context and the system use environment are all taken into account. In the new model adopted, in order to perform a task, the user must build a goal structure, which is similar to the hierarchical structure of the GOMS model (Card, Moran & Newel, 1983): the main goal is broken down into intermediate goals corresponding to the task breakdown, and the final goals correspond to actions. This goal structure incorporates the original goal by creating propositions representing the user's background knowledge, as well as the objects in the environment and the actions. An executable action is activated if there is a link between the original goal and this action. After the action is executed, each system response is interpreted, resulting in the deactivation of goals that have been reached and the construction of new propositions. These new propositions are linked to the current structure involving new actions, and so forth.

Like CW1, CW2 has two phases: preparation and evaluation. During the preparation phase, the tasks to be assessed are selected and broken down into sequences of actions and the user's goals are determined. During the evaluation phase, the evaluator uses three forms that help to guide the evaluation. These forms concern the problems that may arise and the failures that may occur while exploring the model. The first form assesses the relationship between the goals that are needed to manipulate the interface and common goals of the user, in order to determine whether or not there is an appropriate match between the two. Assuming that there is an appropriate match, the second form deals with the problems that arise when selecting the action. Taking the system response after the action has been carried out into consideration, the third form facilitates the development of user's goals.

According to its authors, this version is more complex and cumbersome to use than CW1 (Polson, Lewis, Rieman & Wharton, 1992). Indeed, the evaluator must perform extremely detailed analyses, explicitly describing the user's goals and actions, analyzing how the user chooses an action, and finally explaining how the system feedback and its interpretation by the user changes the goals.
To mitigate the complexity and awkwardness of CW2, three of the original authors, plus 3 others, proposed an automated version (AutoCW2) implemented with Apple's Hypercard (Rieman, et al., 1991). AutoCW2 allows the evaluator to complete the forms without using paper files and provides a simple editor for managing the goal structures, as well as for providing aid for each question.

## 2.3. Third version: CW

The second version of CW has been the subject of various studies and reviews (Rowley & Rhoades, 1992; Wharton, Bradford, Jeffrey & Franzke, 1992; Desurvise, Kondziela & Atwood, 1992; Cuomo & Bowen, 1992), which confirm the awkwardness of the method. Even using the automated version is still too time consuming. Two years after the second version, the same authors published a third version (called CW3 in this article) to address the criticisms (Wharton, Rieman, Lewis & Polson, 1994).

In CW3, the evaluator is invited to imagine a specific and credible scenario for each action that users must run to accomplish their task. To make the scenario credible, the evaluator must justify each action with respect to the user's background and knowledge and the feedback from the interface. To assess each action in the task, the evaluator must answer four questions related to various user thoughts and actions: 1) what is the user thinking at the beginning of the action (Q1: Will the user try to achieve the right effect?, 2) is the user able to locate the command (Q2: Will the user notice that the correct action is available?), 3) is the user able to identify the command (Q3: Will the user associate the correct action with the effect that user is trying to achieve?) and 4) is the user able to interpret the feedback (Q4: If the correct action is performed, will the user see that progress is being made toward solution of the task?).

Studies and reviews were also done concerning this third version of CW (John and Packer (1995); Sears and Hess (1999); Jacobsen and John (2000); Riihiahoo (2000); Huart, Kolski and Sagar (2004)). Most of the reviewing authors agreed that CW is tedious, despite being easy to learn and use.

# 3. VARIANTS OF THE ORIGINAL CW VERSIONS

Though still dependent on its theoretical foundations, the CW method has evolved mostly due to its practical value. This evolution has occurred to compensate for some limitations and to take into account the progress in the field of human-machine interaction (HMI) or the different HMI types (e.g., Web, multimedia) (Jeffries, Miller, Wharton & Uyeda, 1991; John & Packer, 1995; Jacobsen & John, 2000; Huart, Kolski & Sagar, 2004). In this section, eleven extensions of CW are reviewed chronologically

## 3.1. Heuristic Walkthrough (HW)

Heuristic Walkthrough (Sears, 1997) is an evaluation method that combines two inspection processes—one scenario-based and the other heuristic-based—for use as a Usability Walkthrough method (Karat, Campbell & Fiegel, 1992).

Heuristic Walkthrough (HW) thus combines the Heuristic Evaluation method (Nielsen & Molich, 1990; Nielsen, 1992) and CW3 (Wharton, Rieman, Lewis & Polson, 1994). In HW, the evaluation is done in two phases. During phase 1, the evaluator is guided by a prioritized task list and the list of questions from CW3. During phase 2, however, the evaluator is free to explore any aspect of the system, guided by the knowledge obtained in Phase 1 (i.e., from the task list and the list of questions) and a list of heuristics, such as those provided by Nielsen (Nielsen & Molich, 1990; Nielsen, 1992).

Sears used the criteria proposed by Bastien and Scapin (1995) to compare the three methods: Heuristic Evaluation, Cognitive Walkthrough 3 and Heuristic Walkthrough. These criteria are: validity (ability of the method to focus on specific and relevant aspects of the interface), thoroughness (ability of the method to assess all aspects of the interface), and reliability (ability of the method to produce same results under the same conditions). Through this comparison, Sears showed that HW can find more usability problems than CW3, while producing fewer false usability problems than the Heuristic Evaluation method.
## 3.2. Norman's Cognitive Walkthrough (NCW)

As part of the project AVANTI (AdaptiVe and Adaptable iNteractions for multimedia Telecommunication application), the Norman Cognitive Walkthrough method (NCW) addresses the particular problems raised by this project (e.g., the presence of design teams in different cities, even in different countries) and deals with interaction problems at a high level of abstraction (Rizzo, Mandrigiani & Andreadis, 1997). In fact, as the AVANTI team discovered, none of the initial 3 versions of Cognitive Walkthrough is particularly appropriate for design teams composed of people from different cultures. In addition, all three version of CW focus on low-level interactions (e.g., typing on the keyboard, clicking with the mouse).

NCW is certainly based on the Norman model (Norman, 1986), but this model was amended by Rizzo, Mandrigiani and Andreadis (1997) as shown in Figure 1. According to Hutchins, Hollan and Norman (1985), the notion of cognitive distance refers to the amount and quality of information processing needed to fill the gap between states (e.g., intention, evaluation). This notion may be applied to both action execution and outcome evaluation. In the first case, the cognitive distance refers to the amount of information processing needed to reduce the gap between the intention to act and the physical actions through which the intention was communicated to the system, or in other words, the process of translating the user's thoughts and goals into the language of the system. In the second case (outcome evaluation), cognitive distance refers to the amount of mental effort needed to translate the information displayed by the system in the terms of the conceptual model adopted by the user.

The evaluation consists of testing the user's activities by running one or more tasks within a given scenario. The evaluator explores the system, looking for the actions that help to accomplish the task. The evaluator chooses actions whose descriptions correspond with what he/she is trying to do and then interprets the system's response to assess whether or not progress has been made towards accomplishing the task or if the goal should be reconsidered. This process allows the evaluator to, first, determine whether or not the user has correctly interpreted the meaning and form of the interface and, second, whether or not the user was able to set a feasible goal and execute the correct action on the adequate subject.

At each stage of the interaction, certain questions must be answered:

* Q1: Will the feasible and correct action be made sufficiently evident to the user and do the actions match the intention as stated by the user? (Intention-Action)

* Q2: Will the user connect the correct action description with what s/he is trying to do? (Action-Form)

* Q3: Will the user receive feedback in the same place and modality as where s/he has performed her/his action? (Action Input - Feedback Output).

* Q4: Will the user interpret the system's response to the chosen action correctly (i.e., will s/he know if s/he has made a right or wrong choice?) (Outcome - Form).

* Q5: Will the user properly evaluate the results (i.e., will s/he be able to assess if s/he got closer to her/his goal?) (Form - Assessment).

* Q6: If the goal is wrong (or can be ameliorate), will the user understand that the intention s/he is trying to fulfil cannot be accomplished within the current state of the world (or will s/he find out alternative goals?) (Action/Outcome - Concern)" (Rizzo, Mandrigiani & Andreadis, 1997)

If the answer is not completely affirmative, the evaluator communicates the problems to design team members, with specific alternatives. This method allows the team members in different locations to communicate without ambiguity.
<figure><img src="image_3.png" /><figcaption>Figure 1. The modified Norman model (adapted from (Rizzo, Mandrigiani and Andreadis (1997))</figcaption></figure>

## 3.3. Streamlined Cognitive Walkthrough

Spencer (2000) found that CW3 did not produce consistently good results, and for this reason, development teams may judge it to be inappropriate. In addition, in his opinion, CW3 was difficult to apply in large software development companies due to several constraints.

* Clearly, time is a major constraint for designers, who are often under pressure to complete their tasks on time. Any activity that is not immediately useful or that requires a lot of time is left out. Because a lot of time is needed not only to respond to CW3's four questions (see paragraph 2.3), but also to process the voluminous responses produced, this method is consistently omitted.

* During the evaluation session, identifying problems often leads to a lengthy discussion of the design because the evaluation team is trying to solve the problems. This means that the evaluation time increases or is spent on the design process.

* Some designers become defensive during the evaluation session. Feeling that they have already invested so much time in designing the system, they try to defend their design in order to avoid going overtime on the project to take the problems raised by the evaluation into account.

To address these difficulties, Spencer proposed Streamlined CW (SCW). SCW is a variant of CW3 with 5 phases. The first phase defines the walkthrough input. In the second, the evaluation team is convened to define the role of each team member and to determine what should and should not be done during the evaluation, as well as what needs to be done to avoid making the designers defensive about their design. The third phase is the inspection phase, in which the evaluators proceed in the same manner as in CW3, responding to the following two questions:

1. Will the users know what to do at this step?

2. If the users do the right thing, will they know that they did the right thing and are making progress towards their goal?

(Spencer, 2000)

## 3.4. Cognitive Walkthrough for the Web

Cognitive Walkthrough for the Web (CWW) is a method for detecting and fixing errors that occur when browsing and searching for information on a website (Blackmon, Polson, Kitajima & Lewis, 2002; Kitajima, 2006). This is an extension of CW3.
CWW is based on a theory called CoLiDeS (Comprehension-based Linked model of Deliberate Search) (Kitajima, Blackmon & Polson, 2000). CoLiDeS is itself an extension of the model LICAI (Linked model of Comprehension-based Action planning and Instruction taking), which is an exploration model based on understanding (Kitajima & Polson, 1997). CWW allows users to simulate surfing on a webpage with a goal in mind. The exploration consists of selecting an action (e.g., click on an icon or a link) and then assessing the outcome in terms of the goal. CoLiDeS assumes that the selection of an action is a two-phase process: attention and action selection. During the attention phase, the user parses the page into a range of subregions, generates a brief description of each subregion based on his/her background and knowledge about website page layout conventions, and then focuses on the subregion whose description matches his/her current goal. During the action selection phase, the user generates descriptions of all graphic widgets in the target subregion and acts on the one that is closest to his/her goal.

The questions for CWW evaluation are as follows:

Q1: Will the correct action be made sufficiently evident to the user?

Q2: Will the user connect the correct subregion of the page with the goal using heading information and her understanding of the sites page layout conventions?

Q3: Will the user connect the goal with the correct widget in the attended to subregion of the page using link, labels and other kinds of descriptive information ?

Q4: Will the user interpret the system's response to the chosen action correctly?" (Blackmon et al., 2002)

CWW transforms the CoLiDeS approach using the Latent Semantic Analysis (LSA) (Landauer and Dumas, 1997): instead of a subjective assessment of these questions by evaluators, LSA is used to estimate the semantic similarity between texts based on statistical analysis of a large corpus. In CWW, LSA is used to estimate the semantic similarity between the user's goal descriptions and descriptions of the page subregions, as well as the goals and descriptions of possible actions on the webpage.

The evaluation is done in 4 stages (Figure 2). In stage 1, a set of realistic user goals is compiled; each goal described in 100 to 200 words, and then the correct selection for each goal is identified. In stage 2, the semantic similarities between the goals, titles and link labels are calculated. In stage 3, problematic titles and link labels are identified, under CoLiDeS' assumptions. (These assumptions hold that a title may cause a problem if it is not familiar or if it can be confused with others; a title with an LSA value of less than 0.8 is assumed to be unfamiliar, while a pair of headings with an LSA value of more than 0.6 is assumed to be easily confused.) In stage 4, goal-specific competition is inspected.

<figure><img src="image_4.png" /><figcaption>Figure 2. The stages of CW for the Web (adapted from (Blackmon, Polson, Kitajima & Lewis, 2002))</figcaption></figure>
### 3.5. Groupware Walkthrough

A usability inspection method for groupware, Groupware Walkthrough is an "substantive modification of cognitive walkthrough" that allows the "complexities of teamwork" to be considered (Pinelle & Gutwin, 2002). Groupware Walkthrough (GW) includes both a task model and a walkthrough process. The task model allows the identification and analysis of collaborative real-world tasks, as well as allowing the variability of the working group's actions to be expressed. The walkthrough process is designed to assess whether or not the system supports the tasks, which are modelled as a set of possible paths towards a desired result. Every possible path is explored during the walkthrough, and the support for each path in the interface is evaluated.

Collaboration involves two distinct types of work: *taskwork*, which includes the actions that must occur to accomplish the task, and *teamwork*, which refers to the actions that group members must perform as a group in order to accomplish a task. Traditional approaches to evaluation focus on taskwork. Teamwork can be analyzed at high-levels and low-levels of abstraction. High-level abstraction, which includes social and organizational factors, is analyzed using Groupware Task Analysis (GTA) (Van der Veer, Lenting & Bergevoet, 1996; Van der Veer & van Velie, 2000). The methods associated with GTA focus on task specification based on ethnographic observation. Although GTA is an effective way to gather information on the work context, its level of abstraction is too high to be used in a Walkthrough inspection situation. To capture the level of detail needed for the walkthrough, it is necessary to examine teamwork at the lower level of abstraction inherent to the mechanics of collaboration.

Nevertheless, the high-level analysis must precede the low-level analysis. The mechanics of collaboration (Gutwin & Greenberg, 2000) are the core activities of group work, the small-scale actions and interactions that the group must undertake to accomplish a task collaboratively. These activities are invariable through a variety of social and organizational factors. The mechanics of collaboration includes explicit communication, monitoring, action coordination, planning, assistance and protection.

The main components of the task model are scenarios, individual and/or group tasks and sub-tasks, and actions. The scenario is a description of the high-level activities that must be accomplished to produce a specific result. Task analysis begins with the collection of observed data about the work and continues with the identification of episodes of collaborative interaction. Both scenarios and tasks can be specified, and teamwork can be analyzed using the mechanics of collaboration.

Once the teamwork analysis has been completed, GW can be conducted for each collaborative scenario as follows:

* Review the scenario to become familiar with the users, the intended outcome and the surrounding circumstances.

* For each task in the scenario:

- Attempt to carry out each alternate subtask,

- Record how each subtask was carried out, and

- Record the problems encountered but assume they are resolved and continue.

* After each task, ask the following questions:

- Can the task be performed effectively? (i.e., Does the interface supply the means to perform the task correctly?);

- Can the task be performed efficiently? (i.e., Would the group make the effort required to perform the task?); and

- Can the task be performed satisfaction? (i.e., Would the group be motivated to do this task, and would they be happy with the outcome?).

* After completing all tasks, determine whether the interface allows the group to produce the overall intended outcome.
## 3.6. Activity Walkthrough

Activity Walkthrough (Bertelsen, 2004) is a modified version of CW3 based on activity theory. Activity Walkthrough (AW) is a powerful descriptive tool that focuses on understanding human activity, incorporating the concepts of intentionality, history, mediation, collaboration and development (Nardi, 1996). According to activity theory, the unit of analysis is the activity itself. An activity is composed of a subject, an object and the tools that serve as mediation. A subject is a person or group of persons engaged in an activity. An object is held by the subject and motivates the activity. Mediation can occur through the use of different types of tools: material tools and mental tools, including culture, ways of thinking and language. According to Kaptelinin (1996), the computer can be considered as a tool for mediation. The activity is executed through a conscious (intentional) goal directed by actions that are accomplished through unconscious (automatic) operations.

In Activity Walkthrough, the evaluation is conducted in six phases. In phase 1 (preparation), typical tasks to be analyzed are determined based on a needs specification. In phase 2 (contextualization), the activities in which the application is used as a mediator are identified. For each activity, first the actions performed via the application and through which the activity is accomplished must be identified and then the objects and results of these actions. The other means of accomplishing the activity without the application (i.e., other artefacts used as activity mediators) must also be dealt with. In addition, user expectations, based on user experience with the application or similar tools, must be considered. In phase 3 (task verification), the extent to which each task corresponds to purposeful actions in the activities in which the application will be embedded are assessed based on the contextualization of the application. In phase 4 (task analysis), each task is broken down into sequences of atomic operations, as is done in CW3. In phase 5 (evaluation) three questions about the perceptual context, the system's response and the user's learning, respectively, are asked and answered. In phase 6 (verification), the task is analyzed based on the response given in the previous phase. Following these six phases, a report is prepared, summarizing the results of the evaluation process.

## 3.7. Interaction Walkthrough

Interaction Walkthrough (Ryu & Monk, 2004) is a modified version of CW2 based on the theory of cyclic interaction (Fig. 3), initially introduced by Card, Moran and Newell (1983) as the "recognise-act" cycle. Norman's 7-stage model (Norman, 1986) also imagined a cycle of interaction, but neither of these authors expressed explicitly how the environment and context influence user interaction. The means available to the user to manipulate the system is focused on the action ("goal-action path"). An action triggers a system effect through the entry device ("action-effect path"). After the execution phase is complete, the system attains a new state within the environment. Then the "effect-goal path", which deals with perceived changes in the environment, continues the cycle for new goals in the interaction context. These three interaction paths lead to three classes of low-level problems: goal-action, action-effect, and effect-goal.

"Goal-action" problems are often observed in cases of unpredictable actions designed to accomplish a goal. An action can be unpredictable due to the low affordance of a valid action or the high affordance of an invalid action. According to Norman (1988, 1999), affordance refers to the object attributes that allow human beings to know how to use them.
<figure><img src="image_5.png" /><figcaption>Figure 3. Cyclic interaction theory according to Monk (1998)</figcaption></figure>

"Action-effect" problems occur when the same action produces different effects depending on the system mode. There are 3 types of problems provoked by mode ambiguity. The first type of problem is due to hidden modes. In this case, errors tend to occur when the user forgets that the system mode has changed. The second type is due to partially hidden modes. In this case, errors tend to occur when the user can't recognize the mode indicator in the information environment. The third type of problem is due to misleading mode signals. In this case, errors tend to occur when the user perceives an incorrect mode signal, which leads the user to believe that the correct action has been taken, when in fact the opposite is true.

"Effect-goal" problems are due to the goal reorganization process occasioned by the "effect-goal" path. Two types of problems are possible: goal construction problems and goal elimination problems. Goal construction problems occur when the goal is ambiguous or irrelevant, while goal elimination problems occur when the system cues are missing or misleading.

IW evaluation looks at the three paths of the interaction cycle for each of the problem categories described above: affordance (low & high), mode (hidden, partially hidden & misleading), goal (construction & elimination). The evaluation takes place in 3 phases. In the preparation phase, the topics susceptible to have detectable problems are located. For example, for detecting a mode problem, the preparation phase identifies a same action that has different effects and lists the system effects that could inform the user of the current mode. In the walkthrough phase, questions are answered to allow to the different problems to be detected. For detecting a mode problem, the questions are:

"Q1: Does the user recognise (rather than recall) the current mode from system effects?

"Q2: Are system effects sufficiently salient for the user to discriminate the mode change from the previous interaction?

"Q3: Is it possible that mode signals imply different modes?" (Ryu & Monk, 2004)

Finally, in the verification phase, the previously-found problems are reviewed to verify whether or not they conform to the paths indicated by the system designer. (For more details, please consult Ryu & Monk, 2004).

## 3.8. Cognitive Walkthrough with users

Cognitive Walkthrough with Users (Granollers & Lorés, 2006) explicitly integrates users into the walkthrough process. This version of CW (CWU) takes place in 3 phases. In the first phase, CW is performed in the traditional manner. In the second, users are incorporated into the process as follows. First, representative system users must be recruited. After a brief introduction, these users are invited to perform all the tasks defined in the Walkthrough that correspond to their profile. During this interaction, the users are asked to express aloud their thoughts, feelings and opinions on any aspect of the system or prototype. Users perform the tasks without any explanation other than the brief introduction; at the end of each task, they note the main deficiencies detected. Once the users have completed the tasks, they are invited to comment on the problems identified during the first phase in order to situate their point of view. In the third phase, experts review the doubts expressed by users during the second phase.
## 3.9. Extended Cognitive Walkthrough

Using CW often requires knowledge of cognitive psychology. Kato and Hori (2005) noted that some evaluators have difficulty understanding the differences between a correct object and a correct action, and also distinctions between the different questions. In an attempt to circumvent these problems, Kato and Hori (2005; 2006) suggest an extension of CW3, called Extended Cognitive Walkthrough (Extended CW).

The theoretical model of the method is based on the Norman action model (Norman, 1986), but extended as shown in Figure 4. The changes in the model affect the third stage, splitting it up to allow data about the object and the action to be collected and interpreted separately. During the evaluation phase, 9 questions must be answered (instead of the 4 in CW3); these questions are directly related to the extended Norman model (Fig. 4):

* (Q1) Will the user intend to achieve the right effect?

* (Q2-a) Will the user notice that the correct object is available?

* (Q2-b) Will the user know what the correct object refers to?

* (Q2-c) Will the user notice that the correct action is available?

* (Q2-d) Will the user know that the correct action should be applied to the correct object?

* (Q3) Will the user be able to apply the correct action to the correct object without fail or difficulty?

* (Q4) When the correct action is taken, will the user notice the physical change in the system state?

* (Q5) Will the user know what exactly has happened to the system state?

* (Q6) Will the user know that the current system state is nearer to completion of the task? "(Kato & Hori, 2005)

<figure><img src="image_6.png" /><figcaption>Figure 4. Extended Norman's action model (from (Kato and Hori, 2005))</figcaption></figure>

Because information is accessible if it is easily perceptible and understood by system users, the authors of ECW think that information accessibility should be assessed according to its perceivabilty and its understandability. To make their method appropriate for detecting accessibility problems, they included questions Q2-a and Q2-c for assessing perceptibility and Q2-b and Q2-d for assessing user understanding. They therefore find that ECW is better able to identify accessibility problems than CW3.

## 3.10. Distributed Cognitive Walkthrough

Distributed Cognitive Walkthrough (Eden, 2007, 2008) is a variant of CW3. This distributed walkthrough method (DCW) is based on two theories: distributed cognition (Hollan, Hutchins & Kirsh, 2000) and distributed cognitive tasks (Zhang & Norman, 1994).

According to Hollan, Hutchins and Kirsh (2000), the theory of distributed cognition, like any other cognitive theory, seeks to understand the organization of cognitive systems. However, these authors extend the definition of "cognitive" beyond the individual to include interactions between humans and objects in their environment. Applying distributed cognition to observed human activity involves three types of
distribution processes: (1) cognitive processes can be distributed through members of a social group; (2) cognitive processes may imply the coordination of internal and external information structures (see principle of distribution below); and (3) cognitive processes can be distributed over time so that the products of previous events can transform the nature of future events.

The representation of information affects the cognitive behavior of an individual for the same formal task structure. The theory of distributed cognitive tasks contributes to the problems of distributed representation of information, the interaction between internal and external representations, and the nature of the external representation.

The principle of distribution holds that part of a task is represented internally in mind and the other part is represented externally in the physical environment (Zhang & Norman, 1994). The internal representation may involve propositions, mental images, and production rules, while the external representation may involve physical symbols, external rules, external relationships embedded in physical configurations, and so on.

Like CW3, DCW includes 4 questions to which the evaluator must respond, with a negative response indicating a usability problem:

Q1: Will the way that information is represented provide all the knowledge required to carry out the task?

Q2: Will the way that information is represented show relevant previous progress towards completing the overall task?

Q3: Will the way that information is represented provide resources that keep the user from having to figure out or calculate anything in his/her head while carrying out the task?

Q4: If the current task is accomplished, will the way that information is represented be changed in any way so that the result of the task is accessible to current or future users at a later time or in a different place?

## 3.11. Enhanced Cognitive Walkthrough

Enhanced Cognitive Walkthrough (Enhanced CW) is an alternative version of CW3. It was proposed by Bligard & Osvalder (2007) and is used as an analytical approach for predicting and identifying use errors and usability problems. According to the IEC (2004), a use error is an act or omission of an act that has a different result than intended by the manufacturer or expected by the operator.

The approach suggested by Bligard & Osvalder (2007) comprises four phases: (1) the definition of the evaluation, (2) the description of the system, (3) the analysis of the interaction and (4) the compilation of the results and reflection. Enhanced CW intervenes in the third phase (analysis of the interaction), in parallel with the predictive analysis of use errors (Bligard, 2007).

Enhanced CW proceeds in two stages. The first aims to predict usability problems; it consists of inspecting the sequence of user actions, using the following questions:

Q1: Will the user know that the evaluated function is available?

Q2: Will the user try to achieve the right effect?

Q3: Will the user interface give clues that show that the function is available?

Q4: Will the user be able to notice that the correct action is available?

Q5: Will the user associate the right clue with the desired function?

Q6: Will the user associate the correct action with the desired effect?

Q7: Will the user get sufficient feedback to understand that the desired function has been chosen?

Q8: If the correct action is performed, will the user see that progress being made towards the solution of the task?

Q9: Will the user get sufficient feedback to understand that the desired function has been performed?

The answer to each question is a number ranging between 1 and 5, where 1 means “No”, 2 means “probably No”, 3 means that the answer is unknown, 4 means “probably Yes” and finally 5 means “Yes”.
Like the third CW version, each answer must be justified. Any answer other than 5 suggests a potential usability problem.

The second phase of Enhanced CW is the identification of the problems; this phase consists of determining the category of each problem. The categorization is based on the justification and the description of the problem. Depending on the type of the HCI and the task concerned, there can be several problem categories. Bligard and Osvalder (2007) have proposed five categories of utilisability problem:

* problems related to user knowledge and background;

* problems related to information posting (i.e., the interface does not give any indication on the functions available or the way of using them);

* problems related to the way information is illustrated (i.e., the interface's location, appearance and contents can be badly interpreted or not understood);

* the problems related to the sequence of actions (i.e., the actions are probably performed in an unnatural way);

* the problems related to information feedback (i.e., the interface does not give enough indications of what the user should do).

# 4. SUMMARIES

We propose four complementary summaries, which are each described in succession. The first deals with the conceptual, methodological and technological aspects of each version or variant. The second presents comparative studies of at least one version or variant of CW and at least one other evaluation method. The third focuses on non-comparative studies (i.e., the methods depend only on CW). The fourth summary is intended to facilitate the choice between the versions and variants of CW.

## 4.1. Summary of the conceptual, methodological and technological aspects

At the beginning, CW was a method for assessing usability problems in "walk-up-and-use" systems (i.e., systems that can be used with little or no training). Due to its success, practitioners and researchers interested in this method tried to improve it or to adapt it for other specific types of application. Eleven modified or extended versions of CW have been thus far proposed. In most cases, the modifications and extensions concern theoretical or conceptual aspects; however, some concern methodological aspects. Only two versions deal with the technological aspects of the method.

CW1 (Lewis, Polson, Wharton & Rieman, 1990) requires an implicit knowledge of cognitive science in order to understand the terminology used in the forms that the evaluators fill out. For example, to succeed in using the method, the evaluators must understand the distinction between a goal and an action. To address this problem, CW2 (Polson, Lewis, Rieman & Wharton, 1992) is more formal, guiding evaluators through detailed analyses to avoid ambiguities. The addition of Norman's action model and Kintsch's construction-integration model allows detailed analyses, structured according to the goals and actions. But the increased number of forms and lists of questions makes the method more complex and cumbersome to apply. An automated tool was developed (Rieman et al., 1991) to help evaluators fill out the different forms, thus helping them to focus on the evaluation. But even with this help, the authors of CW2 found the method costly in terms of time and energy. CW3 (Wharton, Rieman, Lewis & Polson, 1994) was developed in an effort to reduce the method's complexity and operating costs by introducing methodological changes. Nevertheless, in our opinion, even this third version of CW is far from perfect. In fact, most of the authors of the various extensions presented in this paper have made comments, criticisms and suggestions, ending up proposing an extension that would address the problems they identified.

In Heuristic Walkthrough, changes were made on the methodological level. Since the first phase of HW includes the whole CW process, the second phase could be seen as redundant in terms of evaluation. Clearly, HW—with its second system assessment—is cumbersome. Still, Sears' tests show that this redundancy
allows Heuristic Walkthrough to find more usability problems than CW (Sears, 1997). This is a promising result, which calls for further study.

The Norman CW method adopts the action model as a theoretical foundation, which allows the problem to be dealt with at a high level of abstraction, thus permitting the source of problems to be located during the evaluation. The methodology focuses on the level of cognitive distance, thereby facilitating the location of the problems. However, the reference document for this method (Rizzo, Mandrigiani & Andreadis, 1997) provides no information that would allow us to judge the validity of this method.

Streamlined CW makes several important methodological changes, involving the preparation of the evaluation team, the imposition of background rules for supervising the CW process, and the reformulation of the initial four questions into only two questions. These changes affect the time constraint, eliminate the lengthy design discussions during the evaluation and prevent designers from going on the defensive (i.e., defending the mistaken views that are influenced by their design experience). We think that making the questions more general instead of more detailed could compromise the method's effectiveness for novice evaluators, but this needs to be verified in future experiments.

CW for the Web (CWW) makes changes on the conceptual level, adopting the CoLiDeS cognitive model. In addition, this is the only extension that makes changes in the technological aspects. This extension was designed specifically for assessing the Website usability, with four questions that focus on navigation and information retrieval. To prevent subjective judgements of the answers to these four questions, the method employs Latent Semantics Analysis (LSA). LSA uses rich goal descriptions to incorporate more information about the users' understanding of the tasks, which results in more realistic goals. The choice of semantic space knowledge applied in LSA allows CWW to take a target population (e.g., chosen by age) into account during the evaluation. In our opinion, the effectiveness of this method will depend on the quality of the semantic space knowledge chosen and its interpretation.

Groupware Walkthrough (GW) is the only extension designed to evaluate Computer Supported Cooperative Work (CSCW) applications. Based on a model of the mechanics of collaboration, GW addresses the complexity and particularities of these applications, among other usability problems related to collaboration. Though its use of GTA (Van der Veer, Lenting & Bergevoet, 1996; Van der Veer & van Velie, 2000) does facilitate the detailed examination of the context of each task connected to the evaluation, GW is not able to detect classic usability problems and it would have to be improved in order to detect and take into account the different socio-organizational uses in real collaborative systems (Pinelle & Gutwin, 2002).

Based on the activity theory, Activity Walkthrough allows evaluators to include more context in the evaluation and the dynamic commitment of actions, since the basic element of the analysis is the real activity of users. However, we believe that tackling CW through the activity theory—which requires that many factors be taken into account, including intra- and inter-individual variability, but also use contexts— will certainly complicate the evaluation, making it more cumbersome and increasing the difficulty of results interpretation, which already requires extensive expertise. Both the method's author (Bertelsen, 2004) and others (e.g., Ryu (2008)) appear to share this point of view, since they emphasize that the method is complex and cumbersome.

Interaction Walkthrough (IW) is based on the cyclic interaction model and considers low-level problems. In contrast to other methods, which are supposed to detect fairly complicated problems, locating them and explaining their origins, IW detects problems more easily since they are low-level. However, Ryu and Monk (2004) believe that user behavior is dependent on the technology used and that technology must be seen in the context of a state of activity that has meaning for the user. Given the complexity of the interaction analysis, the validity of this method's results may be doubted.

CW with Users (CWU) is a CW method that embraces real user involvement in the broadest sense of the term. It is an interesting option, in terms of ergonomics, but since it involves both experts and users, the end
result seems to remove the method from the "for experts only" category of inspection methods. Given this
change in category, we wonder whether the chosen models and methods for intervention and analysis are the
most appropriate (e.g., use of concurrent "think-aloud" verbalization).

Extended Cognitive Walkthrough (ECW) modifies CW conceptually, adopting an extended model of the Norman action theory. ECW helps to evaluate information accessibility, taking into account all aspects from cognitive perception to understanding to action implementation. Like in the Norman CW method, the questions used in this method focus on cognitive distances. After trying the method, Kato and Hori (2006) concluded that ECW detects more usability problems than CW3 in a comparable time. Although the theoretical foundations of the method seem solid, the experimental conditions (e.g., type of participants, compensation, types of HMI evaluated) described by Kato and Hori (2005) do not allow us to draw conclusions about the effectiveness of ECW in other conditions, in terms of the validity criteria proposed by Gray and Salzman (1998).

Distributed Cognitive Walkthrough is a variant of CW3 that adopts cognitive distribution theories.
Theoretically, this method can identify usability problems through dimensions, such as time, space and
social structure. However, the author of the method did not provide results of experiments using the method.

Lastly, Bligard and Osvalder (2007) underline the effectiveness of Enhanced CW within the framework of an analytical approach for predicting and identifying usability problems and use errors. It seems to us that it is now necessary to show its effectiveness if used outside of this framework.

Table 1 summarizes the salient features of all the CW versions and extensions. Three columns contain the theoretical/conceptual aspects, the methodological aspects and the technological aspects.

INSERT TABLE 1 ABOUT HERE

To conclude this overview, we would like to emphasize that, although they are not homogeneous, the variations of CW show what happens when users evaluate a particular system by performing tasks with this system (conceptual aspect), providing specific questions (methodological aspect) and using various tools and techniques (technological aspect). Due to space constraints, we cannot detail the questions asked in each method, but in general the questions are designed to evaluate, for each interaction, whether or not users manage to i) formulate goals, ii) perform the appropriate actions that will help them reach their goals, iii) interpret the system responses correctly, and finally iv) accomplish their goals properly.

**4.2. Summary of the comparative studies**

In this section, we look at the diverse studies that evaluate the performance of the various versions and variants of CW. Table 2 summarizes all the comparative studies examined. In these studies, one of the three CW versions is compared with another version or a variant of CW or another evaluation technique. The evaluated system is specified, including the types of evaluators taking part in the study. Then, the main quantified results related to usability problems are provided. To provide more details about the various elements in the table, the conditions of each study and the corresponding conclusions are summarized below<fnref n="1" />.

INSERT TABLE 2 ABOUT HERE

- Lewis et al. (1990)

**Conditions of the study:**

These authors evaluated two tasks for each of the four user interface designs in a mail messaging system. Four evaluators, including three who were conversant with the CE+ theory, took part in the evaluation. Each evaluator independently evaluated the two tasks for each of the four interfaces. The results were compared

<footnote n="1">¹ Insofar as several of these studies are rich in results and analyses, it was necessary to summarize them. The three authors provide the summaries and conclusions in this article for the convenience of the readers. For more details, it is necessary to refer to the original articles (see bibliography)).</footnote>
with the previously available data, which came from empirical evaluations of the same tasks carried out on
the four interfaces with at least 15 subjects.

Conclusions of the study

The authors highlighted 20 problems, 18 of which were found by at least two of the four evaluators.
Then they compared the results from the CW1 evaluations with the empirical data, which led them to
conclude that using CW1 allowed the detection of 50% of the usability problems detected using the
empirical method.

- Polson et al. (1992)

Conditions of the study:

These authors reported the results of tests using CW2 on student projects. Three interfaces were
evaluated: a voice mail directory, a text editor and a document router. The first interface was tested both
with CW2 and with a thinking-aloud user test. The second interface was tested using CW2 on about fifty
varied tasks, and then the results were compared with those obtained by an empirical method (i.e., field
trouble reports and user interviews). Finally, the last interface was evaluated using CW2 on a rather simple
task, and the results were compared with those from subsequent usability tests.

Conclusions of the study

The test on the first interface showed that the CW2 method allowed the detection of 50% of the usability problems found with the thinking-aloud user test. The comparison data for the second interface were not matched specifically to the tasks evaluated during the CW2 tests; nonetheless, CW2 detected 30% of the usability problems, including 70% of the problems considered to be serious. Finally, all the usability problems detected for the third interface with the subsequent usability tests were also detected by CW2.

- Sears (1997)

Conditions of the study:

This study compared the performances obtained with the following methods: CW3, Heuristic
Walkthrough (HW) and Heuristic Evaluation (HE). Twenty computer science graduate students, who had
taken courses in user interface design and evaluation, took part in the evaluation of a system for learning the
visual effects of rendering algorithms. The evaluations were carried out by groups of evaluators, comprising
one to five participants.

Conclusions of the study

The results of the study showed that, for the groups of two to five participants, HW allowed the identification of significantly more minor and intermediate-level problems compared to CW3, while HE allowed the identification of significantly more minor problems than CW3 (see Table 2). In addition, HW and CW3 allowed the identification of significantly more false positive problems than HE for the groups of two to five participants.

- Granoller and Lorès (2006)

Conditions of the study:

CWU was tested on a microscope simulator and a conference system management. For the first system, an expert evaluator evaluated the application with CW3. Then 10 medical students individually carried out the second phase of CWU. For the second system, an expert evaluator evaluated the application. Then 3 users with different profiles representing the end users of the conference system management carried out independently the second phase of CWU.

Conclusions of the study

The results showed that with CW3, the expert evaluator found five usability problems on the first
system. And by using CWU, 11 other usability problems were found. For the second system, the expert
evaluator found 9 problems in the first phase. In the second the three users found 14 other usability
problems.
- Kato and Hori (2005)

Conditions of the study:

This study compared CW3 and Extended CW. Twenty students with prior experience using CW3 took part in the study. Two interactive systems (a digital camera's user interface and a paint software) were evaluated. The participants were asked to use a seven-point scale to rate the ease with which they understood and were able to answer the questions in the two versions of CW. Then, they compared the two versions. Finally, they were asked to pick the version they would most like to use in the future.

Conclusions of the study

There were 43 potential usability problems found on the digital camera interface using CW3 compared to 59 with Extended CW. For the paint software, CW3 allowed the detection of 70 usability problems compared to 62 for Extended CW. The results also showed that the Extended CW questions were easier to understand than those of CW3. Moreover, 70% of the participants judged that it was easier to answer the Extended CW questions than the CW3 questions. For this reason, 70% of them preferred to use Extended CW in the future.

- Eden (2008)

Conditions of the study:

The objective of this study was to compare DCW and CW3 in terms of several criteria: average severity rating, usability relevance rating and actionability rating. The first criterion (average severity rating) measures the usability of all the questions used during a complete evaluation session; according to Eden (2008) "this measure of the average severity rating provides the most direct assessment of the usability of a design for a task, with respect to the evaluation method used" (p. 62). The second (usability relevance rating) provides an overall rating in terms of how well each complete participant evaluation makes relevant usability statements. This criterion allows the assessment of the relevance of the evaluation results as carried out by an unspecified evaluator using a given method. The third criterion (actionability rating) is used to assess up to what point the usability problem descriptions indicate as explicitly as possible what should be changed to resolve the problems.

A scenario drawn from the hospitality industry (specifically, a restaurant scenario) was studied. For this scenario, the waiters must take the various drink orders, which then must be tracked until the drinks have been prepared and served to the customers. The participants were undergraduate students in computer science who did not have experience with usability evaluation methods.

Conclusions of the study

According to the three criteria, both DCW and CW3 provided interesting results. For the first criterion, the average value was 1.68 for DCW compared to 0.95 for CW3, which suggests that DCW seems to encourage the evaluators to be more severe than CW3. For the second criterion, the average value was 2.76 for DCW compared to1.81 for CW3, which indicates that DCW led to more relevant results than CW3. For the third criterion, the average value was 2.38 for DCW compared to 1.71 for CW3, which means that DCW led the evaluators to better describe the solutions to the problems found than CW3.

- Jeffries et al. (1991)

Conditions of the study:

In this study, CW2 was tested by a group of evaluators and then the results were compared to other
evaluation methods (Heuristic evaluation, Usability testing and Guidelines). The interface evaluated was the
graphical interface HP-VUE of an operating system Unix for HP workstation. This interface was not a
"walk-up-and use" interface. Four variable-size groups of evaluators, each assessing a different method, took
part in the study. The group using the heuristic evaluation method was composed of four HCI specialists, the
one using the Usability testing method was composed of six regular PC users who were not familiar with the
UNIX system and led by a human factor specialist. Finally, the groups using the Guidelines and CW2
methods were each composed of three computer scientists, who were not members of the system design
team but were members of the same laboratory.
## Conclusions of the study

The heuristic evaluation method allowed 105 usability problems to be identified, while usability testing identified 31, guidelines identified 35 and CW2, 35. The authors noted that even though the heuristic evaluation method allowed the identification of many problems, particularly serious problems, it required the participation of HCI specialists, whereas CW2 can be used by developers who are not necessarily HCI specialists.

### - John and Marks (1997)

#### Conditions of the study:

The goal of this study was to assess the predictive and persuasive power of six evaluation methods—CW3, Heuristic Evaluation (HE), Claims Analysis, GOMS, User Action Notation, and Reading Specification—by comparing their predictions with that of the user test, Think Aloud). Six evaluators evaluated a multimedia authoring system. They each used a different evaluation method. The evaluators who used Claims Analysis had Bachelor's degree in electrical engineering. Those who used CW3 had a Master's in computer science. Those who used GOMS had a Master's in architecture. Those who used Heuristic Evaluation had Master's in English. Those who used User Action Notation had Bachelor's in computer science. Lastly, those who used Reading Specification were in the junior year of an undergraduate computer science program. Twenty undergraduate business students used the Think Aloud method.

## Conclusions of the study

CW3 allowed the detection of 42 problems compared to 88 for HE, 24 for Claims Analysis, 44 for GOMS, 17 for User Action Notation and 69 for Reading Specification. However, 2 (5%) of the 42 problems found by CW3 were false alarms (i.e., which are not usability problems) compared to 24 (17%) for HE, 6 (24%) for Claims Analysis, 6 (13%) for GOMS, 14 (82%) for User Action Notation and 4 (6%) for Reading Specification.

Among the 40 problems found using CW3, 13 (33%) were related to aspects of the system that had not yet been implemented, compared to 3 of 64 (5%) for HE, 5 of 18 (26%) for Claims Analysis, 17 of 38 (44%) for GOMS, 3 of 3 (100%) User Action Notation and 20 (31%) for Reading Specification. These results confirm the conclusions of Wharton et al. (1994) who stated that CW3 could be used early in the development process. Among the 15 problems found by CW3 related to the aspects of the system that had already been implemented 11 of 15 (73%) led the developers to change the code, compared to 7 of 41 (17%) for HE, 0 of 11 (0%) for Claims Analysis, 3 of 10 (30%) for GOMS, 0 of 0 (0%) for User Action Notation and 9 of 23 (39%) for Reading Specification.

By combining similar problems, the number of problems found by the six evaluators were reduced to 54. Among these 54 problems, 26 were observed in the user tests; among these 26 problems, 13 led to code changes.

### 4.3. Summary of non-comparative studies

Table 3 summarizes all of the non-comparative studies undertaken by various authors. For each study, the system evaluated is described, as well as the type of participant taking part in the study. When numerical results are available, they are provided.

**INSERT TABLE 3 ABOUT HERE**
- Rizzo et al. (1997)

**Conditions of the study:**

This study did not have numerical results. The authors simply described an example implementation of the method. The scenario studied involved a person with wheelchair who lived in Rome and decided to plan a one-day visit to Siena, in Italy. For each activity in the task, the members of design and evaluation team used the questions of the action model.

**Conclusions of the study**

Related to the Norman' s CW method, this study concluded: "The Norman' s CW method allowed to ease the design problems that the design team encounters when they work in different places".

- Spencer (2000)

**Conditions of the study:**

This study highlighted the effectiveness of the Streamlined CW method in a project management context with social constraints (see section 3.3). The “Integrated Development Environment” (IDE) under development was evaluated by a 8-member team (3 usability specialists, 1 graphic designer, and 4 project managers responsible for various aspects of the IDE specifications). Only the team leader, a utilisability specialist, was familiar with CW method. The test was conducted in two sessions, separated by one week. The first session lasted 90 minutes, including 20 minutes devoted to the preparation phase and covered 32 action sequences (only the results of the first session are discussed in their paper).

**Conclusions of the study**

The first session allowed 24 potential problems to be found. The participants agreed that 14 of the 24 usability problems found were due to a lack of user knowledge and the 10 remaining problems were due to a lack of system feedback when the correct action was carried out. The results show that the team members did not waste time defending their design choices.

- Blackmon et al. (2002)

**Conditions of the study:**

This study compared the "first-click" success percentage of the participants on headings or links with usability problems and headings or links without problems. The authors carried out three experiments simulating the search function of an online encyclopedia. The participants in these three experiments were college educated. Experiment 1 was carried out on an initial online encyclopedia. Experiment 2 was carried out on the same encyclopedia, but with an additional post (a long description of the current goal). Experiment 3 was carried out on a second online encyclopedia, using the same procedure as experiment 2 (i.e., with an additional post describing the current goal).

**Conclusions of the study**

Some of the analysis results are shown in Table 3. The success rate of experiment 2 was higher than that of experiment 1 by approximately 23 points, and the success rate of experiment 3 is lower than that of experiment 2 by approximately 29 points. According to the authors, the results show that "the CWW can identify characteristics of Web pages that differentially affect to user performance". In addition, CWW provides specific diagnostics, which can guide the resolution of the problems that it identifies.

- Pinelle and Gutwin (2002)

**Conditions of the study:**

The authors published a case study in order to show how to use GW. They evaluated an initial prototype of a home care system. The system allowed the members of the medical team (e.g., physicians, nurses) to share documents and to communicate via a chat tool.
## Conclusions of the study

Five main usability problems were detected: the person receiving a message might not see it, the variable typing skills in the group could generate difficulties, the system does not provide enough information on a person's availability, the system does not allow multiple meetings of subgroups within the home care team, and the identification of an element on a shared document can cause problems. They noted that GW let them to revise their design easily and quickly.

- Huart et al. (2004)

### Conditions of the study:

This study used CW2 to evaluate four multimedia systems with various degrees of interactivity. The first system, an encyclopedia for children from 8 to 14 years old, had lowest degree of interactivity in the study. The second system was a museum exploration tool intended for any public. The third system was an educational software system intended for children four years old and older. The fourth system, a virtual reality game, had the highest degree of interactivity in the study. Four evaluators—including a ergonomist, a interactive system design and evaluation specialist (both called expert evaluators) and two Master's students in industrial ergonomics (called non-expert evaluators)—evaluated each of the four systems in turn.

## Conclusions of the study

By the end of the evaluations, 80 problems had been detected in the four systems, 22 of which were detected by at least two evaluators. Among the problems detected by the experts, 58 were not detected by the non-experts; among those detected by the non-experts, 6 were not detected by the experts. The authors concluded that CW2 can be used to evaluate multimedia systems with various degrees of interactivity. Nevertheless, the effectiveness of the method depends greatly on the expertise of the evaluator, with the expert evaluators finding many more problems than the non-expert evaluators.

- Bertelsen (2004)

### Conditions of the study:

The objective of this preliminary study was to obtain information about the applicability and usefulness of Activity Walkthrough (AW). The participants were students (level not specified in the study) taking the author's HCI course. The students formed groups of three, with each group evaluating an HCI interface of its choice.

## Conclusions of the study

This preliminary study indicates that AW is very complicated to use in its current form. Nevertheless, several students concluded that the contextualisation in phase 3 is an important advance over state-of-the-art inspection.

- Ryu and Monk (2004)

### Conditions of the study:

The authors described the stages and the necessary questions for using the Interaction Walkthrough (IW) method. While not proposing a complete study, they do illustrate their explanations with examples of HCI.

## Conclusions of the study

The authors concluded that IW method is a promising alternative for evaluating HCI with low-level interaction.

- Bligard and Osvalder (2007)

### Conditions of the study:

In this article, Enhanced CW was integrated into a broader analytical approach for predicting and identifying usability problems and use errors. Two studies were conducted in the medical field on a dialysis machine interface. In the first study, the suggested approach was used to compare three different design solutions. In the second study, the objective was to improve a design.
## Conclusions of the study

The authors considered that the evaluations provided the company with more specific information about the usability problems and use errors related to the dialysis machine interface prototype. However, the results do not provide any information concerning the performance of Enhanced CW if it is used separately from the analytical approach for predicting and identifying usability problems and use errors.

## 4.4. Summary of the studies intended to help make the choice of a version or variant

We did not find any studies intended to help the evaluators (both practitioners and researchers) to choose a method among the various CW versions and variants presented in the literature. *A priori*, this seems an extremely difficult, or even impossible, task. There are very important differences between the methods in terms of structure, experimental methodology, expected results, type of the study, evolution of the versions and variants. The various summaries (sections 4.1, 4.2 and 4.3) that we have proposed may provide some assistance in making this choice, but of course more needs to be done.

Moving in this direction, we offer Table 4, which completes the information given in the preceding summaries. We highlight key quotations from the original articles that we think characterize each method's specificity and give an informal opinion for each version and variant.

## INSERT TABLE 4 ABOUT HERE

## 5. CONCLUSIONS AND PERSPECTIVES

Generally speaking, CW allows the evaluation of the ease with which a user completes a task with minimal system knowledge and the ease of interface exploration/learning. Initially, it was based on a learning model (Polson, Lewis, Rieman & Wharton, 1992) that was itself inspired by the Norman action theory (Norman, 1986). Users integrate a perceptual entry into their background knowledge to build a representation that will enable them to perform a task. Through the interface, CW aims to simulate the user's cognitive process in order to accomplish the task. Forms with specific questions that must be answered guide the user through the walkthrough. CW can be applied in the system design and development phase to identify system usability problems as soon as the system is modelled and its features specified. It can also be used retroactively to determine the difficulties in using a system through executing specific scenarios and special testing. Representing the cognitive processes employed by the user can help to improve system usability.

CW is a widely recognized evaluation method in the HMI scientific community. Its theoretical foundations and its practical interest are such that, since it appeared on the scene, it has been the subject of numerous studies and conceptual, methodological and technological extensions. To demonstrate the efficiency and performance of each method mentioned in this article, the authors of the methods often perform a limited number of tests (sometimes as few as a single test), and their conclusions are too often subjective. To determine which method is the best, the literature provides only a few studies that make partial comparisons, such as Sears (1997), Granoller & Lorés (2005), Kato & Hori (2005,2006) and Eden (2008) (see Table 2). The authors of the various versions and extensions often adopt different methodologies and techniques for judging the validity of the evaluation results. No comprehensive study has ever been made to compare the different versions and extensions to determine which method is better using the same techniques to judge the results.

Interestingly enough, some studies have been done to compare CW with other types of evaluation methods (e.g., Desurvire, Kondziela and Atwood (1992); Jeffries (1991); Karat, Cambell and Fiegel (1992)). However, Gray and Salzman (1998) have examined these comparative studies and have observed that they have many anomalies. Several studies have shown that an evaluation method may be effective for a given system but not necessarily for others. For example, Huart, Kolski and Sagar (2004) noted that CW is not well suited for evaluating certain types of multimedia applications.
Considering the various steps adopted by the authors to show the effectiveness and performance of the methods, we think that a global comparison of the various techniques would constitute a particularly interesting direction for further research.

It would be important to involve various types of evaluators (e.g., expert, beginners) and various types of systems, taking inspiration, for example, from Huart, Kolski and Sagar (2004) who considered in their study several multimedia systems with different levels of interactivity and in diverse contexts (e.g., the DCW method that requires an approach involving distributed cognition).

Our investigations suggest that CW has evolved significantly, particularly in terms of its conceptual aspects. However, we were not able to systematically prove the validity and effectiveness of each change or extension. With respect to the methodological and technological aspects of CW, we find that there are still many imperfections. Future research should thus go in this direction. Many methodological weaknesses remain in terms of preparing for the assessment (e.g., evaluator training, task analysis, context considerations) and using the evaluation results. On the technological front, we believe that the partial automation of the method is necessary because it would help to make the method easier to use and reduce the time needed for the evaluation. We expect to explore these two aspects in future research. Moreover, an audio-video recording could be integrated explicitly in one or more versions or variants of CW to facilitate the collection, analysis and interpretation of the data (towards what John and Marks proposed in 1997).

We have shown that an evaluation method can be effective for a given system, but not inevitably for other systems. This observation has led some researchers to adapt certain versions to particular system types and application domains. For example, Bligard & Osvalder (2007), Edwards, Moloney, Jacko and Sainfort (2008), Niculesen (2008) and Jasper (2008) have adapted certain versions and variants of CW for evaluating HCI in the medical domain. Antona, Mourouzis and Stephanisis (2007) have adapted CW2 for universal access HCI evaluation. Gonzales, Lorés and Granollers (2007) have adapted CW3 for evaluating Latin-American websites. Ruttkay and Akker (2008) have also adapted CW3 for evaluating the interaction between humans and virtual humans<fnref n="2" />. And finally Wang (2008) has also adapted CW3 for designing and evaluating dynamic intelligent menus. Given the start made by the above researchers, we think that carrying out further experiments with CW in various domains would also be an interesting direction for research.

As for us, our detailed analysis of the literature, our application of the CW method in student practical work in the domain of the Web and interactive software for fifteen years, the various experiments with multimedia systems, as well as the observations made above, have led us to study and design an evaluation assistance environment, exploiting a set of variants of the Cognitive Walkthrough method. The first mockup of this environment is described in Mahatody, Kolski & Sagar (2009). From this platform, we hope to generalize the use of CW for various types of HCI and application domains.

## Acknowledgments:

The authors thank the Nord-Pas de Calais region, the state, CISIT and FEDER which contributed to support this research. This research has been carried out under auspices of GDRE’s “HumAn-MAchine SYstems in Transportation – HAMASYT”. We would like to thank the authors who sent us some of their articles in order to help us with our research, and also the anonymous reviewers for their numerous constructive remarks.

<footnote n="2">² According to Cassell, Sullivan, Prevost & Churchill (2000) (quoted in Ruttlay & Akker (2008)), "Virtual humans (VHs) are synthetic characters produced by computational means, which are intended to look like and communicate as real people do"(p. 90).</footnote>
REFERENCES

Antona, M., Mourouzis, A. & Stephanisis, C. (2007). Towards a Walkthrough Method for Universal Access Evaluation, Universal Access in Human Computer Interaction. In Coping with Diversity, Lecture Notes in Computer Science, 4554, Springer Berlin, Heidelberg, 325-334.

Bastien, J.M. & Scapin, D.L. (1995). Evaluating a user interface with ergonomic criteria, International of Human-Computer Interaction, 7, 2, 105-121.

Bastien, J.M.C. (2004). L'inspection ergonomique des logiciels interactifs : intérêts et limites. In Psychologie ergonomique: tendances actuelles, Collection Le Travail Humain, Hoc J.M. & Darses F (Eds.), Paris.

Bertelsen, O.W. (2004). The activity walkthrough: an expert review method based on activity theory. In Proc. NordiCHI, Tampere, Finland.

Blackmon, M., Polson, P., Kitajima, M. & Lewis, C. (2002). Cognitive Walkthrough for the Web, Proceeding of CHI, ACM Press, 463-470.

Bligard, L.O. & Osvalder, A.L. (2007). An Analytical Approach for Predicting and Identifying Use Error and Usability Problem. In HCI and Usability for Medicine and Health Care, Lecture Notes in Computer Science, 4799, Springer Berlin, Heidelberg, 427-440.

Bligard, L.O. (2007). Prediction of Medical Device Usability Problems and Use Errors – An Improved Analytical Methodical Approach, Chalmers University of Technology, Göteborg.

Card, S.K., Moran, T.P., Newell, A. (1983). The Psychology of human-computer interaction. Hillsdale, NJ: Erlbaum.

Cassell, J., Sullivan, J., Prevost, S., Churchill, E. (2000). Embodied Conversational Agents. MIT Press, Cambridge.

Cockton, G., Lavery, D., Woolrych, A. (2003). Inspection-based evaluations. In J.A. Jacko, A. Sears (Eds.), The human-computer interaction handbook, Lawrence Erlbaum Associates, 1118-1138.

Cuomo, D.L. & Bowen, C.D. (1992). Stages of user activity model as basis for user-centered interface evaluation, Proceeding of the Human Factor and Ergonomics Society 41st annual meeting, 1254-1258.

Desurvise, H.W., Kondziela, J.M., Atwood, M.E (1992). What is gained and lost when using evaluation methods other than empirical testing, In A. Monk, D. Diaper & M.D. Harrison (Eds), People and Computers, Proceeding of Human-Computer Interaction, 89-102.

Dix, H., Finlay, J., Abowd, G., Beale, R. (1993). Human-Computer Interaction, Prentice Hall.

Eden, J. (2007). Distributed cognitive walkthrough (DCW): a walkthrough-style usability evaluation method based on theories of distributed cognition. Proceedings of the 6th ACM SIGCHI conference on Creativity & cognition, June 13-15, 2007, Washington, DC, USA.

Eden, J (2008). The Distributed Cognitive Walkthrough: The Impact of Differences in Cognitive Theory on Usability Evaluation, PhD thesis, Drexel University, USA.

Edwards, P. J., Moloney, K.P., Jacko, J.A., Sainfort, F. (2008). Evaluating usability of a commercial electronic health record: A case study, International Journal of Human-Computer Studies, 66, 718-728.

González, M.P., Lorés, J.Granollers, A. (2007). Assessing Usability Problems in Latin-American Academic Webpages with Cognitive Walkthroughs and Datamining Techniques, Usability and Internationalization. HCI and Culture, Lecture Notes in Computer Science, 4559, Springer Berlin, Heidelberg, 306-316.
Granollers, T. & Lorés, J. (2006). Incorporation of users in the Evaluation of Usability by Cognitive Walkthrough. In Navarro-Prieto R., Vidal J.L. (Eds.), HCI related papers of interacción 2004, Springer Netherlands, 243-255.

Gray, W.D., Salzman, M. C. (1998). Damaged Merchandise? A review of experiments that compare usability evaluation methods. Human-Computer Interaction, 11, pp. 203-261.

Grislin, M. & Kolski, C. (1996). Evaluation des Interfaces Homme-Machine lors du développement des systèmes interactifs, Technique et Science Informatiques, 15 (3), 265-296.

Gutwin, C. & Greenberg, S. (2000). The mechanics of collaboration: developing low cost usability evaluation methods for shared workspaces. In Proc. 9th IEEE WETICE 2000, Gaithersburg MD, 98-103.

Hollan, J., Hutchins, E. & Kirsh, D. (2000). Distributed Cognition: Toward a new foundation for Human-Computer Interaction Research. ACM Transactions on Computer-Human Interaction, 7(2), 174-196.

Huart, J., Kolski, C. & Sagar, M. (2004). Evaluation of multimedia applications using inspection methods: The Cognitive Walkthrough case, Interacting with Computer, 16, 183-215.

Hutchins, E.L., Hollan, J.D. & Norman, D.A. (1985). Direct manipulation Interface. Human-Computer Interaction, 1, 311-388.

IEC (2004). Medical electrical equipment - Part 1-6: General requirements for safety - Collateral standard: Usability IEC.

Jacobsen, N.E. & John, B.E. (2000). Two Case Studies In Using Cognitive Walkthrough For Interface Evaluation, Technical Report Carnegie Mellon University, Pittsburgh, CMU-CS-00-132/CMU-HCI-00-100.

Jaspers, M.W.M. (2008). A comparison of usability methods for testing interactive health technologies: Methodological aspects and empirical evidence, International Journal of Medical Informatics, 78 (5), 340-353.

Jeffries, M., Miller, J.R., Wharton, C. & Uyeda, K.M. (1991). User interface evaluation in real world : a comparison of four techniques, In Proceeding of ACM Computer-Human Interaction, ACM Press, 119-124.

John, E.B. & Marks, S.J. (1997). Tracking the effectiveness of usability evaluation methods, Behaviour & Information Technology, 16(4/5), 188-202.

Kaptelinin, V. (1996). Computer-Mediated Activity : Functional Organs in Social and Developmental Contexts". In Nardi B. (ed.), Context and Consciousness: Activity Theory and Human-Computer Interaction, MIT Press, pp. 45-68.

Karat, C.M., Cambell, R. & Fiegel, T. (1992). Comparison of empirical testing and walkthrough methods in user interface evaluation. Proc. ACM CHI, 397-404.

Kato, T. & Hiro, M. (2006). Beyond Perceivability: Critical Requirements for Universal Design of Information. 8th Annual ACM Conf. on Assistive Technologies, ACM Press, 287-288.

Kato, T. & Hori, M. (2005). Articulating the cognitive walkthrough based on an extended model of HCI. Proc. HCI International, Las Vegas.

Kieras, D. (1985). An approach to the formal analysis of user complexity, International Journal of Human-Computer Studies, 22, 365-394.

Kintsch, W. (1988). The role of knowledge in discourse comprehension: A construction-Integration model, Psychological Review, 95 (2), 63-182.

Kitajima, M, Polson, PG. (1997). A comprehension based model of comprehension. Human-Computer Interaction, Vol. 12, pp. 345-389.
Kitajjma, M., Blackmon, M.H., Polson, P. (2000). A Comprehension-based model of Web navigation and its application to Web usability analysis. In People and Computer XIV, pp. 357-373.

Kitajima, M. (2006). Cognitive Walkthrough for the web. International Encyclopedia of Ergonomics and Human Factors (2nd Edition), Chapter 216.

Landauer, T.K. & Dumas, S.T. (1997). A solution to Plato's problem: The Latent Semantic Analysis theory of acquisition, induction, and representation of knowledge. Psychological Review, 104, 211-240.

Lewis, C. & Wharton, C. (1997). Cognitive Walkthrough, In Handbook of Human-Computer Interaction, M. Helander, T.K. Landaeur, P. Prabhu (eds), Elsevier Science B.V, 717-732

Lewis, C. (1986). A model of Mental Model Construction. In Proceeding of ACM Computer-Human Interaction, 306-313.

Lewis, C. (1988). Why and How to learn why: analysis-based generalization of procedure. Cognitive Science, 12, 211-225.

Lewis, C., Polson, P., Wharton, C. & Rieman, J. (1990). Testing a walkthrough methodology for theory-based design of walk-up and-use interface, In Proceeding of ACM Computer-Human Interaction, ACM Press, 235-242.

Mack, R.L. & Nielsen, J. (1994). Executive Summary. In Nielsen J., R.L. Mack (Eds.). Usability Inspection Methods, Elsevier, pp. 4-23.

Mahatody, T., Sagar, M., Kolski, C. (2007a). Cognitive Walkthrough pour l'évaluation des IHM : synthèse des extensions et évolutions conceptuelles, méthodologiques et technologiques. Proceedings of IHM 2007, 19ème Conférence de l'Association Francophone d'Interaction Homme-Machine (Paris, France, 13-15 novembre 2007), International Conference Proceedings Series, ACM Press, Paris, pp. 143-150.

Mahatody, T., Sagar, M., Kolski, C. (2007b). Cognitive Walkthrough for HCI evaluation: basic concepts, evolutions and variants, research issues. Proceedings EAM'07 European Annual Conference on Human-Decision Making and Manual Control, Technical University Of Danemark, Lyngby, juin.

Mahatody, T., Kolski, C. & Sagar, M. (2009). CWE : Assistance environment for evaluation operating a set of variations of cognitive walkthrough ergonomic inspection method, In D. Harris (Ed.), Engineering Psychology and Cognitive Ergonomics, HCII 2009, LNAI 5639, 52-61.

Monk, A. (1998). Cyclic interaction: a unitary approach to intention, action and the environment. Cognition, 68 (2), 95-110.

Nardi, B.A. (1996). Context and Consciousness: Activity Theory and Human-Computer Interaction. M.I.T. Press, Cambridge.

Niculescu, A. (2008). Affordances in Conversational Interactions with Multimodal QA Systems. In HCI and Usability for Education and Work, Lecture Notes in Computer Science, 5298, Springer Berlin, Heidelberg, 221-236.

Nielsen, J. & Mack, R. (1994). Usability Inspection Methods. John Wiley & Sons, New York.

Nielsen, J. & Molich, R. (1990). Heuristic Evaluation of User Interfaces, Proceedings of CHI conference on Human Factors in Computing System, 249-256.

Nielsen, J. (1992). Finding Usability Problems Through Heuristic Evaluation. In Proc. ACM CHI, pp. 373-380.

Norman, D.A. (1986). Cognitive engineering. In D.A. Norman & S.W. Draper (Eds.), User centered systems design: New perspectives in human-computer interaction, Lawrence Erlbaum Associates, Hillsdale, 31-61.

Norman, D.A. (1999). Affordances conventions and design. Interactions, 6 (3), 38-42

Norman, D.A. (1988). The psychology of everyday things. Basic Books.
Pinelle, D. & Gutwin, C. (2002). Groupware walkthrough: Adding context to groupware usability. In *Proceeding of ACM CHI, ACM Press*, 455-462

Polson, P., Lewis, C., Rieman, J., Wharton, C. (1992). Cognitive Walkthrough: a method for theory-based evaluation of user interface, *International Journal of Man-Machine Studies*, 36, 741-773.

Polson, P.G. & Lewis, C.H. (1990). Theory-based design for easily learned interfaces, *Human-Computer Interaction*, 5 (5), 191-220.

Rieman, J., Davies, S. & Hair, D.C., Esemplare, M., Polson, P., Lewis, C. (1991). An Automated Walkthrough: Description and Evaluation, In *Proceeding of ACM Computer-Human Interaction*, 427-428.

Riihiaho, S. (2000). Experiences with usability evaluation methods, Licentiate's thesis, Helsinki Univ. Of Technology, Laboratory of Information Processing Science.

Rizzo, A., Mandrigiani, E. & Andreadis, A. (1997). The AVANTI Project: Prototyping and Evaluation with a Cognitive Walkthrough Based on the Norman's Model of Action. In *Proceeding of Designing Interactive Systems: Processes, Practices, Methods, & Techniques*, 305-309.

Rowley, D.E. & Rhodes, D.G. (1992). The Cognitive Jogthrough: A fast-paced user interface evaluation procedure. In *Proceeding of ACM Computer-Human Interaction*, 398-395.

Ruttkay, Z. & Akker, R. (2008). Affordances and Cognitive Walkthrough for Analyzing Human-Virtual Human Interaction. In *Verbal and Nonverbal Features of Human-Human and Human-Machine Interaction, Lecture Notes in Computer Science*, 5042, Springer, Berlin, Heidelberg, 90-106.

Ryu, H. & Monk, A. (2004). Analysing interaction problems with cyclic interaction theory: Low-level Interaction Walkthrough. *Psychology J.*, 2 (3), 304-330.

Ryu, H. (2008). Collective Web Usability analysis: cognitive and activity walkthroughs. *International Journal of Web Engineering and Technology*, 4(3), 286-312.

Sears, A. & Hess, D.J. (1999). Cognitive Walkthroughs: Understanding the Effect of Task-Description Detail on Evaluator Performance, *International Journal of Human-Computer Interaction*, 11 (3), 185-200.

Sears, A. (1997). Heuristic Walkthroughs: Finding the problems without the noise. *International Journal of Human-Computer Interaction*, 9, 213-234.

Sears, A. (2003). Testing and evaluation. In J.A. Jacko, A. Sears (Eds.), *The human-computer interaction handbook*, Lawrence Erlbaum Associates, 1091-1092.

Spencer, R (2000). The Streamlined Cognitive Walkthrough method, working around social constraints encountered in a software development company, In *Proceeding of ACM CHI, ACM Press*, 353-359.

Sweeney, M., Maguire, M. & Shackel, B. (1993). Evaluating user-computer interaction: a framework. *International Journal of Man-Machine Studies*, 38, 689-711.

Van der Veer, G.C. & van Velie, M. (2000). M. Task-Based Groupware design: Putting Theory into Practice. In Proc. DIS'2000, 326-337.

Van der Veer, G.C., G.C., Lenting, B.F. & Bergevoet, B.A.J (1996). GTA:Groupware Task Analysis – Modeling Complexity. *Acta Psychologica*, 91, 297-322.

Virzi, R.A. (1997). Usability inspection methods. In M. Helander, T.K. Landauer, P. Prablhu (Eds.). *Handbook of Human-Computer Interaction*, Elsevier, Amsterdam, pp. 705-715.

Wang, X. (2008). Design and Evaluation of Intelligent Menu Interface through Cognitive Walkthrough Procedure and Automated Logging for Management Information System. In *Computer Supported Cooperative Work in Design IV, Lecture Notes in Computer Science*, 5236, Springer Berlin, Heidelberg, 408-418.
Wharton, C., Bradford, J., Jeffrey, R., Franzke, M. (1992). Applying cognitive walkthrough to more complex user interfaces: Experiences, issues, and recommendations, Proceedings of Computer-Human Interaction, ACM Press, 381-388.

Wharton, C., Rieman, J., Lewis, C., Polson, P. (1994). The cognitive walkthrough method: A practitioner's guide. In J. Nielsen & R. L. Mack (Eds.), Usability inspection methods, John Wiley & Sons, New York, pp. 105-140.

Zhang, J & Norman, D.A. (1994). Representations in Distributed Cognitive Tasks. In Cognitive Science, 18, 87-122.
<table><caption>Table 1. Summary of all the CW versions and their evolution</caption><thead><tr><td>Name</td><td>Theoretical and conceptual aspects</td><td>Methodological aspects</td><td>Technological aspects</td></tr></thead><tbody><tr><td>CW1 (Lewis et al, 1990)</td><td>CE+ learning by exploration model</td><td>1. Preparation : choosing the task to be evaluated, breaking up the task into atomic actions<br>2. Evaluation using one form</td><td>- without proposed material</td></tr><tr><td>CW2 (Polson et al, 1992)</td><td>CE+ learning by exploration model, Norman's model of action, Construction-intégration model</td><td>1. Preparation : choosing and describing the task to be evaluated, breaking up the task into atomic actions, identifying the target user of the system, describing the initial goals structures<br>2. Evaluation using three forms</td><td>- Evaluation forms : goal structure, choosing and executing action, modification of goal structure<br>- Proposition of automated version (Rieman et al, 1991)</td></tr><tr><td>CW3 (Wharton et al, 1994)</td><td>Learning by exploration model CE+</td><td>1. Preparation : choosing the task to be evaluated, describing in detail each scenario<br>2. Evaluation taking into account the detail of scenario</td><td>- Proposition of guide</td></tr><tr><td>Heuristic Walkthrough (Sears, 1997)</td><td>CE+ learning by exploration model</td><td>Combining CW, Heuristic Evaluation and Usability Walkthroughs</td><td>- List of heuristics</td></tr><tr><td>Norman' CW (Rizzo et al, 1997)</td><td>Norman's model of action</td><td>As CW3 with questionnaire relying Norman's model</td><td>- Questionnaires focusing on the action</td></tr><tr><td>Streamlined Cognitive Walkthrough (Spencer, 2000)</td><td>Like optimised CW</td><td>As CW3 with reinforcement of the evaluation control</td><td>- Proposition of questionnaires<br>- Proposition of ground rules for conducting the evaluation</td></tr><tr><td>Cognitive Walkthrough for the Web (Blackmon et al, 2002; Kitajima, 2006)</td><td>CoLiDeS model</td><td>4 stages : compiling a set of realistic user goal and intended selection, assessing semantic similarity with LSA, identifying problematic heading/link labels, finding goal-specific problems</td><td>- Analysis tools avalaible at: http://autocww.colorado.edu/HomePage.html</td></tr><tr><td>Groupware Walkthrough (Pinelle and Gutwin, 2002)</td><td>Dedicated to Groupware (collaboration processes)</td><td>- Task modeling (scenario, task, subtask)<br>- task analysis with GTA<br>- Evaluation of task scenario</td><td>- Proposition of questionnaires</td></tr><tr><td>Activity Walkthrough (Bertelsen, 2004)</td><td>Activity theory</td><td>7 stages : identifying typical task to be analysed, contextualization, task vérification, task analysis, evaluation, global verification, reporting</td><td>- Proposition of questionnaires<br>- Synthesis report</td></tr><tr><td>Interaction Walkthrough (Ryu and Monk, 2004)</td><td>Cyclic interaction theory (Monk, 1998)</td><td>- Finding the usability problem relying the interaction (about goal-action, action-effect, goal construction and goal elimination)<br>- Four evaluations consisting of three stages for each (preparation, évaluation, vérification)</td><td>- Proposition of questionnaires</td></tr></tbody></table>
<table><thead><tr><td>Name</td><td>Theoretical and conceptual aspects</td><td>Methodological aspects</td><td>Technological aspects</td></tr></thead><tbody><tr><td>Cognitive Walkthrough with User (Granoller and Lorés, 2005)</td><td>- CW involving the user<br/>- User verbalisation</td><td>- CW with real user intervention.<br/>- Run in two stages: CW by expert, user intervention</td><td>- Proposition of questionnaires</td></tr><tr><td>Extended Cognitive Walkthrough (Kato and Hori, 2005)</td><td>Extended Norman's model of action</td><td>As CW3 but the questionnaires are focusing to the cognitive semantic distance identified by the Extended Norman's model</td><td>- Without additional tools proposed</td></tr><tr><td>Distributed Cognitive Walkthrough (Eden, 2007)</td><td>- Distributed Cognition<br/>- Distributed Cognitive Task</td><td>As CW3 but the questionnaires are focusing on the distributed cognition</td><td>- Without additional tools proposed</td></tr><tr><td>Enhanced Cognitive Walkthrough (Bligard and Osvalder, 2007)</td><td>Learning by exploration model CE+</td><td>Considered as a part of an analytical approach for predicting and identifying use errors and usability problems</td><td>- Proposition of (1) questionnaires as CW3 and (2) list of problem types</td></tr></tbody></table>
**Table 2. Summary of the comparative studies**

CW1 = Cognitive Walkthrough, first version

CW2 = Cognitive Walkthrough, second version

CW3 = Cognitive Walkthrough, third version

HW = Heuristic Walkthrough

NCW = Norman's Cognitive Walkthrough

SCW = Streamlined Cognitive Walkthrough

CWW = Cognitive Walkthrough for the Web

GW = Groupware Walkthrough

AW = Activity Walkthrough

IW = Interaction Walkthrough

CWU = Cognitive Walkthrough with Users

TCW = exTended Cognitive Walkthrough

DCW = Distributed Cognitive Walkthrough

HCW = enHanced Cognitive Walkthrough

EM = Empirical Method

TA = Think Aloud

UT = Usability testing

GL = Guidelines

CA = Claims Analysis

GOMS = Goals, Operators, Methods and Selection rules

UAN = User Action Notation

RS = Reading specification
<table><thead><tr><th rowspan="2">Study</th><th colspan="3">CW</th><th colspan="9">CW variants</th><th colspan="10">Other means of evaluation</th><th rowspan="2">Type of system evaluated</th><th rowspan="2">Type and number of evaluators</th><th rowspan="2">Numerical results concerning the detection of usability problems</th></tr><tr><th>C W 1</th><th>C W 2</th><th>C W 3</th><th>H W</th><th>N C W</th><th>S C W</th><th>G W</th><th>A W</th><th>I W</th><th>C W U</th><th>T C W</th><th>D C W</th><th>H C W</th><th>E M</th><th>T A</th><th>H E</th><th>U T</th><th>G L</th><th>C A</th><th>G O M S</th><th>U A N</th><th>R S</th></tr></thead><tbody><tr><td>Lewis et al. (1990)</td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Mail messaging system</td><td>4 experts</td><td>CW1 detected 50% of the problems found using the empirical method</td></tr><tr><td rowspan="2">Polson et al. (1992)</td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Voice mail directory, Students (number not provided)</td><td>CW2 detected 50% of the problems found using the think aloud method</td></tr><tr><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Text editor Students (number not provided)</td><td>CW2 detected 30% of the problems found using other methods (e.g., user interview, field trouble report)</td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td>Document routing system Students (number not provided)</td><td>CW2 detected 100% of the problems found by subsequent user tests</td></tr><tr><td>Sears (1997)</td><td></td><td></td><td>X</td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td>System for learning the visual effects of rendering algorithms</td><td>20 students</td><td>For Heuristic Evaluation: - on average 1.5 to 3 serious problems, depending on the number of evaluators. - on average 2.5 to 5.8 problems of intermediate severity, depending on the number of evaluators. - on average 3 to 10.7 problems of minor severity, depending on the number of evaluators. - on average 1.7 to 7 non-problems, depending on the number of evaluators</td></tr></tbody></table>
<table><thead><tr><th rowspan="2">Study</th><th colspan="3">CW</th><th colspan="9">CW variants</th><th colspan="10">Other means of evaluation</th><th rowspan="2">Type of system evaluated</th><th rowspan="2">Type and number of evaluators</th><th rowspan="2">Numerical results concerning the detection of usability problems</th></tr><tr><th>CW 1</th><th>CW 2</th><th>CW 3</th><th>H</th><th>N</th><th>S</th><th>C</th><th>G</th><th>A</th><th>I</th><th>C</th><th>T</th><th>D</th><th>H</th><th>E</th><th>T</th><th>H</th><th>U</th><th>G</th><th>C</th><th>G</th><th>O</th><th>A</th><th>N</th><th>S</th></tr></thead><tbody><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Sears (1997)<br>(continued)</td><td></td><td></td><td>X</td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Granoller & Lorés (2004)</td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>
<table><thead><tr><th rowspan="2">Study</th><th colspan="3">CW</th><th colspan="9">CW variants</th><th colspan="10">Other means of evaluation</th><th rowspan="2">Type of system evaluated</th><th rowspan="2">Type and number of evaluators</th><th rowspan="2">Numerical results concerning the detection of usability problems</th></tr><tr><th>CW 1</th><th>CW 2</th><th>CW 3</th><th>H</th><th>N</th><th>S</th><th>C</th><th>W</th><th>G</th><th>A</th><th>I</th><th>C</th><th>T</th><th>D</th><th>H</th><th>E</th><th>T</th><th>H</th><th>U</th><th>G</th><th>C</th><th>G</th><th>O</th><th>A</th><th>N</th><th>R</th><th>S</th></tr></thead><tbody><tr><td rowspan="2">Kato & Hori (2005)</td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Eden (2008)</td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Jeffries et al (1991)</td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>
<table><thead><tr><th rowspan="2">Study</th><th colspan="3">CW</th><th colspan="9">CW variants</th><th colspan="10">Other means of evaluation</th><th rowspan="2">Type of system evaluated</th><th rowspan="2">Type and number of evaluators</th><th rowspan="2">Numerical results concerning the detection of usability problems</th></tr><tr><th>CW 1</th><th>CW 2</th><th>CW 3</th><th>H</th><th>N</th><th>S</th><th>C</th><th>G</th><th>A</th><th>I</th><th>C</th><th>T</th><th>D</th><th>H</th><th>E</th><th>T</th><th>H</th><th>U</th><th>G</th><th>C</th><th>G</th><th>O</th><th>A</th><th>N</th><th>S</th></tr></thead><tbody><tr><td>John &amp; Marks (1997)</td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>John &amp; Marks (1997) (Continued)</td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>John &amp; Marks (1997) (Continued)</td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>John &amp; Marks (1997) (Continued)</td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>
<table><caption>Table 3. Summary of the non-comparative studies</caption><thead><tr><th rowspan="2">Study</th><th colspan="3">CW</th><th colspan="10">CW variants</th><th rowspan="2">Type of system evaluated</th><th rowspan="2">Type and number of evaluators</th><th rowspan="2">Conclusions of the study</th></tr><tr><th>C W 1</th><th>C W 2</th><th>C W 3</th><th>H W</th><th>N C W</th><th>S C W</th><th>C W</th><th>G W</th><th>A W</th><th>I W</th><th>C W U</th><th>T C W</th><th>D C W</th><th>H C W</th></tr></thead><tbody><tr><td>Rizzo et al. (1997)</td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Planning system for trips for the elderly and handicapped</td><td>Members of the design and evaluation team</td><td>The method allowed the team working in various laboratories to avoid ambiguity when communicating the problems found during the evaluation.</td></tr><tr><td>Spencer (2000)</td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Integrated Development Environment (IDE) system</td><td>3 usability specialists, 1 graphic designer, and 4 project managers</td><td>Detection of 24 potential problems in 90 minutes.</td></tr><tr><td>Blackmon et al. (2002)</td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Website (online encyclopedia)</td><td>Students (number varied depending on the experiment)</td><td><b>Experiment 1:</b> 41% "first click" success rate for the goals affected by usability problems detected by CWW compared to 70% for the goals not affected by problems.<br><b>Experiment 2:</b> 68% "first click" success rate for the goals affected by usability problems detected by CWW compared to 89% for the goals not affected by problems.<br><b>Experiment 3:</b> 38% "first click" success rate for the goals affected by usability problems detected by CWW compared to 62% for the goals not affected by problems.</td></tr><tr><td>Pinelle & Gutwin (2002)</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Home care system</td><td>The two authors</td><td>Five main types of problems detected</td></tr></tbody></table>
<table><thead><tr><th rowspan="2">Study</th><th colspan="3">CW</th><th colspan="10">CW variants</th><th rowspan="2">Type of system evaluated</th><th rowspan="2">Type and number of evaluators</th><th rowspan="2">Conclusions of the study</th></tr><tr><th>C W 1</th><th>C W 2</th><th>C W 3</th><th>H W</th><th>N C W</th><th>S C W</th><th>C W</th><th>G W</th><th>A W</th><th>I W</th><th>C W U</th><th>T C W</th><th>D C W</th><th>H C W</th></tr></thead><tbody><tr><td>Huart et al. (2004)</td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Multi-media application: encyclopedia for children</td><td rowspan="4">2 experts (1 usability specialist, 1 data-processing specialist) and 2 non-expert ergonomists</td><td>The expert evaluators found 18 problems compared to 9 for the non-expert evaluators.</td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Multi-media application: interactive museum visit</td><td>The expert evaluators found 16 problems compared to 5 for the non-expert evaluators.</td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Multi-media application: educational software system intended for children four years old and older</td><td>The expert evaluators found 20 problems compared to 5 for the non-expert evaluators.</td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Multi-media application: virtual reality game</td><td>The expert evaluators found 21 problems compared to 4 for the non-expert evaluators.</td></tr><tr><td>Bertelsen (2004)</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>Student project</td><td>Students</td><td>Method considered too complicated by the students</td></tr><tr><td>Ryu & Monk (2004)</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td></td><td></td><td>None (only illustrations are provided in the article)</td><td>Not applicable</td><td>No numerical data is provided, but interesting paths are discussed in terms of the helpfulness of the method for the design process.</td></tr><tr><td>Bligard & Osvalder (2007)</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>X</td><td></td><td></td><td>Dialysis machine</td><td>Not communicated</td><td>No numerical data is provided allowing conclusions to be drawn about the validity of Enhanced CW; nevertheless, the global approach seems effective for the evaluation of complex systems (of the type evaluated).</td></tr></tbody></table>
<table><caption>**Table 4.** Quotations and perspectives on the specificity of the various versions and variants</caption><thead><tr><td>CW, Variants and their evolution</td><td>Quotations</td><td>Our point of view</td></tr></thead><tbody><tr><td>CW1</td><td>"The walkthrough with a very limited investment in resources, approximately an hour per task per interface, can detect almost 50 percent of the problems encountered by users of the design." (Lewis et al, 1990, page 240)</td><td>Intended for walk-up-and-use interfaces with at least a mock-up<br>For each user action, rates the percentage of potential users expected to have problems</td></tr><tr><td>CW2</td><td>"The cognitive walkthrough is an evaluation methodology that focuses on ease of learning. It is especially appropriate for the development of applications where users must (or prefer) to master a new application or function by learning through exploration." (Polson et al., 1992, page 742)</td><td>Intended for walk-up-and-use interface with at least a mock-up<br>For each walkthrough question, rates the percentage of potential users expected to have problems</td></tr><tr><td>CW3</td><td>"The cognitive walkthrough method promises to be a valuable addition to the designer's suite of tools. The new version of a method is flexible enough to fit into given software development process. The method identifies problems with a design early in the process and, by describing the reasons for those problems, it suggests design changes early on." (Wharton et al. 1994, page 139)</td><td>Uses a success/failure story to encourage the choice of an action</td></tr><tr><td>HW</td><td>"A new technique is described that combines the benefits of heuristics evaluation, cognitive walkthroughs, and usability walkthrough." (Sears, 1997, page 243)</td><td>This method that associates the approaches well known by usability professionals, particularly heuristic evaluation. This makes it possible to potentially detect more usability problems.</td></tr><tr><td>NCW</td><td>"The design issues are: the problems deriving from distribution of the teams collaborating to the project in several cities (sometimes different European countries); and the need to face high-level interaction problems in the evaluation process. One important action taken to face these issues was the development of a variation of the Cognitive Walkthrough based on the Norman's model of action." (Rizzo et al, 1997, page 305)</td><td>This method allows high-level problems to be solved (unlike IW, see below). It is interesting as a first approach to the evaluation of an interactive system, without going into detail about its realization.</td></tr></tbody></table>
<table><thead><tr><td>CW, Variants and their evolution</td><td>Quotations</td><td>Our point of view</td></tr></thead><tbody><tr><td>SCW</td><td>"Managers, developers, and other team members are pressured for time, tend to lapse into lengthy design discussions, and are sometimes defensive about their user-interface designs. By enforcing four ground rules, explicitly defusing defensiveness, and streamlining the cognitive walkthrough method and data collection procedures, these social constraints can be overcome, and useful, valid data can be obtained. This paper describes a modified cognitive walkthrough process that accomplishes these goals." (Spencer, 2000, page 353)</td><td>This variant has a social dimension that does not exist in the other variants.</td></tr><tr><td>CWW</td><td>"The new cognitive walkthrough for the Web (CWW) is superior for evaluating how well websites support users' navigation and information search task." (Blackmon et al., 2002, page 463)</td><td>This method allows the design of Web pages under construction to be critiqued as they are completed or the pages of an online site to be evaluated. It is an automated method, which is not the case for all the others.</td></tr><tr><td>GW</td><td>"The technique is a substantive modification of cognitive walkthrough to include consideration for the complexities of teamwork. The two components of groupware walkthrough are a task model for identifying and analysing real-world collaborative tasks, and a walkthrough process for assessing a system's support for those tasks." (Pinelle and Gutwin, 2002, page 455)</td><td>This task inspection method uses GTA. It is suitable for evaluation using collaborative scenarios.</td></tr><tr><td>AW</td><td>"The method is a modified version of the cognitive walkthrough, and is aimed to systematically include the context and history of use." (Bertelsen, 2004, page 251)</td><td>This method is based on activity theory. It systematically integrates the use context, which is not the case for the other variants. The advantage of this method is that it allows a compromise to be reached: the contexts are taken into account, without requiring an in-depth description.</td></tr><tr><td>IW</td><td>"The method is a modified version of cognitive walkthrough and the analysis focuses on the issue of direct concern to the practitioner who intends to identify low-level interaction problems in their design specification." (Ryu et Monk, 2004, page 304)</td><td>This method is an alternative for analyzing low-level HCI.</td></tr></tbody></table>
<table><thead><tr><td>CW, Variants and their evolution</td><td>Quotations</td><td>Our point of view</td></tr></thead><tbody><tr><td>CWU</td><td>"The new variant which can be regarded as a new method incorporates users in way that combines the advantages of the initial method with those contributed by the availability of end users in the evaluation of interactive systems." (Granollers et Lores, 2006, page 254)</td><td>This method combines expert and user interventions, unlike all the other versions and variants. It is an interesting approach that integrates "think aloud" verbalization.</td></tr><tr><td>Extended CW</td><td>"Applied to a Web design evaluation study, the extended CW was shown to be more effective in identifying accessibility and usability problems while remaining as efficient as the currently-practiced CW." (Kato et Hori, 2007, page 1)</td><td>This is an interesting method for the evaluators without a lot of knowledge about cognitive psychology. It is intended to facilitate detection of accessibility problems.</td></tr><tr><td>DCW</td><td>"The Distributed Cognitive Walkthrough (DCW) method is useful for the identification of aspects of usability issues related to interaction between people, artifacts, and information, across dimensions such as time, space, and social structures." (Eden, 2008, page 2)<br>"DCW method uses concepts from distributed cognitive theory to view interaction between people and information as transcending interactions with graphical user interfaces, allowing the DCW method to be useful for evaluation of design ideas in almost all areas of interaction design; for example, evaluation of ubiquitous computing, service design (e.g. Starbucks customer/worker experience), and mathematical notations (e.g. Newton versus Leibniz Calculus notation)." (Eden, 2007, page 1)</td><td>This method offers interesting prospects in terms of general interactions (i.e., not only between one human and one interactive system). It is based on distributed cognition, which is not the case for the other versions and variants.</td></tr><tr><td>Enhanced CW</td><td>"The approach is based on the methods Hierarchical Task Analysis (HTA), Enhanced Cognitive Walkthrough (ECW) and Predictive Use Error Analysis (PUEA)." (Bligard, 2007, page 427)<br>"ECW employs a clearly detailed procedure for simulating the user's problem-solving process in each step of the interaction. Throughout the interaction, it is checked whether the supposed user's established goal and previous experience will lead to the next correct action." (Bligard, 2007, page 432)</td><td>This method classifies the problems according to their severity, proposing 5 problem categories that allow a better identification. It is integrated into more global approach to complex systems.</td></tr></tbody></table>