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