| <?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="_iCwb8MM3EdmSIPI87WLu3g" |
| name="repres_interfaces_to_ext_systems,_0gjdYMlgEdmt3adZL5Dmdw" guid="_iCwb8MM3EdmSIPI87WLu3g" |
| changeDate="2008-08-06T18:07:25.375-0700" version="1.0.0"> |
| <mainDescription><p>
 |
| Interfaces with external systems should be consistently handled throughout the system. The architecture need not
 |
| include a specific, detailed design for each system interface. It is often enough to simply identify the existence of
 |
| the interface as a significant part of the architecture and create a <a class="elementLink" href="./../../../core.tech.common.extend_supp/guidances/concepts/component_CB167D48.html" guid="_0YP18MlgEdmt3adZL5Dmdw">Component</a>&nbsp;to encapsulate the detail, so that it can be developed later.
 |
| </p>
 |
| <p>
 |
| The <a class="elementLink" href="./../../../core.tech.common.extend_supp/guidances/guidelines/entity_control_boundary_pattern_C4047897.html" guid="_uF-QYEAhEdq_UJTvM1DM2Q">Entity-Control-Boundary Pattern</a>&nbsp;provides the basis for a useful technique to
 |
| support this.&nbsp;Specifically, if the system communicates with another system, define one or more components to
 |
| describe the communication protocol.&nbsp; The use of a component allows the interface to the external system to be
 |
| defined and stabilized, while leaving the design details of the system interface hidden as the system evolves.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
