<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://www.spamer.me.uk/wiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://www.spamer.me.uk/wiki/feed.php">
        <title>Software Architecture</title>
        <description></description>
        <link>http://www.spamer.me.uk/wiki/</link>
        <image rdf:resource="http://www.spamer.me.uk/wiki/lib/images/favicon.ico" />
       <dc:date>2010-09-08T19:35:13+01:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/batch_process_architecture_patterns?rev=1253813754&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/client-server_architecture_patterns?rev=1253822661&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/continuous_integration?rev=1256514256&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/development_risk?rev=1256509092&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/document_template?rev=1253621500&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/engineering_principle?rev=1256512376&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/heroic_development?rev=1253626850&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/improvise_adapt_overcome?rev=1253622108&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/information_technology_systems_governance?rev=1253642050&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/ip_multicast?rev=1253796935&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/ip_tcp?rev=1253798339&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/ip_udp?rev=1253798207&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/ip_unicast?rev=1253797248&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/iterative_development_methodology?rev=1253622054&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/misc_ballon?rev=1253628098&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/misc_butterfly?rev=1254086925&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/misc_dear_mr_architect?rev=1253628178&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/misc_what_is_success?rev=1253628768&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/n-tier_architecture_patterns?rev=1253823181&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/only_constant_is_change?rev=1256509792&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_delegate_responsibility?rev=1253626920&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_java_checked_vs_unchecked?rev=1253626990&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_java_class_factory?rev=1253813626&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_java_encapsulate_state_with_memento?rev=1253647467&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_java_singleton_example?rev=1253627216&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_java_uml_association?rev=1253627816&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_java_unreachable_host?rev=1253813461&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_java_xslt_tranform?rev=1253637541&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_jdbc_connection_pools_unsafe?rev=1253814746&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_liskov_substitution_principle?rev=1253626740&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_open_closed_principle?rev=1253623652&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_single_responsibility_principle?rev=1253623593&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/oo_strawman_myths?rev=1256515054&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/peer-to-peer_architecture_patterns?rev=1253813855&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/position_paper?rev=1253621420&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/risk_factors?rev=1256509186&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/scientific_method?rev=1256511590&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/service_oriented_architecture_overview?rev=1256508659&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/service_oriented_architecture_patterns?rev=1253813884&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/sidebar?rev=1197983326&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/soa_fan_in?rev=1256511447&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/soa_fan_out?rev=1256511312&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/soa_pipe_line?rev=1256511289&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/software_architecture?rev=1198842780&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/software_engineering?rev=1197643638&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/standards_migration?rev=1253637363&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/start?rev=1256509112&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_business_continuity_planning_disaster_recovery?rev=1253641812&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_incident_analysis?rev=1253641192&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_information_security_classification?rev=1253641967&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_information_technology_security?rev=1253641352&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_personnel_security?rev=1253641774&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_physical_security?rev=1253641719&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_risk_awareness?rev=1253641427&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_security_organization?rev=1253641181&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_security_policy?rev=1253641469&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/systems_governance_threat_risk_assessment?rev=1253641222&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/uml_profile_for_a_service_oriented_architecture?rev=1254858445&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/wiki_doku.php?rev=1270126741&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.spamer.me.uk/wiki/doku.php/xml_document_design?rev=1253649148&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://www.spamer.me.uk/wiki/lib/images/favicon.ico">
        <title>Software Architecture</title>
        <link>http://www.spamer.me.uk/wiki/</link>
        <url>http://www.spamer.me.uk/wiki/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/batch_process_architecture_patterns?rev=1253813754&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T18:35:54+01:00</dc:date>
        <title>batch_process_architecture_patterns</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/batch_process_architecture_patterns?rev=1253813754&amp;do=diff</link>
        <description>Batch Process Architecture Patterns</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/client-server_architecture_patterns?rev=1253822661&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T21:04:21+01:00</dc:date>
        <title>client-server_architecture_patterns</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/client-server_architecture_patterns?rev=1253822661&amp;do=diff</link>
        <description>Client Server Architecture Patterns

Array</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/continuous_integration?rev=1256514256&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T23:44:16+01:00</dc:date>
        <title>continuous_integration</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/continuous_integration?rev=1256514256&amp;do=diff</link>
        <description>*  Source Control
	*  Continuous Commitment
	*  Automated Build
	*  Automated Unit Testing
	*  Automated Deployment to test environment
	*  Test Environment is clone of live environment.
	*  Production Like Test  

	*  Dashboard - Automated Status reporting to all interested / Relevant parties</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/development_risk?rev=1256509092&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:18:12+01:00</dc:date>
        <title>development_risk</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/development_risk?rev=1256509092&amp;do=diff</link>
        <description>Risk Types

Requirements Risk

	*  Do we fully understand the requirements ?
	*  Are the requirements fully documented ?

Skills Risk

	*  Do we have the skills in house?
	*  Can we train the skills
	*  Can we recruit the skills ?
	*  Are the skills common and mundane or rare and unusual ?</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/document_template?rev=1253621500&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T13:11:40+01:00</dc:date>
        <title>document_template</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/document_template?rev=1253621500&amp;do=diff</link>
        <description>Document Subject Matter

Introduction

Purpose

Describe the purpose of the document.


Scope

Describe the scope of the document within the subject.


Audience

Describe document intended audience


Background

Identify the system/product using any applicable names and/or version numbers.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/engineering_principle?rev=1256512376&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T23:12:56+01:00</dc:date>
        <title>engineering_principle</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/engineering_principle?rev=1256512376&amp;do=diff</link>
        <description>Engineering is the application of the scientific method to the solving real world problems.

- understand the fundamental principles underlying problem domain design.
- plan and write the solution within the specified requirements and to a professional standard.
- employ formal methods to produce effective solution to specific requirements.
- develop structured solution sets of simple user-defined classes usinb Object-Oriented principles to achieve overall programming goals.
- develop reasoned j…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/heroic_development?rev=1253626850&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T14:40:50+01:00</dc:date>
        <title>heroic_development</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/heroic_development?rev=1253626850&amp;do=diff</link>
        <description>It's common to hear some development teams bragging about their heroic efforts saying things like.


	*  I was up until 3a fixing some bug.
	*  Unless you're doing a 60 hour week, you're not pulling your weight.
	*  


Try googling for Heroic Programming and you will get thousands of hits, many of them littered with similar phrases.  Why ?  A development team that requires Heroic programming is broken as badly broken as the as their software.  Software that requires an Heroic effort to fix is ei…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/improvise_adapt_overcome?rev=1253622108&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T13:21:48+01:00</dc:date>
        <title>improvise_adapt_overcome</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/improvise_adapt_overcome?rev=1253622108&amp;do=diff</link>
        <description>Improvise


 To compose and perform or deliver without previous preparation.
 To make, provide, or arrange from whatever materials are readily available.

Adapt


 To make suitable to requirements or conditions; adjust or modify fittingly.
 To adjust oneself to different conditions, environment, etc.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/information_technology_systems_governance?rev=1253642050&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:54:10+01:00</dc:date>
        <title>information_technology_systems_governance</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/information_technology_systems_governance?rev=1253642050&amp;do=diff</link>
        <description>Governance of information technology system is about the development of processes, procedures and practice that ensure that the development and managament of system complies with an organisations policy.

The question of how you might achieve an effective governance for live systems requires a comprehensive information system technology strategy with a firm commitment and backing of the most senior executive.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/ip_multicast?rev=1253796935&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T13:55:35+01:00</dc:date>
        <title>ip_multicast</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/ip_multicast?rev=1253796935&amp;do=diff</link>
        <description>In most situations Internet applications utilise unicast packets for transporting information directly from one point to point.  Unicast is used for browsing the web with HTTP, fetching files with FTP or  email delivery SMTP.  

The internet protocol stack provides another method of distributing data to multiple destinations, multicast.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/ip_tcp?rev=1253798339&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T14:18:59+01:00</dc:date>
        <title>ip_tcp</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/ip_tcp?rev=1253798339&amp;do=diff</link>
        <description>Transmission Control Protocol / Internet Protocol


	*  TCP is a connection oriented protocol.  The meaning for connection establishment is that client and server make sure there identity to each other through a well define 3 way handshake.
	*  During handshake they ensure there data handling capacity by sending there Maximum Transmission Unit (MTU) size to each other.
	*  Both client and server send there packet sequence number to each other.
	*  TCP ensure the reliable data transfer through ac…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/ip_udp?rev=1253798207&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T14:16:47+01:00</dc:date>
        <title>ip_udp</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/ip_udp?rev=1253798207&amp;do=diff</link>
        <description>User Datagram Protocol over Internet Protocol.

UDP is a “connectionless” protocol
UDP has no explicit provision for acknowledgement of packets received.

(Sometimes mistakenly called unreliable datagram protocol).


	*  UDP is connection less data transfer, it means there will not be any handshake between peers. Server will listen at some port and accept the packet to the port from any client.
	*  Unreliable data transfer, there is no acknowledge for data.
	*  UDP packet may take any path to re…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/ip_unicast?rev=1253797248&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T14:00:48+01:00</dc:date>
        <title>ip_unicast</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/ip_unicast?rev=1253797248&amp;do=diff</link>
        <description>Point to Point transmission of data over the internet is IP Unicast.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/iterative_development_methodology?rev=1253622054&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T13:20:54+01:00</dc:date>
        <title>iterative_development_methodology</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/iterative_development_methodology?rev=1253622054&amp;do=diff</link>
        <description>Synopsis


A software development process that is flexible, responsive to changing requirements and risk managed.

Background


The demands on software developers in the 21st Century make it necessary to be both responsive to change while minimising the risks inherent in change.  They must endeavouring to maintain a consistent approach whilst keeping up with current best practice.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/misc_ballon?rev=1253628098&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T15:01:38+01:00</dc:date>
        <title>misc_ballon</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/misc_ballon?rev=1253628098&amp;do=diff</link>
        <description>A man in a hot air balloon, realising he was lost, reduced altitude and spotted a woman below. He descended further and shouted to the lady 

“Excuse me, can you help me? I promised a friend I would meet him an hour ago, but I don't know where I am.”</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/misc_butterfly?rev=1254086925&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-27T22:28:45+01:00</dc:date>
        <title>misc_butterfly</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/misc_butterfly?rev=1254086925&amp;do=diff</link>
        <description>An insight into Mentoring &amp; coaching

One day a man finds a cocoon for a butterfly with a small opening, he sits and watches the butterfly for several hours as it struggled to force its body through the little hole. Then it seemed to stop making any progress. It appeared stuck.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/misc_dear_mr_architect?rev=1253628178&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T15:02:58+01:00</dc:date>
        <title>misc_dear_mr_architect</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/misc_dear_mr_architect?rev=1253628178&amp;do=diff</link>
        <description>Please design and build me a house. I am not quite sure of what I need, so you should use your discretion.

My house should have between two and forty-five bedrooms. Just make sure the plans are such that the bedrooms can be easily added or deleted. When you bring the blueprints to me, I will make the final decision of what I want. Also, bring me the cost breakdowns for each configuration so that I can arbitrarily pick one at a later time.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/misc_what_is_success?rev=1253628768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T15:12:48+01:00</dc:date>
        <title>misc_what_is_success</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/misc_what_is_success?rev=1253628768&amp;do=diff</link>
        <description>The distinction between a successful project and a failure is often just a matter of perception.

Why do so many projects fail ?

Perception

Perception is 90% law, if something is framed as a success it will be considered a success.  If something is framed as a failure it will be perceived as a failure.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/n-tier_architecture_patterns?rev=1253823181&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T21:13:01+01:00</dc:date>
        <title>n-tier_architecture_patterns</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/n-tier_architecture_patterns?rev=1253823181&amp;do=diff</link>
        <description>N-Tier Architecture Patterns

Array

Array</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/only_constant_is_change?rev=1256509792&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:29:52+01:00</dc:date>
        <title>only_constant_is_change</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/only_constant_is_change?rev=1256509792&amp;do=diff</link>
        <description>During the life cycle of your project you can be sure that :-


	*  Your requirements will change.
	*  Your environment will change.
	*  Your users will change.
	*  Your platform will change.
	*  Your team will change.
	*  Your software will change.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_delegate_responsibility?rev=1253626920&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T14:42:00+01:00</dc:date>
        <title>oo_delegate_responsibility</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_delegate_responsibility?rev=1253626920&amp;do=diff</link>
        <description>The  getter is an Anti-Pattern when it reveals the internals of a class to the caller.  It is often indicative of an  Anemic Domain Model.  An Anemic Domain Models are thin on behaviour and is little more than a data model.  Avoid this anti-pattern by maintaining the principle of Encapsulation.  Use the principle of a single responsibility (the composite class should not need knowledge of its component class) to refactor the class and use delegation (the composite class tells the component class…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_java_checked_vs_unchecked?rev=1253626990&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T14:43:10+01:00</dc:date>
        <title>oo_java_checked_vs_unchecked</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_java_checked_vs_unchecked?rev=1253626990&amp;do=diff</link>
        <description>RuntimeExceptions are inherently unsafe because Java does not require a catch or throws statement for them, they are unchecked.  Unchecked RuntimeExceptions sidestep the java language features for Exception handling and are reserved for critical failures in the JVM or underlying platform which the application cannot reasonably be expected to handle. The compiler does not force a programmer using a class that throws Unchecked exception to handle them.  Unchecked exceptions can propergate up the c…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_java_class_factory?rev=1253813626&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T18:33:46+01:00</dc:date>
        <title>oo_java_class_factory</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_java_class_factory?rev=1253813626&amp;do=diff</link>
        <description>String Parameterised Class Factory.


    Class.forName( className ).newInstance();</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_java_encapsulate_state_with_memento?rev=1253647467&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T20:24:27+01:00</dc:date>
        <title>oo_java_encapsulate_state_with_memento</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_java_encapsulate_state_with_memento?rev=1253647467&amp;do=diff</link>
        <description>The purpose of the memento pattern is to encapsulate state.


class Memento {
   private State state;

   public Memento(State stateToSave) { state = stateToSave; }
   public State getSavedState() { return state; }
}


When I use the Command Pattern, I combine it with the memento pattern.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_java_singleton_example?rev=1253627216&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T14:46:56+01:00</dc:date>
        <title>oo_java_singleton_example</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_java_singleton_example?rev=1253627216&amp;do=diff</link>
        <description>A Netbeans template for a thread safe singleton in java.


/*
 * __NAME__.java
 *
 * @author __USER__
 *
 * Created on __DATE__, __TIME__
 */

package Templates.Classes;

/** __NAME__
 * uses the singleton pattern to prevent multiple instances.
 * NOTE: provides only a single instance per classloader.
 * see Singleton Pattern [GOF:127]
 * @author __USER__
 */
public class __NAME__
  {
  /** a private static reference to this object.
  */
  private static __NAME__ instance ;

  /** construct a si…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_java_uml_association?rev=1253627816&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T14:56:56+01:00</dc:date>
        <title>oo_java_uml_association</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_java_uml_association?rev=1253627816&amp;do=diff</link>
        <description>When one class knows about the existence of another class and may address its interface directly those classes can be said to have an association.  It means their is a communication path between these two classes.  In a pure OO sense they can send messages to each other.  In a practical sense one class can call the public methods of the other class.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_java_unreachable_host?rev=1253813461&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T18:31:01+01:00</dc:date>
        <title>oo_java_unreachable_host</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_java_unreachable_host?rev=1253813461&amp;do=diff</link>
        <description>Loading a resource (property file, xml, xslt, image etc) from deployment jar file.


    this.getClass().getClassLoader().getResourceAsStream( ... ) ;</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_java_xslt_tranform?rev=1253637541&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T17:39:01+01:00</dc:date>
        <title>oo_java_xslt_tranform</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_java_xslt_tranform?rev=1253637541&amp;do=diff</link>
        <description>import javax.xml.transform.Source;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
import java.io.*;

public class Transform {
    	/** Perform an XSLT transformation,
	*	sending the results 
	*	to System.out.
	 */

    public static void main(String[] args) throws Exception {
        if (args.length != 2) {
            System.err.println(
                &quot;Usage:…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_jdbc_connection_pools_unsafe?rev=1253814746&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T18:52:26+01:00</dc:date>
        <title>oo_jdbc_connection_pools_unsafe</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_jdbc_connection_pools_unsafe?rev=1253814746&amp;do=diff</link>
        <description>The conventional setup for a JDBC connection to database is through the use of connection pooling within the Application Server / Web Container or through an Application configuration files.  These approach require the proliferation of access credentials information  (username and password) to be widely distributed than acceptable by a Security Governance Policy. A configuration file or in any other standard readable location.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_liskov_substitution_principle?rev=1253626740&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T14:39:00+01:00</dc:date>
        <title>oo_liskov_substitution_principle</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_liskov_substitution_principle?rev=1253626740&amp;do=diff</link>
        <description>An operation on a base class must operate on a derrived class without explict knowledge of the type.


package lsp;

/**
 * use polymorphism and delegation to obey LSP
 */
public class Lsp {
	public static void main(String[] args) {
		new Lsp() ;
		}
	public Lsp() {
		Cat pet1 = new Cat() ;
		Dog pet2 = new Dog() ;
		Pet pets[] = { pet1, pet2 } ; 

		// avoid using instanceof or getClass().getName()
		for( int i=0 ; i&lt;pets.length ; i++ ) {
			if (pets[i] instanceof Cat) {
				System.out.println(…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_open_closed_principle?rev=1253623652&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T13:47:32+01:00</dc:date>
        <title>oo_open_closed_principle</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_open_closed_principle?rev=1253623652&amp;do=diff</link>
        <description>Classes should be open to extension but closed to modification.
 * Open to extension allows a derrived class to provided additional behaviour over that of the base class.
 * Closed to modification precludes functionality can be added to a derrived class from modifying the base class.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_single_responsibility_principle?rev=1253623593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T13:46:33+01:00</dc:date>
        <title>oo_single_responsibility_principle</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_single_responsibility_principle?rev=1253623593&amp;do=diff</link>
        <description>All Classes should have a single responsibility (one thing to do) and each responsibility should be entirely encapsulated by a single class.

This principle applies the traditional best practice of keeping Coupling Low and Cohesion High to OO development.  High Cohesion; putting together things that logically belong together, means that a change of requirements will typically impact few classes.  Low Coupling between Classes means that changes to one class will have minimal impact on another cla…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/oo_strawman_myths?rev=1256515054&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T23:57:34+01:00</dc:date>
        <title>oo_strawman_myths</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/oo_strawman_myths?rev=1256515054&amp;do=diff</link>
        <description>There is an anti-OO troll who's rant about OO seem to be gaining some traction.  His arguments are mostly strawmen  (despite his claims otherwise) by somebody who clearly has little grasp what OO is about. I guess he is frightened and fearful for his prospects because he is unable to make the paradigm shift. The clearest evidence of this are the Myths; an OO authority would never proclaim many of these, some just don't make sense, some are 'clearly' miss-quotes or misrepresentations of what OO a…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/peer-to-peer_architecture_patterns?rev=1253813855&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T18:37:35+01:00</dc:date>
        <title>peer-to-peer_architecture_patterns</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/peer-to-peer_architecture_patterns?rev=1253813855&amp;do=diff</link>
        <description>Peer to Peer Architecture Patterns</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/position_paper?rev=1253621420&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T13:10:20+01:00</dc:date>
        <title>position_paper</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/position_paper?rev=1253621420&amp;do=diff</link>
        <description>*  Introduction : Relevant to audience; set up the context and importance of the issue. 
	*  The Problem : Clearly specific issue or question. 
	*  The Position : Take a position with respect to the issue or problem raised. 
	*  Justification : Justify the position. 
	*  Past Positions : Compare the position taken with past positions related to the issue. 
	*  Future Positions : Consider future positions related to the issue. 
	*  Conclusion : identifying specific goals from this issue or positi…</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/risk_factors?rev=1256509186&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:19:46+01:00</dc:date>
        <title>risk_factors</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/risk_factors?rev=1256509186&amp;do=diff</link>
        <description>&quot;Eating the Elephant in one sitting&quot;

Attempting to deliver a new software system in a single phase is a dangerous practice; big projects = big bang = big risks.  Professionals Software Engineers needs to constantly manage mitigate risk; which avoiding analysis paralysis and feature creep.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/scientific_method?rev=1256511590&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:59:50+01:00</dc:date>
        <title>scientific_method</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/scientific_method?rev=1256511590&amp;do=diff</link>
        <description>Applying the scientific method to software development


	*  create a model describing your subject domain,
	*  develop a hypotheses (Solution) using the model,
	*  run experiments (tests) to validate hypotheses,
	*  refine model and repeat</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/service_oriented_architecture_overview?rev=1256508659&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:10:59+01:00</dc:date>
        <title>service_oriented_architecture_overview</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/service_oriented_architecture_overview?rev=1256508659&amp;do=diff</link>
        <description>A service oriented architecture is an approach to the construction of a software system through the integration of loosely coupled software components called services.  A Service is a discrete Software Component capable of providing specific discrete business functionality.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/service_oriented_architecture_patterns?rev=1253813884&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T18:38:04+01:00</dc:date>
        <title>service_oriented_architecture_patterns</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/service_oriented_architecture_patterns?rev=1253813884&amp;do=diff</link>
        <description>Service Oriented Architecture Patterns</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/sidebar?rev=1197983326&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-18T13:08:46+01:00</dc:date>
        <title>sidebar</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/sidebar?rev=1197983326&amp;do=diff</link>
        <description>*   Home
	*  Software Architecture.
	*  Software Engineering.
	*   Object Oriented.
	*  Java Development.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/soa_fan_in?rev=1256511447&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:57:27+01:00</dc:date>
        <title>soa_fan_in</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/soa_fan_in?rev=1256511447&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/soa_fan_out?rev=1256511312&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:55:12+01:00</dc:date>
        <title>soa_fan_out</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/soa_fan_out?rev=1256511312&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/soa_pipe_line?rev=1256511289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:54:49+01:00</dc:date>
        <title>soa_pipe_line</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/soa_pipe_line?rev=1256511289&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/software_architecture?rev=1198842780&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-28T11:53:00+01:00</dc:date>
        <title>software_architecture</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/software_architecture?rev=1198842780&amp;do=diff</link>
        <description>*   Batch Process 
	*   Client Server 
	*   N-Tier 
	*   Peer to Peer 
	*   Service Oriented</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/software_engineering?rev=1197643638&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-14T14:47:18+01:00</dc:date>
        <title>software_engineering</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/software_engineering?rev=1197643638&amp;do=diff</link>
        <description>Software Engineering is the application of ScientificMethods and EngineeringPrinciples to the development of software.

Development Methodology

	*   The only constant is change..
	*   Iterative Development Methodology.
	*   Risk Factors.
	*   Development Risk.
	*  Improvise, Adapt, Overcome.
	*   Heroics are for firefighters not Software Engineers.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/standards_migration?rev=1253637363&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T17:36:03+01:00</dc:date>
        <title>standards_migration</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/standards_migration?rev=1253637363&amp;do=diff</link>
        <description>Software &amp; standards evolution require a need to establish a Policy &amp; Procedures for handling changes to standards.

Policy Aim
The aim of this Policy is to provide a consistent and predictable technology platform for ongoing architectural development by ensuring effective management &amp; governance of versions of standards.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/start?rev=1256509112&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-25T22:18:32+01:00</dc:date>
        <title>start</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/start?rev=1256509112&amp;do=diff</link>
        <description>*  information technology systems governance

	*   Batch Process Architecture Patterns
	*   Client Server Architecture Patterns
	*   N-Tier Architecture Patterns
	*   Peer to Peer Architecture Patterns
	*   Service Oriented Architecture Patterns

Service Oriented Architecture (SOA)

	*  UML Profile for a Service Oriented Architecture
	*  Service Oriented Architecture Overview</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_business_continuity_planning_disaster_recovery?rev=1253641812&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:50:12+01:00</dc:date>
        <title>systems_governance_business_continuity_planning_disaster_recovery</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_business_continuity_planning_disaster_recovery?rev=1253641812&amp;do=diff</link>
        <description>Development of Plans for mission critical systems first, working through less critical systems and new systems during development.

Benefits: Disaster Recovery plans permit rapid and effective response to mitigate business exposures and impacts</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_incident_analysis?rev=1253641192&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:39:52+01:00</dc:date>
        <title>systems_governance_incident_analysis</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_incident_analysis?rev=1253641192&amp;do=diff</link>
        <description>Procedures for consistent reporting of security incidents to ensure appropriate corrective action.  Requirement for periodic, not less than Annual Report on Information Technology Systems security.

Benefits: An ongoing Annual Report will highlight areas where effective mitigation action can be planned</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_information_security_classification?rev=1253641967&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:52:47+01:00</dc:date>
        <title>systems_governance_information_security_classification</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_information_security_classification?rev=1253641967&amp;do=diff</link>
        <description>Information Security Classification defines the sensitivity of information, assigns a level of protection and authority commensurate with the sensitivity.

Benefits: A comprehensive Information Security Classification program will prevent inadvertent disclosure of sensitive and/or classified information.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_information_technology_security?rev=1253641352&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:42:32+01:00</dc:date>
        <title>systems_governance_information_technology_security</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_information_technology_security?rev=1253641352&amp;do=diff</link>
        <description>Public Key Infrastructure (PKI): Public Key Infrastructure for electronic authentication and authorisation service 

Benefits: PKI is used to prevent unauthorised access to applications, systems and assets.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_personnel_security?rev=1253641774&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:49:34+01:00</dc:date>
        <title>systems_governance_personnel_security</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_personnel_security?rev=1253641774&amp;do=diff</link>
        <description>Working with Human Resources Division in the areas of security screening and emergency management

Benefits: Prevent security incidents from occurring through malpractice and negligence.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_physical_security?rev=1253641719&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:48:39+01:00</dc:date>
        <title>systems_governance_physical_security</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_physical_security?rev=1253641719&amp;do=diff</link>
        <description>Working with Human Resources Division in the areas of security screening and emergency management

Benefits: Prevent security incidents from occurring through malpractice and negligence.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_risk_awareness?rev=1253641427&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:43:47+01:00</dc:date>
        <title>systems_governance_risk_awareness</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_risk_awareness?rev=1253641427&amp;do=diff</link>
        <description>Develop security awareness through training.

Benefits: Employees possess the knowledge to operate in a secure manner can prevent security incidents from occurring.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_security_organization?rev=1253641181&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:39:41+01:00</dc:date>
        <title>systems_governance_security_organization</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_security_organization?rev=1253641181&amp;do=diff</link>
        <description>Corporate/Programme/Project security boards and teams.

Benefits: A strong security organisation at all corporate levels is necessary to implement all of the elements of prevention, detection, response, and mitigation.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_security_policy?rev=1253641469&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:44:29+01:00</dc:date>
        <title>systems_governance_security_policy</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_security_policy?rev=1253641469&amp;do=diff</link>
        <description>Development of programme wide IS &amp; IT security policy, including operationing procedures, standards and best practices.

Benefits: Clear consistent security policies and procedures aid to prevent security incidents from occurring.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/systems_governance_threat_risk_assessment?rev=1253641222&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T18:40:22+01:00</dc:date>
        <title>systems_governance_threat_risk_assessment</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/systems_governance_threat_risk_assessment?rev=1253641222&amp;do=diff</link>
        <description>Assessments should be mandated for all systems, address critical systems first, working through less critical systems, assess new systems during development.

Benefits: Threat Risk Assessments detect security gaps, providing the opportunity to respond via mitigation strategies that prevent future incidents.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/uml_profile_for_a_service_oriented_architecture?rev=1254858445&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-06T20:47:25+01:00</dc:date>
        <title>uml_profile_for_a_service_oriented_architecture</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/uml_profile_for_a_service_oriented_architecture?rev=1254858445&amp;do=diff</link>
        <description>UML Profile for a Service Oriented Architecture for use with Sparx Enterprise Architect, download 
 SOA-Profile.xml and Save-As. In Enterprise Architect select Resources -&gt; UML Profile -&gt; Import Profile. Once loaded into EA you can apply stereotypes from the profile to your design.</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/wiki_doku.php?rev=1270126741&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-01T13:59:01+01:00</dc:date>
        <title>wiki_doku.php</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/wiki_doku.php?rev=1270126741&amp;do=diff</link>
        <description>*  information technology systems governance

	*   Batch Process Architecture Patterns
	*   Client Server Architecture Patterns
	*   N-Tier Architecture Patterns
	*   Peer to Peer Architecture Patterns
	*   Service Oriented Architecture Patterns

Service Oriented Architecture (SOA)

	*  UML Profile for a Service Oriented Architecture
	*  Service Oriented Architecture Overview</description>
    </item>
    <item rdf:about="http://www.spamer.me.uk/wiki/doku.php/xml_document_design?rev=1253649148&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-22T20:52:28+01:00</dc:date>
        <title>xml_document_design</title>
        <link>http://www.spamer.me.uk/wiki/doku.php/xml_document_design?rev=1253649148&amp;do=diff</link>
        <description>When designing XML Document we are faced with the question of which parts of the data should be held in an attribute and which parts in an element.  

Canonical data should be held within elements.
IF the data is Metadata about the canonical should be held within attributes.</description>
    </item>
</rdf:RDF>
