| <?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="-25kZ4WEhRZTa5DGdUrQU5g" |
| name="rule_analysis,_lT6WEBDJEdyJtJ3PbfdVDw" guid="-25kZ4WEhRZTa5DGdUrQU5g" authors="Jerome Boyer" |
| changeDate="2008-09-05T13:55:29.534-0700" version="1.0.0"> |
| <mainDescription><a id="XE_rule_analysis" name="XE_rule_analysis"></a> 
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE"><span style="mso-bidi-language: HE">The goal of the rule analysis activity is to
 |
| understand the meaning of the rule as stated by the business person and Subject Matter Expert and to remove any
 |
| ambiguity and semantic issue in this description so that we can prepare for the future rule implementation. The rule
 |
| analyst and the rule writer analyze the rules discovered in a disjointed way into a complete and coherent
 |
| set.</span></span>
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE">From the rule description, the glossary of business terms and may be from a first
 |
| version of the conceptual data model (CDM), the discovery team needs to transform the rules using terms of the business
 |
| object to elements that will be implemented by the rule writers.</span>
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm">
 |
| <span style="mso-bidi-language: HE">The rule analysis includes at least the following activities:</span>
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| <img height="284" alt="" src="./resources/Analysis_BP.bmp" width="800" />
 |
| </p>
 |
| <div style="MARGIN-TOP: 0cm; MARGIN-LEFT: 2em" type="disc">
 |
| <ul style="MARGIN-TOP: 0cm" type="disc">
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">Analyze the description of the rule to find business concept and things,
 |
| and facts</span>
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">Transform Rules&nbsp;to remove ambiguity and to
 |
| make&nbsp;them&nbsp;atomic.The rule should use well-defined terms. Those terms will serve to develop the future
 |
| data models.</span>
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| Build test scenario
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| Design the data model for rules
 |
| </li>
 |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">Synchronize with the data modeling team</span>
 |
| </li>
 |
| </ul>
 |
| </div>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">A rule is atomic if it cannot be further decomposed without losing meaning.</span>
 |
| </p><br class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt" />
 |
| <br />
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">Rule analysis does not deal with rule validation, this will be done later, nor it
 |
| does not deal with rule optimization. One of the most difficult activity of the rule analysis is to resolve
 |
| inconsistencies among rules and ensure completeness among rules. This will not be possible to complete a rule set in
 |
| one iteration, but the analysis activity should address the questions of completeness and prepare for the future
 |
| iteration.</span>
 |
| </p><br class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt" />
 |
| <br />
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
 |
| <span style="mso-bidi-language: HE">It is also very important to start using the rule development IDE as soon as
 |
| possible to understand how complex the rule and the object model are. This is when we implement rules that we are
 |
| seeing real analysis issues. Implemented rule also help to come back to the business users with concrete cases,
 |
| questions and issues.</span>
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |