| <?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.3/uma.ecore" epf:version="1.0.0" xmi:id="-1Lm8-0FY-QIC56u5t2SC9w" name=",__JXkoCk8EduLGM8dfVsrKg" guid="-1Lm8-0FY-QIC56u5t2SC9w" changeDate="2007-02-26T12:49:32.093+0000" version="1.0.0"> |
| <mainDescription><p> |
| Here are some templates for representing the architecture. Architecture can be represented in a variety of ways, |
| according to the needs of the project team. See <a class="elementLink" |
| href="./../../../openup_basic/workproducts/architecture,_0XAf0MlgEdmt3adZL5Dmdw.html" |
| guid="_0XAf0MlgEdmt3adZL5Dmdw">Architecture</a>&nbsp;for more information. |
| </p> |
| <p> |
| Feel free to use one or more of these templates or create your own. |
| </p> |
| <p> |
| The <a class="elementLink" href="./../../../openup_basic/roles/architect,_0X9iEMlgEdmt3adZL5Dmdw.html" |
| guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a> should decide what views are useful for describing the system under |
| consideration.&nbsp; |
| </p> |
| <p> |
| Consider one or more&nbsp;relevant views of the architecture and document each one using the provided template for the |
| architectural view. If needed, document information that applies to more than one view using the template provided for |
| the Software Architecture Document to get an integrated representation of the architecture instead of just snapshots |
| taken from different angles. |
| </p> |
| <p> |
| The structuring of the documents must support the needs of the intended audience. For example, instead of a document |
| for the implementation view developers may find more useful alternative forms for the project directory structure like |
| the template provided for the project startup kit. |
| </p> |
| <p> |
| Keep documentation up-to-date but to an essential minimum. When the architecture is under development, decisions are |
| reconsidered frequently so constant revision of the documentation is an unnecessary expense.&nbsp; Determine points in |
| the development lifecycle when documentation should be updated. |
| </p></mainDescription> |
| <attachments>resources/sw_architecture_doc_tpl.dot|resources/project_startup_kit.zip|resources/sw_architecture_view_tpl.dot|resources/software_arch_document.dot</attachments> |
| </org.eclipse.epf.uma:GuidanceDescription> |