| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-mEJbo_5lG227hXMdftmX_A" |
| name="new_guideline_2,_HrgUQNcuEdy1nJEYZGzN4A" guid="-mEJbo_5lG227hXMdftmX_A" |
| changeDate="2008-10-15T06:32:49.610-0700" version="7.2.0"> |
| <mainDescription><p>
 |
| When architecting a system, developing visual models of the architecture can be quite helpful as such models provide an
 |
| excellent high-level picture of the system, its <a class="elementLink"
 |
| href="./../../../core.tech.common.extend_supp/guidances/concepts/component_CB167D48.html"
 |
| guid="_0YP18MlgEdmt3adZL5Dmdw">Component</a>s and their relationships. Specifically, you may find it useful to develop
 |
| these three Unified Modeling Language (UML) diagrams:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Layer map</strong> (represented as a class diagram using packages) that describes the upper-level layers of
 |
| the architecture
 |
| </li>
 |
| <li>
 |
| <strong>Deployment diagram</strong> (represented by a deployment diagram) that outlines the&nbsp;expected network
 |
| topology
 |
| </li>
 |
| <li>
 |
| <strong>Key Abstractions diagram</strong> (represented by a class diagram) that shows the key
 |
| abstractions/components&nbsp;and important relationships among them
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| For more information on visual modeling, see <a class="elementLinkWithType"
 |
| href="./../../../core.tech.common.extend_supp/guidances/guidelines/using_visual_modeling_DA1CA6E4.html"
 |
| guid="_0SsecNr8EdyXE6np2_hUMA">Guideline: Using Visual Modeling</a>.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
