English 421: Technical Writing

 http://delivery.acm.org/10.1145/810000/801585/p78-neal.pdf?key1=801585&key2=6078027221&coll=GUIDE&dl=GUIDE&CFID=11911542&CFTOKEN=69915750

In this article, it breaks down a step-by-step process to document the usability of software.  While its mid-80's graphics aren't the most helpful thing in the world, its use of bulleted points really help to clarify the main points of each step of the process.  One of the keys of the documentation process is to set some quantitative criteria before getting started, so when it comes time to test the product, then there are some means by which to do so.

Overall, this article does an excellent job of giving specific examples on how to document a software's usability.  To provide a real-life example, it documents the usability of what appears to be now an outdated software program.  While the software itself might not be relevant anymore, their method of breaking the process down into specific tasks for the user to complete and then testing their ability to perform these tasks is certainly relevant.

- Pat Connaughton