| <?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="-Zf7BWTSjLSrv650HXb5Bvw" |
| name=",_LGd_MFtvEdykEsBjRsVfZw" guid="-Zf7BWTSjLSrv650HXb5Bvw" authors="Jerome Boyer" |
| changeDate="2007-12-14T14:19:33.390-0800"> |
| <mainDescription><p>
 |
| There are multiple type of reports the rule team can analyze:<a id="XE_rule_set__get_reports"
 |
| name="XE_rule_set__get_reports"></a>
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The&nbsp;query report to list the rules part of the rule set, rule flow, package, activate or not.
 |
| </li>
 |
| <li>
 |
| Static analysis of conflict resolution
 |
| </li>
 |
| <li>
 |
| rules execution report
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| S<a id="1028579" name="1028579">tatic rule analysis is a mechanism for checking whether the rules are semantically
 |
| consistent. Inconsistencies can be found either in a single rule or in a set of rules</a>.
 |
| </p>
 |
| <p>
 |
| For single rule the analysis will list the rule that never apply, when the conditions of the rule can never be met.
 |
| This could happen when there is mis-used of and/or operator in combined conditions, or if the values in the conditions
 |
| are not in the possible allowable values for a given attribute.<br />
 |
| </p>
 |
| <p>
 |
| Evaluating rule inconsistency in a rule set leads to discover
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Equivalent rules&nbsp;rules with same conditions and&nbsp;actions.
 |
| </li>
 |
| </ul></mainDescription> |
| <purpose>Get different rule report to analyze the conformance to the expected results</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
