Blogs

Individual Blog: Adobe Photoshop Group

We met last night in Hicks to decide what is going into the usibility report. We came up with a broad overview of what is going into the report. Jordan is wriring the background, Reston is writing the method, and shatio is writing the discussion. I am going to take all that and revise it and put the final touches on it and try to make it all flow cohessively... Also I have put the final touches on the document itself and i am waiting for Jordan to send me an outline so I can put it in a professional format...

--- Roya Akhavain

Individual Blog - Webmail Documentation

This week, our group compiled data from the user testing we conducted and created our usability report. In the form of a memorandum directed to Purdue University, we described problems users experienced during the testing and documented changes we deemed necessary based on the outcome of the testing. Overall, the usability testing was a success; each subject was able to complete the tasks asked of them with minimal problems or complications. In the next few days, we will revise the usability report before we turn the entire project in to the professor.

Individual Log Website Design

This week was very busy as we did the testing and final draft of the complete project including the results of the test. Test went smoothly as I brought two subjects to test the product. I helped make the final report in our group meeting. In our group meeting we accomplished the task at hand of analyzing the results of the test and making the final report. I helped make part of the report with the test subjects reactions to the product.

Week 4- Purdue Libraries Individual Blog

 This week the usability test was perform on Monday, April 26, 2009 at Matthews at 7pm. There were 8 participants for our study.  I recorded observations made during the testing that may benefit the final paper. I worked on editing the final technical documentation for the Purdue libraries.

Documentation Project Blog Entry

Nearly everything is finished with the project.  Our usability testing went very smoothly.  We did find a couple of items that need to be clarified, so at the moment we are making those corrections.

Individual blog 4: library

Today was our final group meeting. We made a few final changes to the documentation based on the results of our user study. We also completed the appendix with the usability study. From the results, it looks like our documentation was very helpful to the users.

Purdue Library User Documentation Group Blog #5

All the members of our group met in ENAD to finalize the documentation and to work on the appendix. We analyzed the results to and then put them in table form. All the comments were considered for imporvements for the final draft of the user documentation. The level of confidence and times were averaged for the numbers for overall data. For the tutorial final draft, we made sure everything was overall uniform, such as sizes, indentations of the steps, font, and screen captures. We plan on adding the final touches and then turn in the surveys and turn the document itself into a PDF.

Week 3-Individual Blog( Purdue Libraries)

I worked on finding two users for the usability testing for our documentation, whom meet the criteria for our test.   I worked on editing the third task of the rough draft for the documentation.  A location and meeting time for Monday, April 26, 2009 at 7pm.  Next, week I plan to evaluate the information from the usability test.

Individual Blog: Week Four

This week we conducted the usability testing.  Zach made changes to the documentation after our peer editing was completed.  However, in the testing we at first gave people the original draft.  It worked out well in the end because we had about half the users use the old documentation and half the new.  This allowed us to compare whether or not our changes made a difference.  The testing was very successful we got some great compliments and also some constructive criticism on the product.

Individual Blog: Week Four

This week we conducted the usability testing.  Zach made changes to the documentation after our peer editing was completed.  However, in the testing we at first gave people the original draft.  It worked out well in the end because we had about half the users use the old documentation and half the new.  This allowed us to compare whether or not our changes made a difference.  The testing was very successful we got some great compliments and also some constructive criticism on the product.