<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Ars: Microsoft brain lateralization patent all about software QA</title>
		<link>http://www.digitalmajority.org/forum/t-65848/ars:microsoft-brain-lateralization-patent-all-about-software-qa</link>
		<description>Posts in the discussion thread &quot;Ars: Microsoft brain lateralization patent all about software QA&quot; - Last Thursday, Microsoft filed patent application 20,080,134,132, which describes a method of &quot;Developing Software Components Based on Brain Lateralization.&quot; At first glance, this sounds quite impressive [...]. Closer examination, however, indicates that our dreams of writing C++ code without that pesky keyboard getting in the way remain elusive. Fancy wording or not, Microsoft is essentially attempting to patent something far more basic: the software Quality Assurance (Q&amp;A) process.</description>
				<copyright></copyright>
		<lastBuildDate></lastBuildDate>
		
					<item>
				<guid>http://www.digitalmajority.org/forum/t-65848#post-187562</guid>
				<title>Ars: Microsoft brain lateralization patent all about software QA</title>
				<link>http://www.digitalmajority.org/forum/t-65848/ars:microsoft-brain-lateralization-patent-all-about-software-qa#post-187562</link>
				<description></description>
				<pubDate>Mon, 09 Jun 2008 13:40:27 +0000</pubDate>
				<wikidot:authorName>ggiedke</wikidot:authorName>				<wikidot:authorUserId>32664</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p><a href="http://arstechnica.com/news.ars/post/20080609-microsoft-brain-lateralization-patent-all-about-software-qa.html">http://arstechnica.com/news.ars/post/20080609-microsoft-brain-lateralization-patent-all-about-software-qa.html</a></p> <p>The patent application's abstract reads as follows:</p> <p><em>A software design process includes three elements—an object/component driven element, a situation/scenario driven element, and an arbitrator/communicator element that is logically interposed and serves as an intermediary between the object/component driven and the situation/scenario driven elements. Through an iterative communication process overseen by the arbitrator/communicator, software design can take place and be measured against a metric. The communication process overseen and implemented by the arbitrator/communicator can allow ideas and developments provided by one element to be translated into a format that the other element understands. Once the metric has been achieved, the design process can be terminated.</em></p> <p>Read that over, and you'll notice it mentions neither the brain nor any sort of organizational/methodological principle that could be described as brain-like</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>