<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Software&gt;Usability</title>	<link>http://tc.eserver.org/dir/Design/Software/Usability</link>
	<description>A listing of the most recently indexed works about Design and Software and Usability in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Design&gt;Software&gt;Usability</title>
		<link>http://tc.eserver.org/dir/Design/Software/Usability</link>
	</image>
	<item>
		<title>If It’s Not Easy to Use, It’s Not Used</title>
		<link>http://tc.eserver.org/33421.html</link>
		<guid>http://tc.eserver.org/33421.html</guid>
		<description>Debates about Microsoft Word vs. Adobe Framemaker appear with regular frequency on the tech-writing mailing lists I am subscribed to. Everyone agrees Frame is an awesome publishing tool. Yet, everyone keeps cribbing about it. So, why does a bright bunch of people who are masters at figuring out stuff, otherwise known as tech-writers, only hesitatingly agree Frame is “kind of great”? I think it’s mostly because Frame is so difficult to use.</description>
	</item>
	<item>
		<title>The Usability of Open Source Software</title>
		<link>http://tc.eserver.org/19544.html</link>
		<guid>http://tc.eserver.org/19544.html</guid>
		<description>Open source communities have successfully developed a great deal of software although most computer users only use proprietary applications. The usability of open source software is often regarded as one reason for this limited distribution. In this paper we review the existing evidence of the usability of open source software and discuss how the characteristics of open source development influence usability. We describe how existing human-computer interaction techniques can be used to leverage distributed networked communities, of developers and users, to address issues of usability.</description>
	</item>
	<item>
		<title>Usability in Software Development</title>
		<link>http://tc.eserver.org/19042.html</link>
		<guid>http://tc.eserver.org/19042.html</guid>
		<description>Usability does not begin and end with the web. In fact, long before the Internet was a gleam in the Pentagon&apos;s eye, computer professionals were already aware of the need for human-computer interaction to be as natural and intuitive as possible. In fact, there are many compelling reasons to suggest that usability is even more critical to successful application design than it is for winning websites.</description>
	</item>
	<item>
		<title>Social and Cognitive Effects of Professional Communication on Software Usability</title>
		<link>http://tc.eserver.org/13903.html</link>
		<guid>http://tc.eserver.org/13903.html</guid>
		<description>We designed and piloted a technical communication course for software engineering majors to take concurrently with their capstone project course in software design.  In the pilot, one third of the capstone design course students jointly enrolled in the writing class.  One goal of the collaborative courses was to use writing to improve the usability of students&apos; software.  We studied the effects of writing on students&apos; user-centered beliefs and design practices and on the usability of their product, using surveys, document analyses, expert reviews, and user test results.  When possible, we compared the usability processes and products of teams who did and did not take the writing class.  Our findings suggest that the synergy of this interdisciplinary approach effectively sensitized students to user-centered design, instilled in them a commitment to it, and helped them develop usable products.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Software/Usability.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>