<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
>

<channel>
	<title>CAST Software: On Quality Blog &#187; Software Measurement</title>
	<atom:link href="http://blog.castsoftware.com/category/software-measurement/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.castsoftware.com</link>
	<description>Because Good Software Is Good Business</description>
	<lastBuildDate>Fri, 17 May 2013 17:56:24 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
<!-- podcast_generator="Blubrry PowerPress/4.0.8" -->
	<itunes:summary>Because Good Software Is Good Business</itunes:summary>
	<itunes:author>CAST Software: On Quality Blog</itunes:author>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://blog.castsoftware.com/wp-content/plugins/powerpress/itunes_default.jpg" />
	<itunes:subtitle>Because Good Software Is Good Business</itunes:subtitle>
	<image>
		<title>CAST Software: On Quality Blog &#187; Software Measurement</title>
		<url>http://blog.castsoftware.com/wp-content/plugins/powerpress/rss_default.jpg</url>
		<link>http://blog.castsoftware.com/category/software-measurement/</link>
	</image>
		<item>
		<title>Reduce Software Risk through Improved Quality Measures with CAST, TCS and OMG</title>
		<link>http://blog.castsoftware.com/reduce-software-risk-through-improved-quality-measures-with-cast-tcs-and-omg/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=reduce-software-risk-through-improved-quality-measures-with-cast-tcs-and-omg</link>
		<comments>http://blog.castsoftware.com/reduce-software-risk-through-improved-quality-measures-with-cast-tcs-and-omg/#comments</comments>
		<pubDate>Wed, 12 Dec 2012 13:47:00 +0000</pubDate>
		<dc:creator>Pete Pizzutillo</dc:creator>
				<category><![CDATA[Outsourced Software]]></category>
		<category><![CDATA[Software Demystified]]></category>
		<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Productivity Measurement]]></category>
		<category><![CDATA[Software Risk Management]]></category>
		<category><![CDATA[Technical Debt]]></category>
		<category><![CDATA[Application outsourcing]]></category>
		<category><![CDATA[offshore]]></category>
		<category><![CDATA[Outsourcing]]></category>
		<category><![CDATA[Risk Management in software industry]]></category>
		<category><![CDATA[software analysis and measurement]]></category>
		<category><![CDATA[software risk]]></category>
		<category><![CDATA[vendor control]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4580</guid>
		<description><![CDATA[Webinar Summary I had the pleasure of moderating a panel discussion with Bill Martorelli, Principal Analyst at Forrester Research Inc; Dr. Richard Mark Soley, Chairman and CEO of Object Management Group (OMG); Siva Ganesan, VP &#38; Global Head of Assurance Services at Tata Consultancy Services (TCS); and Lev Lesokhin, EVP, Strategy &#38; Market Development at CAST. We focused on industry trends, and specifically discussed how standardizing quality measures can have a big impact on reducing software risk.  This interactive format allowed attendees to hear four distinct perspectives on the challenges and progress that is being made within organizations directly, and also at systems integrators. Mr. Martorelli started the discussion by &#8230; <a href="http://blog.castsoftware.com/reduce-software-risk-through-improved-quality-measures-with-cast-tcs-and-omg/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/reduce-software-risk-through-improved-quality-measures-with-cast-tcs-and-omg/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Holy Grail: Objective risk level estimation</title>
		<link>http://blog.castsoftware.com/the-holy-grail-objective-risk-level-estimation/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-holy-grail-objective-risk-level-estimation</link>
		<comments>http://blog.castsoftware.com/the-holy-grail-objective-risk-level-estimation/#comments</comments>
		<pubDate>Mon, 19 Nov 2012 20:33:19 +0000</pubDate>
		<dc:creator>Philippe Emmanuel Douziech</dc:creator>
				<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Risk Management]]></category>
		<category><![CDATA[Cyclomatic complexity]]></category>
		<category><![CDATA[Fred Brooks]]></category>
		<category><![CDATA[Integration complexity]]></category>
		<category><![CDATA[Objective risk level assessment]]></category>
		<category><![CDATA[Risk level]]></category>
		<category><![CDATA[Risk probability]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4536</guid>
		<description><![CDATA[In my last post we discussed the complimentary nature of remediation cost and risk level assessment. As a follow up, I wanted to dwell on the objective risk level assessment. Is it even possible? If not, how close to it can we get? How valuable is an estimation of the risk level? Could it be the Holy Grail of software analysis and measurement? Or is it even worth the effort? Risk level By definition, risk level is about the severity of the consequences of a situation and the probability for this situation to happen. A high-probability, low-impact situation can then &#8220;compete&#8221; with a low-probability, high-impact one for the riskiest situation &#8230; <a href="http://blog.castsoftware.com/the-holy-grail-objective-risk-level-estimation/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/the-holy-grail-objective-risk-level-estimation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Build the Best Action Plan for your Application</title>
		<link>http://blog.castsoftware.com/how-to-build-the-best-action-plan-for-your-application/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-to-build-the-best-action-plan-for-your-application</link>
		<comments>http://blog.castsoftware.com/how-to-build-the-best-action-plan-for-your-application/#comments</comments>
		<pubDate>Mon, 17 Sep 2012 20:23:42 +0000</pubDate>
		<dc:creator>Damien Charlemagne</dc:creator>
				<category><![CDATA[Software Analysis]]></category>
		<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Quality]]></category>
		<category><![CDATA[Software Risk Management]]></category>
		<category><![CDATA[Application performance]]></category>
		<category><![CDATA[Application Quality]]></category>
		<category><![CDATA[Performance measurement]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[software performance testing]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4370</guid>
		<description><![CDATA[Applications are built on thousands, millions, maybe even tens of millions, lines of code. They are based on specific architecture gathering technologies, frameworks, and databases set up with their own specific architecture. If you have an action plan to improve your application on a specific issue, what will be your strategy? Do you select one problem related to quality or take the opportunity to refactor part of your application? You know about issues coming from end users, but how do you address those inside the structure of your application? I remember meeting with development teams and management who were trying to find the root cause of performance issues, as delays &#8230; <a href="http://blog.castsoftware.com/how-to-build-the-best-action-plan-for-your-application/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/how-to-build-the-best-action-plan-for-your-application/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Risk Detection and Benchmarking &#8212; Feuding Brothers?</title>
		<link>http://blog.castsoftware.com/risk-detection-and-benchmarking-feuding-brothers/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=risk-detection-and-benchmarking-feuding-brothers</link>
		<comments>http://blog.castsoftware.com/risk-detection-and-benchmarking-feuding-brothers/#comments</comments>
		<pubDate>Thu, 13 Sep 2012 20:18:11 +0000</pubDate>
		<dc:creator>Philippe Emmanuel Douziech</dc:creator>
				<category><![CDATA[Software Analysis]]></category>
		<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Quality Benchmarking]]></category>
		<category><![CDATA[Software Risk Management]]></category>
		<category><![CDATA[automated analysis and measurement]]></category>
		<category><![CDATA[benchmarking]]></category>
		<category><![CDATA[Risk detection]]></category>
		<category><![CDATA[software analysis]]></category>
		<category><![CDATA[Software Quality]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4352</guid>
		<description><![CDATA[Risk detection is the most valid justification to the Software Analysis and Measurement activity: identify any threat that can negatively and severely impact the behavior of applications in operations as well as the application maintenance and development activity. &#8220;Most valid justification&#8221; sounds great, but it’s also quite difficult to manage. Few organizations keep track of software issues that originate from the software source code and architecture so that it is difficult to define objective target requirements that could support a &#8220;zero defects&#8221; approach. Without clear requirements, it is the best way to invest one&#8217;s time and resources in the wrong place: removing too few or too much non-compliant situation in &#8230; <a href="http://blog.castsoftware.com/risk-detection-and-benchmarking-feuding-brothers/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/risk-detection-and-benchmarking-feuding-brothers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cracking Open the Black Box of IT for CEOs</title>
		<link>http://blog.castsoftware.com/cracking-open-the-black-box-of-it-for-ceos/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=cracking-open-the-black-box-of-it-for-ceos</link>
		<comments>http://blog.castsoftware.com/cracking-open-the-black-box-of-it-for-ceos/#comments</comments>
		<pubDate>Tue, 28 Aug 2012 16:46:28 +0000</pubDate>
		<dc:creator>Vincent Delaroche</dc:creator>
				<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Productivity Measurement]]></category>
		<category><![CDATA[Performance measurement]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[software measurement]]></category>
		<category><![CDATA[The Consortium for IT Software Quality]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4333</guid>
		<description><![CDATA[I spend some of my time with CEOs or CFOs, and time and again they tell me that IT is a black box that’s difficult, if not impossible, to measure. They can’t measure productivity. They can’t measure output. They can’t measure outcomes. They can’t measure risk. But, the thing they can measure is the IT cost. Just this week the CEO of a well-known financial services company told me: “I have 2,000 people working in IT with a budget of $200 million a year, and yet I have no idea how the development teams are doing in relation to the competition, or if I’m even getting my money’s worth. And &#8230; <a href="http://blog.castsoftware.com/cracking-open-the-black-box-of-it-for-ceos/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/cracking-open-the-black-box-of-it-for-ceos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Crusty the Clown might know more than your development team does about software testing</title>
		<link>http://blog.castsoftware.com/crusty-the-clown-might-know-more-than-your-development-team-does-about-software-testing/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=crusty-the-clown-might-know-more-than-your-development-team-does-about-software-testing</link>
		<comments>http://blog.castsoftware.com/crusty-the-clown-might-know-more-than-your-development-team-does-about-software-testing/#comments</comments>
		<pubDate>Thu, 09 Aug 2012 16:33:57 +0000</pubDate>
		<dc:creator>Charles Gerth</dc:creator>
				<category><![CDATA[Software Demystified]]></category>
		<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Application Development]]></category>
		<category><![CDATA[Component-based development]]></category>
		<category><![CDATA[load testing]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4296</guid>
		<description><![CDATA[Anybody reading this post probably thinks they know all they need to know about component-based development. But in my experience I have found that many organizations don’t when it comes to complete component testing. There is one crucial aspect of component-based development that is potentially damaging to your career and to your company. But before I go there, let’s rehash why development teams love component-based development. Component-based development is a rules-based approach to defining, implementing, and composing independent components into a software system. What do we get out of this? Well, we get higher reuse, because once it’s built, many of the components can be reused again and again and &#8230; <a href="http://blog.castsoftware.com/crusty-the-clown-might-know-more-than-your-development-team-does-about-software-testing/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/crusty-the-clown-might-know-more-than-your-development-team-does-about-software-testing/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>3 Simple Tips to Maintaining a Rock-Solid Software Architecture</title>
		<link>http://blog.castsoftware.com/3-simple-tips-to-maintaining-a-rock-solid-software-architecture/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=3-simple-tips-to-maintaining-a-rock-solid-software-architecture</link>
		<comments>http://blog.castsoftware.com/3-simple-tips-to-maintaining-a-rock-solid-software-architecture/#comments</comments>
		<pubDate>Mon, 06 Aug 2012 14:11:42 +0000</pubDate>
		<dc:creator>Razak Ellafi</dc:creator>
				<category><![CDATA[Application Failure]]></category>
		<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Risk Management]]></category>
		<category><![CDATA[Architecture status check]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Software Development Life Cycle]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4251</guid>
		<description><![CDATA[I have some good news and I have some bad news. First, the good news: Most smart development teams invest a lot of time designing a rock-solid architecture before the first line of code is even written for a new application. Now, the bad news: Once the architecture is designed, the conversation about it often ends. It’s built and then forgotten while the team runs off and builds the app, or when the application is transferred to a new development team. Thoughtfully designed architectures with solid design principles might begin to degrade almost the instant they are implemented. How can a team maintain a proper architecture, iteration after iteration? There’s &#8230; <a href="http://blog.castsoftware.com/3-simple-tips-to-maintaining-a-rock-solid-software-architecture/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/3-simple-tips-to-maintaining-a-rock-solid-software-architecture/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Tech Babel Fish for CFOs</title>
		<link>http://blog.castsoftware.com/the-tech-babel-fish-for-cfos/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-tech-babel-fish-for-cfos</link>
		<comments>http://blog.castsoftware.com/the-tech-babel-fish-for-cfos/#comments</comments>
		<pubDate>Thu, 26 Jul 2012 20:46:51 +0000</pubDate>
		<dc:creator>Pete Pizzutillo</dc:creator>
				<category><![CDATA[Software Analysis]]></category>
		<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Quality]]></category>
		<category><![CDATA[Software Risk Management]]></category>
		<category><![CDATA[Technical Debt]]></category>
		<category><![CDATA[Application intelligence]]></category>
		<category><![CDATA[Coding patterns]]></category>
		<category><![CDATA[Risk]]></category>
		<category><![CDATA[software maintenance]]></category>
		<category><![CDATA[Technical debt]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4119</guid>
		<description><![CDATA[Any advocate for better software quality knows that one of the biggest challenges is helping the CIO reach the CFO. When your team needs a budget for an important project, those conversations often break down. Thanks to the unavoidable technical complexity of IT, oftentimes the CIO might as well be speaking Esperanto to the CFO. When it comes to budgeting, IT might be the least-understood department in your organization. And what the CFO doesn’t understand, he doesn’t budget for. Instead, capital that should rightfully go towards IT growth and innovation is allocated to other groups and initiatives. That dulls the organization’s competitive edge, and can have a toxic effect on &#8230; <a href="http://blog.castsoftware.com/the-tech-babel-fish-for-cfos/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/the-tech-babel-fish-for-cfos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Android Application Failures Still Try Our Souls</title>
		<link>http://blog.castsoftware.com/android-application-failures-still-try-our-souls/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-application-failures-still-try-our-souls</link>
		<comments>http://blog.castsoftware.com/android-application-failures-still-try-our-souls/#comments</comments>
		<pubDate>Tue, 03 Jul 2012 09:39:44 +0000</pubDate>
		<dc:creator>Jonathan Bloom</dc:creator>
				<category><![CDATA[Application Failure]]></category>
		<category><![CDATA[Software Analysis]]></category>
		<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Quality]]></category>
		<category><![CDATA[Software Risk Management]]></category>
		<category><![CDATA[Application Development]]></category>
		<category><![CDATA[application failure]]></category>
		<category><![CDATA[Application Quality]]></category>
		<category><![CDATA[application security]]></category>
		<category><![CDATA[automated analysis and measurement]]></category>
		<category><![CDATA[software analysis]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Structural Analysis]]></category>
		<category><![CDATA[structural quality]]></category>
		<category><![CDATA[Technical debt]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4056</guid>
		<description><![CDATA[Happy Independence Day everybody! I only hope those of you reading this on your Android device have not turned it sideways or performed some other seemingly innocuous action that has made this application fail. I say this because I recently read yet another blog about “workarounds” to compensate for application failures inherent in Android devices. These pieces have become almost ubiquitous over the past 18 months to the point where one would think Google would just go back and perform the structural quality analysis it needs to do to address the issues. Their failure to do so reminds me on this day before Independence Day of the opening lines of &#8230; <a href="http://blog.castsoftware.com/android-application-failures-still-try-our-souls/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/android-application-failures-still-try-our-souls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Foretelling Facebook’s IPO Failure</title>
		<link>http://blog.castsoftware.com/foretelling-facebook%e2%80%99s-ipo-failure/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=foretelling-facebook%25e2%2580%2599s-ipo-failure</link>
		<comments>http://blog.castsoftware.com/foretelling-facebook%e2%80%99s-ipo-failure/#comments</comments>
		<pubDate>Thu, 28 Jun 2012 09:21:16 +0000</pubDate>
		<dc:creator>Jonathan Bloom</dc:creator>
				<category><![CDATA[Application Failure]]></category>
		<category><![CDATA[Software Analysis]]></category>
		<category><![CDATA[Software Measurement]]></category>
		<category><![CDATA[Software Risk Management]]></category>
		<category><![CDATA[application failure]]></category>
		<category><![CDATA[Application Quality]]></category>
		<category><![CDATA[automated analysis and measurement]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[nasdaq]]></category>
		<category><![CDATA[software analysis]]></category>
		<category><![CDATA[Software Quality]]></category>
		<category><![CDATA[structural quality]]></category>
		<category><![CDATA[Technical debt]]></category>

		<guid isPermaLink="false">http://blog.castsoftware.com/?p=4039</guid>
		<description><![CDATA[I’m not one who believes in fortune tellers or those who claim to be able to predict the future. Heck, I don’t even read my horoscope and cringe whenever someone attempts to force it upon me. Only when my wife has attempted to read me my horoscope have I offered even as much as a polite “hmm.” Nevertheless there are many out there who swear by those who claim to be able to predict the future, especially in the financial industry. And while there were those who predicted a rocky road for Facebook&#8217;s IPO, it is doubtful that anybody could have foreseen NASDAQ&#8217;s technical melt down that surrounded the Facebook IPO. &#8230; <a href="http://blog.castsoftware.com/foretelling-facebook%e2%80%99s-ipo-failure/">Read More <i class="icon-chevron-right"></i></a>]]></description>
		<wfw:commentRss>http://blog.castsoftware.com/foretelling-facebook%e2%80%99s-ipo-failure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 1.955 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-05-17 14:34:11 -->
