| <?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=",_sP_RgBtfEdu_BZ3CL1I6hw" guid="-Ak_E6i3qbz4NMG7ynyf4DA" version="1.0.0"> |
| <mainDescription><a id="XE_roadmap__define" name="XE_roadmap__define"></a></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">
 |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
 |
| style="mso-list: Ignore"><span style="FONT: 7pt 'Times New Roman'">&nbsp;</span></span></span><i
 |
| style="mso-bidi-font-style: normal"><span style="mso-bidi-language: HE">Review the decision points (<a
 |
| class="elementLink" href="./../../agile_rule/workproducts/decision_point_table_5C48ED46.html"
 |
| guid="_SlELAAsbEdyPCr4G1Tb79A">Decision Point Table</a>)&nbsp;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. Do not hesitate to start also with the most complex business scenario.
 |
| It helps convincing business users and rapidly enriches the <a class="elementLink"
 |
| href="./../../agile_rule/guidances/termdefinitions/bom_6AC0E84F.html" guid="_1iTjABCXEdyJtJ3PbfdVDw">Business Object
 |
| Model</a>. 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 <a class="elementLink" href="./../../agile_rule/roles/rule_writer_167E3ADC.html"
 |
| guid="_XiII4wqBEdyPCr4G1Tb79A">Rule Writer</a>s or the development team will enhance the <a class="elementLink"
 |
| href="./../../agile_rule/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 standard 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 ..." it
 |
| will be important to add this in the exception management.</span>
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_srklyAjqEdyj5bYZ0eCR5g" name="Define the source of rule for the discovery" |
| guid="_srklyAjqEdyj5bYZ0eCR5g"> |
| <sectionDescription><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> |
| <P class=MsoNormal style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1"><I style="mso-bidi-font-style: normal"><SPAN style="mso-bidi-language: HE"><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: HE; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Define the source of rule for the discovery</SPAN></SPAN></I><SPAN style="mso-bidi-language: HE">: There are at least three kinds of source to harvest the rules from:</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"></SPAN><SPAN style="mso-bidi-language: HE">Human: A <a href="./../../agile_rule/roles/subject_matter_expert_D73B48C5.html" guid="_XiII5AqBEdyPCr4G1Tb79A">Subject Matter Expert</a>&nbsp;who has the knowledge of the business process and the decisions to take to process a given event. Also a person doing the day today activity is a very good source for rule discovery&nbsp;and business process exception management. The process to extract rule from human source will be done by using elicitation workshop.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></DIV> |
| <LI class=MsoNormal style="MARGIN: 3pt 0cm; tab-stops: list 72.0pt; mso-list: l0 level2 lfo1"><SPAN style="mso-bidi-language: HE">Documentation: legal, internal policies, procedure. Gather the documents with the reference on version, date of validity... The elicitation is based on reading and Question and Answer workshop sessions.<o:p></o:p></SPAN> |
| <LI class=MsoNormal style="MARGIN: 3pt 0cm; tab-stops: list 72.0pt; mso-list: l0 level2 lfo1"><SPAN style="mso-bidi-language: HE">Code: procedure code, SQL procedures, listing… The elicitation is based on reading the code, executes it, getting data and expected results. Some care has to be taken in this case. Sometime the "business rules" implemented in procedural code are loosing their context of execution as soon as we extract them, so code review should always be complemented by workshop sessions for Q&amp;A. A rule in a system done some years ago may not apply in current business context.</SPAN></LI></UL></SPAN></sectionDescription> |
| </sections> |
| <sections xmi:id="_srklxwjqEdyj5bYZ0eCR5g" name="Select acquisition process according to the source of rule." |
| guid="_srklxwjqEdyj5bYZ0eCR5g"> |
| <sectionDescription><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> |
| <P class=MsoNormal style="MARGIN: 3pt 0cm; tab-stops: list 36.0pt; mso-list: l0 level1 lfo1"><I style="mso-bidi-font-style: normal"><SPAN style="mso-bidi-language: HE">Select the acquisition process according to the source of rule</SPAN></I><SPAN style="mso-bidi-language: HE">: Map the rule source to a suitable acquisition process:<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></P> |
| <UL style="MARGIN-TOP: 0cm" type=disc> |
| <UL style="MARGIN-TOP: 0cm" type=circle> |
| <LI class=MsoNormal style="MARGIN: 3pt 0cm; tab-stops: list 72.0pt; mso-list: l0 level2 lfo1"><SPAN style="mso-bidi-language: HE">Human<SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>=&gt; workshop session<o:p></o:p></SPAN> |
| <LI class=MsoNormal style="MARGIN: 3pt 0cm; tab-stops: list 72.0pt; mso-list: l0 level2 lfo1"><SPAN style="mso-bidi-language: HE">Documentation (legal)<SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>=&gt;<SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN><?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:City w:st="on"><st1:place w:st="on">Reading</st1:place></st1:City> and Q&amp; A sessions<o:p></o:p></SPAN> |
| <LI class=MsoNormal style="MARGIN: 3pt 0cm; tab-stops: list 72.0pt; mso-list: l0 level2 lfo1"><SPAN style="mso-bidi-language: HE">Code<SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>=&gt;<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>Mining and Q&amp;A sessions</SPAN></LI></UL></UL> |
| <P class=MsoNormal style="MARGIN: 3pt 0cm; tab-stops: list 72.0pt; mso-list: l0 level2 lfo1"><SPAN style="mso-bidi-language: HE"><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: HE; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Modify for each decision point in the table the acquisition process chosen and the owner of the process</SPAN></SPAN></P></SPAN></sectionDescription> |
| </sections> |
| </org.eclipse.epf.uma:TaskDescription> |
