| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription 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="-Ak_E6i3qbz4NMG7ynyf4DA" |
| name="define_discovery_roadmap,_srklxgjqEdyj5bYZ0eCR5g" guid="-Ak_E6i3qbz4NMG7ynyf4DA" |
| authors="Jerome Boyer" changeDate="2008-09-05T10:15:16.036-0700" version="1.0.0"> |
| <mainDescription><p>
 |
| There are two dimensions to consider when preparing the rule discovery activi-ties or roadmap:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The type of source for rule harvesting
 |
| </li>
 |
| <li>
 |
| The type of analysis used by the project team: use case approach, busi-ness process modeling, mission policies
 |
| analysis
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Tony Morgan in his book "Business Rules and Information Systems: Aligning IT with Business Goals" proposes the
 |
| following discovery processed according to the different source above:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The static analysis process uses reading and highlighting the rules within documentation. The elicitation is based
 |
| on reading session completed with Question / Answer workshop sessions
 |
| </li>
 |
| <li>
 |
| Interactive involves a Subject Matter Expert who has the knowledge of the business process and the decisions to
 |
| take to process a given business event.The process will be done by using elicitation workshop
 |
| </li>
 |
| <li>
 |
| Automated involve using a computer and special application to search for rule statement within procedure code, SQL
 |
| procedures, code listing… Code review should always be complemented by workshop sessions for Q&amp;A.<br />
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| So for each decision point within the DP table do the following steps&nbsp;
 |
| </p></mainDescription> |
| <sections xmi:id="_srklyQjqEdyj5bYZ0eCR5g" name="Review the decision points table with stakeholders and prioritize them" |
| guid="_srklyQjqEdyj5bYZ0eCR5g"> |
| <sectionDescription><p style="MARGIN-LEFT: 36pt; TEXT-INDENT: -18pt; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| <i style="mso-bidi-font-style: normal"><span style="mso-bidi-language: HE">Review the decision points with the
 |
| stakeholders and set the priority</span></i> <span style="mso-bidi-language: HE">on each decision point.</span>
 |
| Depending of the complexity of the business process the team should prioritize which rule harvesting&nbsp;to tackle
 |
| first. A good practice is to start with a simple, well understood decision point, to help training the team on the
 |
| practice, but keep also in mind that the management wants to see the business value of what the team is working on. So
 |
| a decision point that is important by bringing a value, should be in the top of the list.
 |
| </p>
 |
| <p style="MARGIN-LEFT: 36pt; TEXT-INDENT: -18pt; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| If needed review the business context to keep the business needs and reassess the priority accordingly. It is important
 |
| to start by extracting rules that is bringing immediate value to the business users, to get their buy in, and
 |
| motivation to continue to do this painful work. It may be relevant&nbsp;to start&nbsp;with the most complex business
 |
| scenario. It helps convincing business users and rapidly enriches the coneptual data model. It is important to set the
 |
| expectation among the stakeholders that not all the rules will be discovered during this phase. The goal is to complete
 |
| a rule set up to 40-60% to have some tangible decision on standard business event to process. The rule writers or the
 |
| development team will enhance the <a class="elementLink"
 |
| href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_set_4D4C8DB1.html"
 |
| guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a> later on.
 |
| </p>
 |
| <p>
 |
| <span
 |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US">One
 |
| good practice is to implement the decision logic using rules for the main stream of business processing, letting the
 |
| exceptions to the human. It will be always possible to add rules to manage some newly discovered exception later
 |
| on.&nbsp; A typical case is in the underwriting type of rules. An expert will quickly extract some basic rules that
 |
| always need to be true to accept the Application. As soon as the discussions start to be around the "but there is a
 |
| case where ..." a lot of new rules will arrive.</span>
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_srklxwjqEdyj5bYZ0eCR5g" name="Select acquisition process according to the source of rule." |
| guid="_srklxwjqEdyj5bYZ0eCR5g"> |
| <sectionDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span style="mso-bidi-language: HE">Select the acquisition process
 |
| according to the source of rule: Map the rule source to a suitable acquisition process:</span></span>
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <div class="MsoNormal" style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| <span style="mso-bidi-language: HE">Human&nbsp;&nbsp; =&gt; workshop session</span>
 |
| </div>
 |
| </li>
 |
| <li>
 |
| <div class="MsoNormal" style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| <span style="mso-bidi-language: HE">Documentation (legal)&nbsp;&nbsp; =&gt;&nbsp;&nbsp; Active
 |
| reading&nbsp;followed and Q&amp; A sessions</span>
 |
| </div>
 |
| </li>
 |
| <li>
 |
| <div class="MsoNormal" style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| <span style="mso-bidi-language: HE">Code&nbsp;&nbsp; =&gt;&nbsp; Mining followed Q&amp;A sessions and design
 |
| sessions</span>
 |
| </div>
 |
| </li>
 |
| </ul>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| <span style="mso-bidi-language: HE">When the source is people we need to start individual interview to get the core of
 |
| the knowledge and then follow up with workshops to resolve outstanding issues and process exception paths with the
 |
| team.</span>
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| <span style="mso-bidi-language: HE"><br />
 |
| </span><span style="mso-bidi-language: HE">Modify for each decision point in the table the acquisition process chosen
 |
| and the owner of the process</span>
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1">
 |
| <span style="mso-bidi-language: HE"><br />
 |
| &nbsp;</span>
 |
| </p><br class="MsoNormal" style="MARGIN: 3pt 0cm; tab-stops: list 72.0pt; mso-list: l0 level2 lfo1" />
 |
| <br /></sectionDescription> |
| </sections> |
| </org.eclipse.epf.uma:TaskDescription> |
