| LIN | NSN | Item Name | PBIC | Type | DND | Qnty |
|---|---|---|---|---|---|---|
| NETWORK SWITCHING HUB: SYSW40KF | 9 | TPE | N | 1 | ||
| ELLIPTICAL FITNESS CROSSTRAINING | 9 | TPE | N | 1 | ||
| GAME VIDEO ELECTRONIC: PLAYSTATI | 9 | TPE | N | 1 | ||
| TELEVISION: PANASONIC/CT-27D20 | 9 | TPE | N | 2 | ||
| TELEVISION RECEIVER HOME TYPE, W | 9 | TPE | N | 2 | ||
| TELEPHONE SET: PHONE 7940 CISCO | 9 | TPE | N | 1 | ||
| CISCO IP PHONE: 7960 | 9 | TPE | N | 6 | ||
| DISH SATELLITE: K040 | 9 | TPE | N | 2 | ||
| SATELLITE RECEIVER: R1200 | 9 | TPE | N | 1 | ||
| POWER DISTRIBUTION--(B4030205) | 9 | TPE | N | 1 | ||
| MODEM COMMUNICATION DEVICE: KLAS | 9 | TPE | N | 1 | ||
| 3COM SUPERSTACK SWITCH: 4400 | 9 | TPE | N | 1 | ||
| BATTERY BACK-UP: SMART UPS BATTE | 9 | TPE | N | 1 | ||
| LAPTOP GATEWAY :450RGH | 9 | TPE | N | 17 | ||
| PRINTER LASERJET: LASERJET 4250 | 9 | TPE | N | 1 | ||
| PORTABLE EYE WASH STATION: SPEAK | 9 | TPE | N | 1 | ||
| SAFE:YB-920A | 9 | TPE | N | 1 | ||
| WASHING MACHINE: WW8100 | 9 | TPE | N | 2 | ||
| REFRIGERATOR: BC-86 | 9 | TPE | N | 2 | ||
| REFRIGERATOR:ARCELIK R63341 | 9 | TPE | N | 1 | ||
| FREEZER CHEST : BD/C-355 | 9 | TPE | N | 5 | ||
| AIR CONDITIONER: PEED ECOS 2 YOR | 9 | TPE | N | 1 | ||
| EXERCISE EQUIPMENT, TREADMILLS: | 9 | TPE | N | 1 | ||
| EXERCISE EQUIPMENT: EXERCISE BIK | 9 | TPE | N | 1 |


Information for designers
What is a cognitive walkthrough?
The cognitive walkthrough is a method for evaluating the learnability of a product or service.
In
this method, a small group of evaluators from a product team walk through a set of tasks and ask
questions
at each step in the task that get at whether the user would know what to do at that step and if the user
does the right thing, will that user know if she has made progress toward the task goal. If the answer
is “no” to the walkthrough questions, a usability defect is recorded.
source: https://doi.org/10
.1016/B978-0-12-410391-7.00004-X
When should the cognitive walkthough be used?
The cognitive walkthrough can be used during any phase of the development process but is most suited to
the
design stage where a functional specification and other design documents that provide enough information
for
the creation of action sequences (user inputs and system responses) for a set of tasks
Resources
Personnel
The cognitive walkthrough can be conducted by an individual or group. In a group
evaluation, these are the important roles:
- Facilitator. The facilitator is generally the organizer and maestro of the walkthrough
process.
The facilitator is responsible for making
sure that the walkthrough team is prepared for the session and follows the rules of good meeting
management.
- Notetaker. The notetaker records the output of the cognitive walkthrough.
- Product expert. Because the cognitive walkthrough can be conducted early in the design
stage (e.g., after requirements and a functional specification), a product expert is desired to
answer
questions that members of the walkthrough team may have about the system’s
features or feedback.
- Evaluators. Evaluators are representatives from the product team. These representatives can
be
usability practitioners, requirements engineers, business analysts, developers, writers, and
trainers.
Documents and material
- User profile. Description of the primary users who perform the tasks that
will be evaluated in a cognitive walkthrough.
- Task list. The task list should describe the task in a realistic and concrete manner.
- Action sequence for each task in the task list. includes the information such as date,
analysts, users, interface, task, action sequence, comments etc...
- Problem reporting form. This is the form for recording the problems that emerge from the
walkthrough.
- Representation of the UI. Flip charts, electronic display of outputs from cognitive
walkthrough, prototypes, or working features.
Planning procedure of a cognitive walkthrough
- Define the users of the product. Different personas might take different paths through a
system. If you have multiple personas, you can walk through the system with a focus on the
attributes of
each persona that could have an impact on how easily they can learn how to perform tasks with the
target system.
- Determine what tasks and task variants (different ways to do the same task) are most appropriate
for the walkthrough. The choice of tasks must balance complexity, realism, and the time
allocated to
the walkthrough. One strong recommendation is that the first task in the walkthrough be relatively
simple so the team can learn the method before moving on to longer and more complex tasks.
- Develop the ground rules for the walkthrough. Ours are available here.
- Generate the action sequences for each task. An action sequence is a detailed description of
the actions the target users must take to complete a task and the associated system responses at
each
step.
- Provide a representation of the interface. This representation can be a detailed text
scenario, an operating procedure, a set of sketches, a storyboard, a paper prototype, a partially
working prototype, or a fully working product.
- Assemble a group of evaluators for the cognitive walkthrough. Candidates include usability
practitioners, writers, trainers, product managers, quality engineers, and developers.
Conducting a cognitive walkthrough
The cognitive walkthrough involves the following main steps:
- Walk through the action sequences for each task from the perspective of the “typical” users
of the
product.
- Record success stories, failure stories, design suggestions, problems that were not the
direct
output of the walkthrough, assumptions about users, comments about the tasks, and other information
that may be useful in design.
The four-question approach
Wharton et al. (1994, p. 106) propose an approach based on four questions to tackle
each of the items in the action sequences for each task (step 1 of the walkthrough protocol):
- Will the user try to achieve the right action?
- Will the user notice that the correct action is available?
- Will the user associate the correct action with the effect that the user is trying to achieve?
- If the correct action is performed, will the user see that progress is being made toward solution of
the
task?
After the Cognitive Walkthrough
After the walkthrough, follow these steps:
- Bring the appropriate stakeholders together to review the results of the cognitive walkthrough.
- Discuss potential solutions to the UI problems that were found in the walkthrough.
- Determine which solutions you will apply to the product.
- Evaluate the cognitive walkthrough process, and determine if there are improvements you could make
for
subsequent walkthroughs.
Informal user testing
The cognitive walkthrough will have uncovered some issues with the prototype, which must be addressed
(possibly scraping the prototype and restarting). Based on the fixed prototype, you want to perform user
testing. This procedure aims at evaluating both the low-fi prototype and the conceptual model, as well
as
validating the task examples.
When running the participants through the testing protocol, it is best to have at least two team members
at each session: one for managing the session and the other for taking detailed notes. With the user
consent, the user testing sessions are video recorded and transcribed in order to replay them with the
entire team for more detailed analysis.


{% extends "error.html" %} {% block title %}404 - Page not found{% endblock %} {% block main %}
If you think this a mistake on our side please let us know so we can fix the issue.
Otherwise click the button bellow and let us take you back home!


Creative Idea Generator
Helps to generate creative ideas by creating mental collisions.
Data Set 1
Enter Your First Dataset Here
Facebook
Twitter
Stumbleupon
Tinder
Blog
Data Set 2
Enter Your Second Dataset Here
Motorcycles
Habits
Nomads
Finance Planning
Add Sample Data Sets
Clear Datasets
Randomize My Ideas


Local header file for xtio functions. More...
Go to the source code of this file.
Functions | |
| static uint32_t | qspi_is_rx_full (Qspi *qspi) |
| static void | qspi_end_transfer (Qspi *qspi) |
| Ends ongoing transfer by releasing CS of QSPI peripheral. More... | |
| static void | qspi_set_memory_mode (Qspi *qspi) |
| Set QSPI to Memory mode. More... | |
| static void | qspi_set_spi_mode (Qspi *qspi) |
| Set QSPI to SPI mode (Master mode only). More... | |
| static void | qspi_enable_wait_data_read_before_transfer (Qspi *qspi) |
| Enable waiting RX_EMPTY before transfer starts. More... | |
| static void | qspi_disable_wait_data_read_before_transfer (Qspi *qspi) |
| Disable waiting RX_EMPTY before transfer starts. More... | |
| static void | qspi_set_chip_select_mode (Qspi *qspi, uint32_t csmode) |
| Set Chip Select Mode. More... | |
| static void | qspi_set_bits_per_transfer (Qspi *qspi, uint32_t bits) |
| Set the number of data bits transferred. More... | |
| static void | qspi_set_minimum_inactive_qcs_delay (Qspi *qspi, uint8_t uc_dlybct) |
| Set qspi minimum inactive QCS delay. More... | |
| static void | qspi_set_delay_between_consecutive_transfers (Qspi *qspi, uint32_t uc_dlycs) |
| Set qspi delay between consecutive transfers. More... | |
| static void | qspi_set_transfer_delay (Qspi *qspi, uint8_t uc_dlybs) |
| Set qspi clock transfer delay. More... | |
| static uint16_t | qspi_read_spi (Qspi *qspi) |
| Read QSPI RDR register for SPI mode. More... | |
| static void | qspi_write_spi (Qspi *qspi, uint16_t w_data) |
| Write to QSPI Tx register in SPI mode. More... | |
Local header file for xtio functions.
|
inlinestatic |
Disable waiting RX_EMPTY before transfer starts.
| qspi | Pointer to an QSPI instance. |
|
inlinestatic |
Enable waiting RX_EMPTY before transfer starts.
| qspi | Pointer to an QSPI instance. |
|
inlinestatic |
Ends ongoing transfer by releasing CS of QSPI peripheral.
| qspi | Pointer to an Qspi instance. |
|
inlinestatic |
Most of these function are local to qspi.c and should probably stay so. Use config/init functions instead.
|
inlinestatic |
Read QSPI RDR register for SPI mode.
| qspi | Pointer to an Qspi instance. |
|
inlinestatic |
Set the number of data bits transferred.
| qspi | Pointer to an QSPI instance. |
| bits | Bits per transfer. |
|
inlinestatic |
Set Chip Select Mode.
| qspi | Pointer to an QSPI instance. |
| csmode | Chip select mode to be set. |
|
inlinestatic |
Set qspi delay between consecutive transfers.
| qspi | Pointer to a Qspi instance. |
| uc_dlycs | Time to be delay. |
|
inlinestatic |
Set QSPI to Memory mode.
| qspi | Pointer to an QSPI instance. |
|
inlinestatic |
Set qspi minimum inactive QCS delay.
| qspi | Pointer to a Qspi instance. |
| uc_dlybct | Time to be delay. |
|
inlinestatic |
Set QSPI to SPI mode (Master mode only).
| qspi | Pointer to an QSPI instance. |
|
inlinestatic |
Set qspi clock transfer delay.
| qspi | Pointer to a Qspi instance. |
| uc_dlybs | Delay before QSCK. |