Google Git
Sign in
eclipse / epf / org.eclipse.epf.libraries / 491071c1a56e01038b6f3323cb51bc4efd486894 / . / epf_prac_151 / process.abrd.base / capabilitypatterns / develop_bre_architecture / content.xmi
blob: 0c5703dbf3a96123f004b30c4ea339bad7c80235 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1">
<org.eclipse.epf.uma:ProcessDescription xmi:id="-LPRqcx3TAg7m-fqsDb-Qdg" name="architecture,_2_QBQX_BEd2YWI_0AZcMOA" guid="-LPRqcx3TAg7m-fqsDb-Qdg" version="7.5.1"/>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-rA66uZaVDDOF8xewr623tg" name="develop_architecture,_4s7EAH_BEd2YWI_0AZcMOA" guid="-rA66uZaVDDOF8xewr623tg">
<keyConsiderations>&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0in 0in 10pt&quot;>
&lt;span style=&quot;mso-bidi-language: HE&quot;>Integrating the BRE into the business application involves Middleware, server
implementation and architecture background. Integrating BRMS into the business and IT organization involves process
definition, development practices and methodology skills.&lt;/span>
&lt;/p></keyConsiderations>
<refinedDescription>&lt;p>
The architect has to address as soon as possible in the project life cycle:
&lt;/p>
&lt;ul>
&lt;li>
Integrate the Rule Engine into the business application using a service oriented design to facilitate reuse and
scalability. If an embedded solution is the choice for accessing the BRE the design should address the engine
integration at the API level.
&lt;/li>
&lt;li>
Deploy Business Rules Management System into the business and IT organizations. This includes the deployment of the
Rule Developer IDE and Rule Analyst web based component into the IT architecture. It also addresses the change
management processes to design on top of the tools.&lt;br />
&lt;/li>
&lt;/ul>
&lt;p>
For a BRMS deployment architect needs to integrate the following components within the IT architecture:
&lt;/p>
&lt;ul>
&lt;li>
The Rule Engine as an executable class, callable using proprietary API or the JSR94 API. Rule Engine can be an
embedded component or deployed within a pool as reusable components. Java Connector Architecture can be a solution
to manage a pool of Rule Engines. JCA implementation offers a set of services which any deployed adapters can
leverage: such as security and transaction propagation.&amp;nbsp;&lt;br />
&lt;/li>
&lt;li>
The Rule Set(s): As script file, it needs to be managed and deployed dynamically and can follow a specific life
cycle. It can be also packaged as a jar and available after the system startup, or hot deployed using JMX.&lt;br />
&lt;/li>
&lt;li>
The IDE, like a Rule Studio, used by the developers to implement the rules, the rule set structure and the
technical elements of the rule sets.&lt;br />
&lt;/li>
&lt;li>
A Web based Rule management platform to let business users and analysts being able to maintain the rules.&lt;br />
&lt;/li>
&lt;li>
A Rule testing framework to support functional testing of the rule set and non-regression tests.
&lt;/li>
&lt;/ul>
&lt;p>
&lt;img height=&quot;376&quot; alt=&quot;&quot; src=&quot;resources/brmscomponents.jpg&quot; width=&quot;487&quot; />
&lt;/p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-i6qDLS-QtvrGS7XrdQccRw" name="decision_service_architecture,_4tXv8H_BEd2YWI_0AZcMOA" guid="-i6qDLS-QtvrGS7XrdQccRw">
<refinedDescription>&lt;p>
&lt;a class=&quot;elementLink&quot; href=&quot;./../../practice.tech.abrd.base/guidances/termdefinitions/decision_service_6C51F997.html&quot;
guid=&quot;_M0nWsAsYEdyPCr4G1Tb79A&quot;>Decision service&lt;/a> definition should map business decision point and not technical
service like a rule set signature. Decision service&amp;nbsp;definition should not take into account the&amp;nbsp;fact that we
are using a rule engine&amp;nbsp;for the&amp;nbsp;implementation, and should expose reusable interface and
operations&amp;nbsp;that&amp;nbsp;are linked together by a business meaning or semantic.&amp;nbsp;This means a decision service is
part of the business services and not the technical services. &amp;nbsp;
&lt;/p>&lt;br /></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-GVzTM2PClW6NdAGW_5pHQQ" name="design_reference_data_integration,_5BMD0H_BEd2YWI_0AZcMOA" guid="-GVzTM2PClW6NdAGW_5pHQQ">
<refinedDescription>&lt;p>
From the methodology point of view data management need to be looked into: data origination, data management, and data
consumption. The architect needs to understand how the master data are coming from and how they are updated. The life
cycle of such data can lead to version and management control, that may add complexity on top of the services
versioning. The data consumption has to be addressed for the execution environment and also in the case of BRMS
deployment for the rule authoring environment.
&lt;/p>
&lt;p>
The following diagram highlights a high level architecture&amp;nbsp;architect can leverage to design&amp;nbsp;his own solution.
&lt;/p>&lt;br />
&lt;p>
&lt;img height=&quot;499&quot; alt=&quot;&quot; src=&quot;resources/mdm.jpg&quot; width=&quot;557&quot; />&lt;br />
&lt;/p>
&lt;p>
The master data are centralized in a repository, and technology as Master Data Management product can be&amp;nbsp;used for
that. The different sources of data are synchronized with this repository on a regular basis, using different
implementation mechanism based on ETL, ESB, web services or custom layer. A mapping mechanism&amp;nbsp;as to be applied to
persist the data in the repository. The Execution environment can fetch the last version or a given version of the data
from this repository and cache it.
&lt;/p>
&lt;p>
The same applies for the rule authoring environment: The&amp;nbsp;BRMS server can load the data and cache it in the web
server. With such simple architecture the rule writer can have access to a unique definition of the enumerated domains
or other business objects, like a Product definition.
&lt;/p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-0hmrAC1ixwLo8vzDeoMSHw" name="design_models_for_bre,_5QiHYH_BEd2YWI_0AZcMOA" guid="-0hmrAC1ixwLo8vzDeoMSHw">
<refinedDescription>&lt;p>
This is an important activity as we do not expose an enterprise model or a physical model as&amp;nbsp;is to a rule engine.
We need to create views of such complex models. The simplest mechanism uses XML Schema definition to define the model
exchanged between the caller and the rule service. Most of the server implementation are using a Java implementation,
so it may makes sense to leverage a Java to/ from XML binding as JAXB to easily test and implement the business
services and the models.
&lt;/p>
&lt;p>
In any cases&amp;nbsp;&amp;nbsp;the architect and developer of the executable models need to take into account the existing
physical models and the outcomes of the rule discovery and analysis, to be sure that the rule can execute
efficiently.&amp;nbsp;
&lt;/p>
&lt;p>
Developing such models is done by iterations.
&lt;/p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-1NnOz_GLRSSA5tYw0IfOMg" name="integrate_bre,_EAYVQH_CEd2YWI_0AZcMOA" guid="-1NnOz_GLRSSA5tYw0IfOMg">
<refinedDescription>&lt;p>
The Rule Engine as an executable class, callable using proprietary API or the JSR94 API. Rule Engine can be an embedded
component or deployed within a pool as reusable components.
&lt;/p>
&lt;p>
When designing a SOA and the different decision services, the architect should focus and apply the same design pattern
as other business services. The rule engine technology choice is an implementation decision not a service design one.
The service design has to address:
&lt;/p>
&lt;ul>
&lt;li>
the service definition: one or more operations linked to the same data semantic
&lt;/li>
&lt;li>
the operation call approach: synchronous/ asynchronous, stateless/stateful, header based or carrying payload, use
of faults or not
&lt;/li>
&lt;li>
the exception reporting
&lt;/li>
&lt;/ul>
&lt;p>
The service implementation using a rule engine has to look at:
&lt;/p>
&lt;ul>
&lt;li>
the transaction propagation
&lt;/li>
&lt;li>
the reference data caching
&lt;/li>
&lt;li>
the parsing of input message: the claim data
&lt;/li>
&lt;li>
the loading of the related data: the policy related to the claim, or the insured person profile
&lt;/li>
&lt;li>
the preparation of the output message: the result and may be some other technical data
&lt;/li>
&lt;/ul></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-7RFal_ahu_4qnKS-p-tVQQ" name="logical_data_model,_fy3MQlmSEeCcpdiAcH0w-w" guid="-7RFal_ahu_4qnKS-p-tVQQ">
<refinedDescription>&lt;a id=&quot;XE_logical_data_model&quot; name=&quot;XE_logical_data_model&quot;>&lt;/a>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>
&lt;span style=&quot;FONT-SIZE: 10pt; FONT-FAMILY: Arial&quot;>&lt;span
style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>A logical data model or LDM is a graphical
representation of some of the business requirements and especially the concepts manipulated by the business member. LDM
is independent of the technology of implementation, and is mostly used&amp;nbsp;as a communication vehicle for the business
analyst and&amp;nbsp;to prepare the implementation of data models.&amp;nbsp;&amp;nbsp;&lt;/span>&lt;/span>
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>
&lt;span style=&quot;FONT-SIZE: 10pt; FONT-FAMILY: Arial&quot;>&lt;span
style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>From the point of view of an object-oriented developer
data modeling is conceptually similar to class modeling. With data modeling you identify entity types whereas with
class modeling you identify classes.&amp;nbsp; Data attributes are assigned to entity type just as you would assign
attributes and operations to classes. Traditional data modeling is different from class modeling because it focuses
solely on data – class models allow you to explore both the behavior and data aspects of your domain, with a data model
you can only explore data issues.&lt;/span>&lt;/span>
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot; />
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>
&lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>We use UML simple class diagram to represent
a&lt;/span> &lt;span style=&quot;mso-bidi-font-family: Arial&quot;>Logical Data Model&lt;/span> &lt;span
style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>but&amp;nbsp;by applying&amp;nbsp;Agile's principle of multiple
models, it is possible to use other diagrams.&lt;/span>
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot; />
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>
&lt;span style=&quot;mso-bidi-font-family: Arial&quot;>Logical Data Models&lt;/span> &lt;span
style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>are used to explore the domain concepts, and their
relationships, of&amp;nbsp;the problem domain.&amp;nbsp; This could be done for the scope of a single project or for&amp;nbsp;the
entire enterprise.&amp;nbsp; LDMs depict the logical entity types, typically referred to simply as entity types, the data
attributes describing those entities, and the relationships between the entities.&lt;/span>
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>
&amp;nbsp;
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>
Defining a logical data model prepare for future reuse, and help to build common definition of terms. This is one of
major building block for enterprise data model.
&lt;/p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-Ma59gPLPnn5KbrkfjVsCuw" name="decision_point_table,_fy3MRVmSEeCcpdiAcH0w-w" guid="-Ma59gPLPnn5KbrkfjVsCuw">
<refinedDescription>&lt;a id=&quot;XE_decision_point_table&quot; name=&quot;XE_decision_point_table&quot;>&lt;/a>
&lt;p>
&lt;span
style=&quot;FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>Groups
together all potential rules that determine one decision.&lt;/span> &lt;a id=&quot;XE_decision_point&quot; name=&quot;XE_decision_point&quot;>It
can be found in a use case description or in a Business Process Map task description.&lt;/a>&amp;nbsp;Presented in table
format the project team can use the following template:
&lt;/p>&lt;br />
&lt;div align=&quot;center&quot;>
&lt;table class=&quot;ISISTable&quot;
style=&quot;BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; WIDTH: 496.15pt; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver&quot;
cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; width=&quot;662&quot; border=&quot;1&quot;>
&lt;tbody>
&lt;tr style=&quot;HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes&quot;>
&lt;td
style=&quot;BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: gray 1pt solid; WIDTH: 70.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt&quot;
valign=&quot;top&quot; width=&quot;95&quot;>
&lt;p class=&quot;MsoNormalCxSpFirst&quot; style=&quot;TEXT-ALIGN: center; mso-yfti-cnfc: 1&quot; align=&quot;center&quot;>
&lt;b>&lt;i style=&quot;mso-bidi-font-style: normal&quot;>&lt;span style=&quot;COLOR: #005da0; mso-bidi-language: HE&quot;>&lt;font
size=&quot;3&quot;>&lt;font face=&quot;Times New Roman&quot;>Decision Point&lt;span style=&quot;mso-spacerun: yes&quot;>&amp;nbsp;&lt;/span>
Name&lt;/font>&lt;/font>&lt;/span>&lt;/i>&lt;/b>
&lt;/p>
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 148.85pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt&quot;
valign=&quot;top&quot; width=&quot;198&quot;>
&lt;p class=&quot;MsoNormalCxSpMiddle&quot; style=&quot;TEXT-ALIGN: center; mso-yfti-cnfc: 1&quot; align=&quot;center&quot;>
&lt;b>&lt;i style=&quot;mso-bidi-font-style: normal&quot;>&lt;span style=&quot;COLOR: #005da0; mso-bidi-language: HE&quot;>&lt;font
size=&quot;3&quot;>&lt;font face=&quot;Times New Roman&quot;>Description&lt;/font>&lt;/font>&lt;/span>&lt;/i>&lt;/b>
&lt;/p>
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 106.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt&quot;
valign=&quot;top&quot; width=&quot;142&quot;>
&lt;p class=&quot;MsoNormalCxSpMiddle&quot; style=&quot;TEXT-ALIGN: center; mso-yfti-cnfc: 1&quot; align=&quot;center&quot;>
&lt;b>&lt;i style=&quot;mso-bidi-font-style: normal&quot;>&lt;span style=&quot;COLOR: #005da0; mso-bidi-language: HE&quot;>&lt;font
size=&quot;3&quot;>&lt;font face=&quot;Times New Roman&quot;>Source for Rule Discovery&lt;/font>&lt;/font>&lt;/span>&lt;/i>&lt;/b>
&lt;/p>
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 94.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt&quot;
valign=&quot;top&quot; width=&quot;126&quot;>
&lt;p class=&quot;MsoNormalCxSpMiddle&quot; style=&quot;TEXT-ALIGN: center; mso-yfti-cnfc: 1&quot; align=&quot;center&quot;>
&lt;font size=&quot;3&quot;>&lt;font face=&quot;Times New Roman&quot;>&lt;b>&lt;i style=&quot;mso-bidi-font-style: normal&quot;>&lt;span
style=&quot;COLOR: #005da0; mso-bidi-language: HE&quot;>Current&lt;/span>&lt;/i>&lt;/b> &lt;b>&lt;i
style=&quot;mso-bidi-font-style: normal&quot;>&lt;span
style=&quot;COLOR: #005da0; mso-bidi-language: HE&quot;>State&lt;/span>&lt;/i>&lt;/b> &lt;b>&lt;i
style=&quot;mso-bidi-font-style: normal&quot;>&lt;span style=&quot;COLOR: #005da0; mso-bidi-language: HE&quot;>of
Automation&lt;/span>&lt;/i>&lt;/b>&lt;/font>&lt;/font>
&lt;/p>
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt&quot;
valign=&quot;top&quot; width=&quot;100&quot;>
&lt;p class=&quot;MsoNormalCxSpMiddle&quot; style=&quot;TEXT-ALIGN: center; mso-yfti-cnfc: 1&quot; align=&quot;center&quot;>
&lt;b>&lt;i style=&quot;mso-bidi-font-style: normal&quot;>&lt;span style=&quot;COLOR: #005da0; mso-bidi-language: HE&quot;>&lt;font
size=&quot;3&quot;>&lt;font face=&quot;Times New Roman&quot;>Rule Owner -&lt;/font>&lt;/font>&lt;/span>&lt;/i>&lt;/b>
&lt;/p>
&lt;p class=&quot;MsoNormalCxSpMiddle&quot; style=&quot;TEXT-ALIGN: center; mso-yfti-cnfc: 1&quot; align=&quot;center&quot;>
&lt;b>&lt;i style=&quot;mso-bidi-font-style: normal&quot;>&lt;span style=&quot;COLOR: #005da0; mso-bidi-language: HE&quot;>&lt;font
size=&quot;3&quot;>&lt;font face=&quot;Times New Roman&quot;>SME&lt;/font>&lt;/font>&lt;/span>&lt;/i>&lt;/b>
&lt;/p>
&lt;/td>
&lt;/tr>
&lt;tr style=&quot;mso-yfti-irow: 0&quot;>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 70.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;95&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 148.85pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;198&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 106.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;142&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 94.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;126&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;100&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;/tr>
&lt;tr style=&quot;mso-yfti-irow: 1; mso-yfti-lastrow: yes&quot;>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: silver 1pt solid; WIDTH: 70.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;95&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 148.85pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;198&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 106.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;142&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 94.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;126&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;td
style=&quot;BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-left-alt: solid silver 1.0pt; mso-border-top-alt: solid silver 1.0pt&quot;
valign=&quot;top&quot; width=&quot;100&quot;>
&lt;br class=&quot;MsoNormalCxSpMiddle&quot; />
&lt;br />
&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>&lt;br />
&lt;p>
The name should be explicit and without any ambiguity. It helps to link back to the business process or use case step.
An example may be &quot;claim data review&quot;, or &quot;loan eligibility&quot;...
&lt;/p>
&lt;p>
The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
legal&amp;nbsp;manual...
&lt;/p>
&lt;p>
The current state of automation is optional and just list&amp;nbsp;if for this given decision point we can have tools which
can migrate the business rules&amp;nbsp;from one format to another.&amp;nbsp;
&lt;/p>
&lt;p>
The last column can be useful to define who will be the owner of the rule set(s) supporting the decision point. He/She
will be an important actor of the rule discovery.
&lt;/p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-lr_US7ML4CXgAan7X2HI3g" name="fact_model,_fy3MSFmSEeCcpdiAcH0w-w" guid="-lr_US7ML4CXgAan7X2HI3g">
<refinedDescription>&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0cm&quot;>
&lt;span style=&quot;mso-bidi-language: HE&quot;>A Fact Model represents structured business vocabulary with true statement like: A
customer places an order. The fact model looks like the Object Role Model described by Halpin (2001). When the model
starts to grow the notation become quickly invisible and no more helpful, so we do not encourage to follow this
notation.&lt;/span> We prefer using UML class diagram showing just the entities, the associations and may be some
characteristic as attributes of class.
&lt;/p>&lt;br />
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>
&lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>A Fact Model should always include elementary
(atomic) fact type:&lt;/span>
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt&quot;>
&lt;span style=&quot;FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt&quot;>•&lt;/span>&lt;span
style=&quot;FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'&quot;>&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span>
&lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>Noun:&amp;nbsp; Customer, Order, Product&lt;/span>
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt&quot;>
&lt;span style=&quot;FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt&quot;>•&lt;/span>&lt;span
style=&quot;FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'&quot;>&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span>
&lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>Verb:&amp;nbsp; places, briefs&lt;/span>
&lt;/p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
</xmi:XMI>