HELLO MY GROUP MEMBERS
CONGRATULATIONS on ourPhenomenal success !!! We have improved a lot from our first crap presentation .. hahaha....
All well ends well..
Thank you for your co-operation... and listening to my shouts .... hahaha...
Regards,
Anushree..... xxx
Sunday, 5 April 2009
Friday, 3 April 2009
Saturday, 28 March 2009
Hi-Fid Prototype
Hi guys,
I'll be making the next advnced version of HMS P1 now in powerpoint.
All changes will be made acc to the previous c/w. W'll then have a think aloud of the prototype pnthe powerpoint and record it.
Friday, 20 March 2009
The following videos canbe viewed under my channel in youtube which is chintandevhanda. The links are
Prototype Demonstration: http://www.youtube.com/watch?v=eCraeYhrUG8
Think Aloud: http://www.youtube.com/watch?v=cPxvwh7sPlU
Wednesday, 18 March 2009
Evaluation
What is evaluation?
Something you do to test your prototype whether it is working properly. Ask users to test it because they are the one who will use the system in future.
There are 2 types if evaluations:-
1) Formative.
2) Summative.
Formative Evaluation is within the design process evaluation. This provides ways of learning about the design options, user group and analysis of prototypes.
Summative evaluation is a finished system and assesses the quality of the system.
Cognitive Walkthrough:-
An approach to evaluation without users. i.e. formative evaluation. Team members perform this task. User is given a set of relevant questions that are applied to each action. Team goes through each action that the user need to perform on the system. For each and every action, The design is reviewed and problematic features should be noted so that designs can be explored.
Few principles of cognitive design:
1) Automate unwanted workload - Remove mental calculations, estimations, comparisons and any unnecessary thinking to free cognitive resources for high-level tasks.
2) Reduce uncertainty - Display data in a manner that is clear.
3) Fuse data - Bring together lover-level data into a higher-level data to reduce cognitive load.
4) Present new information with meaningful aids to interpretation - Use everyday terms, metaphors, etc.. Use familiar framework.
5) Use names that are conceptually related to function - Names should be context-dependent.
6) Group data in consistently meaningful ways - Within screen, group data logically, across screen group data consistently to reduce search time.
7) Limit data-driven tasks - Reduce the time spent understand raw data by using appropriate colors and graphics.
8) Include in the displays only that information needed by the operator at a given time - Exclude irrelevant information that is not relevant to common tasks so that users can focus on critical data.
9) Provide multiple coding of data - Provide data in multiple formats or levels of detail to satisfy different user preferences.
10) Practice judicious redundancy - To resolve the possible conflict between principles 6 and 8, it is sometimes necessary to include more information than is needed.
Overview of the cognitive walkthrough process:
1- Define inputs to the walkthrough
a) Identification of the users.
b) Sample tasks for evaluation.
c) Action sequences for completing the tasks.
d) Description or implementation of the interface.
2- Organize the analysts
3- Walk through the action sequences for each task
a) Tell a credible story, Considering.........
b) Will the user try to achieve the right effect?
c) Will the user notice that the correct action is available?
d) Will the user associate the correct action with the effect that the user is trying to achieve?
e) If the correct action is performed, will the user see that progress is being made toward a solution of the task?
4- Record critical information
a) User knowledge requirements.
b) Assumptions about the user population.
c) Notes about side issues and design changes.
d) The credible success story.
5- Revise the interface to fix the problems
This is all what i have found about cognitive walkthrough.
Something you do to test your prototype whether it is working properly. Ask users to test it because they are the one who will use the system in future.
There are 2 types if evaluations:-
1) Formative.
2) Summative.
Formative Evaluation is within the design process evaluation. This provides ways of learning about the design options, user group and analysis of prototypes.
Summative evaluation is a finished system and assesses the quality of the system.
Cognitive Walkthrough:-
An approach to evaluation without users. i.e. formative evaluation. Team members perform this task. User is given a set of relevant questions that are applied to each action. Team goes through each action that the user need to perform on the system. For each and every action, The design is reviewed and problematic features should be noted so that designs can be explored.
Few principles of cognitive design:
1) Automate unwanted workload - Remove mental calculations, estimations, comparisons and any unnecessary thinking to free cognitive resources for high-level tasks.
2) Reduce uncertainty - Display data in a manner that is clear.
3) Fuse data - Bring together lover-level data into a higher-level data to reduce cognitive load.
4) Present new information with meaningful aids to interpretation - Use everyday terms, metaphors, etc.. Use familiar framework.
5) Use names that are conceptually related to function - Names should be context-dependent.
6) Group data in consistently meaningful ways - Within screen, group data logically, across screen group data consistently to reduce search time.
7) Limit data-driven tasks - Reduce the time spent understand raw data by using appropriate colors and graphics.
8) Include in the displays only that information needed by the operator at a given time - Exclude irrelevant information that is not relevant to common tasks so that users can focus on critical data.
9) Provide multiple coding of data - Provide data in multiple formats or levels of detail to satisfy different user preferences.
10) Practice judicious redundancy - To resolve the possible conflict between principles 6 and 8, it is sometimes necessary to include more information than is needed.
Overview of the cognitive walkthrough process:
1- Define inputs to the walkthrough
a) Identification of the users.
b) Sample tasks for evaluation.
c) Action sequences for completing the tasks.
d) Description or implementation of the interface.
2- Organize the analysts
3- Walk through the action sequences for each task
a) Tell a credible story, Considering.........
b) Will the user try to achieve the right effect?
c) Will the user notice that the correct action is available?
d) Will the user associate the correct action with the effect that the user is trying to achieve?
e) If the correct action is performed, will the user see that progress is being made toward a solution of the task?
4- Record critical information
a) User knowledge requirements.
b) Assumptions about the user population.
c) Notes about side issues and design changes.
d) The credible success story.
5- Revise the interface to fix the problems
This is all what i have found about cognitive walkthrough.
Think Aloud
So I need to save a task in the calendar?
I see a clock, few name which doesn’t make any sense realy…umm….but where is the calendar……..
And yea I can even see a bell here
…there should be some login system in here ..oh do I need to swipe in my finger …
…but how will it know its me….
Anyways..lets me try that….
Its taking a few moments to respond
Umm..it says identified new user…must be me
Enter your full name:
Jahedur Rahman
Umm..i click on save
Oh theres loads of stuffs on this page
Now m looking for calendar..there it is the icon…I clicking it…
Oh here it is…a calendar…..
I presume.. u need to click one of these date.. o each one of them has a calendar
Oh something is happening
Well it looks Iike I need to give a title to my task
And now m going to the description.. I am typing in the message
I”ll save it…nd thts done….
Chintan: Not yet
I see a small log off button…nd its done
Monday, 16 March 2009
CW
Chintan ,
What you mean "No user button"??? I didnt understand that. And other's we need to think. Again what you mean by color coding in calender?, Because we have already explained that in our 2nd presentation-prototyping.
Two more things, Text Reader button should be in brail(whateva the spelling is.... haha) so that blind people can recognise.
Other thing, you know if there is a msg for everyone thn there should be a common screen without any kinda login process so that everyone can see.. did you get my point?
What you mean "No user button"??? I didnt understand that. And other's we need to think. Again what you mean by color coding in calender?, Because we have already explained that in our 2nd presentation-prototyping.
Two more things, Text Reader button should be in brail(whateva the spelling is.... haha) so that blind people can recognise.
Other thing, you know if there is a msg for everyone thn there should be a common screen without any kinda login process so that everyone can see.. did you get my point?
CW
Some of the really important things whichis missing in our design is
1. No user Button
2. No option Button to change the size, color of text.
3. No feedback (No confirmatory message after the task is done)
4. Our assumed color codes for the calendar wont make sense for users.
Subscribe to:
Posts (Atom)