<?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/"
		>
<channel>
	<title>Comments on: Incorporating Usability</title>
	<atom:link href="http://ifacethoughts.net/2006/02/22/incorporating-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://ifacethoughts.net/2006/02/22/incorporating-usability/</link>
	<description>Thoughts on software development and related, by Abhijit Nadgouda</description>
	<lastBuildDate>Sat, 20 Mar 2010 01:32:39 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Open Source Usability &#124; iface thoughts</title>
		<link>http://ifacethoughts.net/2006/02/22/incorporating-usability/comment-page-1/#comment-118250</link>
		<dc:creator>Open Source Usability &#124; iface thoughts</dc:creator>
		<pubDate>Tue, 23 Oct 2007 15:58:49 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/22/incorporating-usability/#comment-118250</guid>
		<description>[...] usability understanding and the common man was ignored as a user resulting in ingoring usability. Incorporating usability requires its consideration right from inception of an idea or a product, it cuts across all aspects [...]</description>
		<content:encoded><![CDATA[<p>[...] usability understanding and the common man was ignored as a user resulting in ingoring usability. Incorporating usability requires its consideration right from inception of an idea or a product, it cuts across all aspects [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Make It More Usable - Help &#124; iface thoughts</title>
		<link>http://ifacethoughts.net/2006/02/22/incorporating-usability/comment-page-1/#comment-118174</link>
		<dc:creator>Make It More Usable - Help &#124; iface thoughts</dc:creator>
		<pubDate>Tue, 23 Oct 2007 14:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/22/incorporating-usability/#comment-118174</guid>
		<description>[...] Incorporating Usability [...]</description>
		<content:encoded><![CDATA[<p>[...] Incorporating Usability [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iface thoughts &#187; Blog Archive &#187; Web Design - Art Or Engineering?</title>
		<link>http://ifacethoughts.net/2006/02/22/incorporating-usability/comment-page-1/#comment-809</link>
		<dc:creator>iface thoughts &#187; Blog Archive &#187; Web Design - Art Or Engineering?</dc:creator>
		<pubDate>Tue, 10 Oct 2006 14:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/22/incorporating-usability/#comment-809</guid>
		<description>[...] My background biases me towards engineering. On the web Content is the King. Give importance to the content identification, information architecture, user profiling and then design. User a Content Management System. A web site should support the standards, should be usable, accessible (at least to its intended audience) and more importantly secure. But it cannot be just this! In today&#8217;s competition for the top birth, the graphic design plays an important role. Users are not ready to go with anything that is drab and already done. It has to be fresh, with new ideas. And it has to be usable, accessible - wow am I going in circles? [...]</description>
		<content:encoded><![CDATA[<p>[...] My background biases me towards engineering. On the web Content is the King. Give importance to the content identification, information architecture, user profiling and then design. User a Content Management System. A web site should support the standards, should be usable, accessible (at least to its intended audience) and more importantly secure. But it cannot be just this! In today&#8217;s competition for the top birth, the graphic design plays an important role. Users are not ready to go with anything that is drab and already done. It has to be fresh, with new ideas. And it has to be usable, accessible &#8211; wow am I going in circles? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhijit Nadgouda @ iface &#187; Blog Archive &#187; Open Source Usability</title>
		<link>http://ifacethoughts.net/2006/02/22/incorporating-usability/comment-page-1/#comment-369</link>
		<dc:creator>Abhijit Nadgouda @ iface &#187; Blog Archive &#187; Open Source Usability</dc:creator>
		<pubDate>Thu, 13 Apr 2006 17:28:34 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/22/incorporating-usability/#comment-369</guid>
		<description>[...] This resulted in lack of usability understanding and the common man was ignored as a user resulting in ingoring usability. Incorporating usability requires its consideration right from inception of an idea or a product, it cuts across all aspects of software usage. It cannot be built-in halfway down the line. [...]</description>
		<content:encoded><![CDATA[<p>[...] This resulted in lack of usability understanding and the common man was ignored as a user resulting in ingoring usability. Incorporating usability requires its consideration right from inception of an idea or a product, it cuts across all aspects of software usage. It cannot be built-in halfway down the line. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhijit Nadgouda @ iface &#187; Make It More Usable - Help</title>
		<link>http://ifacethoughts.net/2006/02/22/incorporating-usability/comment-page-1/#comment-368</link>
		<dc:creator>Abhijit Nadgouda @ iface &#187; Make It More Usable - Help</dc:creator>
		<pubDate>Mon, 06 Mar 2006 04:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/22/incorporating-usability/#comment-368</guid>
		<description>[...] Incorporating Usability [...]</description>
		<content:encoded><![CDATA[<p>[...] Incorporating Usability [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: More on usability at pleonastic information</title>
		<link>http://ifacethoughts.net/2006/02/22/incorporating-usability/comment-page-1/#comment-367</link>
		<dc:creator>More on usability at pleonastic information</dc:creator>
		<pubDate>Fri, 24 Feb 2006 08:52:02 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/22/incorporating-usability/#comment-367</guid>
		<description>[...] Here is one good article on usability, Iface: Incorporating usabilityÂ by Abhijit Nadgouda. He takes on the task to categorizing softwareÂ into two different types: Functionality driven and Content driven. Operating systems, word processors can be seen as Functionality driven applications while help applications, blogging software can be looked upon as Content driven. He then turns toward the importance of identifying the users since they will decide its value. And when identifying the users it is important to consider their knowledge, background, education, skills and language. And then he turns to the address another very important user - the administrator. His view upon IA: Information ArchitectureÂ is about understanding the user&#8217;s perspective. The information (as core content, or related to the functionality) you provide should be something that the user understands. Only then will the software be useful to him. Information Architecture discipline includes a lot more, but for our purpose lets look at content identification, content prioritization and content classification. [...]</description>
		<content:encoded><![CDATA[<p>[...] Here is one good article on usability, Iface: Incorporating usabilityÂ by Abhijit Nadgouda. He takes on the task to categorizing softwareÂ into two different types: Functionality driven and Content driven. Operating systems, word processors can be seen as Functionality driven applications while help applications, blogging software can be looked upon as Content driven. He then turns toward the importance of identifying the users since they will decide its value. And when identifying the users it is important to consider their knowledge, background, education, skills and language. And then he turns to the address another very important user &#8211; the administrator. His view upon IA: Information ArchitectureÂ is about understanding the user&#8217;s perspective. The information (as core content, or related to the functionality) you provide should be something that the user understands. Only then will the software be useful to him. Information Architecture discipline includes a lot more, but for our purpose lets look at content identification, content prioritization and content classification. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
