| <?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="-5fWKItAqK2Tcw9hfycKKhw" |
| name="rule_analysis,_lT6WEBDJEdyJtJ3PbfdVDw" guid="-5fWKItAqK2Tcw9hfycKKhw" authors="Jerome Boyer" |
| changeDate="2008-02-01T11:10:20.140-0800" version="1.0.0"> |
| <copyrightStatement href="uma://_NFyDwAjqEdyj5bYZ0eCR5g#_WjLJwJLrEdyyIasIx_MrFQ"/> |
| <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 this activity is to prepare the
 |
| rules for the implementation. The rule analyst and the rule writer will 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 logical data model (LDM), the discovery team needs to transform the rules using terms of the business
 |
| object to elements that will be implemented by the rule writers. 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="600" />
 |
| </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">Transform Rules so that they are atomic, standalone elements, this is
 |
| needed for understandability, and ease of implementation and maintenance. &nbsp;The rule should use
 |
| well-defined terms. Those terms will serve to develop the future BOM.</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">Define Rule Schema, and understand underlying rule patterns, and eventually
 |
| remove redundant rules, or resolve overlaps among rules</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">Determine Rule Implementation</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">Build Rule Projects structure, with in-out parameters, rule flow, rule
 |
| packages structure and even different rule projects</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"><span
 |
| style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-bidi-language: AR-SA; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Build
 |
| Rule Business Object models as a view of the enterprise model but for the rule scope. Link it to the executable
 |
| objects model</span></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">Prototype some rules to get end user feedback quicker</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">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> |
