Community Documentation

The improvement process

Last updated August 2, 2011. Created by nielsbom on August 31, 2008.
Edited by Bojhan, bekasu. Log in to edit this page.

One improvement process flow could be as follows:

1- User Research to discover areas where usability is lacking.

2- Analyze results from User research to prioritize issues.

3- Paper/Static mock ups of solutions to the usability issues.

(Optional: Further Usability Analysis and Technical Analysis on feasibility of solution provided by the paper/static mock up.)

4- Hi-Fidelity Prototypes of static mock ups.

5- Module/Code Development.

6- User Research (user testing) on whether the final module/user flow have a positive outcome concerning the issues found in Step 1.

7- Analyze results to find out if any new usability issues appear and/or find unresolved usability issues. Continue issue resolution (if any issues are found) by returning to Step 3.

========
Place holder
Usability is a term used to denote the ease with which people can employ a particular tool or other human-made object in order to achieve a particular goal. Usability can also refer to the methods of measuring usability and the study of the principles behind an object's perceived efficiency or elegance.

In human-computer interaction and computer science, usability usually refers to the elegance and clarity with which the interaction with a computer program or a web site is designed. The term is also used often in the context of products like consumer electronics, or in the areas of communication, and knowledge transfer objects (such as a cookbook, a document or online help). It can also refer to the efficient design of mechanical objects such as a door handle or a hammer.

Archive

Drupal’s online documentation is © 2000-2012 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0. PHP code is distributed under the GNU General Public License.
nobody click here