In this case, what are the requirements?
Well, we have a description or a prototype of this interface.
Ours will be paper based.
The description of the task is simply to authenticate and log in.
The actions the user has to take to complete the task is to input a gesture.
And our user background is actually going to be a pretty general set of
users from,
very familiar with technology to those who don't have a lot of background with it.
So, there's our prototype.
When we're working with it, we'll look to see if users know how to perform
the action, if they can see the interface control we've given them, if they
know that it'll do what they want, and if they understand the feedback they get.
So, let's look at a video of doing a cognitive walkthrough with this interface.
So here's our paper prototype, and you can see I've got two screens developed here.
I have this overlay, which allows me to have the setup for
when a person's initially creating a gesture to log in.
So it says, create a distinctive gesture to log in,
could be a signature or a sketch.
Just make it memorable.
To test this,
we'd actually have someone pretend that they were interacting with the interface.
So they would do their gesture in the middle and click Save.
Then me as someone running the paper prototype would remove this.
Now we've saved the gesture, and this is our log in screen.
It says, enter your distinctive gesture to log in.
I would do the gesture here, and then we can confirm that the user is logged in.
I didn't create a separate page that shows the user is logged in, but
that would be a common thing to do with a paper prototype.
Now, to do a cognitive walkthrough, we need a description or
prototype of the interface.
That's what we have here, and that I've just described.
We need a task description that's basically to log in.
Normally, logging in isn't a great task,
because it's not the user's goal to simply log in.
They want to log in to do something else.
But since we're just checking the log in system here, we'll make that our task.
The list of actions to complete the task would be to click the on button,
which I've labeled on the side here,
I've drawn it out big like that because if you have embedded buttons in an interface,
you obviously can't see that on a two dimensional drawing.
So if the user wants to log in, they would click this on button,
they would get this log in screen coming up, enter your distinctive gesture,
I would enter it, and then the user would get logged in.