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