| <?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="-LP0SlsHoERAIzSe1UpKmlw" |
| name="build_test_scenario,_1dlWkH3GEd2sJcA0evSBQw" guid="-LP0SlsHoERAIzSe1UpKmlw" |
| authors="Jerome Boyer" changeDate="2008-09-22T09:48:44.195-0700"> |
| <mainDescription><p>
 |
| <span
 |
| style="FONT-SIZE: 10pt; FONT-FAMILY: 'Times','serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: DE; mso-bidi-language: AR-SA"><font
 |
| face="Arial">Developing without testing has no sense today (we hope!). Developing rules deployed in rule engine
 |
| helps&nbsp;us supporting efficiently a Test Driven Development approach. Rule set can be isolated&nbsp;early in the
 |
| development process and can be tested in a sandbox environment. Writing tests before the rule makes testing part of a
 |
| validation feedback loop.&nbsp;&nbsp;So during the harvesting phase the analysis team needs to develop test scenario
 |
| and data elements to support the rule writing and testing. Working on concrete scenario leads to clarify ambiguities,
 |
| find holes in the decision processing, and enhance rules decision coverage, and the overall quality.</font></span>
 |
| </p>
 |
| <p>
 |
| At this level the scenario description can be built as user story with persona involvement, and data point to
 |
| illustrate the scenario.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:TaskDescription> |
