<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Coding the Architecture - rbillington</title>
  <link>http://www.codingthearchitecture.com/authors/rbillington/</link>
  <description>Software architecture for developers</description>
  <language>en</language>
  <copyright>Coding the Architecture</copyright>
  <lastBuildDate>Wed, 03 Mar 2010 22:49:31 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Book Review: &#039;Software Systems Architecture - Working with Stakeholders Using Viewpoints and Perspectives&#039;</title>
    <link>http://www.codingthearchitecture.com/2007/03/18/book_review_software_systems_architecture_working_with_stakeholders_using_viewpoints_and_perspectives.html</link>
    
      
      
        <description>
          This is a book that I wish I&#039;d been able to read years ago because it widens the reader&#039;s horizon to include aspects of getting a system designed and built that as a developer you take for granted.&amp;nbsp; That said, it&#039;s a book that particularly resonates once you&#039;ve had some experience in an architectural role and had an opportunity to make some of the mistakes identified in the especially useful &#039;Problems and Pitfalls&#039; section in each chapter.&lt;p&gt;&lt;a href=&#034;http://www.codingthearchitecture.com/2007/03/18/book_review_software_systems_architecture_working_with_stakeholders_using_viewpoints_and_perspectives.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://www.codingthearchitecture.com/2007/03/18/book_review_software_systems_architecture_working_with_stakeholders_using_viewpoints_and_perspectives.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2007/03/18/book_review_software_systems_architecture_working_with_stakeholders_using_viewpoints_and_perspectives.html</guid>
    <pubDate>Sun, 18 Mar 2007 16:26:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Mastering the Requirements Process</title>
    <link>http://www.codingthearchitecture.com/2006/04/25/mastering_the_requirements_process.html</link>
    
      
        <description>
          &lt;p&gt;
I&#039;ve just received a copy of Addison-Wesley&#039;s &#034;Mastering the Requirements Process&#034; 2nd Edition to review over the next few weeks.  The blurb says:
&lt;blockquote&gt;
Mastering the Requirements Process, Second Edition, sets out an industry-proven process for gathering and verifying requirements with an eye toward today&#039;s agile development environments.  In this total update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs while doing the minimum requirements work according to the project&#039;s level of agility.
&lt;/blockquote&gt;
I&#039;ll be reading it over the next couple of weeks and posting a review after that.  Please feel free to post any specific questions and I&#039;ll try to answer them in the review.  
&lt;/p&gt;
        </description>
      
      
    
    
    
    <comments>http://www.codingthearchitecture.com/2006/04/25/mastering_the_requirements_process.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/04/25/mastering_the_requirements_process.html</guid>
    <pubDate>Tue, 25 Apr 2006 20:19:20 GMT</pubDate>
  </item>
  
  <item>
    <title>Book Review - &#039;POJOs in Action&#039; </title>
    <link>http://www.codingthearchitecture.com/2006/03/09/book_review_pojos_in_action.html</link>
    
      
      
        <description>
          Chris Richardson&#039;s book is a well-written and thorough guide to implementing familiar Enterprise Architecture patterns with POJOs.  Aimed at the designer, the book provides valuable advice on the benefits and potential pitfalls of using Spring, Hibernate, JDO and iBATIS to implement scalable, performant systems.  Highly recommended.&lt;p&gt;&lt;a href=&#034;http://www.codingthearchitecture.com/2006/03/09/book_review_pojos_in_action.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://www.codingthearchitecture.com/2006/03/09/book_review_pojos_in_action.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/03/09/book_review_pojos_in_action.html</guid>
    <pubDate>Thu, 09 Mar 2006 12:22:57 GMT</pubDate>
  </item>
  
  <item>
    <title>POJOs in Action</title>
    <link>http://www.codingthearchitecture.com/2006/02/14/pojos_in_action.html</link>
    
      
        <description>
          &lt;p&gt;
I have just received a copy of &lt;a href=&#034;http://www.manning.com/&#034;&gt;Manning&lt;/a&gt;&#039;s &#039;POJOs in Action - Developing Enterprise Applications with Lightweight Frameworks&#039; to review  over the next couple of weeks.  The blurb says:
&lt;blockquote&gt;
There is agreement in the Java community that EJBs often introduce more problems than they solve. Now there is a major trend toward lightweight technologies such as Hibernate, Spring, JDO, iBATIS, and others, all of which allow the developer to work directly with the simpler Plain Old Java Objects, or POJOs. Bowing to the new consensus, EJB 3 now also works with POJOs.
&lt;p&gt;
POJOs in Action describes these new, simpler, and faster ways to develop enterprise Java applications. It shows you how to go about making key design decisions, including how to organize and encapsulate the domain logic, access the database, manage transactions, and handle database concurrency.
&lt;p&gt;
Written for developers and designers, this is a new-generation Java applications guide. It helps you build lightweight applications that are easier to build, test, and maintain. The book is uniquely practical with design alternatives illustrated through numerous code examples.
&lt;/blockquote&gt;
I&#039;ll publish a full review in a couple of weeks.  If you have any specific questions about the book, please post a comment and I&#039;ll try to answer them in the review.
&lt;/p&gt;
        </description>
      
      
    
    
    
    <comments>http://www.codingthearchitecture.com/2006/02/14/pojos_in_action.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/02/14/pojos_in_action.html</guid>
    <pubDate>Tue, 14 Feb 2006 12:40:03 GMT</pubDate>
  </item>
  
  <item>
    <title>Enterprise Architecture Frameworks</title>
    <link>http://www.codingthearchitecture.com/2006/02/12/enterprise_architecture_frameworks.html</link>
    
      
      
        <description>
          The &lt;a href=&#034;http://www.enterprise-architecture.info/&#034;&gt;Institute for Enterprise Architecture&lt;/a&gt; recently published the results of their web-based survey of Enterprise Architecture trends for 2005. So what&#039;s new, and who cares?&lt;p&gt;&lt;a href=&#034;http://www.codingthearchitecture.com/2006/02/12/enterprise_architecture_frameworks.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <category>What is software architecture?</category>
    
    <comments>http://www.codingthearchitecture.com/2006/02/12/enterprise_architecture_frameworks.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/02/12/enterprise_architecture_frameworks.html</guid>
    <pubDate>Sun, 12 Feb 2006 11:47:31 GMT</pubDate>
  </item>
  
  </channel>
</rss>
