<?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"
	>
<channel>
	<title>Comments on: Automation - The Key Benefit</title>
	<atom:link href="http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/feed/" rel="self" type="application/rss+xml" />
	<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/</link>
	<description>Thoughts on software development and related, by Abhijit Nadgouda</description>
	<pubDate>Tue, 06 Jan 2009 20:27:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: The User Interface Friction &#124; iface thoughts</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-53283</link>
		<dc:creator>The User Interface Friction &#124; iface thoughts</dc:creator>
		<pubDate>Sat, 19 May 2007 05:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-53283</guid>
		<description>[...] principle I try to follow in automation, is to avoid introducing new entities and new actions. The automation should be as close as [...]</description>
		<content:encoded><![CDATA[<p>[...] principle I try to follow in automation, is to avoid introducing new entities and new actions. The automation should be as close as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A User, A Slave on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-12991</link>
		<dc:creator>A User, A Slave on iface thoughts</dc:creator>
		<pubDate>Thu, 22 Feb 2007 09:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-12991</guid>
		<description>[...] have maintained that the key benefit of tools, especially software tools, is automation. Automation can boos performance, productivity and efficiency. It cannot replace your knowledge or [...]</description>
		<content:encoded><![CDATA[<p>[...] have maintained that the key benefit of tools, especially software tools, is automation. Automation can boos performance, productivity and efficiency. It cannot replace your knowledge or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theory Of Constraints And Software ROI on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-8750</link>
		<dc:creator>Theory Of Constraints And Software ROI on iface thoughts</dc:creator>
		<pubDate>Tue, 30 Jan 2007 13:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-8750</guid>
		<description>[...] manually and hence was restricted to doing it only once a month. Once they bought a software which automated it, the constraint was broken. However it still did not benefit a lot because they still kept on [...]</description>
		<content:encoded><![CDATA[<p>[...] manually and hence was restricted to doing it only once a month. Once they bought a software which automated it, the constraint was broken. However it still did not benefit a lot because they still kept on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domain Driven Design Quickly on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-2625</link>
		<dc:creator>Domain Driven Design Quickly on iface thoughts</dc:creator>
		<pubDate>Tue, 12 Dec 2006 17:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-2625</guid>
		<description>[...] Domain Driven Design is a way of thinking about software development. To start, think about software as solution of a domain problem, automation of certain domain tasks. What is domain you ask. Domain is any specific subject or area of operations that a organization operates within. [...]</description>
		<content:encoded><![CDATA[<p>[...] Domain Driven Design is a way of thinking about software development. To start, think about software as solution of a domain problem, automation of certain domain tasks. What is domain you ask. Domain is any specific subject or area of operations that a organization operates within. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moore&#8217;s Law Milestone on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-2010</link>
		<dc:creator>Moore&#8217;s Law Milestone on iface thoughts</dc:creator>
		<pubDate>Mon, 27 Nov 2006 12:51:50 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-2010</guid>
		<description>[...] One of the better impacts will be that the factor of cost in technology adoption will get weaker. Having said that, I think cost of software has been increasing for the reason that it is finding more applications in business. Well, you can also look at it as investment when you have to keep a tab on the ROI. As software methodologies have evolved we have become better at the ROI, but even the investment has got more expensive. Open source plays a big role in adopting software in a quicker way, but if the effort is counted along with the money, the overall effort in adopting software is much higher compared to the hardware. The lion&#8217;s share in this is the learning curve for using software and using it the right way is the only way of getting the optimum ROI. Nothing louder than this can shout for software being simple to use, but without sacrificing functionality. As Einstein says, &#8220;Everything should be made as simple as possible, but not simpler.&#8221; This balance is the key to successful automation - the ultimate benefit of hardware and software both! [...]</description>
		<content:encoded><![CDATA[<p>[...] One of the better impacts will be that the factor of cost in technology adoption will get weaker. Having said that, I think cost of software has been increasing for the reason that it is finding more applications in business. Well, you can also look at it as investment when you have to keep a tab on the ROI. As software methodologies have evolved we have become better at the ROI, but even the investment has got more expensive. Open source plays a big role in adopting software in a quicker way, but if the effort is counted along with the money, the overall effort in adopting software is much higher compared to the hardware. The lion&#8217;s share in this is the learning curve for using software and using it the right way is the only way of getting the optimum ROI. Nothing louder than this can shout for software being simple to use, but without sacrificing functionality. As Einstein says, &#8220;Everything should be made as simple as possible, but not simpler.&#8221; This balance is the key to successful automation - the ultimate benefit of hardware and software both! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iface thoughts &#187; Blog Archive &#187; OOP And FP</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-1139</link>
		<dc:creator>iface thoughts &#187; Blog Archive &#187; OOP And FP</dc:creator>
		<pubDate>Sat, 04 Nov 2006 13:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-1139</guid>
		<description>[...] I always like to confirm my understandings of the technology world with the real world. I always like to express benefits of technology in the layman&#8217;s language. Why? Because I feel that technology is just a means of solving problems and providing value in the real world. My peace of mind with Object Oriented Programming (OOP) stems from my conviction that it helps build the software as close as possible to the real world, which is the best possible case of automation. All my understanding of OOP is based on interface, not the keyword, but the concept. Things like these help me convince others why and what difference OOP can make. In business terms, provide the bottom-line justification. [...]</description>
		<content:encoded><![CDATA[<p>[...] I always like to confirm my understandings of the technology world with the real world. I always like to express benefits of technology in the layman&#8217;s language. Why? Because I feel that technology is just a means of solving problems and providing value in the real world. My peace of mind with Object Oriented Programming (OOP) stems from my conviction that it helps build the software as close as possible to the real world, which is the best possible case of automation. All my understanding of OOP is based on interface, not the keyword, but the concept. Things like these help me convince others why and what difference OOP can make. In business terms, provide the bottom-line justification. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iface thoughts &#187; Blog Archive &#187; Semantic Markup</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-867</link>
		<dc:creator>iface thoughts &#187; Blog Archive &#187; Semantic Markup</dc:creator>
		<pubDate>Wed, 18 Oct 2006 14:06:55 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-867</guid>
		<description>[...] Semantic Markup can make automation easier. One of the bigger problems in automation is that the data is not addressed the same everywhere. Semantic Markup can be used to build Semantic Web and software can be used for maximum benefit. [...]</description>
		<content:encoded><![CDATA[<p>[...] Semantic Markup can make automation easier. One of the bigger problems in automation is that the data is not addressed the same everywhere. Semantic Markup can be used to build Semantic Web and software can be used for maximum benefit. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iface thoughts &#187; Blog Archive &#187; Theory Of Constraints And Software Concerns</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-724</link>
		<dc:creator>iface thoughts &#187; Blog Archive &#187; Theory Of Constraints And Software Concerns</dc:creator>
		<pubDate>Fri, 22 Sep 2006 03:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-724</guid>
		<description>[...] TOC tells that an organization can benefit if its constraints are targeted and resolved. If a software has to be beneficial, it has to follow the same way. The key benefit of software is automation - automation of processes. TOC, through its focus on constraints, which are part of processes in an organization, typically leading to BPR. Use of TOC in Business or System Modeling can lead to right automation of these optimized processes which will provide maximum benefit to the organization. [...]</description>
		<content:encoded><![CDATA[<p>[...] TOC tells that an organization can benefit if its constraints are targeted and resolved. If a software has to be beneficial, it has to follow the same way. The key benefit of software is automation - automation of processes. TOC, through its focus on constraints, which are part of processes in an organization, typically leading to BPR. Use of TOC in Business or System Modeling can lead to right automation of these optimized processes which will provide maximum benefit to the organization. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhijit Nadgouda @ iface &#187; Software Development Is Like Running A Restaurant</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-309</link>
		<dc:creator>Abhijit Nadgouda @ iface &#187; Software Development Is Like Running A Restaurant</dc:creator>
		<pubDate>Sat, 22 Jul 2006 05:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-309</guid>
		<description>[...] Having said all this, running a restaurant is still a metaphor. The biggest difference is that the software development is about automation that is expected to serve for a longer time. This is what makes it complex, it is expected to serve for a time in which the customer&#8217;s needs and requirements keep changing. [...]</description>
		<content:encoded><![CDATA[<p>[...] Having said all this, running a restaurant is still a metaphor. The biggest difference is that the software development is about automation that is expected to serve for a longer time. This is what makes it complex, it is expected to serve for a time in which the customer&#8217;s needs and requirements keep changing. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhijit Nadgouda @ iface &#187; Blog Archive &#187; Requirements Are Important</title>
		<link>http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-308</link>
		<dc:creator>Abhijit Nadgouda @ iface &#187; Blog Archive &#187; Requirements Are Important</dc:creator>
		<pubDate>Mon, 03 Jul 2006 12:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/02/06/automation-the-key-benefit/#comment-308</guid>
		<description>[...] Most of the times businesses decide that they want to start using a software because they think that it will solve their problems. However, the problems are only the symptoms. It is important to gather more information so that the diagnosis can be successful and the right cure can be proposed. Especially in today&#8217;s age, softwares are not just adopted by businesses, softwares become integral to execution of the business processes. However, the software can provide the perceived Return On Investment (ROI) only if the automation attacks not the problems, but the root causes of these problems. To be able to do that it is imperative to gather more information - which is the requirements gathering. [...]</description>
		<content:encoded><![CDATA[<p>[...] Most of the times businesses decide that they want to start using a software because they think that it will solve their problems. However, the problems are only the symptoms. It is important to gather more information so that the diagnosis can be successful and the right cure can be proposed. Especially in today&#8217;s age, softwares are not just adopted by businesses, softwares become integral to execution of the business processes. However, the software can provide the perceived Return On Investment (ROI) only if the automation attacks not the problems, but the root causes of these problems. To be able to do that it is imperative to gather more information - which is the requirements gathering. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
