EPF_Practices/core.tech.common.extend_supp/guidances/concepts/business_pattern.xmi - epf/org.eclipse.epf.libraries - Git at Google

 <?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="-Of51hmgdsO_U2-pnbJ67Cg"
     name="new_concept,_RoSdMBWYEduCK502eDgjUQ" guid="-Of51hmgdsO_U2-pnbJ67Cg" changeDate="2008-02-10T19:39:04.750-0800"
     version="7.2.0">
   <mainDescription>&lt;p>&#xD;
     Business Patterns are a form of Design Pattern&amp;nbsp;(see &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.tech.common.extend_supp/guidances/concepts/pattern_10BE6D96.html&quot; guid=&quot;_0YJvUMlgEdmt3adZL5Dmdw&quot;>Concept: Pattern&lt;/a>) and are the business-domain counterpart of &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.tech.common.extend_supp/guidances/concepts/arch_mechanism_2932DFB6.html&quot; guid=&quot;_mzxI0A4LEduibvKwrGxWxA&quot;>Concept: Architectural Mechanisms&lt;/a>. Just as similar problems in the technical domain&#xD;
     may be solved by using Architecture Mechanisms, similar problems in the business domain can be solved by using Business&#xD;
     Patterns.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
     Business Patterns are often found in COTS products. For example, packaged applications that support Enterprise Resource&#xD;
     Planning or Customer Relationship Management ship with functionality to support a variety of generic business&#xD;
     processes. Similarly, it is frequently possible to identify related or similar behavior in the Use&#xD;
     Case&amp;nbsp;Scenarios&amp;nbsp;and thereby derive generic designs that you can use in the design of the system. These&#xD;
     elements of generic behavior can be&amp;nbsp;expressed as Design&amp;nbsp;Patterns and applied to the system design.&#xD;
 &lt;/p>&lt;br /></mainDescription>
 </org.eclipse.epf.uma:ContentDescription>
	<?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="-Of51hmgdsO_U2-pnbJ67Cg"
	name="new_concept,_RoSdMBWYEduCK502eDgjUQ" guid="-Of51hmgdsO_U2-pnbJ67Cg" changeDate="2008-02-10T19:39:04.750-0800"
	version="7.2.0">
	<mainDescription><p>
	Business Patterns are a form of Design Pattern&nbsp;(see <a class="elementLinkWithType" href="./../../../core.tech.common.extend_supp/guidances/concepts/pattern_10BE6D96.html" guid="_0YJvUMlgEdmt3adZL5Dmdw">Concept: Pattern</a>) and are the business-domain counterpart of <a class="elementLinkWithType" href="./../../../core.tech.common.extend_supp/guidances/concepts/arch_mechanism_2932DFB6.html" guid="_mzxI0A4LEduibvKwrGxWxA">Concept: Architectural Mechanisms</a>. Just as similar problems in the technical domain
	may be solved by using Architecture Mechanisms, similar problems in the business domain can be solved by using Business
	Patterns.
	</p>
	<p>
	Business Patterns are often found in COTS products. For example, packaged applications that support Enterprise Resource
	Planning or Customer Relationship Management ship with functionality to support a variety of generic business
	processes. Similarly, it is frequently possible to identify related or similar behavior in the Use
	Case&nbsp;Scenarios&nbsp;and thereby derive generic designs that you can use in the design of the system. These
	elements of generic behavior can be&nbsp;expressed as Design&nbsp;Patterns and applied to the system design.
	</p><br /></mainDescription>
	</org.eclipse.epf.uma:ContentDescription>