<?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>LIXLI - Health, Memory and Study Skills &#187; Software Architect</title>
	<atom:link href="http://www.lixli.com/category/software-architect/feed" rel="self" type="application/rss+xml" />
	<link>http://www.lixli.com</link>
	<description>Get Noticed !</description>
	<lastBuildDate>Sat, 30 Oct 2010 17:16:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<!-- google_ad_section_end --><!-- google_ad_section_start -->	<item>
		<title>IBM Cognos Powerplay Tutorial</title>
		<link>http://www.lixli.com/software-architect/ibm-cognos-powerplay-tutorial.html</link>
		<comments>http://www.lixli.com/software-architect/ibm-cognos-powerplay-tutorial.html#comments</comments>
		<pubDate>Sat, 03 Oct 2009 19:01:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Cognos Bi Tutorial]]></category>
		<category><![CDATA[Cognos Business Intelligence]]></category>
		<category><![CDATA[Cognos Cubes Tutorial]]></category>
		<category><![CDATA[Cognos Data Warehousing]]></category>
		<category><![CDATA[Cognos Impromptu Tutorial]]></category>
		<category><![CDATA[Cognos Powerplay Cubes]]></category>
		<category><![CDATA[Cognos Powerplay Training]]></category>
		<category><![CDATA[Cognos Powerplay Transformer]]></category>
		<category><![CDATA[Cognos Powerplay Tutorial]]></category>
		<category><![CDATA[Cognos Reportnet Tutorial]]></category>
		<category><![CDATA[Cognos Transformer Tutorial]]></category>
		<category><![CDATA[Ibm Cognos Powerplay]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=207</guid>
		<description><![CDATA[Cognos PowerPlay lets you identify and analyze trends in business and financial performance for better business decisions. IBM Cognos PowerPlay lets you analyze large volumes of dimensionally modeled data with sub-second response times using either a Windows client or Web browser. View data from any angle and in any combination to identify and analyze the [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/ibm-cognos-powerplay-tutorial.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bridge Design Pattern &#8211; Concepts Code Examples</title>
		<link>http://www.lixli.com/software-architect/bridge-design-pattern-concepts-code-examples.html</link>
		<comments>http://www.lixli.com/software-architect/bridge-design-pattern-concepts-code-examples.html#comments</comments>
		<pubDate>Mon, 24 Aug 2009 14:26:50 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Adapter Design Pattern]]></category>
		<category><![CDATA[Adapter Design Pattern C]]></category>
		<category><![CDATA[Bridge Design Pattern]]></category>
		<category><![CDATA[Composite Design Pattern]]></category>
		<category><![CDATA[Different Bridge Designs]]></category>
		<category><![CDATA[Mandatory Bridge Designs]]></category>
		<category><![CDATA[Popsicle Bridge Designs]]></category>
		<category><![CDATA[Strong Bridge Designs]]></category>
		<category><![CDATA[Truss Bridges Designs]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=169</guid>
		<description><![CDATA[Bridge pattern is useful when both the class as well as what it does varies. The class itself can be thought of as the. The bridge pattern can also be thought of as two layers of abstraction. : the implementation can be decoupled even more by deferring the presence of the implementation to the point [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/bridge-design-pattern-concepts-code-examples.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Thoughts on Singleton Design Pattern &#8211; Good Bad Ugly</title>
		<link>http://www.lixli.com/software-architect/thoughts-on-singleton-design-pattern-good-bad-ugly.html</link>
		<comments>http://www.lixli.com/software-architect/thoughts-on-singleton-design-pattern-good-bad-ugly.html#comments</comments>
		<pubDate>Mon, 17 Aug 2009 11:12:11 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Design Patterns Singleton]]></category>
		<category><![CDATA[Gang Of Four Singleton]]></category>
		<category><![CDATA[Gof Singleton Pattern]]></category>
		<category><![CDATA[Python Singleton Pattern]]></category>
		<category><![CDATA[Singleton Double Checked Locking]]></category>
		<category><![CDATA[Singleton Pattern Asp Net]]></category>
		<category><![CDATA[Singleton Pattern C]]></category>
		<category><![CDATA[Static Methods Singleton]]></category>

		<guid isPermaLink="false">http://www.lixli.com/software-architect/thoughts-on-singleton-design-pattern-good-bad-ugly.html</guid>
		<description><![CDATA[Singleton patternis one of the best-known patterns in software engineering. Essentially, a singleton is a class which only allows a single instance of itself to be created, and usually gives simple access to that instance. Most commonly, singletons don&#8217;t allow any parameters to be specified when creating the instance &#8211; as otherwise a second request [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/thoughts-on-singleton-design-pattern-good-bad-ugly.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is It Legal To Copyright An Application?</title>
		<link>http://www.lixli.com/software-architect/is-it-legal-to-copyright-an-application.html</link>
		<comments>http://www.lixli.com/software-architect/is-it-legal-to-copyright-an-application.html#comments</comments>
		<pubDate>Fri, 14 Aug 2009 18:43:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Copyrighting Intellectual Property]]></category>
		<category><![CDATA[Copyrighting Photographs]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=153</guid>
		<description><![CDATA[Copyright Nearly every freeware or shareware application contains the text &#8220;Copyright (c) 19xx by &#8230;&#8221;. But is it legal to put that message into an application without registering the copyright? Yes! It is legal! Yes, it is legal to copyright an application. Under the Berne convention, copyright is granted to you by default the moment [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/is-it-legal-to-copyright-an-application.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is Good Software?</title>
		<link>http://www.lixli.com/software-architect/what-is-good-software.html</link>
		<comments>http://www.lixli.com/software-architect/what-is-good-software.html#comments</comments>
		<pubDate>Fri, 14 Aug 2009 14:40:11 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Write Good Software]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=151</guid>
		<description><![CDATA[Matthias Kahlert&#8217;s views on &#8211; What should be called a Good Software. Software Quality If you want the people to pay for your application it should have a high quality standard. It should be adequate to commercial application. You should especially invest your time into the user interface. There can be as many good features [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/what-is-good-software.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Understand Software Version Numbers System</title>
		<link>http://www.lixli.com/software-architect/understand-software-version-numbers-system.html</link>
		<comments>http://www.lixli.com/software-architect/understand-software-version-numbers-system.html#comments</comments>
		<pubDate>Fri, 14 Aug 2009 14:34:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Apple Numbers Software]]></category>
		<category><![CDATA[Number 6 Software]]></category>
		<category><![CDATA[Number Six Software]]></category>
		<category><![CDATA[Software Build Number]]></category>
		<category><![CDATA[Software Release Numbering]]></category>
		<category><![CDATA[Software Serial Number]]></category>
		<category><![CDATA[Software Version Numbers]]></category>
		<category><![CDATA[Verizon Software Update Number]]></category>
		<category><![CDATA[Version Numbering System]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=149</guid>
		<description><![CDATA[Have you ever tried to decipher the software version numbers? Here is a nice article by Matthias Kahlert. Related Terms &#8211; Software Build Number, Version Numbering System, Software Release Numbering, Verizon Software Update Number, Apple Numbers Software, Number 6 Software, Software Serial Number, Number Six Software Have you ever wondered what the digits of the [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/understand-software-version-numbers-system.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is Composition in Object Oriented World?</title>
		<link>http://www.lixli.com/software-architect/what-is-composition-in-object-oriented-world.html</link>
		<comments>http://www.lixli.com/software-architect/what-is-composition-in-object-oriented-world.html#comments</comments>
		<pubDate>Sun, 02 Aug 2009 04:50:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Aggregation Object Oriented]]></category>
		<category><![CDATA[Composition Aggregation C++]]></category>
		<category><![CDATA[Uml Composition Aggregation]]></category>
		<category><![CDATA[Uml Notation Aggregation]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=105</guid>
		<description><![CDATA[Compositionis a method of reuse in which new functionality is obtained by creating an object composed of other objects. The new functionality is obtained by delegating functionality to one of the objects being composed. Sometimes it is called aggregation or containment, although some authors give special meanings to these terms. For example: Aggregation &#8211; when [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/what-is-composition-in-object-oriented-world.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is abstraction in Object Oriented World ?</title>
		<link>http://www.lixli.com/software-architect/what-is-abstraction-in-object-oriented-world.html</link>
		<comments>http://www.lixli.com/software-architect/what-is-abstraction-in-object-oriented-world.html#comments</comments>
		<pubDate>Sun, 02 Aug 2009 04:42:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Data Encapsulation Oops]]></category>
		<category><![CDATA[Multiple Inheritance Oops]]></category>
		<category><![CDATA[Oops Asp Net]]></category>
		<category><![CDATA[Oops Concepts Abstraction]]></category>
		<category><![CDATA[Oops In C]]></category>
		<category><![CDATA[Oops Interview Questions]]></category>
		<category><![CDATA[Oops Object Oriented Programming]]></category>
		<category><![CDATA[Oops Vb Net]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=102</guid>
		<description><![CDATA[Abstraction arises from a recognition of similarities between certain objects, situations, or processes in the real world, and the decision to concentrate upon those similarities and to ignore for the time being the differences. &#8212; Tony Hoare An abstraction denotes the essential characteristics of an object that distinguish it from all other kinds of objects [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/what-is-abstraction-in-object-oriented-world.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GoF Design Patterns Template</title>
		<link>http://www.lixli.com/software-architect/gof-design-patterns-template.html</link>
		<comments>http://www.lixli.com/software-architect/gof-design-patterns-template.html#comments</comments>
		<pubDate>Sun, 02 Aug 2009 03:49:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Gang Of Four Gof Patterns]]></category>
		<category><![CDATA[Gof Abstract Factory]]></category>
		<category><![CDATA[Gof Decorator Pattern]]></category>
		<category><![CDATA[GoF Design Patterns Template]]></category>
		<category><![CDATA[Gof Factory Pattern]]></category>
		<category><![CDATA[Gof Patterns C]]></category>
		<category><![CDATA[Gof Singleton Pattern]]></category>
		<category><![CDATA[Gof Strategy Pattern]]></category>
		<category><![CDATA[Observer Pattern Gof]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=97</guid>
		<description><![CDATA[The GoF design patterns are in the middle of these levels of abstraction A design pattern names, abstracts, and identifies key aspects of a common design structure that makes it useful for creating a reusable object-oriented design. The GoF design patterns are descriptions of communicating objects and classes that are customized to solve a general [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/gof-design-patterns-template.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design Patterns &#8211; Books to Master Design Patterns</title>
		<link>http://www.lixli.com/software-architect/design-patterns-books-to-master-design-patterns.html</link>
		<comments>http://www.lixli.com/software-architect/design-patterns-books-to-master-design-patterns.html#comments</comments>
		<pubDate>Sun, 02 Aug 2009 03:35:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Design Patterns Book]]></category>
		<category><![CDATA[Gang Of Four Object Oriented]]></category>
		<category><![CDATA[Object Oriented Abstraction]]></category>
		<category><![CDATA[Object Oriented Design Encapsulation]]></category>
		<category><![CDATA[Object Oriented Design Patterns C++]]></category>
		<category><![CDATA[Object Oriented Interfaces]]></category>
		<category><![CDATA[Prototype Object Oriented]]></category>
		<category><![CDATA[Smalltalk Object Oriented]]></category>
		<category><![CDATA[Uml Object Oriented Design]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=95</guid>
		<description><![CDATA[Here are some top notch books if you are interested in mastering Design Patterns. Related Terms: Object Oriented Design Patterns, Creational Patterns, Design Patterns Grady Booch, Design Patterns Erich Gamma, Addison Wesley Design Patterns, Ejb Design Patterns, Christopher Alexander Design Patterns, Facade Design Pattern, Analysis Patterns: Reusable Object Models, Martin Fowler, Addison-Wesley, 1997 AntiPatterns, Brown, [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/design-patterns-books-to-master-design-patterns.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design Patterns Notes</title>
		<link>http://www.lixli.com/software-architect/design-patterns-notes.html</link>
		<comments>http://www.lixli.com/software-architect/design-patterns-notes.html#comments</comments>
		<pubDate>Thu, 16 Jul 2009 05:43:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[.Net Design Patterns]]></category>
		<category><![CDATA[Design Patterns C++]]></category>
		<category><![CDATA[Design Patterns Pdf]]></category>
		<category><![CDATA[Design Patterns Php]]></category>
		<category><![CDATA[Design Patterns Tutorial]]></category>
		<category><![CDATA[J2ee Design Patterns]]></category>
		<category><![CDATA[Java Design Patterns]]></category>
		<category><![CDATA[Singleton Design Patterns]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=58</guid>
		<description><![CDATA[Overview of Design Patterns The concept of patterns was first introduced by Christopher Alexander in his work The Timeless Way of Building (1977). His patterns were originally aimed to capture knowledge and experience for designing and constructing buildings. Alexander noticed that all good architecture designs share a set of successful solutions. He called these principles [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/design-patterns-notes.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Quick Look at Design Patterns</title>
		<link>http://www.lixli.com/software-architect/a-quick-look-at-design-patterns.html</link>
		<comments>http://www.lixli.com/software-architect/a-quick-look-at-design-patterns.html#comments</comments>
		<pubDate>Fri, 03 Jul 2009 08:22:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Design Patterns Facade]]></category>
		<category><![CDATA[Design Patterns Microsoft]]></category>
		<category><![CDATA[Design Patterns Mvc]]></category>
		<category><![CDATA[Factory Design Patterns]]></category>
		<category><![CDATA[Object Oriented Design Patterns]]></category>
		<category><![CDATA[Singleton Design Patterns]]></category>
		<category><![CDATA[Uml]]></category>
		<category><![CDATA[Uml Design Patterns]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=48</guid>
		<description><![CDATA[Here we will look at what a design pattern means, the difference between design pattern and idiom What Is a Pattern? A pattern describes a problem that frequently occurs in software design and implementation, Based on experience, describes the solution to that problem that is robust and reusable. In short, Design Patterns are introduced to [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/a-quick-look-at-design-patterns.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Summary of Models Supported By Uml</title>
		<link>http://www.lixli.com/software-architect/summary-of-models-supported-by-uml.html</link>
		<comments>http://www.lixli.com/software-architect/summary-of-models-supported-by-uml.html#comments</comments>
		<pubDate>Fri, 03 Jul 2009 08:04:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Sparx Systems Uml]]></category>
		<category><![CDATA[Uml Deployment Diagram]]></category>
		<category><![CDATA[Uml Model Class Diagram]]></category>
		<category><![CDATA[Uml Model Eclipse]]></category>
		<category><![CDATA[Uml Model Tutorial]]></category>
		<category><![CDATA[Uml Object Oriented]]></category>
		<category><![CDATA[Uml Xml Schema]]></category>
		<category><![CDATA[Unified Modeling Language Uml]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=46</guid>
		<description><![CDATA[The following UML diagrams provide multiple viewpoints of the system under development. Use Case Diagrams Use case defines the scenarios in which the system is used. The inputs and possible outcomes of the system Analyst uses use case diagram to represent possible usages of the application We can also see the relationships among the use [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/summary-of-models-supported-by-uml.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Prefer Principles, Axioms And Analogies To Opinion And Taste</title>
		<link>http://www.lixli.com/software-architect/prefer-principles-axioms-and-analogies-to-opinion-and-taste.html</link>
		<comments>http://www.lixli.com/software-architect/prefer-principles-axioms-and-analogies-to-opinion-and-taste.html#comments</comments>
		<pubDate>Mon, 29 Jun 2009 09:13:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Agile Design Principles]]></category>
		<category><![CDATA[Agile Software Development Principles]]></category>
		<category><![CDATA[Dependency Inversion Principle]]></category>
		<category><![CDATA[Design Principles Design Patterns]]></category>
		<category><![CDATA[Liskov Substitution Principle]]></category>
		<category><![CDATA[Open Closed Principle]]></category>
		<category><![CDATA[Principles Object Oriented Design]]></category>
		<category><![CDATA[Software Design Concepts Principles]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=14</guid>
		<description><![CDATA[When creating your architecture you should explicitly use principles axioms and analogies to guide the creation. This gives the architecture a number of benefits that are not present if you simply create by implicitly leveraging your experience opinions and tastes. Documenting your architecture will be easier. You can start by describing the principles that were [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/prefer-principles-axioms-and-analogies-to-opinion-and-taste.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design Patterns &#8211; To Use Or Not To Use ?</title>
		<link>http://www.lixli.com/software-architect/design-patterns-to-use-or-not-to-use.html</link>
		<comments>http://www.lixli.com/software-architect/design-patterns-to-use-or-not-to-use.html#comments</comments>
		<pubDate>Mon, 29 Jun 2009 09:02:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Design Patterns Facade]]></category>
		<category><![CDATA[Design Patterns Microsoft]]></category>
		<category><![CDATA[Design Patterns Mvc]]></category>
		<category><![CDATA[Factory Design Patterns]]></category>
		<category><![CDATA[Object Oriented Design Patterns]]></category>
		<category><![CDATA[Singleton Design Patterns]]></category>
		<category><![CDATA[Uml Design Patterns]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=11</guid>
		<description><![CDATA[One of the problems of the fresh programmers today is that they get to hear a lot of contradictions, from equally credible people, on various topics in programming. One such controversial topic is use of GoF Design Patterns, especially the ones talked about in the book by GoF. This puts these programmers in a dilemma [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/design-patterns-to-use-or-not-to-use.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>If You Design It &#8211; You Should Be Able To Code It</title>
		<link>http://www.lixli.com/software-architect/if-you-design-it-you-should-be-able-to-code-it.html</link>
		<comments>http://www.lixli.com/software-architect/if-you-design-it-you-should-be-able-to-code-it.html#comments</comments>
		<pubDate>Mon, 29 Jun 2009 08:45:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Object Oriented Software Design]]></category>
		<category><![CDATA[Software Architectural Design]]></category>
		<category><![CDATA[Software Design Concepts]]></category>
		<category><![CDATA[Software Design Diagrams]]></category>
		<category><![CDATA[Software Design Life Cycle]]></category>
		<category><![CDATA[Software Design Phases]]></category>
		<category><![CDATA[Software Design Uml]]></category>
		<category><![CDATA[Software Module Design]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=9</guid>
		<description><![CDATA[As an architect, it&#8217;s tempting to create elaborate designs and abstractions that elegantly address the problem at hand. It is even more tempting to sprinkle new technologies into the project. At the end of the day, someone has to implement your design, and the architectural acrobatics that you have the developers perform impact the project. [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/if-you-design-it-you-should-be-able-to-code-it.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Your Customer is Not Your Customer !</title>
		<link>http://www.lixli.com/software-architect/your-customer-is-not-your-customer.html</link>
		<comments>http://www.lixli.com/software-architect/your-customer-is-not-your-customer.html#comments</comments>
		<pubDate>Mon, 29 Jun 2009 08:35:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Software Architect]]></category>
		<category><![CDATA[Customer Experience]]></category>
		<category><![CDATA[Customer Focus]]></category>
		<category><![CDATA[Customer Loyalty]]></category>
		<category><![CDATA[Customer Retention]]></category>
		<category><![CDATA[Customer Satisfaction]]></category>
		<category><![CDATA[Customer Segmentation]]></category>
		<category><![CDATA[Customer Value]]></category>

		<guid isPermaLink="false">http://www.lixli.com/?p=7</guid>
		<description><![CDATA[As you work in requirements meetings to design software pretend that your customer is not your customer. It turns out that this is a very easy thing to do because it is true. Your customer is not your customer. Your customer&#8217;s customer is your customer. If your customer&#8217;s customer wins your customer wins. Which means [...]]]></description>
		<wfw:commentRss>http://www.lixli.com/software-architect/your-customer-is-not-your-customer.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	<!-- google_ad_section_end --></channel>
</rss>

