Usability Testing

As a necessity for computer interfaces, it is important to test the quality and the function of all the implemented features to ensure that everything is working in proper order. The same applies for software and their hardware counterparts, as each needs repetitive and stringent means of testing to insure against the likelihood of error or defect.

In the realm of computer science, software is an always changing field. As the famous saying goes
"Products are never finished, only abandoned.", figuratively: it means that while the product itself has fulfilled all the requirements, it is not particular "finished" in terms of efficiency or portability. There is always for improvement, just never enough time.

To make ends meet in software working envornments, the traditional means of development used to be known as the "waterfall method". This method is nearly obselete due to its inflexible structure and quality control. Following the flow chart below, companies would require a software team to implement each category in its own independent workflow, without any involvement from any of the other categories. This has a tendency to create a frustrating workflow, especially if requirements or specifications change (which they WILL). It does not allow the programmer to go back and modify any previous works since it will be too late.


To counteract the frustration of the waterfall method, the iterative design was implemented. Instead of having each process being an independent and detached work process, testing occurs at every level. This way, quality and usability can be tested thoroughly to ensure optimum functionality.


Nielsen, J. (n.d.). Nielsen Norman Group. Parallel & Iterative Design + Competitive Testing = High Usability. Retrieved April 13, 2014, from http://www.nngroup.com/articles/parallel-and-iterative-design/

Waterfall model. (n.d.). Princeton University. Retrieved April 13, 2014, from https://www.princeton.edu/~achaney/tmve/wiki100k/docs/Waterfall_model.html