| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription 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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-wmNktMd6FNHo9XGSzcXqXQ" |
| name="decision_service_architecture,_6BE7QAp_EdyPCr4G1Tb79A" guid="-wmNktMd6FNHo9XGSzcXqXQ" |
| authors="Jerome Boyer" changeDate="2010-08-13T16:17:04.875-0700"> |
| <mainDescription><p>
 |
| <a class="elementLink" href="./../../practice.tech.abrd.base/guidances/termdefinitions/decision_service_6C51F997.html"
 |
| guid="_M0nWsAsYEdyPCr4G1Tb79A">Decision service</a> definition should map business decision point and not technical
 |
| service like a rule set signature. Decision service&nbsp;definition should not take into account the&nbsp;fact that we
 |
| are using a rule engine&nbsp;for the&nbsp;implementation, and should expose reusable interface and
 |
| operations&nbsp;that&nbsp;are linked together by a business meaning or semantic.&nbsp;This means a decision service is
 |
| part of the business services and not the technical services. &nbsp;
 |
| </p><br /></mainDescription> |
| </org.eclipse.epf.uma:ArtifactDescription> |
