<?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 for Claudia Müller-Birn</title>
	<atom:link href="http://www.clmb.de/wordpress/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.clmb.de/wordpress</link>
	<description>&#124;&#124;&#124;&#124;&#124; academic homepage &#124;&#124;&#124;&#124;&#124;</description>
	<lastBuildDate>Fri, 13 Nov 2009 15:12:15 +0100</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Usability in small-sized open source software projects by Claudia</title>
		<link>http://www.clmb.de/wordpress/?p=442&#038;cpage=1#comment-325</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Fri, 13 Nov 2009 15:12:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.cl-mueller.de/wordpress/?p=442#comment-325</guid>
		<description>Unfortunately it is not that easy. First of all, you need a common understanding of an efficient interface design. Actually, we internally applied an adapted user-oriented design process. It worked out fine, but now we are struggling with the implementation. Secondly, the whole community should share this understanding. Even though we had these discussions, there is still no awareness of talking about usability before (!) implementing a new function. Thirdly, we need the resources to define our guidelines, but this is a problem we share with every software project. :-)

However, it doesn&#039;t stop here because now we have to think how to grasp the user experiences. Maybe there is a certain work around we find very intuitive but nobody else. Just simply imagine you have a certain problem in using SONIVIS and you want to tell us, where you problem is. How can you do that with a text-based bug tracking system?</description>
		<content:encoded><![CDATA[<p>Unfortunately it is not that easy. First of all, you need a common understanding of an efficient interface design. Actually, we internally applied an adapted user-oriented design process. It worked out fine, but now we are struggling with the implementation. Secondly, the whole community should share this understanding. Even though we had these discussions, there is still no awareness of talking about usability before (!) implementing a new function. Thirdly, we need the resources to define our guidelines, but this is a problem we share with every software project. <img src='http://www.clmb.de/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>However, it doesn&#8217;t stop here because now we have to think how to grasp the user experiences. Maybe there is a certain work around we find very intuitive but nobody else. Just simply imagine you have a certain problem in using SONIVIS and you want to tell us, where you problem is. How can you do that with a text-based bug tracking system?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Usability in small-sized open source software projects by Max</title>
		<link>http://www.clmb.de/wordpress/?p=442&#038;cpage=1#comment-324</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Fri, 13 Nov 2009 15:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.cl-mueller.de/wordpress/?p=442#comment-324</guid>
		<description>Well, simply follow the &lt;a href=&quot;http://developer.apple.com/mac/library/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/XHIGIntro.html&quot; rel=&quot;nofollow&quot;&gt;Apple User Interface Guidelines&lt;/a&gt; and you&#039;re done. They are really concise and good. I like especially the section &quot;Apply the 80% Rule&quot;.</description>
		<content:encoded><![CDATA[<p>Well, simply follow the <a href="http://developer.apple.com/mac/library/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/XHIGIntro.html" rel="nofollow">Apple User Interface Guidelines</a> and you&#8217;re done. They are really concise and good. I like especially the section &#8220;Apply the 80% Rule&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
