<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://www.visualspec.org/technical-design/RSS">
  <title>Technical Design</title>
  <link>http://www.visualspec.org</link>
  
  <description>
    
       
       
  </description>
  
  
  
            <syn:updatePeriod>daily</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2009-08-10T11:23:04Z</syn:updateBase>
        
  
  <image rdf:resource="http://www.visualspec.org/logo.jpg"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="http://www.visualspec.org/technical-design/technical-design"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://www.visualspec.org/technical-design/technical-design">        <title>Technical Design</title>        <link>http://www.visualspec.org/technical-design/technical-design</link>        <description>The primary objective for technical analysis is to produce a technical design that can be used for the implementation of a system. The technical design should clearly outline to the implementers the exact tasks that need to be undertaken to produce a working system. The technical analysis should make implementation choices, and make assumptions about vendors and infrastructure. Even at this stage, a technical design can be vendor and deployment independent. If required, it is possible to make a layered technical design, that separates an implementation model from a vendor realization.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>danielcodrea</dc:creator>        <dc:rights></dc:rights>                <dc:date>2009-08-11T08:07:41Z</dc:date>        <dc:type>Page</dc:type>    </item>




</rdf:RDF>
