| <?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:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-_O0viDuqU93cNwdUU02Fmg" |
| name="rule_discovery,_jfdmsAsHEdyPCr4G1Tb79A" guid="-_O0viDuqU93cNwdUU02Fmg" authors="Jerome Boyer" |
| changeDate="2008-11-20T21:40:54.769-0800" version="1.0.0"> |
| <mainDescription><a id="XE_rule_discovery" name="XE_rule_discovery"></a> 
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE"><span style="mso-bidi-language: HE">Rule Discovery is also named Business Rules
 |
| Modeling in the industry and has the focus to develop simple modeling artifacts like rule descriptions, business entity
 |
| diagrams and business process maps.</span><span style="mso-bidi-language: HE">&nbsp;</span></span>
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE">The purposes of Rule Discovery&nbsp; are:</span>
 |
| </p>
 |
| <ul style="MARGIN-TOP: 0cm" type="disc">
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo2; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">To define the rule classification from the business process</span>
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo2; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">To attach decision point to business process activities and / or use case
 |
| steps</span>
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">To define the rule sources for the discovery and the type of roadmap to support
 |
| the knowledge acquisition.</span>
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">To formalize the rules using templates and business term and language
 |
| understood by the business user</span>
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">To prepare the test data &nbsp;for the rules</span>
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">To define the object model for the rules</span>
 |
| </li>
 |
| </ul>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE">If the business modeling activity is done&nbsp;during the Inception&nbsp;phase of
 |
| the project you should leverage the previous artifacts like the conceptual data model and the decision point
 |
| table.</span><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE">The discovery activities&nbsp; are conducted during the Elaboration phase of the
 |
| project, but the same process is conducted even after the system has gone into production when there is a new business
 |
| event, or when there is a need to modify the decision logic&nbsp;of the application.</span>
 |
| </p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
 |
| <br />
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE"><img style="WIDTH: 720px; HEIGHT: 352px" height="318" alt=""
 |
| src="./resources/Discovery_process.gif" width="600" />&nbsp;</span>
 |
| </p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
 |
| <br />
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE">The most unique aspect of the rules discovery phase is the perception of a business
 |
| event as a set of decision-rich activities. We unravel a business event as a set of decisions and policies. We then
 |
| dissect the decisions and policies into executable and precise business rules that guide the business event in a
 |
| predictable and desirable manner.</span>
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |