<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1">
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-jzW4f1Axu2Di_TL2d2yVWQ" name="extensible_general_architecture,_fMjtEMWxEe6PpZUqNEM0jA" guid="-jzW4f1Axu2Di_TL2d2yVWQ">
    <refinedDescription>&lt;p>&#xD;
    It contains a general and abstracted view to solution architecture. As projects are related and we can reuse components&#xD;
    and concepts in each project, we&#xD;
&lt;/p></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-_JSZUQ9K3vrMz6vYjLmOGQ" name="architecture_notebook,_JUXYUMXeEe6PpZUqNEM0jA" guid="-_JSZUQ9K3vrMz6vYjLmOGQ">
    <refinedDescription>&lt;p>&#xD;
    It provides a place for maintaining the list of architectural issues, along with the associated architectural&#xD;
    decisions, designs, patterns, code documented (or pointed to), and so forth -- all at appropriate levels to make it&#xD;
    easy to understand what architectural decisions have been made and remain to be made.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    It is helpful for architects to use this artifact to collaborate with other team members in developing the architecture&#xD;
    and to help team members understand the motivation behind architectural decisions so that those decisions can be&#xD;
    robustly implemented. For example, the architect may put constraints on how data is packaged and communicated between&#xD;
    different parts of the system. This may appear to be a burden, but the justification in the Architecture Notebook can&#xD;
    explain that there is a significant performance bottleneck when communicating with a legacy system. The rest of the&#xD;
    system must adapt to this bottleneck by following a specific data packaging scheme.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    This artifact should also inform the team members how the system is partitioned or organized so that the team can adapt&#xD;
    to the needs of the system. It also gives a first glimpse of the system and its technical motivations to whoever must&#xD;
    maintain and change the architecture later.&#xD;
&lt;/p></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DeliveryProcessDescription xmi:id="-lFQuuu6PzlThxcbqjfpuiQ" name="agile,_JRY7gcTbEe6Mfs1ZUCdjrw" guid="-lFQuuu6PzlThxcbqjfpuiQ"/>
</xmi:XMI>
