| <?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="-AUjqKQk_naPhdZWAQR-Mmg" |
| name=",_nOQHsAp6EdyPCr4G1Tb79A" guid="-AUjqKQk_naPhdZWAQR-Mmg" authors="Jerome Boyer" |
| changeDate="2008-01-23T21:41:01.250-0800" version="1.0.0"> |
| <copyrightStatement href="uma://_NFyDwAjqEdyj5bYZ0eCR5g#_hRkAkAjqEdyj5bYZ0eCR5g"/> |
| <mainDescription><p>
 |
| In a BRMS deployment there are at least the following components to intergrate in the core business application and in
 |
| the IT architecture:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The Rule Engine as an executable class, calleable using proprietary API or JSR94 API. Rule Engine can be embedded
 |
| component or deployed in a pool. Java Connector Architecture can be a solution to manage a pool of Rule Engines. It
 |
| offers a lot of services provided by the JEE container, that an architect can leverage.
 |
| </li>
 |
| <li>
 |
| The Rule Set(s) as script files which needs to be managed and deployed dynamically or at system startup to the rule
 |
| engine.
 |
| </li>
 |
| <li>
 |
| An IDE, like a Rule Studio, to develop the core rule set.
 |
| </li>
 |
| <li>
 |
| A Web based Rule management platform, to let business users, analysts be able to maintain the rules.
 |
| </li>
 |
| <li>
 |
| A Rule testing framework to support functional testing of the rule set and non-regression tests.
 |
| </li>
 |
| </ul></mainDescription> |
| <sections xmi:id="_yIEJ4Ap6EdyPCr4G1Tb79A" name="Design the decision service interface" |
| guid="_yIEJ4Ap6EdyPCr4G1Tb79A"/> |
| <purpose>Develop the piece of the software architecture related to the execution of the rules, and their management.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
