<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Usability&gt;Specifications</title>	<link>http://tc.eserver.org/dir/Articles/Usability/Specifications</link>
	<description>A listing of the most recently indexed works about Articles and Usability and Specifications 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;Usability&gt;Specifications</title>
		<link>http://tc.eserver.org/dir/Articles/Usability/Specifications</link>
	</image>
	<item>
		<title>So What IS User Requirements Gathering?</title>
		<link>http://tc.eserver.org/34467.html</link>
		<guid>http://tc.eserver.org/34467.html</guid>
		<description>Requirements gathering is all about aiming at the right target. It doesn&apos;t matter how accurate you are, if you aim at the wrong target, you miss.</description>
	</item>
	<item>
		<title>Bridging the Gap with Requirements Definition</title>
		<link>http://tc.eserver.org/23984.html</link>
		<guid>http://tc.eserver.org/23984.html</guid>
		<description>Developing a new product or service is tricky. When everything goes well, the product can redefine a market or even create an entirely new one, to the benefit of its manufacturer and its consumers. When the product doesn&apos;t click with its audience, though, the costs—development, employee, manufacturing—can be staggering. How do you ensure that your new product doesn&apos;t flop? One effective method is to conduct a requirements definition phase before developing a new product.</description>
	</item>
	<item>
		<title>Identifying Web Site Requirements</title>
		<link>http://tc.eserver.org/14709.html</link>
		<guid>http://tc.eserver.org/14709.html</guid>
		<description>The authors emphasize the importance of conducting thorough research on business goals, branding goals, user needs, and technical resources before Web designers undertake a redesign. The article also offers suggestions about how to define, develop, and communicate a client&apos;s brand.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Usability/Specifications.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>