<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>WQusability</title>	<link>http://tc.eserver.org/publisher/WQusability</link>
	<description>A listing of works published by WQusability 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>WQusability</title>
		<link>http://tc.eserver.org/dir/WQusability</link>
	</image>
	<item>
		<title>Utiliser les 5 E pour Comprendre les Utilisateurs</title>
		<link>http://tc.eserver.org/29294.html</link>
		<guid>http://tc.eserver.org/29294.html</guid>
		<description>En matière d&apos;amélioration de votre site web, produit ou logiciel, comment passer de la simple volonté à l&apos;action? Que dites-vous de ceci pour commencer: si la réponse c&apos;est l&apos;utilisabilité, quelle peut bien être la question?</description>
	</item>
	<item>
		<title>&amp;#35821;&amp;#35328;&amp;#21644;&amp;#21487;&amp;#29992;&amp;#24615;</title>
		<link>http://tc.eserver.org/26998.html</link>
		<guid>http://tc.eserver.org/26998.html</guid>
		<description>&amp;#21487;&amp;#29992;&amp;#24615;&amp;#26159; &amp;#22909;&amp;#30340;&amp;#27807; &amp;#36890;&amp;#25216;&amp;#26415; &amp;#30340;&amp;#19968; &amp;#20010;&amp;#37325;&amp;#35201;&amp;#37096; &amp;#20998;&amp;#12290;&amp;#24456;&amp;#22810;&amp;#20316;&amp;#32773;&amp;#23558;&amp;#21487;&amp;#29992;&amp;#24615;&amp;#25216;&amp;#26415;&amp;#22914;&amp;#31449;&amp;#28857;&amp;#35775;&amp;#38382;&amp;#12289;&amp;#29992;&amp;#25143;&amp;#20219;&amp;#21153;&amp;#20998;&amp;#26512; &amp;#21644;&amp;#21487;&amp;#29992;&amp;#24615;&amp;#27979;&amp;#35797;&amp;#32467;&amp;#21512;&amp;#21040;&amp;#20182;&amp;#20204;&amp;#30340; &amp;#24037;&amp;#20316;&amp;#20013;&amp;#12290;</description>
	</item>
	<item>
		<title>Language and Usability</title>
		<link>http://tc.eserver.org/26997.html</link>
		<guid>http://tc.eserver.org/26997.html</guid>
		<description>Usability is an important part of good technical communication. Many writers incorporate usability techniques such as site visits, user task analysis and usability testing into their work.</description>
	</item>
	<item>
		<title>Being User-Centered When Implementing a UCD Process</title>
		<link>http://tc.eserver.org/20928.html</link>
		<guid>http://tc.eserver.org/20928.html</guid>
		<description>For those who are interested in usability – whether long-time advocates or newly introduced – this is a good time to introduce a user-centered design process.</description>
	</item>
	<item>
		<title>Crossing the Chasm: Promoting Usability in the Software Development Community</title>
		<link>http://tc.eserver.org/20931.html</link>
		<guid>http://tc.eserver.org/20931.html</guid>
		<description>User-centered design should be a core part of every software development effort yet, despite its well-documented paybacks, it has yet to be widely adopted. Too often, user-centered design remains the province of visionaries rather than the everyday practice of programmers and analysts. Despite a general consensus on a basic approach to user-centered design (UCD), there is little understanding of the process and how it fits into larger software development methodologies.</description>
	</item>
	<item>
		<title>Designing for Interactive Television</title>
		<link>http://tc.eserver.org/20933.html</link>
		<guid>http://tc.eserver.org/20933.html</guid>
		<description>We are so accustomed to watching television that we easily overlook the limited resolution of the television screen. Compared to TV, even VGA looks good. Although both use a similar display monitor, they differ in both the way the screen is &apos;painted&apos; and in how much information can be placed on the screen. To design effectively for interactive television, it is essential to understand the technical constraints of the medium.</description>
	</item>
	<item>
		<title>Dimensions of Usability: Defining the Conversation, Driving the Process</title>
		<link>http://tc.eserver.org/20923.html</link>
		<guid>http://tc.eserver.org/20923.html</guid>
		<description>Have you ever wondered if your colleagues or clients really understand usability? Too often, standards or guidelines substitute for really engaging our business, technical and design&#xD;colleagues in a discussion of what usability means. By looking at usability from five&#xD;dimensions, we can create a consensus around usability goals and use that definition to&#xD;provide the basis for planning user centered design activities.</description>
	</item>
	<item>
		<title>GetSmart: Interface Design and Production Meet Editorial on a New CD-ROM Magazine</title>
		<link>http://tc.eserver.org/20934.html</link>
		<guid>http://tc.eserver.org/20934.html</guid>
		<description>The technology of magazine production is well established. Editors have access to high-resolution print screens, and can use a wide variety of fonts, layout designs and graphics to create attractive and readable pages. Readers are used to seeing a lot of information on a single page - some in body text, some in sidebars or callouts. On screen, by contrast, the resolution is relatively low - 72 dpi as opposed to 2400 dpi. Readers are not yet accustomed to reading directly from the screen, and an overly cluttered screen or one with fonts which are too small can quickly become unreadable.</description>
	</item>
	<item>
		<title>Lessons from the Novartis InfoWeb: Creating a Successful Knowledge Management System</title>
		<link>http://tc.eserver.org/20932.html</link>
		<guid>http://tc.eserver.org/20932.html</guid>
		<description>Discussion of a global knowledge management system created in&#xD;Lotus Notes for Novartis Consumer Health.</description>
	</item>
	<item>
		<title>Prototyping and Usability Testing with Visio</title>
		<link>http://tc.eserver.org/20930.html</link>
		<guid>http://tc.eserver.org/20930.html</guid>
		<description>An overview of prototyping: uses, functions and types of prototypes.</description>
	</item>
	<item>
		<title>Storytelling: Using Narrative to Communicate Design Ideas</title>
		<link>http://tc.eserver.org/20929.html</link>
		<guid>http://tc.eserver.org/20929.html</guid>
		<description>What makes a story appropriate? Convincing?</description>
	</item>
	<item>
		<title>Using the 5Es to Understand Users</title>
		<link>http://tc.eserver.org/20924.html</link>
		<guid>http://tc.eserver.org/20924.html</guid>
		<description>One of the exercises I find helpful is to look at usability requirements for different aspects of the user experience. For each of the five dimensions of usability (the 5Es), we think about how it is reflected in requirements for each of the user groups.</description>
	</item>
	<item>
		<title>What&apos;s In A Name?</title>
		<link>http://tc.eserver.org/20927.html</link>
		<guid>http://tc.eserver.org/20927.html</guid>
		<description>In defining a field, each person seems to look at the world and place themselves in the center of the circle, giving their specialty top billing as the summation of all the others. What exactly is gained by this political one-upmanship? In the face of this inflation, I find myself pulling back to the simplest craft title I can find. Or avoiding titles altogether.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/WQusability.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>