<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;User Centered Design&gt;Specifications</title>	<link>http://tc.eserver.org/dir/Articles/User-Centered-Design/Specifications</link>
	<description>A listing of the most recently indexed works about Articles and User Centered Design 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;User Centered Design&gt;Specifications</title>
		<link>http://tc.eserver.org/dir/Articles/User-Centered-Design/Specifications</link>
	</image>
	<item>
		<title>Using Customer Tests to Drive Development</title>
		<link>http://tc.eserver.org/34496.html</link>
		<guid>http://tc.eserver.org/34496.html</guid>
		<description>Test-driven development or TDD is a widely accepted practice used by agile software development teams of many flavors – not only Extreme Programming teams. For each small bit of functionality they code, programmers first write unit tests, then they write the code that makes those unit tests pass. TDD is seen as a design tool, since it forces the programmer to think about many aspects of each feature before coding.</description>
	</item>
	<item>
		<title>Goal Oriented Requirements</title>
		<link>http://tc.eserver.org/27575.html</link>
		<guid>http://tc.eserver.org/27575.html</guid>
		<description>Your requirements document needs to focus on the user’s goals. They should not be marketing’s list of features &apos;we’ve got to have&apos; because the competition has these features. They should not be a list of things the programmers think ought to be included &apos;because we can add those things for very little cost.&apos; Feature bloat does not benefit the user.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/User-Centered-Design/Specifications.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>