| <?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.3/uma.ecore" xmi:id="-Of51hmgdsO_U2-pnbJ67Cg" name="new_concept,_RoSdMBWYEduCK502eDgjUQ" guid="-Of51hmgdsO_U2-pnbJ67Cg" changeDate="2006-07-21T11:59:56.413-0700"> |
| <mainDescription><p> Business Patterns are a form of Design Pattern&nbsp;(see <a class="elementLinkWithType" |
| href="./../../../openup_basic/guidances/concepts/using_patterns,_0cr7cACrEdu8m4dIntu6jA.html" |
| guid="_0cr7cACrEdu8m4dIntu6jA">Concept: Using Patterns</a>) and are the business-domain |
| counterpart of <a |
| class="elementLinkWithType" |
| href="./../../../openup_basic/guidances/concepts/architecture_mechanism,_mzxI0A4LEduibvKwrGxWxA.html" |
| guid="_mzxI0A4LEduibvKwrGxWxA">Concept: Architectural Mechanism</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> |