Bobby Lab Frank Ritter 4 nov 19 Use an automatic testing tool, see the future, and practice good lab reporting. Purposes ======= If a tool like Bobby ends up being available, report on what it found, what it would mean to expand this tool, and how you would expand it. If you after an ernest search can't find such a tool, note what it could or should have found with what you now know about humans, such tools, and interfaces, and what it would mean to expand this tool, and how you would expand it. Learn an automatic web site testing tool Apply (run) that tool on a web site. your project web site or a mockup of your project interface is ideal, but not always available. If this approach is not a good match to your project web site, then you can use any web site. Include a 1 paragraph note about why you did not choose your project and chose what you did. Also note what would be necessary to use the tool with your project. (See Pew and Mavor, 2007, or other papers by Pew for support if you wish.) Practice writing a lab report, getting formating, style, English, references, more clean and correct. Reflect upon the role of TA, automatic testing, and user modeling in the RD-ICM, and in HCI in general. Lab ========= 1. Find a Bobby-like tool. In ~one paragraph to one page, note why you chose that tool. Yes, you may have chosen it because it came up first, but spend 5-30 min. to understand how to tell someone that it is a great tool. Practice noting and explaining such things. 2. Describe the web site being analysed in 1-3 paragraphs. This is to briefly describe it and to avoid later misunderstandings about it. Include a screenshot to provide context. Label your figure and caption it. See the book or any reading for an example of how to do this. Or the final project template. 3. Describe what you did. There may be not much, but there may be settings you chose or a specific version of the tool you used. 4. You can give the raw feedback from the tool as an appendix, but perhaps put snippets in a Results section. In the results section note what the tool found. You need to include implications for your project, which would make the section be called results and discussion, or have two sections, Results, and then Discussion and Conclusion. Or, have three sections, Results, Discussion, and Conclusion. The one combination you cannot have is a single section called "Results, Discussion, and Conclusion". 5. Throughout, but particularly in the discussion and conclusion sections, note what you have learned, and the implications for the project you are doing, and the implications for the field (if appropriate). Advantages and limitations of the tool should be addressed. 6. Include 4 to 18 references, 2 from the class readings, 2 not. You can find a recent summary of such tools at http://acs.ist.psu.edu/papers/ritter19dip.pdf You can see how to format references in any paper we have read, and in the APA Manual of Style. HCI tends to use (perhaps 80%?) (name, year) format, which I greatly prefer. Some formats use numeric references. While I can understand over time who and what (Anderson, 2007) is, I seem to always guess who and what [1] is, it seems to change in every paper I read! If you do use [1] numeric style, please write graciously, "Ritter and colleagues [2] found...." Overall, this might be about 5-10 pages. Over 15 and you are doing too much work. You might get out in less than 5, but it would be difficult. Due, start of class, 2 weeks after lab announced. (Ps. this is general template for all HCI, cogsci, military, commercial, industrial work and work reports)