<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:GuidanceDescription 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="-h09djKXIOUJlez8h6UXrWw" name=",_me8WcAANEdyRS9uciXlZ6g" guid="-h09djKXIOUJlez8h6UXrWw" changeDate="2007-05-12T01:50:56.100+0330">
  <mainDescription>&lt;p>&#xD;
    Attached are templates for describing the architecture in a small, co-located project. At a minimum, all projects&#xD;
    should describe the goals and philosophy of the architecture, identify assumptions and dependencies, reference the&#xD;
    architecturally significant requirements, describe the architectural mechanisms, and describe decisions and constraints&#xD;
    with their justifications.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Architects should consider when it's appropriate to add more information to the Architecture Notebook. A small project&#xD;
    shouldn't spend lots of time documenting the architecture, but all critical elements of the system must be communicated&#xD;
    to current and future team members. Consider including useful architectural views, references to architecturally&#xD;
    significant areas of the design, key abstractions, critical system interface descriptions, and a description of the&#xD;
    architectural framework or pattern.&#xD;
&lt;/p></mainDescription>
  <attachments>resources/architecture_notebook_tpl.dot</attachments>
</org.eclipse.epf.uma:GuidanceDescription>
