<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Mojofat</title>	<link>http://tc.eserver.org/publisher/Mojofat</link>
	<description>A listing of works published by Mojofat 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>Mojofat</title>
		<link>http://tc.eserver.org/dir/Mojofat</link>
	</image>
	<item>
		<title>Functional Spec Tutorial: What and Why</title>
		<link>http://tc.eserver.org/19648.html</link>
		<guid>http://tc.eserver.org/19648.html</guid>
		<description>Functional specifications (functional specs), in the end, are the blueprint for how you want a particular web project or application to look and work. It details what the finished product will do, how a user will interact with it, and what it will look like. By creating a blueprint of the product first, time and productivity are saved during the development stage because the programmers can program instead of also working out the logic of the user-experience. It will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Mojofat.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>