<?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: Military Software Sucks</title>
	<atom:link href="http://www.lessonsoffailure.com/software/military-software-sucks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lessonsoffailure.com/software/military-software-sucks/</link>
	<description>Humans + Software Development = Always Interesting</description>
	<lastBuildDate>Mon, 12 Dec 2011 21:05:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Amgis</title>
		<link>http://www.lessonsoffailure.com/software/military-software-sucks/comment-page-1/#comment-131</link>
		<dc:creator>Amgis</dc:creator>
		<pubDate>Mon, 08 Feb 2010 21:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.lessonsoffailure.com/?p=253#comment-131</guid>
		<description>Could also be that all of the receivers would need to be able to handle this encrypted feed:
Every armored vehicle
Every forward observer radio
Every mobile command station (computers in tents)
Every state side command installation
Every Jet Fighter (they can share this too)
Every Bomber
Every Support air craft
Every Navy ship
The marines
and don&#039;t forget the coast guard too...

The branches of the military still don&#039;t have radios that work well with each other.  Most of them aren&#039;t configurable by software upgrades either.  

I don&#039;t know if encrypted video takes up more bandwidth but that seems to be a factor.  Satellite time is expensive and in short supply.
https://www.strategypage.com/htmw/htiw/articles/20091218.aspx</description>
		<content:encoded><![CDATA[<p>Could also be that all of the receivers would need to be able to handle this encrypted feed:<br />
Every armored vehicle<br />
Every forward observer radio<br />
Every mobile command station (computers in tents)<br />
Every state side command installation<br />
Every Jet Fighter (they can share this too)<br />
Every Bomber<br />
Every Support air craft<br />
Every Navy ship<br />
The marines<br />
and don&#8217;t forget the coast guard too&#8230;</p>
<p>The branches of the military still don&#8217;t have radios that work well with each other.  Most of them aren&#8217;t configurable by software upgrades either.  </p>
<p>I don&#8217;t know if encrypted video takes up more bandwidth but that seems to be a factor.  Satellite time is expensive and in short supply.<br />
<a href="https://www.strategypage.com/htmw/htiw/articles/20091218.aspx" rel="nofollow">https://www.strategypage.com/htmw/htiw/articles/20091218.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: igorbrejc.net &#187; Fresh Catch For December 26th</title>
		<link>http://www.lessonsoffailure.com/software/military-software-sucks/comment-page-1/#comment-52</link>
		<dc:creator>igorbrejc.net &#187; Fresh Catch For December 26th</dc:creator>
		<pubDate>Sat, 26 Dec 2009 23:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.lessonsoffailure.com/?p=253#comment-52</guid>
		<description>[...] Military Software Sucks &#124; Lessons of Failure [...]</description>
		<content:encoded><![CDATA[<p>[...] Military Software Sucks | Lessons of Failure [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.lessonsoffailure.com/software/military-software-sucks/comment-page-1/#comment-43</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 17 Dec 2009 19:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.lessonsoffailure.com/?p=253#comment-43</guid>
		<description>LOL!  Here I am railing on the military&#039;s poor estimation and I&#039;m off by a factor of a 1,000.  Post updated.  Thanks for pointing that out, and making my comments even MORE relevant.</description>
		<content:encoded><![CDATA[<p>LOL!  Here I am railing on the military&#8217;s poor estimation and I&#8217;m off by a factor of a 1,000.  Post updated.  Thanks for pointing that out, and making my comments even MORE relevant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HS</title>
		<link>http://www.lessonsoffailure.com/software/military-software-sucks/comment-page-1/#comment-42</link>
		<dc:creator>HS</dc:creator>
		<pubDate>Thu, 17 Dec 2009 19:40:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.lessonsoffailure.com/?p=253#comment-42</guid>
		<description>Perhaps encryption was discarded after its costs were overestimated by a couple orders of magnitude.  $1,760,000 / 1,000 = $1,760.</description>
		<content:encoded><![CDATA[<p>Perhaps encryption was discarded after its costs were overestimated by a couple orders of magnitude.  $1,760,000 / 1,000 = $1,760.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.lessonsoffailure.com/software/military-software-sucks/comment-page-1/#comment-41</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:05:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.lessonsoffailure.com/?p=253#comment-41</guid>
		<description>Yep.  Agreed.  And yes, I totally wrote off the hardware side of it, your points are all valid...my systems engineer friend at NASA is no doubt cringing at me right this second.  But still, this is a critical flaw and poorly executed.</description>
		<content:encoded><![CDATA[<p>Yep.  Agreed.  And yes, I totally wrote off the hardware side of it, your points are all valid&#8230;my systems engineer friend at NASA is no doubt cringing at me right this second.  But still, this is a critical flaw and poorly executed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.lessonsoffailure.com/software/military-software-sucks/comment-page-1/#comment-40</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 17 Dec 2009 17:57:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.lessonsoffailure.com/?p=253#comment-40</guid>
		<description>I agree with the incompetence, and not taking their medicine early. As an engineer with experience on commercial projects, I am sure that some engineer did mention this, and possibly even &quot;went to the mattress&quot; on it, but his &quot;lead&quot; or manager to drop it or be fired. Happens on the time. Remember the space shuttle challenger?

But, the costs are actually higher. Adding the extra processor increases the electrical power requirements on the aircraft, takes up volume, and weight. This is likely to have impacts on the aircrafts, size, weight, speed, range, and operating costs. So the number is likely many times higher than your calculations, but there is still no excuse for shipping an expensive weapon that can be defeated by a MAC.</description>
		<content:encoded><![CDATA[<p>I agree with the incompetence, and not taking their medicine early. As an engineer with experience on commercial projects, I am sure that some engineer did mention this, and possibly even &#8220;went to the mattress&#8221; on it, but his &#8220;lead&#8221; or manager to drop it or be fired. Happens on the time. Remember the space shuttle challenger?</p>
<p>But, the costs are actually higher. Adding the extra processor increases the electrical power requirements on the aircraft, takes up volume, and weight. This is likely to have impacts on the aircrafts, size, weight, speed, range, and operating costs. So the number is likely many times higher than your calculations, but there is still no excuse for shipping an expensive weapon that can be defeated by a MAC.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

