<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://norbertbieberstein.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Norbert Bieberstein</title>
 <link>http://norbertbieberstein.sys-con.com/</link>
 <description>Latest News from Norbert Bieberstein</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 08:20:22 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>SOA Book Excerpt: The First-Class Constructs of SOA - Part 3</title>
 <link>http://norbertbieberstein.sys-con.com/node/674146</link>
 <description>The specification phase helps design the details of the three first-class constructs of SOA: services, service components, and flows. It uses a combination of three high-level activities to determine which services to expose, provides a detailed specification for the exposed services, and specifies the flows (processes) and service components. The three activities are called service specification, subsystem analysis, and component specification.&lt;p&gt;&lt;a href=&quot;http://norbertbieberstein.sys-con.com/node/674146&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 17 Sep 2008 13:20:00 EDT</pubDate>
 <guid isPermaLink="true">http://norbertbieberstein.sys-con.com/node/674146</guid>
 <comments>http://norbertbieberstein.sys-con.com/node/674146#feedback</comments>
</item>
<item>
 <title>SOA Book Excerpt: Service Oriented Modeling and Architecture - Part 2</title>
 <link>http://norbertbieberstein.sys-con.com/node/667647</link>
 <description>Service Oriented Modeling and Architecture (SOMA) is a modeling and design technique developed by IBM that provides prescriptive steps for how to enable target business processes by defining and developing a service-based IT solution. SOMA provides the communication link between the business requirements and the IT solution. It provides guidance on how to use business model and information as inputs to derive and define a service-based IT model.&lt;p&gt;&lt;a href=&quot;http://norbertbieberstein.sys-con.com/node/667647&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 09 Sep 2008 16:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://norbertbieberstein.sys-con.com/node/667647</guid>
 <comments>http://norbertbieberstein.sys-con.com/node/667647#feedback</comments>
</item>
<item>
 <title>SOA Book Excerpt: A Methodology for Service Modeling and Design - Part 1</title>
 <link>http://norbertbieberstein.sys-con.com/node/664388</link>
 <description>When the programming model shifted from the traditional procedural model to that of object-orientation, a major paradigm shift occurred in the world of IT development. The focus was on encapsulating the state and behavior of entities and calling that encapsulation a class. Instances of a class were called objects, which occupied some space in the memory. &lt;p&gt;&lt;a href=&quot;http://norbertbieberstein.sys-con.com/node/664388&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 04 Sep 2008 14:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://norbertbieberstein.sys-con.com/node/664388</guid>
 <comments>http://norbertbieberstein.sys-con.com/node/664388#feedback</comments>
</item>
<item>
 <title>SOA Project Planning Aspects</title>
 <link>http://norbertbieberstein.sys-con.com/node/168398</link>
 <description>The architectural consideration of SOA in the preceding chapter offers advice on what directions to choose and how to define the strategic goals for an SOA project. This chapter takes the next step toward execution by focusing on how to plan an SOA project. The topics in this chapter constitute the best practices we have uncovered for forming a project office (see Section 4.1), how to define the phases of SOA adoption, the need for and mechanisms of SOA governance, and finally, the various project roles and how they interact with each other.&lt;p&gt;&lt;a href=&quot;http://norbertbieberstein.sys-con.com/node/168398&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 11 Jan 2006 14:30:00 EST</pubDate>
 <guid isPermaLink="true">http://norbertbieberstein.sys-con.com/node/168398</guid>
 <comments>http://norbertbieberstein.sys-con.com/node/168398#feedback</comments>
</item>
</channel>
</rss>
