Showing posts with label task analysis. Show all posts
Showing posts with label task analysis. Show all posts
Thursday, 15 March 2007
Prototype Testing - Scenarios
Below are the key scenarios to be used for the testing of the touch screen interface and the watch, written in the use case style used in earlier stages. These scenarios will be combined with a mockup of the system.
Thursday, 1 March 2007
Example task
John and Rana are working on the initial task analysis, so I'm just posting an example to follow up from the post about use cases. Obviously the tasks at this stage are slightly vague as we don't know all the details about the product yet (e.g. how exactly the user inputs information).
Name: Logging and inputting weight information.
Initiator: User
Goal: User takes a measurement of their weight and stores it in the device, ready for viewing and/or sending to their GP later.
Main Success Scenario:
1. User weighs themselves on a separate device (e.g. scales).
2. User navigates through the device to the section for inputting weight.
3. User inputs their weight.
4. User saves the information.
Possible Issues:
2. User may have difficulty finding the relevant section.
3. User may input the incorrect amount.
3b. User may input the amount in an unexpected format (e.g. lbs, when the device was expecting kg).
4. User may forget to save the information.
Name: Logging and inputting weight information.
Initiator: User
Goal: User takes a measurement of their weight and stores it in the device, ready for viewing and/or sending to their GP later.
Main Success Scenario:
1. User weighs themselves on a separate device (e.g. scales).
2. User navigates through the device to the section for inputting weight.
3. User inputs their weight.
4. User saves the information.
Possible Issues:
2. User may have difficulty finding the relevant section.
3. User may input the incorrect amount.
3b. User may input the amount in an unexpected format (e.g. lbs, when the device was expecting kg).
4. User may forget to save the information.
Tuesday, 27 February 2007
Use Case Webpage
For the MSc Internet Workshop module we have been given very useful instructions on writing use cases for software in more detail than you would get with a use case diagram. Although the page uses this specification in a more technical context, I think this could easily be adapted for our project, and is particularly useful in documenting at which stages in a task an elderly person may have problems. e.g. UTOPIA Project video:
Name: Installing a webcam driver
Initiator: Elderly woman
Goal: Given a webcam, a PC and a set of instructions, set up the webcam so that user can talk to her relatives.
Main Success Scenario:
1. Turn computer on
2. Log in
3. Place webcam CD into CD drive
4. etc
Potential Issues:
1. User cannot find the power button
2. User has forgotten their password
3. User does not know how to open CD drive
3b. User does not know which way the CD goes
4. etc
This method could also be applied using our personas as different initiators, thus possibly creating different issues.
Name: Installing a webcam driver
Initiator: Elderly woman
Goal: Given a webcam, a PC and a set of instructions, set up the webcam so that user can talk to her relatives.
Main Success Scenario:
1. Turn computer on
2. Log in
3. Place webcam CD into CD drive
4. etc
Potential Issues:
1. User cannot find the power button
2. User has forgotten their password
3. User does not know how to open CD drive
3b. User does not know which way the CD goes
4. etc
This method could also be applied using our personas as different initiators, thus possibly creating different issues.
Subscribe to:
Posts (Atom)