| <?xml version="1.0" encoding="UTF-8"?> |
| <xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1"> |
| <org.eclipse.epf.uma:ProcessDescription xmi:id="-z9VrO6XKxLBPsLPbkRNDlg" name="discovery,_40DokXqkEd2o_5d3MWaNxQ" guid="-z9VrO6XKxLBPsLPbkRNDlg" version="7.5.1"/> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-lm3kKBz3aGKgtfJqku4utw" name="identify_decision_point,_ELiLsD3hEd-rQL4FfV6WbQ" guid="-lm3kKBz3aGKgtfJqku4utw"> |
| <refinedDescription><p> |
| A <a class="elementLink" href="./../../practice.tech.abrd.base/guidances/termdefinitions/decision_point_B1C5EFE2.html" |
| guid="_XUyFIEb1EdySHMdInS9eGA">Decision point</a>&nbsp;represents an activity in a business process where decisions are |
| done. When looking at a task description it is important to search for mental thinking verb, most of the time there is |
| a set of knowledge to apply to execute this task, which leads to decision. This could be human knowledge or business |
| logic implementation in a software component. The type of decision will most likely be a reject or accept of the |
| business event or flag it for future processing downstream in the business process. The decision may also include some |
| computational expressions to assign value to attribute of the business transaction. Therefore to find decision point in |
| a business process or use case description start by searching for mental, action verb like analyze, check, validate, |
| evaluate, verify, assess, ... |
| </p> |
| <p> |
| In a BPMN process diagram a business process analyst and/ or a rule analyst can annotate the process to highlight |
| decision point in the process. |
| </p> |
| <p> |
| <img height="363" alt="" src="resources/FindDecisionPoint.bmp" width="1572" /> |
| </p> |
| <p> |
| The search for decision point, attached to a business process description (done with use case or with BPMN does not |
| matter), helps to drive the rule analysis, and helps the business to focus at the business rule&nbsp;enforcement. |
| If&nbsp;the business team misses where the rule should be enforced, he can spend months defining business rules which |
| IT does not understand where to deploy them. The decision point can help drive the discovery of the business policies |
| and rules, for an implementation point of view, as well as a way to organize the top down approach. A decision point |
| support multiple rules, and if implemented with a rule engine, the rules are packaged as rule set. |
| </p> |
| <p> |
| Also finding the decision points involves studying<br /> |
| • Which use cases/scenarios represent decisions - At what steps in the use case is a decision made?<br /> |
| • Which requirements constitute rich set of decisions?<br /> |
| • Which steps/cases/requirements represent significant complexity?<br /> |
| • Which steps/cases/requirements are most subject to change?<br /> |
| • Look for decision diamonds in the flow charts and activity diagrams, the gateway by itself route the data to the next |
| activity, but the activity before the gateway should be rich in decisions. |
| </p> |
| <p> |
| The documentation of the decision point can be done in table format. |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-68Th4UZYizWD_CWSKyd3iw" name="review_decision_point_table,_H0NM8Ht0Ed2obd5av1OT7w" guid="-68Th4UZYizWD_CWSKyd3iw"> |
| <refinedDescription><a id="XE_decision_point_table__review" name="XE_decision_point_table__review"></a>See the step description&nbsp;below.</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Jj9nvyH0gVrdCHxKpOws0A" name="decision_point_table,_H0NM8nt0Ed2obd5av1OT7w" guid="-Jj9nvyH0gVrdCHxKpOws0A"> |
| <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a> |
| <p> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Groups |
| together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It |
| can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table |
| format the project team can use the following template: |
| </p><br /> |
| <div align="center"> |
| <table class="ISISTable" |
| style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; WIDTH: 496.15pt; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver" |
| cellspacing="0" cellpadding="0" width="662" border="1"> |
| <tbody> |
| <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes"> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: gray 1pt solid; WIDTH: 70.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt" |
| valign="top" width="95"> |
| <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center"> |
| <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font |
| size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span> |
| Name</font></font></span></i></b> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 148.85pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt" |
| valign="top" width="198"> |
| <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center"> |
| <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font |
| size="3"><font face="Times New Roman">Description</font></font></span></i></b> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 106.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt" |
| valign="top" width="142"> |
| <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center"> |
| <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font |
| size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 94.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt" |
| valign="top" width="126"> |
| <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center"> |
| <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span |
| style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i |
| style="mso-bidi-font-style: normal"><span |
| style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i |
| style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of |
| Automation</span></i></b></font></font> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt" |
| valign="top" width="100"> |
| <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center"> |
| <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font |
| size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b> |
| </p> |
| <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center"> |
| <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font |
| size="3"><font face="Times New Roman">SME</font></font></span></i></b> |
| </p> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 0"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 70.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="95"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 148.85pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="198"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 106.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="142"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 94.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="126"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="100"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 70.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="95"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 148.85pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="198"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 106.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="142"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 94.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="126"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="100"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </div><br /> |
| <p> |
| The name should be explicit and without any ambiguity. It helps to link back to the business process or use case step. |
| An example may be "claim data review", or "loan eligibility"... |
| </p> |
| <p> |
| The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies, |
| legal&nbsp;manual... |
| </p> |
| <p> |
| The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which |
| can migrate the business rules&nbsp;from one format to another.&nbsp; |
| </p> |
| <p> |
| The last column can be useful to define who will be the owner of the rule set(s) supporting the decision point. He/She |
| will be an important actor of the rule discovery. |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-FWD_oEKFs78KJKJ_KSHXHw" name="business_process_map,_H0NM83t0Ed2obd5av1OT7w" guid="-FWD_oEKFs78KJKJ_KSHXHw"> |
| <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a> |
| <p> |
| A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a |
| business event: a claim is received and needs to be processed within 15 days. |
| </p> |
| <p> |
| A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute |
| to achieving the goal of the super-process. |
| </p> |
| <p> |
| The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The |
| entry point is a mail with the loan application received, then the process follow a set of activities to decide if the |
| loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This |
| process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group |
| tasks per actors. |
| </p> |
| <p> |
| <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br /> |
| <br /> |
| &nbsp; |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Zt7Ibx5DM49KKxndcqRTtw" name="define_discovery_roadmap,_JbeFsHt0Ed2obd5av1OT7w" guid="-Zt7Ibx5DM49KKxndcqRTtw"> |
| <refinedDescription><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></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-rLfn7xRB2TQqbODEHjDh-g" name="rule_discovery_roadmap,_JbeFsnt0Ed2obd5av1OT7w" guid="-rLfn7xRB2TQqbODEHjDh-g"> |
| <refinedDescription><a id="XE_rule_discovery__roadmap" name="XE_rule_discovery__roadmap"></a>For each decision point we can complete the |
| information about the discovery roadmap and plan. The following table format can be used as template.<br |
| class="ISISGuidance" style="MARGIN: 3pt 0cm 3pt 36pt" /></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Z6HScOkPIosgyp7UCf6Qlg" name="organise_workshop,_LIaIoHt0Ed2obd5av1OT7w" guid="-Z6HScOkPIosgyp7UCf6Qlg"> |
| <refinedDescription><a id="XE_workshop__organize" name="XE_workshop__organize"></a> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| To make the better use of the development and business team's time it is important to plan in advance the workshop |
| sessions and to clearly state what is in the agenda. We recommend organizing the day in two parts: |
| </p> |
| <ul style="MARGIN-TOP: 0cm" type="disc"> |
| <li style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt"> |
| Do morning discovery workshop using elicitation techniques with the project stakeholders and subject matter expert. |
| During the&nbsp;rule harvesting phase the analyst team may want to use the rule template document to enter the rule |
| description and use some simple diagramming techniques to define the business entities (A good tool is the UML |
| class diagram but without the details of the methods) |
| </li> |
| <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt"> |
| Second part of the day is used by&nbsp;the analyst and development team to perform analysis activities and later on |
| to author the rules. |
| </li> |
| </ul> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| As explained in <a class="elementLink" |
| href="./../../practice.tech.abrd.base/guidances/concepts/cycle_approach_7FA44D8F.html" |
| guid="_ftAoIAjrEdyj5bYZ0eCR5g">Cycle Approach to Rules Development</a> the discovery workshops are in phase 1, 2, and |
| 3, but with different frequency of occurrence. Phase 1 and 2, the workshops can be set every morning, but starting on |
| phase 3 it could happen every two days or more (but never more than a week to keep the focus and efficiency in the |
| process).<br class="MsoNormal" style="MARGIN: 3pt 0cm" /> |
| </p> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| The team should verify to have access to a dedicated meeting room with white boards, pencils, paper; post it, and |
| potentially a UML tool to quickly develop diagrams.. |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-CdOZnJTJqXUWqZwWTv00YA" name="discovery_workshop_itinerary,_LIaIoXt0Ed2obd5av1OT7w" guid="-CdOZnJTJqXUWqZwWTv00YA"> |
| <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| <b style="mso-bidi-font-weight: normal">Goal:</b> <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These |
| series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help: |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To link rules to business context |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business |
| language. |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To prepare for for the logical data model |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation |
| </p><br class="MsoNormal" style="MARGIN: 3pt 0cm" /> |
| <br /> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session |
| </p> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise |
| Architect, ISIS rule templates |
| </p> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| <b style="mso-bidi-font-weight: normal">Agenda</b>: |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language |
| understood by the business user |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To prepare the tests for the rules |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> To define the object model for the rule |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules |
| </p> |
| <p class="MsoNormal" |
| style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt"> |
| <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span |
| style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule |
| change requirements |
| </p> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model |
| </p> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| <b style="mso-bidi-font-weight: normal">Invitees</b>: |
| </p> |
| <div align="center"> |
| <table class="ISISTable" |
| style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver" |
| cellspacing="0" cellpadding="0" border="1"> |
| <tbody> |
| <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes"> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: gray 1pt solid; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid" |
| valign="top" width="322"> |
| <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center"> |
| <strong><em><font face="Times New Roman" color="#005DA0" |
| size="3">Business</font></em></strong>&nbsp; |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt" |
| valign="top" width="322"> |
| <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center"> |
| <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span |
| style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b> |
| </p> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 0"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="322"> |
| <p class="MsoNormalCxSpMiddle"> |
| <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="322"> |
| <p class="MsoNormalCxSpMiddle"> |
| <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span> |
| </p> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 1"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="322"> |
| <p class="MsoNormalCxSpMiddle"> |
| <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="322"> |
| <p class="MsoNormalCxSpMiddle"> |
| <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span> |
| </p> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 2"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="322"> |
| <p class="MsoNormalCxSpMiddle"> |
| <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="322"> |
| <p> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| &nbsp; |
| </p> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="322"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="322"> |
| <br class="MsoNormalCxSpMiddle" /> |
| <br /> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </div> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm"> |
| <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual |
| data model |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-00teH0OUZQu5a2dSdjcT0g" name="execute_rule_discovery_roadmap,_ac8CoHt0Ed2obd5av1OT7w" guid="-00teH0OUZQu5a2dSdjcT0g"> |
| <refinedDescription><p> |
| Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is |
| critical. They will change their minds as the project proceeds and that's perfectly fine. |
| </p> |
| <p> |
| The documentation of the rule may be done using different language. The natural language is initially used during |
| business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their |
| ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and |
| unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business |
| terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic. |
| </p> |
| <p> |
| Conceptualization and representation play fundamental roles in thinking, communicating, and modeling. |
| </p> |
| <p> |
| A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have |
| imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct |
| semantically. We use the rule description template to log the rule. |
| </p> |
| <p> |
| The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule |
| refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business |
| Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally |
| representations of concepts, definitions, instances, and rules&nbsp;in natural language. |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-oMh2j3Q0H1ko6v__BoxY0Q" name="business_terms_glossary,_ac8CoXt0Ed2obd5av1OT7w" guid="-oMh2j3Q0H1ko6v__BoxY0Q"> |
| <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"> |
| <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from |
| the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this |
| kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the |
| organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span> |
| </p> |
| <p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"> |
| <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging |
| the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the |
| responsibility of&nbsp;a team.</span> |
| </p> |
| <div align="center"> |
| <table class="ISISTable" |
| style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver; mso-table-layout-alt: fixed" |
| cellspacing="0" cellpadding="0" border="1"> |
| <tbody> |
| <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes"> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: gray 1pt solid; WIDTH: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt" |
| valign="top" width="104"> |
| <p class="MsoNormalCxSpMiddle" |
| style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center"> |
| <font size="3"><b><i style="mso-bidi-font-style: normal"><span |
| style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt" |
| valign="top" width="76"> |
| <p class="MsoNormalCxSpMiddle" |
| style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center"> |
| <b><i style="mso-bidi-font-style: normal"><span |
| style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font |
| size="3">Acronym</font></span></i></b> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt" |
| valign="top" width="425"> |
| <p class="MsoNormalCxSpMiddle" |
| style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center"> |
| <font size="3"><b><i style="mso-bidi-font-style: normal"><span |
| style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font> |
| </p> |
| </td> |
| <td |
| style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt" |
| valign="top" width="76"> |
| <p class="MsoNormalCxSpMiddle" |
| style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center"> |
| <font size="3"><b><i style="mso-bidi-font-style: normal"><span |
| style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font> |
| </p> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 0"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="104"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="76"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="425"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="76"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 1"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="104"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="76"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="425"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="76"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 2"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="104"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="76"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="425"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="76"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| </tr> |
| <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes"> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="104"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="76"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="425"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| <td |
| style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt" |
| valign="top" width="76"> |
| <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" /> |
| <br /> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </div></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-WnGCuUFJzEEm0quNf1yoRg" name="rule_description_doc,_ac8Cont0Ed2obd5av1OT7w" guid="-WnGCuUFJzEEm0quNf1yoRg"> |
| <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a> |
| <p> |
| The rule description document is used during the discovery phase, and during the first iterations for building a rule |
| set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule |
| Authoring phase. |
| </p> |
| <p> |
| It is also interesting to leverage SBVR to document the rule. |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-TyRUd1xh4OgmE7l9ZXFTCg" name="conceptual_data_model,_ac8Co3t0Ed2obd5av1OT7w" guid="-TyRUd1xh4OgmE7l9ZXFTCg"> |
| <refinedDescription><p> |
| A conceptual data model describes the things important for an organization as entity classes and characteristics of the |
| things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or |
| conceivable and used in a day to day conversation. |
| </p> |
| <p> |
| Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and |
| the business team members. |
| </p> |
| <p> |
| With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and |
| are described during the initial requirements iterations. In our approach conceptual data model are the first version |
| of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule |
| elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the |
| iterations the CDMs are replaced by the LDMs. |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-dUUjRXpEQ7U-x2t9WG3nXg" name="business_event_description,_h4FMVlmSEeCcpdiAcH0w-w" guid="-dUUjRXpEQ7U-x2t9WG3nXg"> |
| <refinedDescription><p> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 9.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">Trigger |
| for the execution of a business process.</span> The processing of a business event can be done manually or using |
| software products and applications. Some decisions need to be done on the event for example to accept/ reject it or to |
| initiate some business processes. Those decisions can be implemented using a rule engine technology. |
| </p> |
| <p> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 9.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">The |
| following list gives some examples of business event:</span> |
| </p> |
| <ul> |
| <li> |
| <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Claim is received</span> |
| </li> |
| <li> |
| <div class="MsoNormal" style="MARGIN: 0in 0in 0pt"> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Tax |
| form is filled</span> |
| </div> |
| </li> |
| <li> |
| <div class="MsoNormal" style="MARGIN: 0in 0in 0pt"> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Loan |
| application is received</span> |
| </div> |
| </li> |
| <li> |
| <div class="MsoNormal" style="MARGIN: 0in 0in 0pt"> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Car |
| is out of the chain</span> |
| </div> |
| </li> |
| <li> |
| <div class="MsoNormal" style="MARGIN: 0in 0in 0pt"> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Train |
| wheel goes in front of infrared sensor</span> |
| </div> |
| </li> |
| <li> |
| <div class="MsoNormal" style="MARGIN: 0in 0in 0pt"> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">RFID |
| read</span> |
| </div> |
| </li> |
| <li> |
| <div class="MsoNormal" style="MARGIN: 0in 0in 0pt"> |
| <span |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Wafer |
| is started within the Fab</span> |
| </div> |
| </li> |
| </ul></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| </xmi:XMI> |