<?xml version="1.0"?>
<rss version="2.0">

<channel>
	<title>The SOA Magazine Contributions by Larry Guger</title>
	<link>http://www.soamag.com</link>
	<description>
The SOA Magazine is a monthly online publication provided by SOA Systems Inc. and Prentice Hall/PearsonPTR and is officially associated with the "Prentice Hall Service-Oriented Computing Series from Thomas Erl."
	</description>
	<category>SOA</category>
	<language>en-us</language>
	<copyright>Copyright 2006-2008, SOA Systems Inc.</copyright> 

	<item>
		<title>Service-Orientation and Systems of Record: The Northwest Customer Support Example</title>
		<link>http://www.soamag.com/I22/0908-3.asp</link>
		<description>
Service-orientation makes information systems more flexible as well as more agile. Information technology systems can be integrated better and code that was written once for one system can be leveraged by IT departments for other systems. These are the key goals of using a service -oriented approach to systems design. This paper is in part a retrospective and in part a direction recommendation of, and for, the service-orientation approaches taken for enterprise systems in general. Lessons learned and new approaches will be discussed as well as the specific needs that arise when dealing with systems of record and data submitted to those systems. Examples using customer data will be used throughout.
 		</description>
		<category>SOA</category>
		<guid>http://www.soamag.com/I22/0908-3.asp#When:22.09.08</guid>
	</item>
	<item>
		<title>Service-Orientation vs. Object-Orientation: Understanding the Impedance Mismatch</title>
		<link>http://www.soamag.com/I20/0708-1.asp</link>
		<description>
Object-oriented programming languages and techniques provide a powerful means for designing and building applications. These techniques do not always translate well into a service-oriented paradigm. Service-orientation demands a different set of design guidelines and requirements than object-oriented design approaches because we are essentially outfitting programs with new characteristics in support of new goals. Understanding how an object-oriented design can negatively impact a service-oriented design is key to building services that support an agile enterprise. This article examines where the two designs impact each other as well as methods for addressing their incompatibilities (which we refer to as the "impedence mismatch") while still leveraging opportunities to use them together.
 		</description>
		<category>SOA</category>
		<guid>http://www.soamag.com/I20/0708-1.asp#When:18.07.08</guid>
	</item>

</channel>
</rss>
