<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Documentation&gt;Usability&gt;History</title>	<link>http://tc.eserver.org/dir/Articles/Documentation/Usability/History</link>
	<description>A listing of the most recently indexed works about Articles and Documentation and Usability and History 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>Articles&gt;Documentation&gt;Usability&gt;History</title>
		<link>http://tc.eserver.org/dir/Articles/Documentation/Usability/History</link>
	</image>
	<item>
		<title>Grappling with Distributed Usability: A Cultural-Historical Examination of Documentation Genres Over Four Decades</title>
		<link>http://tc.eserver.org/29049.html</link>
		<guid>http://tc.eserver.org/29049.html</guid>
		<description>Traditional models of usability assume that usability is a quality that can be designed into a particular artifact. Yet constructivist theory implies that usability cannot be located in a single artifact; rather, it must be conceived as a quality of the entire activity in which the artifact is used. This article describes a distributed approach to usability, based on activity theory and genre theory. It then illustrates the approach with a four-decade examination of a traffic accident location and analysis system (ALAS). Using the theoretical framework of genre ecologies, the article demonstrates how usability is distributed across the many official and unofficial (ad hoc) genres employed by ALAS users.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Documentation/Usability/History.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>