<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Coding the Architecture - slides tag</title>
  <link>http://www.codingthearchitecture.com/tags/slides/</link>
  <description>Software architecture for developers</description>
  <language>en</language>
  <copyright>Coding the Architecture</copyright>
  <lastBuildDate>Mon, 21 May 2012 09:41:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Documenting your software architecture - why and how?</title>
    <link>http://www.codingthearchitecture.com/2009/10/19/documenting_your_software_architecture_why_and_how.html</link>
    
      
        <description>
          &lt;p&gt;
&lt;a href=&#034;http://www.codingthearchitecture.com/presentations/sa2009-documenting-your-software-architecture-why-and-how/&#034;&gt;&lt;img src=&#034;http://www.codingthearchitecture.com/images/sa2009-documenting-your-software-architecture-why-and-how.png&#034; alt=&#034;Documenting your software architecture - why and how?&#034; border=&#034;0&#034; align=&#034;right&#034; style=&#034;padding: 0px 0px 8px 8px&#034; /&gt;&lt;/a&gt; Another of the sessions that I delivered at the recent &lt;a href=&#034;http://www.software-architect.co.uk/&#034;&gt;Software Architect 2009 conference&lt;/a&gt; was entitled &#034;Documenting your software architecture - why and how?&#034; and covered some of the drivers for creating software architecture documentation along with some guidelines on how to do this. As I said in the session, any software architecture documentation should be &lt;i&gt;complementary to the code&lt;/i&gt; and &lt;i&gt;describe what the code itself doesn&#039;t&lt;/i&gt;. For example, it&#039;s really hard to identify things like architectural principles, operational aspects and how security works from just the code itself.
&lt;/p&gt;

&lt;p&gt;
As with &lt;a href=&#034;http://www.codingthearchitecture.com/2009/10/15/broadening_the_t.html&#034;&gt;Broadening the T&lt;/a&gt;, I&#039;m going to put one or more essays together that cover the content in more detail. In the meantime, you can &lt;a href=&#034;http://www.codingthearchitecture.com/presentations/sa2009-documenting-your-software-architecture-why-and-how/&#034;&gt;view or download the slides&lt;/a&gt;.
&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>How do you share software architecture?</category>
    
    <comments>http://www.codingthearchitecture.com/2009/10/19/documenting_your_software_architecture_why_and_how.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2009/10/19/documenting_your_software_architecture_why_and_how.html</guid>
    <pubDate>Mon, 19 Oct 2009 12:39:57 GMT</pubDate>
  </item>
  
  <item>
    <title>Broadening the T</title>
    <link>http://www.codingthearchitecture.com/2009/10/15/broadening_the_t.html</link>
    
      
        <description>
          &lt;p&gt;
&lt;a href=&#034;http://www.codingthearchitecture.com/presentations/sa2009-broadening-the-t/&#034;&gt;&lt;img src=&#034;http://www.codingthearchitecture.com/images/sa2009-broadening-the-t.png&#034; alt=&#034;Broadening the T&#034; border=&#034;0&#034; align=&#034;right&#034; style=&#034;padding: 0px 0px 8px 8px&#034; /&gt;&lt;/a&gt; One of the sessions that I delivered at the recent &lt;a href=&#034;http://www.software-architect.co.uk/&#034;&gt;Software Architect 2009 conference&lt;/a&gt; was entitled &#034;Broadening the T&#034; and covered the sort of skills and knowledge that I think are needed by hands-on software architects. This included things like seeing the big picture, dealing with non-functional requirements (we focussed on performance and scalability), using patterns at the architecture level, testing architectures, monitoring and diagnosing performance problems. Some concrete advice was given throughout the presentation with Java and .NET being used to give some real-world context.
&lt;/p&gt;

&lt;p&gt;
I have a load of notes on the Keynote version of the slides and I&#039;m going to put one or more essays together that cover the content in more detail. In the meantime, you can &lt;a href=&#034;http://www.codingthearchitecture.com/presentations/sa2009-broadening-the-t/&#034;&gt;view or download the slides&lt;/a&gt;.
&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>What is the the role of a software architect?</category>
    
    <comments>http://www.codingthearchitecture.com/2009/10/15/broadening_the_t.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2009/10/15/broadening_the_t.html</guid>
    <pubDate>Thu, 15 Oct 2009 08:46:00 GMT</pubDate>
  </item>
  
  <item>
    <title>A developer&#039;s guide to load testing - slides</title>
    <link>http://www.codingthearchitecture.com/2009/06/11/a_developers_guide_to_load_testing_slides.html</link>
    
      
        <description>
          &lt;p&gt;
Thanks to everybody that came along to the &lt;a href=&#034;http://www.codingthearchitecture.com/2009/06/02/a_developers_guide_to_load_testing.html&#034;&gt;CTA user group earlier in the week&lt;/a&gt;. The tube strike may had reduced the numbers but we still had some great discussion about load testing. My slides are available to &lt;a href=&#034;http://static.codingthearchitecture.com/presentations/20090609-load-testing.pdf&#034;&gt;download&lt;/a&gt; (~4MB) and if anybody wants to continue the discussion, please feel free to use the &lt;a href=&#034;http://groups.google.com/group/codingthearchitecture&#034;&gt;Google Group&lt;/a&gt;.
&lt;/p&gt;

&lt;div align=&#034;center&#034;&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/20090609-load-testing.pdf&#034;&gt;&lt;img src=&#034;http://www.codingthearchitecture.com/images/20090609-load-testing-thumbnail.png&#034; alt=&#034;A developer&#039;s guide to load testing&#034; border=&#034;0&#034; /&gt;&lt;/a&gt;
&lt;br /&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/20090609-load-testing.pdf&#034;&gt;A developer&#039;s guide to load testing&lt;/a&gt; (PDF, ~4MB) 
&lt;/div&gt;

&lt;p&gt;
I&#039;ll post an update when the Skills Matter podcast/video is available to view online.
&lt;/p&gt;

        </description>
      
      
    
    
    
    <category>How do you deliver software architecture?</category>
    
    <comments>http://www.codingthearchitecture.com/2009/06/11/a_developers_guide_to_load_testing_slides.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2009/06/11/a_developers_guide_to_load_testing_slides.html</guid>
    <pubDate>Thu, 11 Jun 2009 18:40:49 GMT</pubDate>
  </item>
  
  <item>
    <title>Java for .NET developers</title>
    <link>http://www.codingthearchitecture.com/2009/03/30/java_for_net_developers.html</link>
    
      
        <description>
          &lt;p&gt;
Once again, thanks to everybody that came along to my Java for .NET developers talk at DevWeek 2009 last week. As I said during the session, I wanted to provide a good general overview along with some content that went beyond the basics, which is why I decided to include some slides after the DevWeek books were printed. For those of you not there; the session went through an overview of Java, getting Java, building a hello world application, IDEs and tooling, an Eclipse demo, an overview of Java webapps, some beyond the basics material (JVM flags, garbage collection tuning, monitoring/management with JConsole, ClassLoaders/isolation) and some recommended paths to get started. As I promised, here&#039;s the link to download the slides...
&lt;/p&gt;

&lt;div align=&#034;center&#034;&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/dw2009-java-for-dotnet-developers.pdf&#034;&gt;&lt;img src=&#034;http://www.codingthearchitecture.com/images/dw2009-jfdnd-thumbnails.png&#034; alt=&#034;Java for .NET developers&#034; border=&#034;0&#034; /&gt;&lt;/a&gt;
&lt;br/&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/dw2009-java-for-dotnet-developers.pdf&#034;&gt;An introduction to the Java platform for .NET developers&lt;/a&gt; (PDF, ~7.4MB)
&lt;br /&gt;&lt;br /&gt;
&lt;/div&gt;
        </description>
      
      
    
    
    
    <comments>http://www.codingthearchitecture.com/2009/03/30/java_for_net_developers.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2009/03/30/java_for_net_developers.html</guid>
    <pubDate>Mon, 30 Mar 2009 11:54:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Pitfalls for software architects</title>
    <link>http://www.codingthearchitecture.com/2009/03/30/pitfalls_for_software_architects.html</link>
    
      
        <description>
          &lt;p&gt;
Thanks to everybody that came along to my &#034;Pitfalls for new software architects&#034; talk at DevWeek 2009 last week ... I hope you found it a useful look at some of the traps that I&#039;ve seen people (including myself!) fall into over the years. The pitfalls are structured into a number of different areas as shown in the diagram below.
&lt;/p&gt;

&lt;div align=&#034;center&#034;&gt;
&lt;img src=&#034;http://www.codingthearchitecture.com/images/book/role-1.png&#034; alt=&#034;Role of a hands-on software architect&#034; /&gt;
&lt;/div&gt;

&lt;p&gt;
Each of these areas is part of our view of &lt;a href=&#034;http://www.codingthearchitecture.com/pages/book/role.html&#034;&gt;what a hands-on software architect should do&lt;/a&gt;, and the talk itself compliments a session I delivered at Software Architect 2008 called &#034;Why software projects fail&#034;. You can download the slides for both sessions below.
&lt;/p&gt;

&lt;div align=&#034;center&#034;&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/dw2009-pitfalls-for-new-software-architects.pdf&#034;&gt;&lt;img src=&#034;http://www.codingthearchitecture.com/images/dw2009-pfnsa-thumbnails.png&#034; alt=&#034;Pitfalls for new software architects&#034; border=&#034;0&#034; /&gt;&lt;/a&gt;
&lt;br/&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/dw2009-pitfalls-for-new-software-architects.pdf&#034;&gt;Pitfalls for new software architects&lt;/a&gt; (PDF, ~4MB)
&lt;br /&gt;&lt;br /&gt;
&lt;/div&gt;

&lt;div align=&#034;center&#034;&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/sa2008-why-software-projects-fail.pdf&#034;&gt;&lt;img src=&#034;http://www.codingthearchitecture.com/images/sa2008-wspf-thumbnails.png&#034; alt=&#034;Why software projects fail&#034; border=&#034;0&#034; /&gt;&lt;/a&gt;
&lt;br/&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/sa2008-why-software-projects-fail.pdf&#034;&gt;Why software projects fail&lt;/a&gt; (PDF, ~6MB)
&lt;/div&gt;
        </description>
      
      
    
    
    
    <comments>http://www.codingthearchitecture.com/2009/03/30/pitfalls_for_software_architects.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2009/03/30/pitfalls_for_software_architects.html</guid>
    <pubDate>Mon, 30 Mar 2009 08:50:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>

