<?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/"
	>

<channel>
	<title>Shortcast opinions and ideas &#187; Architecture</title>
	<atom:link href="http://www.gumza.com/tag/architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gumza.com</link>
	<description>-zunGumza .. converse</description>
	<lastBuildDate>Fri, 21 Jan 2011 21:59:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Twelve Metrics to Monitor for SOA&#8217;s ROI</title>
		<link>http://www.gumza.com/2009/04/24/twelve-metrics-to-monitor-for-soas-roi/</link>
		<comments>http://www.gumza.com/2009/04/24/twelve-metrics-to-monitor-for-soas-roi/#comments</comments>
		<pubDate>Sat, 25 Apr 2009 04:47:57 +0000</pubDate>
		<dc:creator>TTB</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Architecture]]></category>

		<guid isPermaLink="false">http://www.gumza.com/2009/04/24/twelve-metrics-to-monitor-for-soas-roi/</guid>
		<description><![CDATA[SOA expert and blogger David Linthicum and Dan Foody of Progress&#8217;s SOA Infrastructure blog have excellent caveats about calculating SOA&#8217;s ROI and what will and won&#8217;t impress the business when it comes to SOA metrics.
Here goes:

Return on investment (ROI) per service (Mark Little, CTO of Red Hat). ROI per service can serve as an early [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p>SOA expert and blogger David Linthicum and Dan Foody of Progress&#8217;s SOA Infrastructure blog have excellent caveats about calculating SOA&#8217;s ROI and what will and won&#8217;t impress the business when it comes to SOA metrics.</p>
<p>Here goes:</p>
<ol>
<li><strong>Return on investment (ROI) per service</strong> (Mark Little, CTO of Red Hat). ROI per service can serve as an early indicator of your overall ROI. Little warns that all services won&#8217;t generate a positive ROI, and some services may only perform a business task in conjunction with others, which means you&#8217;d have to look at the ROI across several services.</li>
<li><strong>Revenue per service</strong> (Little). Not all services will generate revenue, of course.</li>
<li><strong>Service growth rate/reuse</strong> (Little), or Number of New Services Generated and Used as a Percentage of Total Services (Dr. Jerry Smith, CTO of Symphony Services). This metric can help you ensure you&#8217;re reusing services when possible and not developing redundant services. It&#8217;s also useful in calculating ROI for a service.</li>
<li><strong>Business agility</strong> (Little and Linthicum) or Mean Time to Service Development (Smith), measured in how long it takes for a service to go from the design stage to the deployment stage.</li>
<li><strong>Mean Time to Service Change</strong> (Smith). The time it takes to change a service is another option for measuring agility.</li>
<li><strong>Reliability</strong> (Little), measured in mean time to failure (MTTF) and mean time to recovery (MTTR). Smith calls this “Service availability,” but he adds another factor to measure as part of it: “Cost of Not Using or Stopping a Service.&#8221; Smith notes that a well-designed SOA will have “low shutdown or switching costs.”</li>
<li><strong>Service Vitality Index</strong>, (Smith) which “tracks the amount of revenue from new services over the last 12 months as a proportion of total service revenue.”</li>
</ol>
<p>Leo Shuster, who is responsible for National City Bank&#8217;s SOA, wrote an excellent piece on SOA ROI in February and, in addition to many of the above IT metrics, he suggested you also look at the following business and financial metrics:</p>
<p><strong>Business and financial Metrics</strong></p>
<ol>
<li>Efficiencies associated with service reuse</li>
<li>Integration time savings</li>
<li>Related opportunity costs</li>
<li>Cost savings/avoidance</li>
<li>Reduction in project and maintenance costs</li>
</ol>
<p>He also offered this formula for calculating SOA&#8217;s ROI:</p>
<p>SOA ROI ($) = Cost Savings/Efficiencies Achieved &#8211; All SOA-Related Investments</p>
<p>or</p>
<p>SOA ROI (%) = SOA ROI ($) All SOA-Related Investments</p>
<p><a href="http://www.itbusinessedge.com/cm/blogs/lawson/twelve-metrics-to-monitor-for-soas-roi/?cs=32060" title="Twelve metrics to monitor SOA">Source</a></p>
     

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.gumza.com/2009/04/24/twelve-metrics-to-monitor-for-soas-roi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>10 Must-Know Topics for Software Architects in 2009
10 Must-Know Topics for Software Architects in 2009</title>
		<link>http://www.gumza.com/2009/04/23/10-must-know-topics-for-software-architects-in-200910-must-know-topics-for-software-architects-in-2009/</link>
		<comments>http://www.gumza.com/2009/04/23/10-must-know-topics-for-software-architects-in-200910-must-know-topics-for-software-architects-in-2009/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 18:08:45 +0000</pubDate>
		<dc:creator>TTB</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[skills]]></category>

		<guid isPermaLink="false">http://www.gumza.com/2009/04/23/10-must-know-topics-for-software-architects-in-200910-must-know-topics-for-software-architects-in-2009/</guid>
		<description><![CDATA[Last few years technology stack has changed quite significantly and so has the need for skills to architect the solutions understanding these technology elements. i created a quick list from dion hindcliffe&#8217;s 10 Must-Know Topics for Software Architects in 2009. Read the article for more detailed explanation on each in the list mentioned here.

&#160;&#160;

Cloud Computing.
Non-relational [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p><strong>Last few years technology stack has changed quite significantly and so has the need for skills to architect the solutions understanding these technology elements. i created a quick list from dion hindcliffe&#8217;s 10 Must-Know Topics for Software Architects in 2009. <span style="font-weight: normal;">Read the <a href="http://hinchcliffe.org/archive/2009/03/17/16712.aspx" title="10things architect must know">article</a> for more detailed explanation on each in the list mentioned here.</span></strong></p>
<p style="text-align: center;"><strong><img src="http://www.gumza.com/wp-content/uploads/2009/04/200904231056.jpg" width="199" height="287" alt="200904231056.jpg" /></strong></p>
<p>&nbsp;&nbsp;</p>
<ol>
<li>Cloud Computing.</li>
<li>Non-relational databases.</li>
<li>Next-generation distributed computing.</li>
<li>Web-Oriented Architecture (WOA).</li>
<li>Mashups.</li>
<li>Open Supply Chains via APIs.</li>
<li>Dynamic Languages.</li>
<li>Social computing.</li>
<li>Crowdsourcing and peer production architectures.</li>
<li>New Application Models.</li>
</ol>
<p></p>
     

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.gumza.com/2009/04/23/10-must-know-topics-for-software-architects-in-200910-must-know-topics-for-software-architects-in-2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

