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