blob: 7203b7a25b2dd06927e44876acc92e14a3729325 [file] [log] [blame]
<?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="-f_C19dHfbYGTJrBoaWdPJA"
name="types_of_rule_discovery_roadmap,_aS75QBtjEdu_BZ3CL1I6hw" guid="-f_C19dHfbYGTJrBoaWdPJA"
authors="Jerome Boyer" changeDate="2008-09-04T16:24:03.226-0700" version="1.0.0">
<mainDescription>&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0cm&quot;>&#xD;
&lt;span style=&quot;mso-bidi-language: HE&quot;>&lt;span style=&quot;mso-bidi-language: HE&quot;>The following table is giving the different&#xD;
possible starting points for the discovery activity.&lt;/span>&lt;/span>&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0cm&quot;>&#xD;
&lt;span style=&quot;mso-bidi-language: HE&quot;>&lt;span style=&quot;mso-bidi-language: HE&quot;>&amp;nbsp;&lt;/span>&lt;/span>&#xD;
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0cm&quot; />&#xD;
&lt;br />&#xD;
&lt;table title=&quot;&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; width=&quot;85%&quot; border=&quot;1&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;th id=&quot;&quot; scope=&quot;col&quot; abbr=&quot;&quot;>&#xD;
Analysis techniques used - starting point&#xD;
&lt;/th>&#xD;
&lt;th id=&quot;&quot; scope=&quot;col&quot; abbr=&quot;&quot;>&#xD;
Description&#xD;
&lt;/th>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td>&#xD;
Business Events&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
Start with the business events listed in the inception artifacts.&lt;br />&#xD;
Each business event is processed by a set of activities that can be described in document or business&#xD;
process&lt;br />&#xD;
Use when the organization does not utilize use cases.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td>&#xD;
Use Case&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
Analyze Use case description to find decision points and then rules&lt;br />&#xD;
Preferred approach, used by team used to develop use cases, or Agile user stories.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td>&#xD;
Business process / Workflow&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
Evaluate individual process steps and tasks to define the&amp;nbsp;decision&amp;nbsp;behind each activty&amp;nbsp;and&#xD;
then the rules.&lt;br />&#xD;
Used when the organization utilizes process decomposition for the requirements gathering and analysis phase&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td>&#xD;
Data Analysis&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
Used in case of data change oriented rules project&lt;br />&#xD;
Starts with the logical data model and how evaluate how entities are created&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td>&#xD;
Mission Policies&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
Based on a top-down rules and business policies approach&lt;br />&#xD;
Rules sources are high level manager, decision makers&lt;br />&#xD;
Part of a business process reengineering effort&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&lt;br />&#xD;
&lt;br />&#xD;
&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0cm&quot; />&#xD;
&lt;br />&#xD;
&lt;br /></mainDescription>
</org.eclipse.epf.uma:ContentDescription>