<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Requirements Are Important</title>
	<atom:link href="http://iface.wordpress.com/2006/07/03/requirements-are-important/feed/" rel="self" type="application/rss+xml" />
	<link>http://iface.wordpress.com/2006/07/03/requirements-are-important/</link>
	<description>Software For Business, By Design</description>
	<lastBuildDate>Tue, 23 Oct 2007 16:11:19 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Abhijit Nadgouda @ iface &#187; Activity Centred Design</title>
		<link>http://iface.wordpress.com/2006/07/03/requirements-are-important/#comment-1856</link>
		<dc:creator>Abhijit Nadgouda @ iface &#187; Activity Centred Design</dc:creator>
		<pubDate>Fri, 21 Jul 2006 11:30:35 +0000</pubDate>
		<guid isPermaLink="false">https://iface.wordpress.com/2006/07/03/requirements-are-important/#comment-1856</guid>
		<description>[...] Once the purpose is established, the context(s) can be identified. Although it is entirely user centric, more factors contribute to the context. If it is the software, then the layout design, the usability design, the usage patterns and more importantly tracking the usage history are part of providing the context. Some of this can be gathered when the requirements are being identified, and some has to be built when the software is being used. Usage patterns can be developed for certain users and corresponding contexts can be provided. [...]</description>
		<content:encoded><![CDATA[<p>[...] Once the purpose is established, the context(s) can be identified. Although it is entirely user centric, more factors contribute to the context. If it is the software, then the layout design, the usability design, the usage patterns and more importantly tracking the usage history are part of providing the context. Some of this can be gathered when the requirements are being identified, and some has to be built when the software is being used. Usage patterns can be developed for certain users and corresponding contexts can be provided. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
