<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-je0zRqgX0Tg_761Z77cIkg" name="arch_constraints,_jdKSsNpiEdyP58ppo1Ieaw" guid="-je0zRqgX0Tg_761Z77cIkg" changeDate="2008-02-13T10:37:37.000-0800" version="7.2.0">
  <mainDescription>&lt;p>&#xD;
    A variety of factors may place constraints on the architecture being developed:&#xD;
&lt;/p>&#xD;
&lt;div style=&quot;MARGIN-LEFT: 2em&quot;>&#xD;
    &lt;ul>&#xD;
        &lt;li>&#xD;
            Network topology&#xD;
        &lt;/li>&#xD;
        &lt;li>&#xD;
            Use of a given database vendor or an existing database&#xD;
        &lt;/li>&#xD;
        &lt;li>&#xD;
            Web environment (server configurations, firewall, DMZs, and so forth)&#xD;
        &lt;/li>&#xD;
        &lt;li>&#xD;
            Servers (hardware model, operating system)&#xD;
        &lt;/li>&#xD;
        &lt;li>&#xD;
            Use of third-party software or a particular technology&#xD;
        &lt;/li>&#xD;
        &lt;li>&#xD;
            Compliance with existing standards&#xD;
        &lt;/li>&#xD;
    &lt;/ul>&#xD;
&lt;/div>&#xD;
&lt;p>&#xD;
    For example, if the company uses only one type of database, you will probably try to use it as much as possible to&#xD;
    leverage&amp;nbsp;the existing database administration skills, rather than introducing a new one.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    These architectural constraints, combined with the requirements, help you define&amp;nbsp;an appropriate&amp;nbsp;candidate for&#xD;
    the system architecture. Capturing these constraints will ease integration with the environment; and may reduce risk,&#xD;
    cost and duplication of solution elements.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
