blob: b5a4291780098e2e4920c7428859c91d8ec363d0 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:GuidanceDescription xmi:version="2.0"
xmlns:xmi="" xmlns:org.eclipse.epf.uma=""
xmlns:epf="" epf:version="1.5.0" xmi:id="-h09djKXIOUJlez8h6UXrWw"
name=",_me8WcAANEdyRS9uciXlZ6g" guid="-h09djKXIOUJlez8h6UXrWw" changeDate="2007-05-11T15:20:56.100-0700">
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;
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;