<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ArtifactDescription 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" xmi:id="-xqfa60aDWZ5ACwrR-HYwIQ" name="new_artifact,_SN-vQMXcEe6PpZUqNEM0jA" guid="-xqfa60aDWZ5ACwrR-HYwIQ">
  <mainDescription>&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></mainDescription>
  <purpose>To capture and make architectural decisions and to explain those decisions to developers.&amp;nbsp;</purpose>
  <impactOfNotHaving>Without this artifact, there will be no coordination of the individual design efforts, and it will be difficult to&#xD;
establish and communicate an overall architectural vision of the project.</impactOfNotHaving>
  <reasonsForNotNeeding>&lt;p>&#xD;
    This artifact is not required if an existing reference architecture is being used or another approach or set of&#xD;
    artifacts are being used to document the architecture. This artifact may not be needed if the design is relatively&#xD;
    straight-forward and does not have any architecturally significant risks.&#xD;
&lt;/p></reasonsForNotNeeding>
</org.eclipse.epf.uma:ArtifactDescription>
