Bug 329220 - Should remove unnecessary local descriptors
Removed all dangling role descriptors throughout the library including openup and abrd processes.
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/analyze_business_rules/content.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/analyze_business_rules/content.xmi
index 9a524c0..ab2701b 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/analyze_business_rules/content.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/analyze_business_rules/content.xmi
@@ -1,2 +1,255 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-D3NR4UjCNAA8tz8ik9KxuA" name="analyze,_qx-1wX9WEd26h9j0X6pKmw" guid="-D3NR4UjCNAA8tz8ik9KxuA" version="7.5.1"/>
+<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="-D3NR4UjCNAA8tz8ik9KxuA" name="analyze,_qx-1wX9WEd26h9j0X6pKmw" guid="-D3NR4UjCNAA8tz8ik9KxuA" version="7.5.1"/>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-N_CKAaJNHSW61yq8ZoC2jg" name="extract_rule_meaning,_tlXjYH9WEd26h9j0X6pKmw" guid="-N_CKAaJNHSW61yq8ZoC2jg">
+ <refinedDescription><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">During the elicitation activity the raw description of the rule uses business terms as used in common
+ language used by the people. This presents what the business users think about the way things are done in the company.
+ They are linking words with statements with all the different semantic attached to them. The first activity focuses on
+ analyzing this rule description&nbsp;to extract&nbsp;the business entities and terms used in a formal non ambiguous
+ fashion.&nbsp;</font></span>
+</p>
+<p>
+ We are discussing about Business Term here, as reference to a business concept used in daily business operations.They
+ are often found in different departments or refer to the same business concept from a different perspective: they are
+ synonyms. A term may describe business concept which will be mapped to a Class, a characteristic of a business entity
+ which will be mapped to attribute of a class, and sometime a term may describe the way a business object behave, in
+ that last case it will be mapped within method of a final state machine.
+</p>
+<p>
+ The second concept presented in the analysis of rule is the Fact. Fact is a combination of terms that describes what
+ business people know about their business. It connects terms into sensible business relevant observations.<br
+ style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple" />
+ As stated by the SBVR specification meaning is built of concepts, questions and propositions. the concepts will build
+ our underlying data model used by the executable rules, and the proposition will structure the data model and can also
+ be mapped to rules.<br />
+</p>
+<p
+style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple">
+ All these informations&nbsp;help to build a&nbsp;first logical data model used to build the underlying object
+ model&nbsp;used by the rules. We can use UML tool to design a class diagram, generates java code and import such code
+ in the rule IDE.<br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-tcywvwJFy76naDhkV-kE1g" name="rule_description_doc,_tlzoQn9WEd26h9j0X6pKmw" guid="-tcywvwJFy76naDhkV-kE1g">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-WdZgViZU-KFgjnSALDjXiw" name="fact_model,_tlzoQ39WEd26h9j0X6pKmw" guid="-WdZgViZU-KFgjnSALDjXiw">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Uesh6anvRV-n8YiCvPAkIg" name="logical_data_model,_tlzoRH9WEd26h9j0X6pKmw" guid="-Uesh6anvRV-n8YiCvPAkIg">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-KQ7Tq2GDC0gGvnqUTC7HpA" name="transform_rules,_t32agH9WEd26h9j0X6pKmw" guid="-KQ7Tq2GDC0gGvnqUTC7HpA">
+ <keyConsiderations>This activity will also be done during the implementation of the rule set, but it is started during the analysis, so we are
+detailing it in this context.</keyConsiderations>
+ <refinedDescription><p>
+ Rule Analyst has to study the rule discovered and try to transform it so that the implementation and the management of
+ the rule will be more easy. This includes transforming the rule in atomic element using a syntax without ambiguity,
+ remove redundant rules, conflicting rules, and finally try to redefine the scope of the rule by searching by
+ non-handled cases.&nbsp;
+</p>
+<p>
+ At this stage rule analyst can build some rule template which&nbsp;are built from rules that have the same set of
+ conditions with some little variations: adding new value in test condition, or new condition.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Lwx7QOcZjNCEknbhZVYHpA" name="build_test_scenario,_uMueUH9WEd26h9j0X6pKmw" guid="-Lwx7QOcZjNCEknbhZVYHpA">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ZXqKURahjzSp8B1-MBY6Hw" name="synchronize_data_model,_ueoGoH9WEd26h9j0X6pKmw" guid="-ZXqKURahjzSp8B1-MBY6Hw">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst needs to continuously verify that business terms used in rule statements are part of the logical data
+ model (classes/ attributes) and physical data model (PDM). The model exposed to the rule needs to get data from data
+ sources. If a concept is not in the data it has to be quickly handled and managed by the application architect.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst should be in continuous communication with the data model developer, responsible to develop the XML
+ schema or java model (or .Net), and the physical mapping to database.<br />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Part of most of the business application are the list of code, enumerated date or domain values. It is important to
+ well design how those data are defined, accessed by the application, and the rule authoring environment.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ It can be helpful for some major business term to define a mapping to a class-attribute, and if the BRMS supports this
+ function it is recommended to detail the "verbalization" of the business term.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<div align="center">
+ <table class="MsoNormalTable" style="WIDTH: 351pt; BORDER-COLLAPSE: collapse; mso-padding-alt: 0in 0in 0in 0in"
+ cellspacing="0" cellpadding="0" width="468" border="0">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes">
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: gray 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Business Term</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">OO mapping</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Verbalization</span></i>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LTV</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LoanApplication.ltv</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">The loan to value ratio</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in left 3.0in" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/analyze_business_rules/model.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/analyze_business_rules/model.xmi
index 7de875a..6b8eb75 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/analyze_business_rules/model.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/analyze_business_rules/model.xmi
@@ -2,27 +2,42 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__Y770bekEd-D7YZN9NgldQ" guid="__Y770bekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__Y770rekEd-D7YZN9NgldQ" id="-D3NR4UjCNAA8tz8ik9KxuA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_DwUHgVmSEeCcpdiAcH0w-w" id="-N_CKAaJNHSW61yq8ZoC2jg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_DwUHglmSEeCcpdiAcH0w-w" id="-tcywvwJFy76naDhkV-kE1g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_DwUHg1mSEeCcpdiAcH0w-w" id="-WdZgViZU-KFgjnSALDjXiw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_DwUHhFmSEeCcpdiAcH0w-w" id="-Uesh6anvRV-n8YiCvPAkIg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Dwd4gFmSEeCcpdiAcH0w-w" id="-KQ7Tq2GDC0gGvnqUTC7HpA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Dwd4gVmSEeCcpdiAcH0w-w" id="-Lwx7QOcZjNCEknbhZVYHpA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Dwd4glmSEeCcpdiAcH0w-w" id="-ZXqKURahjzSp8B1-MBY6Hw" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_qx-1wH9WEd26h9j0X6pKmw" name="analyze_business_rules" guid="_qx-1wH9WEd26h9j0X6pKmw">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_tlXjYH9WEd26h9j0X6pKmw" name="extract_rule_meaning" guid="_tlXjYH9WEd26h9j0X6pKmw" presentationName="Extract Rule Meaning" superActivities="_qx-1wX9WEd26h9j0X6pKmw" isSynchronizedWithSource="false" mandatoryInput="_tlzoQn9WEd26h9j0X6pKmw" output="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw" performedPrimarilyBy="_tlzoQH9WEd26h9j0X6pKmw _tlzoQX9WEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_tlXjYH9WEd26h9j0X6pKmw" name="extract_rule_meaning" guid="_tlXjYH9WEd26h9j0X6pKmw" presentationName="Extract Rule Meaning" briefDescription="Extract the semantic of the rule to prepare for a data model and to remove any ambiguity and redundancy." superActivities="_qx-1wX9WEd26h9j0X6pKmw" isSynchronizedWithSource="false" mandatoryInput="_tlzoQn9WEd26h9j0X6pKmw" output="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw">
+ <presentation xmi:id="-N_CKAaJNHSW61yq8ZoC2jg" href="uma://-D3NR4UjCNAA8tz8ik9KxuA#-N_CKAaJNHSW61yq8ZoC2jg"/>
+ <concepts href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_gPfSoIpzEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8_mWgH3GEd2sJcA0evSBQw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_o19QgF2BEd2T6cNSe41mOg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_tlzoQH9WEd26h9j0X6pKmw" name="business_analyst" guid="_tlzoQH9WEd26h9j0X6pKmw" presentationName="Business Analyst" isPlanned="false" superActivities="_qx-1wX9WEd26h9j0X6pKmw" modifies="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_tlzoQX9WEd26h9j0X6pKmw" name="rule_analyst" guid="_tlzoQX9WEd26h9j0X6pKmw" presentationName="Rule Analyst" isPlanned="false" superActivities="_qx-1wX9WEd26h9j0X6pKmw" modifies="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw" responsibleFor="_tlzoQ39WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_tlzoQn9WEd26h9j0X6pKmw" name="rule_description_doc" guid="_tlzoQn9WEd26h9j0X6pKmw" presentationName="Rule Description Document" isPlanned="false" superActivities="_qx-1wX9WEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_tlzoQn9WEd26h9j0X6pKmw" name="rule_description_doc" guid="_tlzoQn9WEd26h9j0X6pKmw" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_qx-1wX9WEd26h9j0X6pKmw">
+ <presentation xmi:id="-tcywvwJFy76naDhkV-kE1g" href="uma://-D3NR4UjCNAA8tz8ik9KxuA#-tcywvwJFy76naDhkV-kE1g"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_tlzoQ39WEd26h9j0X6pKmw" name="fact_model" guid="_tlzoQ39WEd26h9j0X6pKmw" presentationName="Fact Model" isPlanned="false" superActivities="_qx-1wX9WEd26h9j0X6pKmw">
+ <presentation xmi:id="-WdZgViZU-KFgjnSALDjXiw" href="uma://-D3NR4UjCNAA8tz8ik9KxuA#-WdZgViZU-KFgjnSALDjXiw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_tlzoRH9WEd26h9j0X6pKmw" name="logical_data_model" guid="_tlzoRH9WEd26h9j0X6pKmw" presentationName="Logical Data Model" isPlanned="false" superActivities="_qx-1wX9WEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_tlzoRH9WEd26h9j0X6pKmw" name="logical_data_model" guid="_tlzoRH9WEd26h9j0X6pKmw" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_qx-1wX9WEd26h9j0X6pKmw">
+ <presentation xmi:id="-Uesh6anvRV-n8YiCvPAkIg" href="uma://-D3NR4UjCNAA8tz8ik9KxuA#-Uesh6anvRV-n8YiCvPAkIg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_t32agH9WEd26h9j0X6pKmw" name="transform_rules" guid="_t32agH9WEd26h9j0X6pKmw" presentationName="Transform Rules" superActivities="_qx-1wX9WEd26h9j0X6pKmw" linkToPredecessor="_vBEFUH9WEd26h9j0X6pKmw" isSynchronizedWithSource="false" mandatoryInput="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw" output="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw" performedPrimarilyBy="_tlzoQX9WEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_t32agH9WEd26h9j0X6pKmw" name="transform_rules" guid="_t32agH9WEd26h9j0X6pKmw" presentationName="Transform Rules" briefDescription="Transform the rule to avoid ambiguity and make them more atomic" superActivities="_qx-1wX9WEd26h9j0X6pKmw" linkToPredecessor="_vBEFUH9WEd26h9j0X6pKmw" isSynchronizedWithSource="false" mandatoryInput="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw" output="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw">
+ <presentation xmi:id="-KQ7Tq2GDC0gGvnqUTC7HpA" href="uma://-D3NR4UjCNAA8tz8ik9KxuA#-KQ7Tq2GDC0gGvnqUTC7HpA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_K6-3kDmnEdy8N6BRpa8ByQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x_5XgH9iEd26h9j0X6pKmw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8mZw8DmhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_7HEPsDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_tFwpYDmoEdy8N6BRpa8ByQ"/>
@@ -32,18 +47,19 @@
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_0-T6ADmoEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_vBEFUH9WEd26h9j0X6pKmw" guid="_vBEFUH9WEd26h9j0X6pKmw" pred="_tlXjYH9WEd26h9j0X6pKmw"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_uMueUH9WEd26h9j0X6pKmw" name="build_test_scenario" guid="_uMueUH9WEd26h9j0X6pKmw" presentationName="Build Test Scenarios" superActivities="_qx-1wX9WEd26h9j0X6pKmw" linkToPredecessor="_vWrwAH9WEd26h9j0X6pKmw" isSynchronizedWithSource="false" additionallyPerformedBy="_uMueUX9WEd26h9j0X6pKmw _tlzoQH9WEd26h9j0X6pKmw" performedPrimarilyBy="_tlzoQX9WEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_uMueUH9WEd26h9j0X6pKmw" name="build_test_scenario" guid="_uMueUH9WEd26h9j0X6pKmw" presentationName="Build Test Scenarios" briefDescription="Work with analysis team to define concrete scenario with real data so that we can later on test the process and the rules." superActivities="_qx-1wX9WEd26h9j0X6pKmw" linkToPredecessor="_vWrwAH9WEd26h9j0X6pKmw" isSynchronizedWithSource="false">
+ <presentation xmi:id="-Lwx7QOcZjNCEknbhZVYHpA" href="uma://-D3NR4UjCNAA8tz8ik9KxuA#-Lwx7QOcZjNCEknbhZVYHpA"/>
+ <guidelines href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <supportingMaterials href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_vLvAUGjFEd2PJ-nlV-86WA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1dlWkH3GEd2sJcA0evSBQw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_vWrwAH9WEd26h9j0X6pKmw" guid="_vWrwAH9WEd26h9j0X6pKmw" pred="_t32agH9WEd26h9j0X6pKmw"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_uMueUX9WEd26h9j0X6pKmw" name="subject_matter_expert" guid="_uMueUX9WEd26h9j0X6pKmw" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_qx-1wX9WEd26h9j0X6pKmw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ueoGoH9WEd26h9j0X6pKmw" name="synchronize_data_model" guid="_ueoGoH9WEd26h9j0X6pKmw" presentationName="Synchronize Data Models" superActivities="_qx-1wX9WEd26h9j0X6pKmw" linkToPredecessor="_vobnUH9WEd26h9j0X6pKmw" isSynchronizedWithSource="false" mandatoryInput="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw" output="_tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw" performedPrimarilyBy="_tlzoQX9WEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ueoGoH9WEd26h9j0X6pKmw" name="synchronize_data_model" guid="_ueoGoH9WEd26h9j0X6pKmw" presentationName="Synchronize Data Models" briefDescription="Ensure the terms and entities used in the rule march element in the different date models used by the IT components" superActivities="_qx-1wX9WEd26h9j0X6pKmw" linkToPredecessor="_vobnUH9WEd26h9j0X6pKmw" isSynchronizedWithSource="false" mandatoryInput="_tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw" output="_tlzoRH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw">
+ <presentation xmi:id="-ZXqKURahjzSp8B1-MBY6Hw" href="uma://-D3NR4UjCNAA8tz8ik9KxuA#-ZXqKURahjzSp8B1-MBY6Hw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_prtzIDmiEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_vobnUH9WEd26h9j0X6pKmw" guid="_vobnUH9WEd26h9j0X6pKmw" pred="_uMueUH9WEd26h9j0X6pKmw"/>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_qx-1wX9WEd26h9j0X6pKmw" name="analyze_business_rules" guid="_qx-1wX9WEd26h9j0X6pKmw" presentationName="Analyze Business Rules" breakdownElements="_tlXjYH9WEd26h9j0X6pKmw _tlzoQH9WEd26h9j0X6pKmw _tlzoQX9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw _tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _t32agH9WEd26h9j0X6pKmw _uMueUH9WEd26h9j0X6pKmw _uMueUX9WEd26h9j0X6pKmw _ueoGoH9WEd26h9j0X6pKmw">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_qx-1wX9WEd26h9j0X6pKmw" name="analyze_business_rules" guid="_qx-1wX9WEd26h9j0X6pKmw" presentationName="Analyze Business Rules" breakdownElements="_tlXjYH9WEd26h9j0X6pKmw _tlzoQn9WEd26h9j0X6pKmw _tlzoQ39WEd26h9j0X6pKmw _tlzoRH9WEd26h9j0X6pKmw _t32agH9WEd26h9j0X6pKmw _uMueUH9WEd26h9j0X6pKmw _ueoGoH9WEd26h9j0X6pKmw">
<presentation xmi:id="-D3NR4UjCNAA8tz8ik9KxuA" href="uma://-D3NR4UjCNAA8tz8ik9KxuA#-D3NR4UjCNAA8tz8ik9KxuA"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/author_business_rules/content.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/author_business_rules/content.xmi
index 52f357e..f6a7d93 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/author_business_rules/content.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/author_business_rules/content.xmi
@@ -1,2 +1,109 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-TUyCFXMljyPPGFQbnWy_Zw" name="authoring,_OQxnAX_CEd2YWI_0AZcMOA" guid="-TUyCFXMljyPPGFQbnWy_Zw" version="7.5.1"/>
+<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="-TUyCFXMljyPPGFQbnWy_Zw" name="authoring,_OQxnAX_CEd2YWI_0AZcMOA" guid="-TUyCFXMljyPPGFQbnWy_Zw" version="7.5.1"/>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-aoZNCrSMHCobCqrNM4Z5JA" name="develop_unit_tests,_VsH-QH_CEd2YWI_0AZcMOA" guid="-aoZNCrSMHCobCqrNM4Z5JA">
+ <refinedDescription><a id="XE_unit_tests__develop" name="XE_unit_tests__develop"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Rule Unit Testing is the process of testing a specific rule in the context of the rule set in which it is deployed.
+ Rule Unit Testing allows rule writers to:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Validate each rule in the context of its rule set
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Control the rule set quality
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Conduct some impact analysis when rules are in conflict
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Helps to have non-regression tests
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There is a major difference between testing a code, and a rule. A rule engine per
+ design may not put a rule in the agenda if the conditions are not matched. This means that when the rule writer write a
+ new rule, even if the data are sent to trigger the execution of this new rule it is possible that a rule fired before
+ the new one, with change the condition of the data so that this new rule will never be eligible. Developing a complete
+ set of unit test is an efficient way to see this problem, and to improve the rule set design. Some powerful BRMS
+ platform has rules consistency checking which helps to do some static analysis of those potential conflict by analyzing
+ the conditions and the actions of the rules. For sure real test cases will complete the picture.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<span
+style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Using
+a Test Driven Development approach rule writer can develop the test script preparing the data to trigger each rule,
+depending of the BRMS platform used, the script generation can be done automatically or not. What is important is develop
+reusable test case organized in test suite which include assertion statement to validate the expected results. This is
+efficient tool to put in place automatic non regression tests.</span></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ch1YD3W6ZaDbDWdgfmcFbw" name="develop_rules,_VTsQIH_CEd2YWI_0AZcMOA" guid="-ch1YD3W6ZaDbDWdgfmcFbw">
+ <refinedDescription><a id="XE_rule__develop" name="XE_rule__develop"></a>
+<p>
+ Programming using rule approach enforces to know how a rule engine is working. This is not a complex skill, rue author
+ needs to understand&nbsp; the concepts of asserting, retracting object into working memory and modifying them. It is
+ recommended to read what a <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_engine_A66B71B3.html"
+ guid="_QQcSoEXXEdy14e5PT9v3HQ">Rule engine</a>&nbsp;is to get those concepts.
+</p>
+<p>
+ Rule development can follow a test driven development approach: the developer can develop the test cases to trigger the
+ rule execution and then write the rules. Once done the new rules are extracted with the other rules in the rule set,
+ deployed to the unit test environment and the test executes. When designing with interface the unit test uses the
+ facade to access the rule engine for&nbsp;the execution.
+</p>
+<p>
+ When rules are complex and include a lot of conditions it may make sense to add condition by steps. It may be easy to
+ make error by using a wrong boolean operator. When the rue language support navigating into collection the testing may
+ include test around the presence and not presence of element in the collection.
+</p>
+<p>
+ It is always interesting once the rule is developed to perform rule analysis if the BRMS product has this capability.
+ The analysis helps to see if the current rule is in conflict with existing rules.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-bNDT40_Dob9KbffUI6mIJA" name="ruleset,_VTsQIn_CEd2YWI_0AZcMOA" guid="-bNDT40_Dob9KbffUI6mIJA">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-cNLxGN0Xk1GRudfSGVb8ig" name="enhance_object_models,_WyUKQH_CEd2YWI_0AZcMOA" guid="-cNLxGN0Xk1GRudfSGVb8ig">
+ <refinedDescription>Typically the developer adds helper methods in the data model to facilitate the rule writing. Develop utility classes. The
+data elements should not have persistence logic in it. For example in Java do not put JDBC code in the Customer object. Let
+try to stick to the Java bean specification for all the&nbsp;business objects, and leverage a service layer, with service
+facades objects to help gathering and process data.&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-g7yvSbhyKtzLJkvnHGyvKA" name="execute_rule_set,_XDv4gH_CEd2YWI_0AZcMOA" guid="-g7yvSbhyKtzLJkvnHGyvKA">
+ <refinedDescription><a id="XE_rule_set__execute" name="XE_rule_set__execute"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-KokWTSqEp1OW6qZiJx7Fnw" name="log_issue,_XR5pQH_CEd2YWI_0AZcMOA" guid="-KokWTSqEp1OW6qZiJx7Fnw">
+ <refinedDescription><ul>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Formally log any issues and decisions done during the rule
+ analysis and the rule authoring activities.</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The issue
+ log is used to manage feedbacks, and to improve the rule set quality.</span></span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-weight: bold">As a social process, people will
+ change their mind, it is a good practice to log decision on a timely manner.</span>
+ </div>
+ </li>
+</ul><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/author_business_rules/model.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/author_business_rules/model.xmi
index b449c10..9884a6f 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/author_business_rules/model.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/author_business_rules/model.xmi
@@ -2,12 +2,20 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__ZPd0bekEd-D7YZN9NgldQ" guid="__ZPd0bekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__ZPd0rekEd-D7YZN9NgldQ" id="-TUyCFXMljyPPGFQbnWy_Zw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_HSEXAFmSEeCcpdiAcH0w-w" id="-aoZNCrSMHCobCqrNM4Z5JA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_HSOIAFmSEeCcpdiAcH0w-w" id="-ch1YD3W6ZaDbDWdgfmcFbw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_HSOIAVmSEeCcpdiAcH0w-w" id="-bNDT40_Dob9KbffUI6mIJA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_HSXR8FmSEeCcpdiAcH0w-w" id="-cNLxGN0Xk1GRudfSGVb8ig" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_HSXR8VmSEeCcpdiAcH0w-w" id="-g7yvSbhyKtzLJkvnHGyvKA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_HSXR8lmSEeCcpdiAcH0w-w" id="-KokWTSqEp1OW6qZiJx7Fnw" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_OQxnAH_CEd2YWI_0AZcMOA" name="author_business_rules" guid="_OQxnAH_CEd2YWI_0AZcMOA">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_VsH-QH_CEd2YWI_0AZcMOA" name="develop_unit_tests" guid="_VsH-QH_CEd2YWI_0AZcMOA" presentationName="Develop Rule Unit Tests" superActivities="_OQxnAX_CEd2YWI_0AZcMOA" isSynchronizedWithSource="false" performedPrimarilyBy="_VsRvQH_CEd2YWI_0AZcMOA _VTsQIX_CEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_VsH-QH_CEd2YWI_0AZcMOA" name="develop_unit_tests" guid="_VsH-QH_CEd2YWI_0AZcMOA" presentationName="Develop Rule Unit Tests" briefDescription="The goal of this task is to track down anomalies in the rules such as conflicts, redundancies or overlaps.
" superActivities="_OQxnAX_CEd2YWI_0AZcMOA" isSynchronizedWithSource="false">
+ <presentation xmi:id="-aoZNCrSMHCobCqrNM4Z5JA" href="uma://-TUyCFXMljyPPGFQbnWy_Zw#-aoZNCrSMHCobCqrNM4Z5JA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ioCPkDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_VTsQIH_CEd2YWI_0AZcMOA" name="develop_rules" guid="_VTsQIH_CEd2YWI_0AZcMOA" presentationName="Develop Rules" superActivities="_OQxnAX_CEd2YWI_0AZcMOA" output="_VTsQIn_CEd2YWI_0AZcMOA" performedPrimarilyBy="_VTsQIX_CEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_VTsQIH_CEd2YWI_0AZcMOA" name="develop_rules" guid="_VTsQIH_CEd2YWI_0AZcMOA" presentationName="Develop Rules" briefDescription="This task is about developing each rule in the rule project." superActivities="_OQxnAX_CEd2YWI_0AZcMOA" output="_VTsQIn_CEd2YWI_0AZcMOA">
+ <presentation xmi:id="-ch1YD3W6ZaDbDWdgfmcFbw" href="uma://-TUyCFXMljyPPGFQbnWy_Zw#-ch1YD3W6ZaDbDWdgfmcFbw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Y2CxEDzEEdyA6a_I80swHw"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_bsPp8ErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_qfzk4ErtEdyEE-k1R6LmOA"/>
@@ -15,25 +23,24 @@
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_zAvrMErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_GvK9oEruEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_VTsQIX_CEd2YWI_0AZcMOA" name="rule_writer" guid="_VTsQIX_CEd2YWI_0AZcMOA" presentationName="Rule Writer" isPlanned="false" superActivities="_OQxnAX_CEd2YWI_0AZcMOA" modifies="_VTsQIn_CEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_VTsQIn_CEd2YWI_0AZcMOA" name="ruleset" guid="_VTsQIn_CEd2YWI_0AZcMOA" presentationName="Rule Set" isPlanned="false" superActivities="_OQxnAX_CEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_VTsQIn_CEd2YWI_0AZcMOA" name="ruleset" guid="_VTsQIn_CEd2YWI_0AZcMOA" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_OQxnAX_CEd2YWI_0AZcMOA">
+ <presentation xmi:id="-bNDT40_Dob9KbffUI6mIJA" href="uma://-TUyCFXMljyPPGFQbnWy_Zw#-bNDT40_Dob9KbffUI6mIJA"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_VsRvQH_CEd2YWI_0AZcMOA" name="developer" guid="_VsRvQH_CEd2YWI_0AZcMOA" presentationName="Developer" isPlanned="false" superActivities="_OQxnAX_CEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_WyUKQH_CEd2YWI_0AZcMOA" name="enhance_object_models" guid="_WyUKQH_CEd2YWI_0AZcMOA" presentationName="Enhance Object Models" superActivities="_OQxnAX_CEd2YWI_0AZcMOA" performedPrimarilyBy="_VsRvQH_CEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_WyUKQH_CEd2YWI_0AZcMOA" name="enhance_object_models" guid="_WyUKQH_CEd2YWI_0AZcMOA" presentationName="Enhance Object Models" briefDescription="The data model is started during the analysis and design tasks. But it will involve over time. So this activity supports the enhancement of the object models." superActivities="_OQxnAX_CEd2YWI_0AZcMOA">
+ <presentation xmi:id="-cNLxGN0Xk1GRudfSGVb8ig" href="uma://-TUyCFXMljyPPGFQbnWy_Zw#-cNLxGN0Xk1GRudfSGVb8ig"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_UXrv8Eb3EdySHMdInS9eGA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_XDv4gH_CEd2YWI_0AZcMOA" name="execute_rule_set" guid="_XDv4gH_CEd2YWI_0AZcMOA" presentationName="Execute Rule Set" superActivities="_OQxnAX_CEd2YWI_0AZcMOA" output="_VTsQIn_CEd2YWI_0AZcMOA" performedPrimarilyBy="_VTsQIX_CEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_XDv4gH_CEd2YWI_0AZcMOA" name="execute_rule_set" guid="_XDv4gH_CEd2YWI_0AZcMOA" presentationName="Execute Rule Set" briefDescription="Execute the tests to trigger the rule execution. Analyze the output logs. Report issues." superActivities="_OQxnAX_CEd2YWI_0AZcMOA" output="_VTsQIn_CEd2YWI_0AZcMOA">
+ <presentation xmi:id="-g7yvSbhyKtzLJkvnHGyvKA" href="uma://-TUyCFXMljyPPGFQbnWy_Zw#-g7yvSbhyKtzLJkvnHGyvKA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_JCHfMEXhEdy14e5PT9v3HQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_XR5pQH_CEd2YWI_0AZcMOA" name="log_issue" guid="_XR5pQH_CEd2YWI_0AZcMOA" presentationName="Log Issue" superActivities="_OQxnAX_CEd2YWI_0AZcMOA" isSynchronizedWithSource="false" performedPrimarilyBy="_VTsQIX_CEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_XR5pQH_CEd2YWI_0AZcMOA" name="log_issue" guid="_XR5pQH_CEd2YWI_0AZcMOA" presentationName="Log Issue" superActivities="_OQxnAX_CEd2YWI_0AZcMOA" isSynchronizedWithSource="false">
+ <presentation xmi:id="-KokWTSqEp1OW6qZiJx7Fnw" href="uma://-TUyCFXMljyPPGFQbnWy_Zw#-KokWTSqEp1OW6qZiJx7Fnw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yGbYIEb0EdySHMdInS9eGA"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_OQxnAX_CEd2YWI_0AZcMOA" name="author_business_rules" guid="_OQxnAX_CEd2YWI_0AZcMOA" presentationName="Author Business Rules" breakdownElements="_VsH-QH_CEd2YWI_0AZcMOA _VTsQIH_CEd2YWI_0AZcMOA _VTsQIX_CEd2YWI_0AZcMOA _VTsQIn_CEd2YWI_0AZcMOA _VsRvQH_CEd2YWI_0AZcMOA _WyUKQH_CEd2YWI_0AZcMOA _XDv4gH_CEd2YWI_0AZcMOA _XR5pQH_CEd2YWI_0AZcMOA">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_OQxnAX_CEd2YWI_0AZcMOA" name="author_business_rules" guid="_OQxnAX_CEd2YWI_0AZcMOA" presentationName="Author Business Rules" breakdownElements="_VsH-QH_CEd2YWI_0AZcMOA _VTsQIH_CEd2YWI_0AZcMOA _VTsQIn_CEd2YWI_0AZcMOA _WyUKQH_CEd2YWI_0AZcMOA _XDv4gH_CEd2YWI_0AZcMOA _XR5pQH_CEd2YWI_0AZcMOA">
<presentation xmi:id="-TUyCFXMljyPPGFQbnWy_Zw" href="uma://-TUyCFXMljyPPGFQbnWy_Zw#-TUyCFXMljyPPGFQbnWy_Zw"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/define_rule_governance/content.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/define_rule_governance/content.xmi
index 064a5ed..3ddc690 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/define_rule_governance/content.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/define_rule_governance/content.xmi
@@ -1,2 +1,279 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-Cr6J3-t_GtgvW9ciCDH6Gg" name="governance,_2o6S8X_DEd2YWI_0AZcMOA" guid="-Cr6J3-t_GtgvW9ciCDH6Gg" version="7.5.1"/>
+<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="-Cr6J3-t_GtgvW9ciCDH6Gg" name="governance,_2o6S8X_DEd2YWI_0AZcMOA" guid="-Cr6J3-t_GtgvW9ciCDH6Gg" version="7.5.1"/>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-fCDaucRMlxkKAL8a24-bxw" name="define_rule_life_cycle,_4hT_BH_DEd2YWI_0AZcMOA" guid="-fCDaucRMlxkKAL8a24-bxw">
+ <refinedDescription><a id="XE_life_cycle__define" name="XE_life_cycle__define"></a>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A rule architect has to develop with the business
+ users what will be the <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_life_cycle_B982650C.html"
+ guid="_s5iCsFH7Edy72tV0zV7--Q">rule life cycle</a>. There are a lot of different possibilities for defining this rule
+ life cycle. For the implementation point of view we need to define a</span> <span lang="EN"
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial; mso-ansi-language: EN">"Status" meta property attached
+ to a rule element.</span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">The following states
+ have been identified as a simple but still efficient life cycle:</span>
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">New</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule is created, and can be modified by its
+ owner</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Defined</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule has been defined and is currently in unit
+ test</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Rejected</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule has been tested un-successfully</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Validated</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule has been tested successfully and can be
+ deployed</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Promoted</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule has been part of a rule set deployed on
+ production platform</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Retired</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule was deployed or validated on a production
+ platform but no more active.</span>
+</p><br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In the state diagram below the following abbreviations are used:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Rule Writer or Rule Author is the end user of the BRMS application
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Rule Admin is an administrator of the rule set.
+ </li>
+ <li class="MsoNormal"
+ style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt; mso-pagination: none; mso-layout-grid-align: none">
+ Rule Tester can be an automatic process or a human.
+ </li>
+</ul>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt; mso-pagination: none; mso-layout-grid-align: none">
+ <img height="382" alt="" src="resources/rule_life_cycle.gif" width="409" />
+</p><br class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt; mso-pagination: none; mso-layout-grid-align: none" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-JrwmZx8H_aWdkygsowd4sw" name="define_ruleset_life_cycle,_4hT_BX_DEd2YWI_0AZcMOA" guid="-JrwmZx8H_aWdkygsowd4sw">
+ <refinedDescription><a id="XE_rule_set__define_life_cycle" name="XE_rule_set__define_life_cycle"></a>
+<p>
+ As it was done for the rule life cycle, it may be needed to complete the rule governance by defining a rule set life
+ cycle.&nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-O8-5z_vtgPCdeufHqvVOvw" name="brms_organization_chart,_4hT_DH_DEd2YWI_0AZcMOA" guid="-O8-5z_vtgPCdeufHqvVOvw">
+ <refinedDescription><a id="XE_BRMS__organization_chart" name="XE_BRMS__organization_chart"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-etBOp7Nf8DJQ9VQ3IITl6w" name="rule_governance_actors,_4hT_DX_DEd2YWI_0AZcMOA" guid="-etBOp7Nf8DJQ9VQ3IITl6w">
+ <refinedDescription><a id="XE_rule_governance__actors" name="XE_rule_governance__actors"></a>
+<p>
+ The easiest way is to lists the different actors involved in the governance processes within a table format.
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-table-layout-alt: fixed; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 67.5pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="90">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font
+ face="Times New Roman">Role</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 62.2pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="83">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font
+ face="Times New Roman">Unit</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 230.3pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="307">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font
+ face="Times New Roman">Role-Responsibilities</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 153pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="204">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font
+ face="Times New Roman">Skill</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0; mso-yfti-lastrow: yes">
+ <td
+ style="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: 67.5pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="90">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 62.2pt; 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"
+ valign="top" width="83">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span style="FONT-SIZE: 8pt">Business unit</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 230.3pt; 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"
+ valign="top" width="307">
+ <br class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt; mso-add-space: auto; mso-list: l0 level1 lfo1; tab-stops: list 18.0pt" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 153pt; 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"
+ valign="top" width="204">
+ <br class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt; mso-add-space: auto; mso-list: l0 level1 lfo1; tab-stops: list 18.0pt" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-F1m9WCyarSsTUt8OeW0FLQ" name="rule_life_cycle,_4hT_Dn_DEd2YWI_0AZcMOA" guid="-F1m9WCyarSsTUt8OeW0FLQ">
+ <refinedDescription><a id="XE_rule__life_cycle" name="XE_rule__life_cycle"></a>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; tab-stops: list 27.0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">In the state diagram below the following
+ abbreviations are used:</span>
+</p><br class="MsoNormal" style="MARGIN: 0in 0in 0pt; tab-stops: list 27.0pt" />
+<br />
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Rule
+ Writer or Rule Author is the end user of the BRMS application</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Rule
+ Admin is an administrator of the rule set.</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Rule
+ Tester can be an automatic process or a human.</span>
+</p><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none" />
+<br />
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><img alt=""
+ src="resources/rule_life_cycle.gif" /></span>
+</p><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none" />
+<br />
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><span lang="EN"
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial; mso-ansi-language: EN">Some complementary
+ guidelines:</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<br />
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 27pt; TEXT-INDENT: -27pt; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">When a
+ rule is created its status is new</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 27pt; TEXT-INDENT: -27pt; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A rule
+ once promoted could not be deleted.</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 27pt; TEXT-INDENT: -27pt; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A rule
+ can be set active or inactive at any state, by using the inactive property</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 27pt; TEXT-INDENT: -27pt; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">From
+ this life cycle it is important to note that once a rule is promoted the user could not update it. He needs to create a
+ new rule by copy and paste and restart the life cycle up to Validated. Once the rule is ready for deployment a rule
+ administrator will retired the first rule and promote the new one. This is important to follow this process to maintain
+ the integrity of the rule set.</span>
+</p><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<p class="ISISGuidance" style="MARGIN: 0in 0in 0pt">
+ <span style="COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: Arial">There is a common requirement that may need to
+ be supported to enhance the rule life cycle: "During its life cycle a rule can be deployed only to a specific Test
+ Decision Service, before going to production".</span>
+</p><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-hOw_lv8PvVPmcYRZ2Q7nmw" name="ruleset,_4hT_D3_DEd2YWI_0AZcMOA" guid="-hOw_lv8PvVPmcYRZ2Q7nmw">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-KKBOWURFUivD1HVYiy959Q" name="rule_repository_in_db,_4hT_EH_DEd2YWI_0AZcMOA" guid="-KKBOWURFUivD1HVYiy959Q">
+ <refinedDescription><a id="XE_rule_repository__in_db" name="XE_rule_repository__in_db"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/define_rule_governance/model.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/define_rule_governance/model.xmi
index 91ff7f0..71c4ee3 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/define_rule_governance/model.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/define_rule_governance/model.xmi
@@ -2,30 +2,41 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__ZiYwLekEd-D7YZN9NgldQ" guid="__ZiYwLekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__ZiYwbekEd-D7YZN9NgldQ" id="-Cr6J3-t_GtgvW9ciCDH6Gg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WwGLQVmSEeCcpdiAcH0w-w" id="-fCDaucRMlxkKAL8a24-bxw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WwGLQlmSEeCcpdiAcH0w-w" id="-JrwmZx8H_aWdkygsowd4sw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WwGLQ1mSEeCcpdiAcH0w-w" id="-O8-5z_vtgPCdeufHqvVOvw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WwGLRFmSEeCcpdiAcH0w-w" id="-etBOp7Nf8DJQ9VQ3IITl6w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WwP8QFmSEeCcpdiAcH0w-w" id="-F1m9WCyarSsTUt8OeW0FLQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WwP8QVmSEeCcpdiAcH0w-w" id="-hOw_lv8PvVPmcYRZ2Q7nmw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WwP8QlmSEeCcpdiAcH0w-w" id="-KKBOWURFUivD1HVYiy959Q" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_2o6S8H_DEd2YWI_0AZcMOA" name="define_rule_governance" guid="_2o6S8H_DEd2YWI_0AZcMOA">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_8vcLgKvlEd2Pv_z50upsAg" name="develop_organization_map" guid="_8vcLgKvlEd2Pv_z50upsAg" presentationName="Develop Organization Map" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" additionallyPerformedBy="_4hT_B3_DEd2YWI_0AZcMOA" output="_4hT_DH_DEd2YWI_0AZcMOA _4hT_DX_DEd2YWI_0AZcMOA" performedPrimarilyBy="_GvZGIKvpEd2Pv_z50upsAg">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_8vcLgKvlEd2Pv_z50upsAg" name="develop_organization_map" guid="_8vcLgKvlEd2Pv_z50upsAg" presentationName="Develop Organization Map" briefDescription="The first task in rule governance consists in understanding the enterprise's organizational structure to help in defining the adequate rule governance actors and the Rule Management Team." superActivities="_2o6S8X_DEd2YWI_0AZcMOA" output="_4hT_DH_DEd2YWI_0AZcMOA _4hT_DX_DEd2YWI_0AZcMOA">
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_fCRxoGDmEdyKlZvvtnMrMg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_npFyQGDtEdyKlZvvtnMrMg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_IFeJQKveEd2Pv_z50upsAg"/>
<selectedSteps href="uma://-AnRIdz0rPYyQVyzGVBxSqA#__8xccKvgEd2Pv_z50upsAg"/>
<selectedSteps href="uma://-AnRIdz0rPYyQVyzGVBxSqA#_MJLScKviEd2Pv_z50upsAg"/>
<selectedSteps href="uma://-AnRIdz0rPYyQVyzGVBxSqA#_U7ZWAKviEd2Pv_z50upsAg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_1AufcKv9Ed2Pv_z50upsAg" name="define_ruleset_ownership" guid="_1AufcKv9Ed2Pv_z50upsAg" presentationName="Define Rule Set Ownership and Access Control" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" additionallyPerformedBy="_GvZGIKvpEd2Pv_z50upsAg" performedPrimarilyBy="_4hT_B3_DEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_1AufcKv9Ed2Pv_z50upsAg" name="define_ruleset_ownership" guid="_1AufcKv9Ed2Pv_z50upsAg" presentationName="Define Rule Set Ownership and Access Control" briefDescription="For each rule set it has to be defined one owner and access control for team members and others. " superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_O93X4KvzEd2Pv_z50upsAg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_c83oYKv-Ed2Pv_z50upsAg" name="define_policy_change_templates" guid="_c83oYKv-Ed2Pv_z50upsAg" presentationName="Define Business Policy Change Templates" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" additionallyPerformedBy="_d6VEMKzEEd2aLdlF48Bk1g" performedPrimarilyBy="_4hT_CX_DEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_c83oYKv-Ed2Pv_z50upsAg" name="define_policy_change_templates" guid="_c83oYKv-Ed2Pv_z50upsAg" presentationName="Define Business Policy Change Templates" briefDescription="Define an inventory of probable ways in which the policies may or will change and with which frequency." superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_tzUvgKv7Ed2Pv_z50upsAg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_4hT_BH_DEd2YWI_0AZcMOA" name="define_rule_life_cycle" guid="_4hT_BH_DEd2YWI_0AZcMOA" presentationName="Define Rule Life Cycle" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" output="_4hT_Dn_DEd2YWI_0AZcMOA" performedPrimarilyBy="_4hT_B3_DEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_4hT_BH_DEd2YWI_0AZcMOA" name="define_rule_life_cycle" guid="_4hT_BH_DEd2YWI_0AZcMOA" presentationName="Define Rule Life Cycle" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" output="_4hT_Dn_DEd2YWI_0AZcMOA">
+ <presentation xmi:id="-fCDaucRMlxkKAL8a24-bxw" href="uma://-Cr6J3-t_GtgvW9ciCDH6Gg#-fCDaucRMlxkKAL8a24-bxw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_RBu1YFH7Edy72tV0zV7--Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_4hT_BX_DEd2YWI_0AZcMOA" name="define_ruleset_life_cycle" guid="_4hT_BX_DEd2YWI_0AZcMOA" presentationName="Define Rule Set Life Cycle " superActivities="_2o6S8X_DEd2YWI_0AZcMOA" additionallyPerformedBy="_4hT_CH_DEd2YWI_0AZcMOA" performedPrimarilyBy="_4hT_B3_DEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_4hT_BX_DEd2YWI_0AZcMOA" name="define_ruleset_life_cycle" guid="_4hT_BX_DEd2YWI_0AZcMOA" presentationName="Define Rule Set Life Cycle " superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
+ <presentation xmi:id="-JrwmZx8H_aWdkygsowd4sw" href="uma://-Cr6J3-t_GtgvW9ciCDH6Gg#-JrwmZx8H_aWdkygsowd4sw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_RBu1YVH7Edy72tV0zV7--Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_wGoukKv-Ed2Pv_z50upsAg" name="plan_deployment" guid="_wGoukKv-Ed2Pv_z50upsAg" presentationName="Plan Deployment" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" performedPrimarilyBy="_4hT_B3_DEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_wGoukKv-Ed2Pv_z50upsAg" name="plan_deployment" guid="_wGoukKv-Ed2Pv_z50upsAg" presentationName="Plan Deployment" briefDescription="Plan deployment procedures for the different platforms: testing, staging and production. Also plan for production monitoring. " superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_E5968Kv8Ed2Pv_z50upsAg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_49L4gKv-Ed2Pv_z50upsAg" name="develop_process_maps" guid="_49L4gKv-Ed2Pv_z50upsAg" presentationName="Develop Process Maps" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" additionallyPerformedBy="_4hT_B3_DEd2YWI_0AZcMOA" performedPrimarilyBy="_GvZGIKvpEd2Pv_z50upsAg">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_49L4gKv-Ed2Pv_z50upsAg" name="develop_process_maps" guid="_49L4gKv-Ed2Pv_z50upsAg" presentationName="Develop Process Maps" briefDescription="For each of the rule development and management processes, the architect should develop a process map to be followed during rule governance." superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_deyUkKv8Ed2Pv_z50upsAg"/>
<selectedSteps href="uma://-aim_xTKZyZptD_PbMWAtVA#_9jqRIKy-Ed2aLdlF48Bk1g"/>
<selectedSteps href="uma://-aim_xTKZyZptD_PbMWAtVA#_K4JmAKy_Ed2aLdlF48Bk1g"/>
@@ -34,49 +45,35 @@
<selectedSteps href="uma://-aim_xTKZyZptD_PbMWAtVA#_rMlWsKy_Ed2aLdlF48Bk1g"/>
<selectedSteps href="uma://-aim_xTKZyZptD_PbMWAtVA#__pNL4Ky_Ed2aLdlF48Bk1g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_b0uJ8KzBEd2aLdlF48Bk1g" name="monitor_improve_process" guid="_b0uJ8KzBEd2aLdlF48Bk1g" presentationName="Monitor and Improve Process" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" additionallyPerformedBy="_4hT_B3_DEd2YWI_0AZcMOA" performedPrimarilyBy="_GvZGIKvpEd2Pv_z50upsAg">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_b0uJ8KzBEd2aLdlF48Bk1g" name="monitor_improve_process" guid="_b0uJ8KzBEd2aLdlF48Bk1g" presentationName="Monitor and Improve Process" briefDescription="Rule governance process should be monitored and improved to achieve better efficiency." superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_w0x40KzAEd2aLdlF48Bk1g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_4hT_Bn_DEd2YWI_0AZcMOA" name="maintain_rules" guid="_4hT_Bn_DEd2YWI_0AZcMOA" presentationName="Maintain Rules" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" additionallyPerformedBy="_4hT_C3_DEd2YWI_0AZcMOA" mandatoryInput="_4hT_D3_DEd2YWI_0AZcMOA _4hT_EH_DEd2YWI_0AZcMOA" output="_4hT_D3_DEd2YWI_0AZcMOA _4hT_EH_DEd2YWI_0AZcMOA" performedPrimarilyBy="_4hT_CX_DEd2YWI_0AZcMOA _4hT_Cn_DEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_4hT_Bn_DEd2YWI_0AZcMOA" name="maintain_rules" guid="_4hT_Bn_DEd2YWI_0AZcMOA" presentationName="Maintain Rules" briefDescription="The goal of this task is to maintain the rules in order to correct faults or improve performance." superActivities="_2o6S8X_DEd2YWI_0AZcMOA" mandatoryInput="_4hT_D3_DEd2YWI_0AZcMOA _4hT_EH_DEd2YWI_0AZcMOA" output="_4hT_D3_DEd2YWI_0AZcMOA _4hT_EH_DEd2YWI_0AZcMOA">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_z9ORcKnrEdyzmOHu2kw1UA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_GvZGIKvpEd2Pv_z50upsAg" name="rule_steward" guid="_GvZGIKvpEd2Pv_z50upsAg" presentationName="Rule Steward" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" modifies="_4hT_DH_DEd2YWI_0AZcMOA _4hT_DX_DEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_bYUkIJyiEd23W8_-Tub7Ww"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_4hT_B3_DEd2YWI_0AZcMOA" name="rule_architect" guid="_4hT_B3_DEd2YWI_0AZcMOA" presentationName="Rule Architect" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" modifies="_4hT_Dn_DEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_4hT_CH_DEd2YWI_0AZcMOA" name="rule_administrator" guid="_4hT_CH_DEd2YWI_0AZcMOA" presentationName="Rule Administrator" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4QqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_4hT_CX_DEd2YWI_0AZcMOA" name="rule_analyst" guid="_4hT_CX_DEd2YWI_0AZcMOA" presentationName="Rule Analyst" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" modifies="_4hT_D3_DEd2YWI_0AZcMOA _4hT_EH_DEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_4hT_Cn_DEd2YWI_0AZcMOA" name="rule_writer" guid="_4hT_Cn_DEd2YWI_0AZcMOA" presentationName="Rule Writer" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA" modifies="_4hT_D3_DEd2YWI_0AZcMOA _4hT_EH_DEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_4hT_C3_DEd2YWI_0AZcMOA" name="business_analyst" guid="_4hT_C3_DEd2YWI_0AZcMOA" presentationName="Business Analyst" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_d6VEMKzEEd2aLdlF48Bk1g" name="Subject Matter Expert" guid="_d6VEMKzEEd2aLdlF48Bk1g" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4hT_DH_DEd2YWI_0AZcMOA" name="brms_organization_chart" guid="_4hT_DH_DEd2YWI_0AZcMOA" presentationName="Organization Chart" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
+ <presentation xmi:id="-O8-5z_vtgPCdeufHqvVOvw" href="uma://-Cr6J3-t_GtgvW9ciCDH6Gg#-O8-5z_vtgPCdeufHqvVOvw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#__hcZYGDrEdyKlZvvtnMrMg"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4hT_DX_DEd2YWI_0AZcMOA" name="rule_governance_actors" guid="_4hT_DX_DEd2YWI_0AZcMOA" presentationName="Rule Governance Actors" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
+ <presentation xmi:id="-etBOp7Nf8DJQ9VQ3IITl6w" href="uma://-Cr6J3-t_GtgvW9ciCDH6Gg#-etBOp7Nf8DJQ9VQ3IITl6w"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_npFyQGDtEdyKlZvvtnMrMg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_VzXG0GDtEdyKlZvvtnMrMg"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4hT_Dn_DEd2YWI_0AZcMOA" name="rule_life_cycle" guid="_4hT_Dn_DEd2YWI_0AZcMOA" presentationName="Rule Life Cycle" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
+ <presentation xmi:id="-F1m9WCyarSsTUt8OeW0FLQ" href="uma://-Cr6J3-t_GtgvW9ciCDH6Gg#-F1m9WCyarSsTUt8OeW0FLQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_DmUjsFH8Edy72tV0zV7--Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4hT_D3_DEd2YWI_0AZcMOA" name="ruleset" guid="_4hT_D3_DEd2YWI_0AZcMOA" presentationName="Rule Set" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4hT_D3_DEd2YWI_0AZcMOA" name="ruleset" guid="_4hT_D3_DEd2YWI_0AZcMOA" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
+ <presentation xmi:id="-hOw_lv8PvVPmcYRZ2Q7nmw" href="uma://-Cr6J3-t_GtgvW9ciCDH6Gg#-hOw_lv8PvVPmcYRZ2Q7nmw"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4hT_EH_DEd2YWI_0AZcMOA" name="rule_repository_in_db" guid="_4hT_EH_DEd2YWI_0AZcMOA" presentationName="Rule Repository in DB" isPlanned="false" superActivities="_2o6S8X_DEd2YWI_0AZcMOA">
+ <presentation xmi:id="-KKBOWURFUivD1HVYiy959Q" href="uma://-Cr6J3-t_GtgvW9ciCDH6Gg#-KKBOWURFUivD1HVYiy959Q"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_jqxtYFttEdykEsBjRsVfZw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_2o6S8X_DEd2YWI_0AZcMOA" name="define_rule_governance" guid="_2o6S8X_DEd2YWI_0AZcMOA" presentationName="Define Rule Governance" breakdownElements="_8vcLgKvlEd2Pv_z50upsAg _1AufcKv9Ed2Pv_z50upsAg _c83oYKv-Ed2Pv_z50upsAg _4hT_BH_DEd2YWI_0AZcMOA _4hT_BX_DEd2YWI_0AZcMOA _wGoukKv-Ed2Pv_z50upsAg _49L4gKv-Ed2Pv_z50upsAg _b0uJ8KzBEd2aLdlF48Bk1g _4hT_Bn_DEd2YWI_0AZcMOA _GvZGIKvpEd2Pv_z50upsAg _4hT_B3_DEd2YWI_0AZcMOA _4hT_CH_DEd2YWI_0AZcMOA _4hT_CX_DEd2YWI_0AZcMOA _4hT_Cn_DEd2YWI_0AZcMOA _4hT_C3_DEd2YWI_0AZcMOA _d6VEMKzEEd2aLdlF48Bk1g _4hT_DH_DEd2YWI_0AZcMOA _4hT_DX_DEd2YWI_0AZcMOA _4hT_Dn_DEd2YWI_0AZcMOA _4hT_D3_DEd2YWI_0AZcMOA _4hT_EH_DEd2YWI_0AZcMOA">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_2o6S8X_DEd2YWI_0AZcMOA" name="define_rule_governance" guid="_2o6S8X_DEd2YWI_0AZcMOA" presentationName="Define Rule Governance" breakdownElements="_8vcLgKvlEd2Pv_z50upsAg _1AufcKv9Ed2Pv_z50upsAg _c83oYKv-Ed2Pv_z50upsAg _4hT_BH_DEd2YWI_0AZcMOA _4hT_BX_DEd2YWI_0AZcMOA _wGoukKv-Ed2Pv_z50upsAg _49L4gKv-Ed2Pv_z50upsAg _b0uJ8KzBEd2aLdlF48Bk1g _4hT_Bn_DEd2YWI_0AZcMOA _4hT_DH_DEd2YWI_0AZcMOA _4hT_DX_DEd2YWI_0AZcMOA _4hT_Dn_DEd2YWI_0AZcMOA _4hT_D3_DEd2YWI_0AZcMOA _4hT_EH_DEd2YWI_0AZcMOA">
<presentation xmi:id="-Cr6J3-t_GtgvW9ciCDH6Gg" href="uma://-Cr6J3-t_GtgvW9ciCDH6Gg#-Cr6J3-t_GtgvW9ciCDH6Gg"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/deploy_business_rules/content.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/deploy_business_rules/content.xmi
index 7752373..708f5a5 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/deploy_business_rules/content.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/deploy_business_rules/content.xmi
@@ -1,2 +1,21 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-bUpJuAJ9G1gNUYahDjpPSw" name="deployment,_d9Oe8X9YEd26h9j0X6pKmw" guid="-bUpJuAJ9G1gNUYahDjpPSw" version="7.5.1"/>
+<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="-bUpJuAJ9G1gNUYahDjpPSw" name="deployment,_d9Oe8X9YEd26h9j0X6pKmw" guid="-bUpJuAJ9G1gNUYahDjpPSw" version="7.5.1"/>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ES65eVL1z5Jdpq38iB099w" name="deploy_rules,_fKYOkH9YEd26h9j0X6pKmw" guid="-ES65eVL1z5Jdpq38iB099w">
+ <refinedDescription><a id="XE_rule__deploy" name="XE_rule__deploy"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-4mHTAj_-HqRpSZirDsCVSQ" name="ruleset,_fKYOkX9YEd26h9j0X6pKmw" guid="-4mHTAj_-HqRpSZirDsCVSQ">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-RlDD3QrzC4Q6jEgiidJMmg" name="synchronize_with_wrms,_fcstoH9YEd26h9j0X6pKmw" guid="-RlDD3QrzC4Q6jEgiidJMmg">
+ <refinedDescription><a id="XE_web-based_brms__synchronize" name="XE_web-based_brms__synchronize"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-MzmademiTOM2WTRZYUndBg" name="rule_repository_in_db,_fc2eoH9YEd26h9j0X6pKmw" guid="-MzmademiTOM2WTRZYUndBg">
+ <refinedDescription><a id="XE_rule_repository__in_db" name="XE_rule_repository__in_db"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/deploy_business_rules/model.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/deploy_business_rules/model.xmi
index 3a447da..4095191 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/deploy_business_rules/model.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/deploy_business_rules/model.xmi
@@ -2,27 +2,30 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__ZiYw7ekEd-D7YZN9NgldQ" guid="__ZiYw7ekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__ZiYxLekEd-D7YZN9NgldQ" id="-bUpJuAJ9G1gNUYahDjpPSw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Zf71oVmSEeCcpdiAcH0w-w" id="-ES65eVL1z5Jdpq38iB099w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Zf71olmSEeCcpdiAcH0w-w" id="-4mHTAj_-HqRpSZirDsCVSQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_ZgFmoFmSEeCcpdiAcH0w-w" id="-RlDD3QrzC4Q6jEgiidJMmg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_ZgFmoVmSEeCcpdiAcH0w-w" id="-MzmademiTOM2WTRZYUndBg" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_d9Oe8H9YEd26h9j0X6pKmw" name="deploy_business_rules" guid="_d9Oe8H9YEd26h9j0X6pKmw">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_fKYOkH9YEd26h9j0X6pKmw" name="deploy_rules" guid="_fKYOkH9YEd26h9j0X6pKmw" presentationName="Deploy Rules" superActivities="_d9Oe8X9YEd26h9j0X6pKmw" mandatoryInput="_fKYOkX9YEd26h9j0X6pKmw" output="_fKYOkX9YEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_fKYOkH9YEd26h9j0X6pKmw" name="deploy_rules" guid="_fKYOkH9YEd26h9j0X6pKmw" presentationName="Deploy Rules" briefDescription="Deploy rule set in the integrated core application" superActivities="_d9Oe8X9YEd26h9j0X6pKmw" mandatoryInput="_fKYOkX9YEd26h9j0X6pKmw" output="_fKYOkX9YEd26h9j0X6pKmw">
+ <presentation xmi:id="-ES65eVL1z5Jdpq38iB099w" href="uma://-bUpJuAJ9G1gNUYahDjpPSw#-ES65eVL1z5Jdpq38iB099w"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_AgQVAD5QEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_fKYOkX9YEd26h9j0X6pKmw" name="ruleset" guid="_fKYOkX9YEd26h9j0X6pKmw" presentationName="Rule Set" isPlanned="false" superActivities="_d9Oe8X9YEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_fKYOkX9YEd26h9j0X6pKmw" name="ruleset" guid="_fKYOkX9YEd26h9j0X6pKmw" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_d9Oe8X9YEd26h9j0X6pKmw">
+ <presentation xmi:id="-4mHTAj_-HqRpSZirDsCVSQ" href="uma://-bUpJuAJ9G1gNUYahDjpPSw#-4mHTAj_-HqRpSZirDsCVSQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_fcstoH9YEd26h9j0X6pKmw" name="synchronize_with_wrms" guid="_fcstoH9YEd26h9j0X6pKmw" presentationName="Synchronize with Web-Based Rule Management System" superActivities="_d9Oe8X9YEd26h9j0X6pKmw" output="_fc2eoH9YEd26h9j0X6pKmw" performedPrimarilyBy="_fcstoX9YEd26h9j0X6pKmw _fcston9YEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_fcstoH9YEd26h9j0X6pKmw" name="synchronize_with_wrms" guid="_fcstoH9YEd26h9j0X6pKmw" presentationName="Synchronize with Web-Based Rule Management System" superActivities="_d9Oe8X9YEd26h9j0X6pKmw" output="_fc2eoH9YEd26h9j0X6pKmw">
+ <presentation xmi:id="-RlDD3QrzC4Q6jEgiidJMmg" href="uma://-bUpJuAJ9G1gNUYahDjpPSw#-RlDD3QrzC4Q6jEgiidJMmg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YkGwYFtsEdykEsBjRsVfZw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_fcstoX9YEd26h9j0X6pKmw" name="rule_writer" guid="_fcstoX9YEd26h9j0X6pKmw" presentationName="Rule Writer" isPlanned="false" superActivities="_d9Oe8X9YEd26h9j0X6pKmw" modifies="_fc2eoH9YEd26h9j0X6pKmw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_fcston9YEd26h9j0X6pKmw" name="rule_administrator" guid="_fcston9YEd26h9j0X6pKmw" presentationName="Rule Administrator" isPlanned="false" superActivities="_d9Oe8X9YEd26h9j0X6pKmw" modifies="_fc2eoH9YEd26h9j0X6pKmw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4QqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_fc2eoH9YEd26h9j0X6pKmw" name="rule_repository_in_db" guid="_fc2eoH9YEd26h9j0X6pKmw" presentationName="Rule Repository in DB" isPlanned="false" superActivities="_d9Oe8X9YEd26h9j0X6pKmw">
+ <presentation xmi:id="-MzmademiTOM2WTRZYUndBg" href="uma://-bUpJuAJ9G1gNUYahDjpPSw#-MzmademiTOM2WTRZYUndBg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_jqxtYFttEdykEsBjRsVfZw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_d9Oe8X9YEd26h9j0X6pKmw" name="deploy_business_rules" guid="_d9Oe8X9YEd26h9j0X6pKmw" presentationName="Deploy Business Rules" breakdownElements="_fKYOkH9YEd26h9j0X6pKmw _fKYOkX9YEd26h9j0X6pKmw _fcstoH9YEd26h9j0X6pKmw _fcstoX9YEd26h9j0X6pKmw _fcston9YEd26h9j0X6pKmw _fc2eoH9YEd26h9j0X6pKmw">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_d9Oe8X9YEd26h9j0X6pKmw" name="deploy_business_rules" guid="_d9Oe8X9YEd26h9j0X6pKmw" presentationName="Deploy Business Rules" breakdownElements="_fKYOkH9YEd26h9j0X6pKmw _fKYOkX9YEd26h9j0X6pKmw _fcstoH9YEd26h9j0X6pKmw _fc2eoH9YEd26h9j0X6pKmw">
<presentation xmi:id="-bUpJuAJ9G1gNUYahDjpPSw" href="uma://-bUpJuAJ9G1gNUYahDjpPSw#-bUpJuAJ9G1gNUYahDjpPSw"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/design_bre_integration/content.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/design_bre_integration/content.xmi
index 4d09ec4..5540a88 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/design_bre_integration/content.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/design_bre_integration/content.xmi
@@ -1,2 +1,1210 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-18b5hLyhHSSG8Wk1_T7fVQ" name="design,_4NT9AX9XEd26h9j0X6pKmw" guid="-18b5hLyhHSSG8Wk1_T7fVQ" version="7.5.1"/>
+<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="-18b5hLyhHSSG8Wk1_T7fVQ" name="design,_4NT9AX9XEd26h9j0X6pKmw" guid="-18b5hLyhHSSG8Wk1_T7fVQ" version="7.5.1"/>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-6wO1WkYhqlhcM-5FwEvgmA" name="determine_rule_implementation,_59VJIH9XEd26h9j0X6pKmw" guid="-6wO1WkYhqlhcM-5FwEvgmA">
+ <refinedDescription><a id="XE_rule__determine_implementation" name="XE_rule__determine_implementation"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Project teams involved in BRMS deployment are often asking the following type of questions:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus a&nbsp;BPM?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ How do I decide what decisions should I put into a BRE?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus code?&nbsp;
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ There are definitively multiple variables which could influence the decision on where to implement rules. We can start
+ by looking at the BRMS value propositions, it should help to get a first set of variables:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Adaptability – Measure the ability to change the business logic easily. The motivation can be due to short deadline
+ constraint, or frequent small changes or important change that may occur every month or quarter.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Transparency – Represents the need to clearly implement the business logic as what was agreed upon the business
+ unit and the IT team, in a way that every parties understand the logic. This is leading to express the logic in
+ natural or close to natural language.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Auditability – Represents the ability to trace from the business motivation to the execution of the policy to
+ better understand what was the logic behind a decision.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Reusability – Need to share business logic across processes or applications and stay . consistent across
+ applications/transactions
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Manageability- This variable addresses the life cycle management of the business logic. Who writes what, and when,
+ and all the questions related to maintenance and evolutions of the rule-based service.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The purpose here is not to say it is not possible to support those variables in standard software development
+ practices, but more to find some good patterns on how to decide on where to implement the business logic.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ When looking at a business rules statement software engineer can see different possible choices of implementation like:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Data model: designing an object oriented object model involves supporting a lot of business rules. A statement like
+ a mortgage application can have a primary and a secondary borrower, will be supported by two classes and a 1 to 2
+ relationship. At the instantiation of those classes the control of the cardinality can be done in the application
+ logic, or the database, or the GUI structure.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Application code: implementing the logic in function, procedural code or methods in service layer or business
+ objects.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ BPM process flow, tasks or links: BPM tools are addressing business process efficiency issue specifically on "who
+ is involved", "when they should be involved". "what they need to do". BPM supports manual human and automated
+ actors. At a glance the business logic to implement in BPM is linked to people, task, and data to process within a
+ task. When supporting purely automated tasks BPM is orchestrating the application logic and services (BPEL engine).
+ BRMS complements BPM by adding the why to a BPM task, why it behaves a certain way, why this decision is done.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Rule engine: <span style="mso-spacerun: yes">&nbsp;</span>using predefined structure like if then else statement or
+ decision table, rule flow, decision tree, function, rule template or other high level language...
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Graphical user interface: <span style="mso-spacerun: yes">&nbsp;</span>using scripting language or server side code
+ in controller class it is possible to implement data validation type of business rules.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In the following paragraphs address each of different choices with their impact on the variables
+</p><br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in Data Model</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Rule which is controlling the structure of the model and the reference integrity
+ should be in the physical data model, the O/R mapping layer or on the domain object model.</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule setting constraint on relationship -
+ <span style="mso-spacerun: yes">&nbsp;</span>like a loan application could only have two borrowers</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule on the structure of the business
+ entities - like this attribute is part of this object</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following facts are based on a simple
+ user authentication problem, are well implemented in an object model and the supporting application code which
+ create the instance from the data (O/R mapping layer or DAO or service layer):</span>
+ </li>
+</ul>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of users who can login to the application</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of groups of user</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A User is part of a group</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group includes a list of Users</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group has one user reference who is the creator of the group</span>
+</p>
+<p>
+ Terms and facts and derived attributes&nbsp;are the primary constituents of data models and are represented in a UML
+ class diagram, and logical data model (entities/relationship model), or a physical data model.
+</p>
+<p>
+ <span style="mso-bidi-language: HE">The following table lists the impact of this implementation on the previously
+ defined variables</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 221.4pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very static implementation. A change in the constraints of the object model
+ impact, data persistence, logical data model, service and presentation layers. Change is managed on
+ a monthly or yearly basis</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Data model represented as UML classes diagram is doing a poor job to
+ communicate to business. Entities diagram represents a more high level representation of the domain
+ model, but forces the team to maintain the link between the implementation and the business
+ representation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tool, with a strict development process and
+ disciplines can help to trace back to the business motivation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Domain Object model can be designed as reusable. But in the reality each
+ application needs a view of the core business object model, and so part of the implemented
+ application will be to build those view.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tools and strict discipline can help maintain the
+ business logic.</font></span>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in application code</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Implementing business rule in application code is
+ currently the most common way the IT developer is doing it. The major justifications are performance and flexibility of
+ the coding language. Using hard coded if/then/else statements isn't too flexible, but in the hands of a top notch
+ programmer it can be very fast and arguably as fast as or faster than a rule engine. Assuming the programmer has
+ unlimited time to optimize the execution for a fixed set of rules. If the ruleset changes frequently and the system
+ can't tolerate a big drop in performance, than a rule engine is the solution.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following example of business rules may be
+ easily implemented in code:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span class="ISISCodeParagraphChar"><font face="Courier">verify in each items the customer bought since he is customer
+ with us there is at least one article of type T so that we can propose the new product Y with X % of discount, except
+ if the customer is from the state of New York or New Jersey</font></span><span
+ style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">We can implement this in a method which loops on
+ the articles bought by a given customer and do the search. At a first analysis, navigating in a collection of objects
+ and testing multiples conditions on them is easy to implement using the power of programming language.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One thing interesting will be the hard coding of
+ the value of New York, New Jersey... If this logic change we need to add if statements in the code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Other type of rules are related to the control of
+ the execution of a set of "services" to support specific use case. Dispatching, orchestration, data manipulation, … are
+ better candidate to be implemented in application code. Those rules are more static, often more complex, and
+ definitively linked to context of execution. The context may be too complex to expose to a rule engine.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Orchestration are now very well supported by
+ BPM-BPEL engine because the developer needs to add flexibility on the service selection and invocation.<span
+ style="mso-spacerun: yes">&nbsp;</span></span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The evaluation of the important variables
+ is:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 334.25pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">the necessity to change code when a business rule changes is still
+ unpleasant: software build are more efficient and cost less than before but deployment may be
+ expensive depending of the complexity of the production environment. <span
+ style="mso-spacerun: yes">&nbsp;</span></font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Changing code under time pressure usually leads to poor
+ quality</font></span>
+ </p><br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. The logic as defined by the business is split in multiple parts of the
+ code, methods and procedures.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. Only strict use of configuration management tools with a strict
+ development process may help.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">If the logic is implemented in a service layer with defined interface it may
+ be possible to reuse part of the methods.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Developer is
+ responsible to implement the change, and use configuration management tools and strict development
+ disciplines.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in process map</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Business process automation is the technology components substituting and/or
+ supplementing manual processes to manage information flow within an organization to lower costs, reduce risk, and
+ increase consistency. In this context Business rules describe the structure, operation, and strategy of an
+ organization's business process. The business process definition can be seen as a business rule. Typically a rule
+ involving routing of transactional data to a queue, a task, or a sub process will be most likely implemented in a
+ process map. Defined at the link level business rules are linked to the structure of the process flow. Once designed
+ and implemented there is few chance those rule will change. Changing a business process is most of the time risky: we
+ do not want to change thing working and involving a lot of parties and stakeholders. In fact</span> new policies,
+ regulations or business strategies may affect the rules without changing the core business processes.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">A rule like: "<i style="mso-bidi-font-style: normal">if there is an exception in
+ the claim processing we want a supervisor to study the claim and the accumulated reasons extracted by the process so
+ far"</i> will most likely finish as guard on a process map link:</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <img height="348" alt="" src="resources/BRinBPM.bmp" width="313" />
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Task 1 will most of the time call a rule engine to take decision on the claim. One of the pattern is to accumulate all
+ the possible reasons in a list. If the list include an exception or high priority reason, the process map will route to
+ the "Process Exception" task. This task can queue the work item to a supervisor queues.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There are a lot tasks in a business process that are decision rich, so with a lot
+ of business rule to execute before completing the task. Those rules can be executed by a rule engine. The integration
+ Rule Engine – BPM will bring the value to support those cases. But as good practice it is always possible to try to
+ re-arrange an activity diagram of a use case or a process map so that some activities are purely automatically executed
+ in a rule engine mapped as a rule flow.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Business rules hardly coded in using BPM notation is not efficient and lead
+ to complex map. The real design implementation is to mix BPM map and business rules-decision
+ delegated in a process task. In this type of implementation we can leverage the best of both
+ worlds, and the adaptability is excellent.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: when the integration of BPMS and BRMS is done perfectly, the
+ business and IT team have a clear understanding of the process execution and the decision done by a
+ task by studying the rules attached to the task.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: both tools has version control, and it is possible to link
+ process map version to rule set version.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rules defined in a task should be expose to the other application as a
+ service. So reusability can be achieved. Rules in a BPM map are not really reusable.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Process logic will
+ have a more stable life cycle, and it is managed in the BPMS. <span
+ style="mso-spacerun: yes">&nbsp;</span></span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a rule engine</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Any type of rule using a forward chaining approach will best fit in any RETE rule
+ engine. To avoid long explanation a rule engine will perform very efficiently the following rules which are more
+ complex to implement in code:</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Set parameter = A / (B ^ 2)</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If parameter is above 30 then the risk is<span
+ style="mso-spacerun: yes">&nbsp;</span> medium</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If the risk is medium then alert the manager</span>
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><span style="mso-spacerun: yes">&nbsp;</span>If we enter a new value for A all the
+ depend rules will be fired. Rules can be entered in any order we want, it is less declarative than procedural
+ code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Backward chaining rule pattern can also been supported by a rule engine. The rule
+ system works down the tree to find the data that it requires. It will ask question to be able to infer decisions. It is
+ possible to implement backward chaining with product using pure inference by&nbsp;using a goal object.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">As we already stated one of the key factor is flexibility. We already encounter the
+ following decision: "This rule will not change"... but in fact it will do in the future or some of related one"
+ .</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">We can for example take a simple example of a static rule defined as</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 1.9pt 0cm 0pt 18pt; TEXT-ALIGN: justify">
+ <span class="ISISCodeParagraphChar"><font face="Courier">If the status of the customer is gold and the product is
+ &lt;&gt; then apply &lt;&gt; % discount</font></span><span style="mso-bidi-language: HE">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">This rule can be implemented within application code using some tables in a
+ database that link the product, the category of possible status and the discount to apply. But when discussing with the
+ business user to understand what is a gold customer? We can get other conditions that definitively will change over
+ time: "A customer who spend more than &lt;&gt; the amount of money... during the last 6 months ...No !<span
+ style="mso-spacerun: yes">&nbsp;</span> during the last four month only for the product X because it was only available
+ for 4 months!, … Okay but customer in the states {,,,,} could not be part of the gold status... Ah I forgot, ... A
+ customer must have 18 years old, and by the way customer working for our company or subsidiaries could not be part of
+ the gold...</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Excellent, rule can change quickly and be deployed quickly too</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: by adding meta data to implemented rule we can clearly link rule
+ to business strategies and policies</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent and most of the rule engine has log mechanism to trace what were
+ the rules executed on a given transaction.</font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rule reports are important to the business as part of
+ documentation</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very good if the BRMS use rule repository and the rule analyst designed a
+ rule sharing approach</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Excellent as rules
+ are externalized and managed as a standalone artifact. Rule configuration management is complex,
+ and integrity between rule life cycle and rule set versioning is not a simple
+ practice.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a graphical user interface</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ We will base the integration on the Model-View-Controller (MVC) design pattern. The presentation tier handles the
+ client interaction by abstracting the low-level protocol details into an event-based mechanism. The view's main
+ requirement is synchronization with the model so that data displayed to the user is up to date. The controller is
+ responsible to prepare the data and manage the view flow and content. Delegating the creation of content to a rule
+ engine is possible but need to be done synchronously.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The business rule will be related to control the list of widget the GUI will present. A typical pattern is around
+ product catalog application or dynamic questionnaire. The rule pattern to control the content looks like:
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the selection on this page was &lt;&gt; then add this &lt;&gt; to the model
+ used in view &lt;&gt;</i>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ A rule to control the flow of page looks like
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the user visited page &lt;&gt; (and | or page &lt;&gt;) then next page is
+ &lt;&gt;</i>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Both rules may be enriched with business type decision based on data of the model.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In these pattern it is clear we need to keep the previous context of decision, and events the user created.<span
+ style="mso-spacerun: yes">&nbsp;</span> So most of the current applications are putting the business rule in the
+ controller class or in the java script of the view, but it is possible to design the controller to use a rule engine,
+ as soon as the decision needs to change. This is particularly true for e-commerce web site, where marketing campaign
+ can quickly be put in place by proposing product or product feature more dynamically.<span
+ style="mso-spacerun: yes">&nbsp;</span>
+</p><br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-CuJ8KsGj2Ge8INilrucD1w" name="define_ruleset,_BZaDsH9ZEd26h9j0X6pKmw" guid="-CuJ8KsGj2Ge8INilrucD1w">
+ <refinedDescription><a id="XE_rule_set__define" name="XE_rule_set__define"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">When designing an application using one BRE and a simple rule set this activity
+ will be done quickly. The rule developer still needs to think about the parameters the exception management, <span
+ style="mso-spacerun: yes">&nbsp;</span>what are the rule part of the rule set, and how they are executed.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">So for a simple unique rule set the following information needs to be designed and
+ documented:</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Input, output parameters</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Type of data model</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Rule execution flow using a rule flow. But it is still possible with modern BRE
+ to use re-entrant rule set, so executing a rule flow from a rule task or rule package.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Exception management</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Inference objects like a result object which may be used to control the future
+ execution of the caller application or the BRE.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">What are the rule part of the rule set</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">What is their execution order. It is recommended to avoid using a ordering
+ mechanism like the rule priority, but some time at a rule task level it is needed to use sorting mechanism</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">When does a rule is not candidate to enter in a rule set. This is linked to the
+ rule life cycle.</span>
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-SUg_Lde8qOSnwbqR7aE35Q" name="build_object_models,_6OKacH9XEd26h9j0X6pKmw" guid="-SUg_Lde8qOSnwbqR7aE35Q">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">Depending of the technology used there is different approach to this task. The
+ domain object model at the enterprise level will represent a complex data model a rule architect does not want to
+ expose as-is to the rule engine and the rule authoring environment. Navigating a complex graph of objects will bring
+ unnecessary complexity for the rule writer. So we recommend to always try to use a view of the enterprise domain object
+ model. For example in Financial Industry the business domain&nbsp;data model defined in MISMO (<a
+ href="http://www.mismo.org/"><font color="#005DA0">www.mismo.org</font></a>), brings a lot of value for an enterprise
+ willing to define a common ontology for their data models. But exposing the MISMO model as it is within a BRMS rule
+ authoring IDE will put too much complexity. As the Architect is responsible to design decision service reusable cross
+ application, it may make sense to consider view of this object model in the context of the service.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">For the application the view can be defined in two entities:</span>
+</p>
+<ul style="MARGIN-TOP: 0in" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in">
+ <span style="mso-bidi-language: HE">the Domain Object Model using java or xml schema as the underling
+ technology</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in">
+ <span style="mso-bidi-language: HE">or out of the box object view, like ILOG-Business Object Model element. The BOM
+ is mandatory to write rule on, but it&nbsp;can be created from an existing java model or XSD or created
+ top-down.</span>
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">If the model does not exist in the application, or at the enterprise level we still
+ recommend to develop the domain model, using an UML designer and code generation tools.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-font-weight: bold; mso-bidi-font-style: italic">It is also important to consider designing a java
+ model or XSD schema which is closed to the business concepts used by the rule but built as a view of the domain object
+ model (We called that the Rule Business Object Pattern or RBO): in the example of standard object model like MISMO or
+ ACORD, it makes sense to do not expose all the class definition, attributes and enumerated to avoid exposing a complex
+ rule language to the business user. This view will be instantiated by the application business logic in the context of
+ preparing the data for the rule services</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ When designing a Domain Object model one of the challenges is to determine what should be an entity and what should be
+ an attribute of the entity.<span style="mso-spacerun: yes">&nbsp;</span> This is why knowledge engineers like the
+ Enterprise Ontology as a start point for developing these concepts.<span style="mso-spacerun: yes">&nbsp;</span> The
+ Enterprise Ontology describes the major entities and concepts that apply to all enterprises and it provides a very good
+ starting point for the establishment of static object models and data models.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The difference between a class and an entity type is that classes have both data and behaviors whereas entity types
+ just have data. A normal entity depicts one concept.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Use multiple different UML class diagram to represent entities and their relations. Then enhance them to have a
+ complete class diagram from which you should be able to generate java code or XSD.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Capture Meta data about each entity: business name, business definition, super type or subtype, number of occurrences,
+ primary key, and alternate keys.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">It is possible to consider designing a Domain Model using Interface, and then apply
+ different type of implementation according to different execution pattern or platforms. For example we can design
+ a;</span>
+</p>
+<ul style="MARGIN-TOP: 0in" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030902" name="1030902"><span style="mso-bidi-language: HE">Staged deployment with different execution
+ classes</span></a>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030906" name="1030906"><span style="mso-bidi-language: HE">Dynamic model (XML based or dynamic classes)
+ versus static model</span></a>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030907" name="1030907"><span style="mso-bidi-language: HE">Production/test models (active objects versus
+ mock objects)</span></a>
+ </li>
+</ul><a id="XE_object_model__build" name="XE_object_model__build"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-9LXp5OR5EN9FZBKkwS1J8w" name="build_rule_project_structure,_6cKaMH9XEd26h9j0X6pKmw" guid="-9LXp5OR5EN9FZBKkwS1J8w">
+ <refinedDescription><a id="XE_rule_project__build_structure" name="XE_rule_project__build_structure"></a><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; TEXT-ALIGN: justify; mso-list: l0 level1 lfo1; tab-stops: list .25in" />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><span style="mso-bidi-language: HE">This activity is linked to the tool used. There
+ is still some considerations when designing the project structure for the rules and application:</span></span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Apply good design practice of implementing the application using a n-tier
+ approach. The service layer includes the interfaces of the rule decision service entries.</span><br
+ class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 18pt" />
+ <br />
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><img height="491" alt="" src="resources/projStruct.bmp" width="515" /></span>
+</p>
+<div style="MARGIN-TOP: 0cm; MARGIN-LEFT: 2em" type="disc">
+ <ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE"><span style="mso-bidi-language: HE">Organize rule project so that a few
+ person can concurrently work on&nbsp;rule artifact at the same time.</span></span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Organize rule project so that they are manageable in term of performance at
+ the execution and at the rule authoring level.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ Separate representation of the domain object model in java project.
+ </li>
+ </ul>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-nwZcYuKm35TyaeUzE1tIug" name="prototype_rules,_6qw24H9XEd26h9j0X6pKmw" guid="-nwZcYuKm35TyaeUzE1tIug">
+ <refinedDescription><a id="XE_rule__prototyping" name="XE_rule__prototyping"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The goal of the Rule Analysis activity is to prepare the rules for the
+ implementation. The rule analyst and the rule writer will analyze the rules discovered in a disjointed way into a
+ complete and coherent set. From the rule description, the glossary of business terms and may be from a first version of
+ the logical data model (LDM), the discovery team needs to transform the rules using the terms of the business to
+ elements that will be implemented by the rule writers. The rule analyst executes a set of iterative tasks to reach rule
+ implementation.</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-09Itbxe1JXVwpusKQdRW6A" name="decision_point_table,_BZaDsX9ZEd26h9j0X6pKmw" guid="-09Itbxe1JXVwpusKQdRW6A">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Vv_9K8Dz3DHl2GFZ69FiAQ" name="rule_description_doc,_BZaDsn9ZEd26h9j0X6pKmw" guid="-Vv_9K8Dz3DHl2GFZ69FiAQ">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-pAIEUuJxXz-6pgjLh_pMzw" name="ruleset,_BZaDs39ZEd26h9j0X6pKmw" guid="-pAIEUuJxXz-6pgjLh_pMzw">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/design_bre_integration/model.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/design_bre_integration/model.xmi
index e16afd5..1c85b5b 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/design_bre_integration/model.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/design_bre_integration/model.xmi
@@ -2,18 +2,22 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__ZrisbekEd-D7YZN9NgldQ" guid="__ZrisbekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__ZrisrekEd-D7YZN9NgldQ" id="-18b5hLyhHSSG8Wk1_T7fVQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b5a1gVmSEeCcpdiAcH0w-w" id="-6wO1WkYhqlhcM-5FwEvgmA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b5a1glmSEeCcpdiAcH0w-w" id="-CuJ8KsGj2Ge8INilrucD1w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b5a1g1mSEeCcpdiAcH0w-w" id="-SUg_Lde8qOSnwbqR7aE35Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b5j_cFmSEeCcpdiAcH0w-w" id="-9LXp5OR5EN9FZBKkwS1J8w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b5j_cVmSEeCcpdiAcH0w-w" id="-nwZcYuKm35TyaeUzE1tIug" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b5j_clmSEeCcpdiAcH0w-w" id="-09Itbxe1JXVwpusKQdRW6A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b5twcFmSEeCcpdiAcH0w-w" id="-Vv_9K8Dz3DHl2GFZ69FiAQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b5twcVmSEeCcpdiAcH0w-w" id="-pAIEUuJxXz-6pgjLh_pMzw" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_4NT9AH9XEd26h9j0X6pKmw" name="design_bre_integration" guid="_4NT9AH9XEd26h9j0X6pKmw">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59VJIH9XEd26h9j0X6pKmw" name="determine_rule_implementation" guid="_59VJIH9XEd26h9j0X6pKmw" presentationName="Determine Rule Implementation" superActivities="_4NT9AX9XEd26h9j0X6pKmw" performedPrimarilyBy="_59VJIX9XEd26h9j0X6pKmw _59VJIn9XEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59VJIH9XEd26h9j0X6pKmw" name="determine_rule_implementation" guid="_59VJIH9XEd26h9j0X6pKmw" presentationName="Determine Rule Implementation" briefDescription="This task tries to answer the question of where to implement the business rules that have been discovered." superActivities="_4NT9AX9XEd26h9j0X6pKmw">
+ <presentation xmi:id="-6wO1WkYhqlhcM-5FwEvgmA" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-6wO1WkYhqlhcM-5FwEvgmA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_qzveUBk5Edyoe_hnDlTB5A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_59VJIX9XEd26h9j0X6pKmw" name="rule_analyst" guid="_59VJIX9XEd26h9j0X6pKmw" presentationName="Rule Analyst" isPlanned="false" superActivities="_4NT9AX9XEd26h9j0X6pKmw" responsibleFor="_BZaDsn9ZEd26h9j0X6pKmw _BZaDsX9ZEd26h9j0X6pKmw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_59VJIn9XEd26h9j0X6pKmw" name="rule_architect" guid="_59VJIn9XEd26h9j0X6pKmw" presentationName="Rule Architect" isPlanned="false" superActivities="_4NT9AX9XEd26h9j0X6pKmw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_BZaDsH9ZEd26h9j0X6pKmw" name="define_ruleset" guid="_BZaDsH9ZEd26h9j0X6pKmw" presentationName="Define Rule Set" superActivities="_4NT9AX9XEd26h9j0X6pKmw" linkToPredecessor="_ENXZEH9ZEd26h9j0X6pKmw" mandatoryInput="_BZaDsX9ZEd26h9j0X6pKmw _BZaDsn9ZEd26h9j0X6pKmw" output="_BZaDs39ZEd26h9j0X6pKmw">
+ <presentation xmi:id="-CuJ8KsGj2Ge8INilrucD1w" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-CuJ8KsGj2Ge8INilrucD1w"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_7L2MIDyOEdyA6a_I80swHw"/>
<selectedSteps href="uma://-gt8CaPXz6HldH1v7OnThvg#_uGtsEErrEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-gt8CaPXz6HldH1v7OnThvg#_pIE9sEafEdySHMdInS9eGA"/>
@@ -23,10 +27,12 @@
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_ENXZEH9ZEd26h9j0X6pKmw" guid="_ENXZEH9ZEd26h9j0X6pKmw" pred="_59VJIH9XEd26h9j0X6pKmw"/>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6OKacH9XEd26h9j0X6pKmw" name="build_object_models" guid="_6OKacH9XEd26h9j0X6pKmw" presentationName="Build Object Models" superActivities="_4NT9AX9XEd26h9j0X6pKmw" linkToPredecessor="_EWT5sH9ZEd26h9j0X6pKmw">
+ <presentation xmi:id="-SUg_Lde8qOSnwbqR7aE35Q" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-SUg_Lde8qOSnwbqR7aE35Q"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZffcIDmiEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_EWT5sH9ZEd26h9j0X6pKmw" guid="_EWT5sH9ZEd26h9j0X6pKmw" pred="_BZaDsH9ZEd26h9j0X6pKmw"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6cKaMH9XEd26h9j0X6pKmw" name="build_rule_project_structure" guid="_6cKaMH9XEd26h9j0X6pKmw" presentationName="Build Rule Project Structure" superActivities="_4NT9AX9XEd26h9j0X6pKmw" linkToPredecessor="_E6_UEH9ZEd26h9j0X6pKmw" performedPrimarilyBy="_59VJIX9XEd26h9j0X6pKmw _59VJIn9XEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6cKaMH9XEd26h9j0X6pKmw" name="build_rule_project_structure" guid="_6cKaMH9XEd26h9j0X6pKmw" presentationName="Build Rule Project Structure" briefDescription="Designing and building how the rule will be managed is an important activity of a BRMS project. This task describes how to build the set of rule and non rules projects that support the business application." superActivities="_4NT9AX9XEd26h9j0X6pKmw" linkToPredecessor="_E6_UEH9ZEd26h9j0X6pKmw">
+ <presentation xmi:id="-9LXp5OR5EN9FZBKkwS1J8w" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-9LXp5OR5EN9FZBKkwS1J8w"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_O92DQDV5EdyTBtGu8YeFfg"/>
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_OBfOkDuhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_RVoYoDyNEdyA6a_I80swHw"/>
@@ -35,7 +41,9 @@
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_94ET8DugEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_E6_UEH9ZEd26h9j0X6pKmw" guid="_E6_UEH9ZEd26h9j0X6pKmw" pred="_BZaDsH9ZEd26h9j0X6pKmw"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6qw24H9XEd26h9j0X6pKmw" name="prototype_rules" guid="_6qw24H9XEd26h9j0X6pKmw" presentationName="Prototype Rules" superActivities="_4NT9AX9XEd26h9j0X6pKmw" linkToPredecessor="_Gg-acH9ZEd26h9j0X6pKmw _Gg-acX9ZEd26h9j0X6pKmw" additionallyPerformedBy="_6qw24X9XEd26h9j0X6pKmw" performedPrimarilyBy="_59VJIX9XEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6qw24H9XEd26h9j0X6pKmw" name="prototype_rules" guid="_6qw24H9XEd26h9j0X6pKmw" presentationName="Prototype Rules" briefDescription="Prototyping rules is an important step of the rule analysis, as it is when we are really coding that issues arrived. Paper work is fine, but working rules is far better." superActivities="_4NT9AX9XEd26h9j0X6pKmw" linkToPredecessor="_Gg-acH9ZEd26h9j0X6pKmw _Gg-acX9ZEd26h9j0X6pKmw">
+ <presentation xmi:id="-nwZcYuKm35TyaeUzE1tIug" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-nwZcYuKm35TyaeUzE1tIug"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x-GVQIsqEd2gksNyFVJN4g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_dds-IDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_tA5YEDyIEdyA6a_I80swHw"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_usf-QDyIEdyA6a_I80swHw"/>
@@ -45,19 +53,26 @@
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_Gg-acH9ZEd26h9j0X6pKmw" guid="_Gg-acH9ZEd26h9j0X6pKmw" pred="_6OKacH9XEd26h9j0X6pKmw"/>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_Gg-acX9ZEd26h9j0X6pKmw" guid="_Gg-acX9ZEd26h9j0X6pKmw" pred="_6cKaMH9XEd26h9j0X6pKmw"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6qw24X9XEd26h9j0X6pKmw" name="rule_writer" guid="_6qw24X9XEd26h9j0X6pKmw" presentationName="Rule Writer" isPlanned="false" superActivities="_4NT9AX9XEd26h9j0X6pKmw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_BZaDsX9ZEd26h9j0X6pKmw" name="decision_point_table" guid="_BZaDsX9ZEd26h9j0X6pKmw" presentationName="Decision Point Table" isPlanned="false" superActivities="_4NT9AX9XEd26h9j0X6pKmw">
+ <presentation xmi:id="-09Itbxe1JXVwpusKQdRW6A" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-09Itbxe1JXVwpusKQdRW6A"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_BZaDsn9ZEd26h9j0X6pKmw" name="rule_description_doc" guid="_BZaDsn9ZEd26h9j0X6pKmw" presentationName="Rule Description Document" isPlanned="false" superActivities="_4NT9AX9XEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_BZaDsn9ZEd26h9j0X6pKmw" name="rule_description_doc" guid="_BZaDsn9ZEd26h9j0X6pKmw" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_4NT9AX9XEd26h9j0X6pKmw">
+ <presentation xmi:id="-Vv_9K8Dz3DHl2GFZ69FiAQ" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-Vv_9K8Dz3DHl2GFZ69FiAQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_BZaDs39ZEd26h9j0X6pKmw" name="ruleset" guid="_BZaDs39ZEd26h9j0X6pKmw" presentationName="Rule Set" isPlanned="false" superActivities="_4NT9AX9XEd26h9j0X6pKmw">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_BZaDs39ZEd26h9j0X6pKmw" name="ruleset" guid="_BZaDs39ZEd26h9j0X6pKmw" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_4NT9AX9XEd26h9j0X6pKmw">
+ <presentation xmi:id="-pAIEUuJxXz-6pgjLh_pMzw" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-pAIEUuJxXz-6pgjLh_pMzw"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_4NT9AX9XEd26h9j0X6pKmw" name="design_bre_integration" guid="_4NT9AX9XEd26h9j0X6pKmw" presentationName="Design BRMS Integration" breakdownElements="_59VJIH9XEd26h9j0X6pKmw _59VJIX9XEd26h9j0X6pKmw _59VJIn9XEd26h9j0X6pKmw _BZaDsH9ZEd26h9j0X6pKmw _6OKacH9XEd26h9j0X6pKmw _6cKaMH9XEd26h9j0X6pKmw _6qw24H9XEd26h9j0X6pKmw _6qw24X9XEd26h9j0X6pKmw _BZaDsX9ZEd26h9j0X6pKmw _BZaDsn9ZEd26h9j0X6pKmw _BZaDs39ZEd26h9j0X6pKmw">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_4NT9AX9XEd26h9j0X6pKmw" name="design_bre_integration" guid="_4NT9AX9XEd26h9j0X6pKmw" presentationName="Design BRMS Integration" breakdownElements="_59VJIH9XEd26h9j0X6pKmw _BZaDsH9ZEd26h9j0X6pKmw _6OKacH9XEd26h9j0X6pKmw _6cKaMH9XEd26h9j0X6pKmw _6qw24H9XEd26h9j0X6pKmw _BZaDsX9ZEd26h9j0X6pKmw _BZaDsn9ZEd26h9j0X6pKmw _BZaDs39ZEd26h9j0X6pKmw">
<presentation xmi:id="-18b5hLyhHSSG8Wk1_T7fVQ" href="uma://-18b5hLyhHSSG8Wk1_T7fVQ#-18b5hLyhHSSG8Wk1_T7fVQ"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/develop_bre_architecture/content.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/develop_bre_architecture/content.xmi
index 9f45a20..b163c14 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/develop_bre_architecture/content.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/develop_bre_architecture/content.xmi
@@ -1,2 +1,362 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-LPRqcx3TAg7m-fqsDb-Qdg" name="architecture,_2_QBQX_BEd2YWI_0AZcMOA" guid="-LPRqcx3TAg7m-fqsDb-Qdg" version="7.5.1"/>
+<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><p class="MsoNormal" style="MARGIN: 0in 0in 10pt">
+ <span style="mso-bidi-language: HE">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.</span>
+</p></keyConsiderations>
+ <refinedDescription><p>
+ The architect has to address as soon as possible in the project life cycle:
+</p>
+<ul>
+ <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.
+ </li>
+ <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.<br />
+ </li>
+</ul>
+<p>
+ For a BRMS deployment architect needs to integrate the following components within the IT architecture:
+</p>
+<ul>
+ <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.&nbsp;<br />
+ </li>
+ <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.<br />
+ </li>
+ <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.<br />
+ </li>
+ <li>
+ A Web based Rule management platform to let business users and analysts being able to maintain the rules.<br />
+ </li>
+ <li>
+ A Rule testing framework to support functional testing of the rule set and non-regression tests.
+ </li>
+</ul>
+<p>
+ <img height="376" alt="" src="resources/BRMScomponents.bmp" width="487" />
+</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><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 /></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><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.
+</p>
+<p>
+ The following diagram highlights a high level architecture&nbsp;architect can leverage to design&nbsp;his own solution.
+</p><br />
+<p>
+ <img height="499" alt="" src="resources/MDM.bmp" width="557" /><br />
+</p>
+<p>
+ The master data are centralized in a repository, and technology as Master Data Management product can be&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&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.
+</p>
+<p>
+ The same applies for the rule authoring environment: The&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.
+</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><p>
+ This is an important activity as we do not expose an enterprise model or a physical model as&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.
+</p>
+<p>
+ In any cases&nbsp;&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.&nbsp;
+</p>
+<p>
+ Developing such models is done by iterations.
+</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><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.
+</p>
+<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:
+</p>
+<ul>
+ <li>
+ the service definition: one or more operations linked to the same data semantic
+ </li>
+ <li>
+ the operation call approach: synchronous/ asynchronous, stateless/stateful, header based or carrying payload, use
+ of faults or not
+ </li>
+ <li>
+ the exception reporting
+ </li>
+</ul>
+<p>
+ The service implementation using a rule engine has to look at:
+</p>
+<ul>
+ <li>
+ the transaction propagation
+ </li>
+ <li>
+ the reference data caching
+ </li>
+ <li>
+ the parsing of input message: the claim data
+ </li>
+ <li>
+ the loading of the related data: the policy related to the claim, or the insured person profile
+ </li>
+ <li>
+ the preparation of the output message: the result and may be some other technical data
+ </li>
+</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><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Ma59gPLPnn5KbrkfjVsCuw" name="decision_point_table,_fy3MRVmSEeCcpdiAcH0w-w" guid="-Ma59gPLPnn5KbrkfjVsCuw">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</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><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/develop_bre_architecture/model.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/develop_bre_architecture/model.xmi
index 7c42b40..236f0be 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/develop_bre_architecture/model.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/develop_bre_architecture/model.xmi
@@ -2,34 +2,73 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__Z1TsLekEd-D7YZN9NgldQ" guid="__Z1TsLekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__Z1TsbekEd-D7YZN9NgldQ" id="-LPRqcx3TAg7m-fqsDb-Qdg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_gyMiUVmSEeCcpdiAcH0w-w" id="-rA66uZaVDDOF8xewr623tg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_gyMiUlmSEeCcpdiAcH0w-w" id="-i6qDLS-QtvrGS7XrdQccRw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_gyMiU1mSEeCcpdiAcH0w-w" id="-GVzTM2PClW6NdAGW_5pHQQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_gyMiVFmSEeCcpdiAcH0w-w" id="-0hmrAC1ixwLo8vzDeoMSHw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_gyMiVVmSEeCcpdiAcH0w-w" id="-1NnOz_GLRSSA5tYw0IfOMg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_gyMiVlmSEeCcpdiAcH0w-w" id="-7RFal_ahu_4qnKS-p-tVQQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_gyVsQFmSEeCcpdiAcH0w-w" id="-Ma59gPLPnn5KbrkfjVsCuw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_gyVsQVmSEeCcpdiAcH0w-w" id="-lr_US7ML4CXgAan7X2HI3g" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_2_QBQH_BEd2YWI_0AZcMOA" name="develop_bre_architecture" guid="_2_QBQH_BEd2YWI_0AZcMOA">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_4s7EAH_BEd2YWI_0AZcMOA" name="develop_architecture" guid="_4s7EAH_BEd2YWI_0AZcMOA" presentationName="Develop Business Rule Application Architecture" superActivities="_2_QBQX_BEd2YWI_0AZcMOA" output="_4tXv8H_BEd2YWI_0AZcMOA" performedPrimarilyBy="_4tN-8H_BEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_4s7EAH_BEd2YWI_0AZcMOA" name="develop_architecture" guid="_4s7EAH_BEd2YWI_0AZcMOA" presentationName="Develop Business Rule Application Architecture" briefDescription="The purpose of the architecture activities is to support the following major items:
•	Integrate the Rule Engine into the business application
•	Deploy Business Rules Management System into the business and IT organizations." superActivities="_2_QBQX_BEd2YWI_0AZcMOA" mandatoryInput="_fy3MQlmSEeCcpdiAcH0w-w _fy3MRVmSEeCcpdiAcH0w-w" output="_4tXv8H_BEd2YWI_0AZcMOA">
+ <presentation xmi:id="-rA66uZaVDDOF8xewr623tg" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-rA66uZaVDDOF8xewr623tg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_O1kAANvfEduv2KOT-Teh6w"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gjdYMlgEdmt3adZL5Dmdw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_nOQHsAp6EdyPCr4G1Tb79A"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_RMRccChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_yIEJ4Ap6EdyPCr4G1Tb79A"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_r5SRoChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_venZkChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_yFzeQChaEd2bfOOTyXGWkw"/>
+ <selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_HDD68Im5Ed2cL6yqw-_-uA"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_04xVIChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_27c-kChaEd2bfOOTyXGWkw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_4tN-8H_BEd2YWI_0AZcMOA" name="rule_architect" guid="_4tN-8H_BEd2YWI_0AZcMOA" presentationName="Rule Architect" isPlanned="false" superActivities="_2_QBQX_BEd2YWI_0AZcMOA" modifies="_4tXv8H_BEd2YWI_0AZcMOA">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4tXv8H_BEd2YWI_0AZcMOA" name="decision_service_architecture" guid="_4tXv8H_BEd2YWI_0AZcMOA" presentationName="Decision Service Architecture" isPlanned="false" superActivities="_2_QBQX_BEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4tXv8H_BEd2YWI_0AZcMOA" name="decision_service_architecture" guid="_4tXv8H_BEd2YWI_0AZcMOA" presentationName="Decision Service Architecture" briefDescription="A decision service is a piece of logic which uses a decision engine like a rule engine in order to infer actions on the input data." isPlanned="false" superActivities="_2_QBQX_BEd2YWI_0AZcMOA">
+ <presentation xmi:id="-i6qDLS-QtvrGS7XrdQccRw" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-i6qDLS-QtvrGS7XrdQccRw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YRiuIItDEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_6BE7QAp_EdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_5BMD0H_BEd2YWI_0AZcMOA" name="design_reference_data_integration" guid="_5BMD0H_BEd2YWI_0AZcMOA" presentationName="Design Integration to Reference Data" superActivities="_2_QBQX_BEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_5BMD0H_BEd2YWI_0AZcMOA" name="design_reference_data_integration" guid="_5BMD0H_BEd2YWI_0AZcMOA" presentationName="Design Integration to Reference Data" briefDescription="Reference data are everywhere in business application, from basic enumeration value like the US sates to business codes with business meaning (like medical code). Those references data should be managed in a central Data Base or repository. The Rule engine needs to access them at execution but also during the authoring phase." superActivities="_2_QBQX_BEd2YWI_0AZcMOA">
+ <presentation xmi:id="-GVzTM2PClW6NdAGW_5pHQQ" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-GVzTM2PClW6NdAGW_5pHQQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_HMQasGDFEdyKlZvvtnMrMg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_5QiHYH_BEd2YWI_0AZcMOA" name="design_models_for_bre" guid="_5QiHYH_BEd2YWI_0AZcMOA" presentationName="Design Business Object Models for Rule Engine Processing" superActivities="_2_QBQX_BEd2YWI_0AZcMOA" performedPrimarilyBy="_4tN-8H_BEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_5QiHYH_BEd2YWI_0AZcMOA" name="design_models_for_bre" guid="_5QiHYH_BEd2YWI_0AZcMOA" presentationName="Design Business Object Models for Rule Engine Processing" briefDescription="Design the object model to be processed by the rule engine. " superActivities="_2_QBQX_BEd2YWI_0AZcMOA" mandatoryInput="_fy3MSFmSEeCcpdiAcH0w-w _fy3MQlmSEeCcpdiAcH0w-w" output="_fy3MS1mSEeCcpdiAcH0w-w">
+ <presentation xmi:id="-0hmrAC1ixwLo8vzDeoMSHw" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-0hmrAC1ixwLo8vzDeoMSHw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_lYC2IGDAEdyKlZvvtnMrMg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_EAYVQH_CEd2YWI_0AZcMOA" name="integrate_bre" guid="_EAYVQH_CEd2YWI_0AZcMOA" presentationName="Integrate BRE with Service Layer" superActivities="_2_QBQX_BEd2YWI_0AZcMOA" isSynchronizedWithSource="false" performedPrimarilyBy="_4tN-8H_BEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_EAYVQH_CEd2YWI_0AZcMOA" name="integrate_bre" guid="_EAYVQH_CEd2YWI_0AZcMOA" presentationName="Integrate BRE within Service Layer" briefDescription="The integration of the rule engine can be done in different approaches depending of the type of application, and architecture." superActivities="_2_QBQX_BEd2YWI_0AZcMOA" isSynchronizedWithSource="false">
+ <presentation xmi:id="-1NnOz_GLRSSA5tYw0IfOMg" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-1NnOz_GLRSSA5tYw0IfOMg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_IuFgEIm-Ed2dvb7--2nAHw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YRiuIItDEd2gksNyFVJN4g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_6-p2EH_BEd2YWI_0AZcMOA"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_2_QBQX_BEd2YWI_0AZcMOA" name="develop_bre_architecture" guid="_2_QBQX_BEd2YWI_0AZcMOA" presentationName="Develop BRMS Integration Architecture" breakdownElements="_4s7EAH_BEd2YWI_0AZcMOA _4tN-8H_BEd2YWI_0AZcMOA _4tXv8H_BEd2YWI_0AZcMOA _5BMD0H_BEd2YWI_0AZcMOA _5QiHYH_BEd2YWI_0AZcMOA _EAYVQH_CEd2YWI_0AZcMOA">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_fy3MQlmSEeCcpdiAcH0w-w" name="logical_data_model" guid="_fy3MQlmSEeCcpdiAcH0w-w" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_2_QBQX_BEd2YWI_0AZcMOA">
+ <methodElementProperty xmi:id="_fy3MQ1mSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-7RFal_ahu_4qnKS-p-tVQQ" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-7RFal_ahu_4qnKS-p-tVQQ"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_fy3MRVmSEeCcpdiAcH0w-w" name="decision_point_table" guid="_fy3MRVmSEeCcpdiAcH0w-w" presentationName="Decision Point Table" isPlanned="false" superActivities="_2_QBQX_BEd2YWI_0AZcMOA">
+ <methodElementProperty xmi:id="_fy3MRlmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-Ma59gPLPnn5KbrkfjVsCuw" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-Ma59gPLPnn5KbrkfjVsCuw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_fy3MSFmSEeCcpdiAcH0w-w" name="fact_model" guid="_fy3MSFmSEeCcpdiAcH0w-w" presentationName="Fact Model" isPlanned="false" superActivities="_2_QBQX_BEd2YWI_0AZcMOA">
+ <methodElementProperty xmi:id="_fy3MSVmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-lr_US7ML4CXgAan7X2HI3g" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-lr_US7ML4CXgAan7X2HI3g"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_fy3MS1mSEeCcpdiAcH0w-w" name="executable_object_model" guid="_fy3MS1mSEeCcpdiAcH0w-w" presentationName="Executable Object Model" briefDescription="A Java, .Net or XML schema implementation of the logical data model" isPlanned="false" superActivities="_2_QBQX_BEd2YWI_0AZcMOA">
+ <methodElementProperty xmi:id="_fy3MTFmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_U003IIm4Ed2cL6yqw-_-uA"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_2_QBQX_BEd2YWI_0AZcMOA" name="develop_bre_architecture" guid="_2_QBQX_BEd2YWI_0AZcMOA" presentationName="Develop BRMS Integration Architecture" breakdownElements="_4s7EAH_BEd2YWI_0AZcMOA _4tXv8H_BEd2YWI_0AZcMOA _5BMD0H_BEd2YWI_0AZcMOA _5QiHYH_BEd2YWI_0AZcMOA _EAYVQH_CEd2YWI_0AZcMOA _fy3MQlmSEeCcpdiAcH0w-w _fy3MRVmSEeCcpdiAcH0w-w _fy3MSFmSEeCcpdiAcH0w-w _fy3MS1mSEeCcpdiAcH0w-w">
<presentation xmi:id="-LPRqcx3TAg7m-fqsDb-Qdg" href="uma://-LPRqcx3TAg7m-fqsDb-Qdg#-LPRqcx3TAg7m-fqsDb-Qdg"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/discover_business_rules/content.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/discover_business_rules/content.xmi
index ffa8d7d..200a81b 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/discover_business_rules/content.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/discover_business_rules/content.xmi
@@ -1,2 +1,754 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-z9VrO6XKxLBPsLPbkRNDlg" name="discovery,_40DokXqkEd2o_5d3MWaNxQ" guid="-z9VrO6XKxLBPsLPbkRNDlg" version="7.5.1"/>
+<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="-z9VrO6XKxLBPsLPbkRNDlg" name="discovery,_40DokXqkEd2o_5d3MWaNxQ" guid="-z9VrO6XKxLBPsLPbkRNDlg" version="7.5.1"/>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-lm3kKBz3aGKgtfJqku4utw" name="identify_decision_point,_ELiLsD3hEd-rQL4FfV6WbQ" guid="-lm3kKBz3aGKgtfJqku4utw">
+ <refinedDescription><p>
+ A <a class="elementLink" href="./../../practice.tech.abrd.base/guidances/termdefinitions/decision_point_B1C5EFE2.html"
+ guid="_XUyFIEb1EdySHMdInS9eGA">Decision point</a>&nbsp;represents an activity in a business process where decisions are
+ done. When looking at a task description it is important to search for mental thinking verb, most of the time there is
+ a set of knowledge to apply to execute this task, which leads to decision. This could be human knowledge or business
+ logic implementation in a software component. The type of decision will most likely be a reject or accept of the
+ business event or flag it for future processing downstream in the business process. The decision may also include some
+ computational expressions to assign value to attribute of the business transaction. Therefore to find decision point in
+ a business process or use case description start by searching for mental, action verb like analyze, check, validate,
+ evaluate, verify, assess, ...
+</p>
+<p>
+ In a BPMN process diagram a business process analyst and/ or a rule analyst can annotate the process to highlight
+ decision point in the process.
+</p>
+<p>
+ <img height="363" alt="" src="resources/FindDecisionPoint.bmp" width="1572" />
+</p>
+<p>
+ The search for decision point, attached to a business process description (done with use case or with BPMN does not
+ matter), helps to drive the rule analysis, and helps the business to focus at the business rule&nbsp;enforcement.
+ If&nbsp;the business team misses where the rule should be enforced, he can spend months defining business rules which
+ IT does not understand where to deploy them. The decision point can help drive the discovery of the business policies
+ and rules, for an implementation point of view, as well as a way to organize the top down approach. A decision point
+ support multiple rules, and if implemented with a rule engine, the rules are packaged as rule set.
+</p>
+<p>
+ Also finding the decision points involves studying<br />
+ • Which use cases/scenarios represent decisions - At what steps in the use case is a decision made?<br />
+ • Which requirements constitute rich set of decisions?<br />
+ • Which steps/cases/requirements represent significant complexity?<br />
+ • Which steps/cases/requirements are most subject to change?<br />
+ • Look for decision diamonds in the flow charts and activity diagrams, the gateway by itself route the data to the next
+ activity, but the activity before the gateway should be rich in decisions.
+</p>
+<p>
+ The documentation of the decision point can be done in table format.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-68Th4UZYizWD_CWSKyd3iw" name="review_decision_point_table,_H0NM8Ht0Ed2obd5av1OT7w" guid="-68Th4UZYizWD_CWSKyd3iw">
+ <refinedDescription><a id="XE_decision_point_table__review" name="XE_decision_point_table__review"></a>See the step description&nbsp;below.</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Jj9nvyH0gVrdCHxKpOws0A" name="decision_point_table,_H0NM8nt0Ed2obd5av1OT7w" guid="-Jj9nvyH0gVrdCHxKpOws0A">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-FWD_oEKFs78KJKJ_KSHXHw" name="business_process_map,_H0NM83t0Ed2obd5av1OT7w" guid="-FWD_oEKFs78KJKJ_KSHXHw">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Zt7Ibx5DM49KKxndcqRTtw" name="define_discovery_roadmap,_JbeFsHt0Ed2obd5av1OT7w" guid="-Zt7Ibx5DM49KKxndcqRTtw">
+ <refinedDescription><p>
+ There are two dimensions to consider when preparing the rule discovery activi-ties or roadmap:
+</p>
+<ul>
+ <li>
+ The type of source for rule harvesting
+ </li>
+ <li>
+ The type of analysis used by the project team: use case approach, busi-ness process modeling, mission policies
+ analysis
+ </li>
+</ul>
+<p>
+ Tony Morgan in his book "Business Rules and Information Systems: Aligning IT with Business Goals" proposes the
+ following discovery processed according to the different source above:
+</p>
+<ul>
+ <li>
+ The static analysis process uses reading and highlighting the rules within documentation. The elicitation is based
+ on reading session completed with Question / Answer workshop sessions
+ </li>
+ <li>
+ Interactive involves a Subject Matter Expert who has the knowledge of the business process and the decisions to
+ take to process a given business event.The process will be done by using elicitation workshop
+ </li>
+ <li>
+ Automated involve using a computer and special application to search for rule statement within procedure code, SQL
+ procedures, code listing... Code review should always be complemented by workshop sessions for Q&amp;A.<br />
+ </li>
+</ul>
+<p>
+ So for each decision point within the DP table do the following steps&nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-rLfn7xRB2TQqbODEHjDh-g" name="rule_discovery_roadmap,_JbeFsnt0Ed2obd5av1OT7w" guid="-rLfn7xRB2TQqbODEHjDh-g">
+ <refinedDescription><a id="XE_rule_discovery__roadmap" name="XE_rule_discovery__roadmap"></a>For each decision point we can complete the
+information about the discovery roadmap and plan. The following table format can be used as template.<br
+class="ISISGuidance" style="MARGIN: 3pt 0cm 3pt 36pt" /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Z6HScOkPIosgyp7UCf6Qlg" name="organise_workshop,_LIaIoHt0Ed2obd5av1OT7w" guid="-Z6HScOkPIosgyp7UCf6Qlg">
+ <refinedDescription><a id="XE_workshop__organize" name="XE_workshop__organize"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ To make the better use of the development and business team's time it is important to plan in advance the workshop
+ sessions and to clearly state what is in the agenda. We recommend organizing the day in two parts:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Do morning discovery workshop using elicitation techniques with the project stakeholders and subject matter expert.
+ During the&nbsp;rule harvesting phase the analyst team may want to use the rule template document to enter the rule
+ description and use some simple diagramming techniques to define the business entities (A good tool is the UML
+ class diagram but without the details of the methods)
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Second part of the day is used by&nbsp;the analyst and development team to perform analysis activities and later on
+ to author the rules.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ As explained in <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/concepts/cycle_approach_7FA44D8F.html"
+ guid="_ftAoIAjrEdyj5bYZ0eCR5g">Cycle Approach to Rules Development</a> the discovery workshops are in phase 1, 2, and
+ 3, but with different frequency of occurrence. Phase 1 and 2, the workshops can be set every morning, but starting on
+ phase 3 it could happen every two days or more (but never more than a week to keep the focus and efficiency in the
+ process).<br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The team should verify to have access to a dedicated meeting room with white boards, pencils, paper; post it, and
+ potentially a UML tool to quickly develop diagrams..
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-CdOZnJTJqXUWqZwWTv00YA" name="discovery_workshop_itinerary,_LIaIoXt0Ed2obd5av1OT7w" guid="-CdOZnJTJqXUWqZwWTv00YA">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-00teH0OUZQu5a2dSdjcT0g" name="execute_rule_discovery_roadmap,_ac8CoHt0Ed2obd5av1OT7w" guid="-00teH0OUZQu5a2dSdjcT0g">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-oMh2j3Q0H1ko6v__BoxY0Q" name="business_terms_glossary,_ac8CoXt0Ed2obd5av1OT7w" guid="-oMh2j3Q0H1ko6v__BoxY0Q">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-WnGCuUFJzEEm0quNf1yoRg" name="rule_description_doc,_ac8Cont0Ed2obd5av1OT7w" guid="-WnGCuUFJzEEm0quNf1yoRg">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-TyRUd1xh4OgmE7l9ZXFTCg" name="conceptual_data_model,_ac8Co3t0Ed2obd5av1OT7w" guid="-TyRUd1xh4OgmE7l9ZXFTCg">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-dUUjRXpEQ7U-x2t9WG3nXg" name="business_event_description,_h4FMVlmSEeCcpdiAcH0w-w" guid="-dUUjRXpEQ7U-x2t9WG3nXg">
+ <refinedDescription><p>
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 9.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">Trigger
+ for the execution of a business process.</span> The processing of a business event can be done manually or using
+ software products and applications. Some decisions need to be done on the event for example to accept/ reject it or to
+ initiate some business processes. Those decisions can be implemented using a rule engine technology.
+</p>
+<p>
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 9.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">The
+ following list gives some examples of business event:</span>
+</p>
+<ul>
+ <li>
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Claim is received</span>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Tax
+ form is filled</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Loan
+ application is received</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Car
+ is out of the chain</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Train
+ wheel goes in front of infrared sensor</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">RFID
+ read</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Wafer
+ is started within the Fab</span>
+ </div>
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/capabilitypatterns/discover_business_rules/model.xmi b/epf_prac_151/process.abrd.base/capabilitypatterns/discover_business_rules/model.xmi
index 0ab8360..5121d7a 100644
--- a/epf_prac_151/process.abrd.base/capabilitypatterns/discover_business_rules/model.xmi
+++ b/epf_prac_151/process.abrd.base/capabilitypatterns/discover_business_rules/model.xmi
@@ -2,21 +2,41 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__Z1Ts7ekEd-D7YZN9NgldQ" guid="__Z1Ts7ekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__Z1TtLekEd-D7YZN9NgldQ" id="-z9VrO6XKxLBPsLPbkRNDlg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jI_akVmSEeCcpdiAcH0w-w" id="-lm3kKBz3aGKgtfJqku4utw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jI_aklmSEeCcpdiAcH0w-w" id="-68Th4UZYizWD_CWSKyd3iw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jI_ak1mSEeCcpdiAcH0w-w" id="-Jj9nvyH0gVrdCHxKpOws0A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jI_alFmSEeCcpdiAcH0w-w" id="-FWD_oEKFs78KJKJ_KSHXHw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jI_alVmSEeCcpdiAcH0w-w" id="-Zt7Ibx5DM49KKxndcqRTtw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jI_allmSEeCcpdiAcH0w-w" id="-rLfn7xRB2TQqbODEHjDh-g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jJJLkFmSEeCcpdiAcH0w-w" id="-Z6HScOkPIosgyp7UCf6Qlg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jJJLkVmSEeCcpdiAcH0w-w" id="-CdOZnJTJqXUWqZwWTv00YA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jJJLklmSEeCcpdiAcH0w-w" id="-00teH0OUZQu5a2dSdjcT0g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jJJLk1mSEeCcpdiAcH0w-w" id="-oMh2j3Q0H1ko6v__BoxY0Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jJSVgFmSEeCcpdiAcH0w-w" id="-WnGCuUFJzEEm0quNf1yoRg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jJSVgVmSEeCcpdiAcH0w-w" id="-TyRUd1xh4OgmE7l9ZXFTCg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_jJSVglmSEeCcpdiAcH0w-w" id="-dUUjRXpEQ7U-x2t9WG3nXg" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_40DokHqkEd2o_5d3MWaNxQ" name="discover_business_rules" guid="_40DokHqkEd2o_5d3MWaNxQ">
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Q2X4YXtxEd2tkbw8c1Rm7g" name="rule_analyst" guid="_Q2X4YXtxEd2tkbw8c1Rm7g" presentationName="Rule Analyst" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ" modifies="_H0NM8nt0Ed2obd5av1OT7w _JbeFsnt0Ed2obd5av1OT7w _ac8CoXt0Ed2obd5av1OT7w _ac8Cont0Ed2obd5av1OT7w _ac8Co3t0Ed2obd5av1OT7w" responsibleFor="_ac8Co3t0Ed2obd5av1OT7w _ac8Cont0Ed2obd5av1OT7w _JbeFsnt0Ed2obd5av1OT7w _H0NM8nt0Ed2obd5av1OT7w">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Q2X4YntxEd2tkbw8c1Rm7g" name="business_analyst" guid="_Q2X4YntxEd2tkbw8c1Rm7g" presentationName="Business Analyst" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Q2X4ZHtxEd2tkbw8c1Rm7g" name="use_case_model" guid="_Q2X4ZHtxEd2tkbw8c1Rm7g" presentationName="Use-Case Model" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Q2X4ZHtxEd2tkbw8c1Rm7g" name="use_case_model" guid="_Q2X4ZHtxEd2tkbw8c1Rm7g" presentationName="Use-Case Model" briefDescription="This artifact captures a model of the intended functions and environment of the system and serves as a contract between the customer and the team." isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ELiLsD3hEd-rQL4FfV6WbQ" name="identify_decision_point" guid="_ELiLsD3hEd-rQL4FfV6WbQ" presentationName="Identify Decision Points" superActivities="_40DokXqkEd2o_5d3MWaNxQ" output="_H0NM8nt0Ed2obd5av1OT7w">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ELiLsD3hEd-rQL4FfV6WbQ" name="identify_decision_point" guid="_ELiLsD3hEd-rQL4FfV6WbQ" presentationName="Identify Decision Points" briefDescription="Decision points are points of variability and decision in a business process. The goal of this task is to list the potential decision points in scope for the project." superActivities="_40DokXqkEd2o_5d3MWaNxQ" output="_H0NM8nt0Ed2obd5av1OT7w _h4FMVlmSEeCcpdiAcH0w-w">
+ <presentation xmi:id="-lm3kKBz3aGKgtfJqku4utw" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-lm3kKBz3aGKgtfJqku4utw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yNUigIMUEd-68ahhmSUqHw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_A2d5sCyQEd-ER8gMc_Ftrw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_H0NM8Ht0Ed2obd5av1OT7w" name="review_decision_point_table" guid="_H0NM8Ht0Ed2obd5av1OT7w" presentationName="Review Decision Points Table, Business Process Map, Use Case Model" superActivities="_40DokXqkEd2o_5d3MWaNxQ" isSynchronizedWithSource="false" additionallyPerformedBy="_H0NM8Xt0Ed2obd5av1OT7w _Q2X4YntxEd2tkbw8c1Rm7g" mandatoryInput="_H0NM8nt0Ed2obd5av1OT7w" optionalInput="_H0NM83t0Ed2obd5av1OT7w _Q2X4ZHtxEd2tkbw8c1Rm7g" output="_H0NM8nt0Ed2obd5av1OT7w" performedPrimarilyBy="_Q2X4YXtxEd2tkbw8c1Rm7g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_H0NM8Ht0Ed2obd5av1OT7w" name="review_decision_point_table" guid="_H0NM8Ht0Ed2obd5av1OT7w" presentationName="Review Decision Point Table, Business Process Map, Use Case Model" briefDescription="After the business modeling activity of the Inception Phase the project team should have a decision point table document as a source for the rule discovery phase. A review of each decision point is needed. If this table is not present the team can start by the current business process description and then layouts this DP table." superActivities="_40DokXqkEd2o_5d3MWaNxQ" isSynchronizedWithSource="false" mandatoryInput="_H0NM83t0Ed2obd5av1OT7w" optionalInput="_Q2X4ZHtxEd2tkbw8c1Rm7g _H0NM8nt0Ed2obd5av1OT7w" output="_H0NM8nt0Ed2obd5av1OT7w">
+ <presentation xmi:id="-68Th4UZYizWD_CWSKyd3iw" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-68Th4UZYizWD_CWSKyd3iw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Fpgz4HqsEd2o_5d3MWaNxQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWzAjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_sruWzQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_XA_IIHrPEd2o_5d3MWaNxQ"/>
@@ -25,28 +45,33 @@
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_1KxREHrNEd2o_5d3MWaNxQ"/>
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_sruWzgjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_H0NM8Xt0Ed2obd5av1OT7w" name="subject_matter_expert" guid="_H0NM8Xt0Ed2obd5av1OT7w" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_H0NM8nt0Ed2obd5av1OT7w" name="decision_point_table" guid="_H0NM8nt0Ed2obd5av1OT7w" presentationName="Decision Point Table" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <presentation xmi:id="-Jj9nvyH0gVrdCHxKpOws0A" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-Jj9nvyH0gVrdCHxKpOws0A"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_H0NM83t0Ed2obd5av1OT7w" name="business_process_map" guid="_H0NM83t0Ed2obd5av1OT7w" presentationName="Business Process Map" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_H0NM83t0Ed2obd5av1OT7w" name="business_process_map" guid="_H0NM83t0Ed2obd5av1OT7w" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <presentation xmi:id="-FWD_oEKFs78KJKJ_KSHXHw" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-FWD_oEKFs78KJKJ_KSHXHw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_JbeFsHt0Ed2obd5av1OT7w" name="define_discovery_roadmap" guid="_JbeFsHt0Ed2obd5av1OT7w" presentationName="Define Rule Discovery Roadmap" superActivities="_40DokXqkEd2o_5d3MWaNxQ" linkToPredecessor="_KKtxUHt0Ed2obd5av1OT7w" isSynchronizedWithSource="false" additionallyPerformedBy="_JbeFsXt0Ed2obd5av1OT7w _Q2X4YntxEd2tkbw8c1Rm7g" mandatoryInput="_H0NM8nt0Ed2obd5av1OT7w" optionalInput="_Q2X4ZHtxEd2tkbw8c1Rm7g _H0NM83t0Ed2obd5av1OT7w" output="_JbeFsnt0Ed2obd5av1OT7w" performedPrimarilyBy="_Q2X4YXtxEd2tkbw8c1Rm7g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_JbeFsHt0Ed2obd5av1OT7w" name="define_discovery_roadmap" guid="_JbeFsHt0Ed2obd5av1OT7w" presentationName="Define Discovery Roadmap" briefDescription="The definition of the discovery roadmap is an important step to understand how the development team will extract the rules from the different kind of sources. There are multiple types of roadmaps according to the different starting points and rule sources." superActivities="_40DokXqkEd2o_5d3MWaNxQ" linkToPredecessor="_KKtxUHt0Ed2obd5av1OT7w" isSynchronizedWithSource="false" mandatoryInput="_H0NM8nt0Ed2obd5av1OT7w" optionalInput="_Q2X4ZHtxEd2tkbw8c1Rm7g _H0NM83t0Ed2obd5av1OT7w _h4FMWVmSEeCcpdiAcH0w-w" output="_JbeFsnt0Ed2obd5av1OT7w">
+ <presentation xmi:id="-Zt7Ibx5DM49KKxndcqRTtw" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-Zt7Ibx5DM49KKxndcqRTtw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWygjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxgjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-Ak_E6i3qbz4NMG7ynyf4DA#_srklyQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-Ak_E6i3qbz4NMG7ynyf4DA#_srklxwjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_KKtxUHt0Ed2obd5av1OT7w" guid="_KKtxUHt0Ed2obd5av1OT7w" pred="_H0NM8Ht0Ed2obd5av1OT7w"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_JbeFsXt0Ed2obd5av1OT7w" name="project_manager" guid="_JbeFsXt0Ed2obd5av1OT7w" presentationName="Project Manager" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ" modifies="_LIaIoXt0Ed2obd5av1OT7w">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_JbeFsnt0Ed2obd5av1OT7w" name="rule_discovery_roadmap" guid="_JbeFsnt0Ed2obd5av1OT7w" presentationName="Rule discovery roadmap" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_JbeFsnt0Ed2obd5av1OT7w" name="rule_discovery_roadmap" guid="_JbeFsnt0Ed2obd5av1OT7w" presentationName="Rule Discovery Roadmap" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <presentation xmi:id="-rLfn7xRB2TQqbODEHjDh-g" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-rLfn7xRB2TQqbODEHjDh-g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWygjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2QjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1QjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_LIaIoHt0Ed2obd5av1OT7w" name="organise_workshop" guid="_LIaIoHt0Ed2obd5av1OT7w" presentationName="Organize Workshop" superActivities="_40DokXqkEd2o_5d3MWaNxQ" linkToPredecessor="_L4_RAHt0Ed2obd5av1OT7w" additionallyPerformedBy="_Q2X4YntxEd2tkbw8c1Rm7g _Q2X4YXtxEd2tkbw8c1Rm7g" mandatoryInput="_JbeFsnt0Ed2obd5av1OT7w" output="_LIaIoXt0Ed2obd5av1OT7w" performedPrimarilyBy="_JbeFsXt0Ed2obd5av1OT7w">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_LIaIoHt0Ed2obd5av1OT7w" name="organise_workshop" guid="_LIaIoHt0Ed2obd5av1OT7w" presentationName="Organize Workshop" briefDescription="In case of human source for the rule the team needs to organize elicitation workshops" superActivities="_40DokXqkEd2o_5d3MWaNxQ" linkToPredecessor="_L4_RAHt0Ed2obd5av1OT7w" mandatoryInput="_JbeFsnt0Ed2obd5av1OT7w" output="_LIaIoXt0Ed2obd5av1OT7w">
+ <presentation xmi:id="-Z6HScOkPIosgyp7UCf6Qlg" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-Z6HScOkPIosgyp7UCf6Qlg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0QjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWxAjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-ffYBUOhR5mZssG9eZxktmg#_sruWyQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-ffYBUOhR5mZssG9eZxktmg#_sruWxwjqEdyj5bYZ0eCR5g"/>
@@ -56,9 +81,13 @@
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_L4_RAHt0Ed2obd5av1OT7w" guid="_L4_RAHt0Ed2obd5av1OT7w" pred="_JbeFsHt0Ed2obd5av1OT7w"/>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_LIaIoXt0Ed2obd5av1OT7w" name="discovery_workshop_itinerary" guid="_LIaIoXt0Ed2obd5av1OT7w" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <presentation xmi:id="-CdOZnJTJqXUWqZwWTv00YA" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-CdOZnJTJqXUWqZwWTv00YA"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ac8CoHt0Ed2obd5av1OT7w" name="execute_rule_discovery_roadmap" guid="_ac8CoHt0Ed2obd5av1OT7w" presentationName="Execute rule discovery roadmap" hasMultipleOccurrences="true" superActivities="_40DokXqkEd2o_5d3MWaNxQ" isRepeatable="true" linkToPredecessor="_a7e_0Ht0Ed2obd5av1OT7w" additionallyPerformedBy="_Q2X4YntxEd2tkbw8c1Rm7g _H0NM8Xt0Ed2obd5av1OT7w" mandatoryInput="_H0NM83t0Ed2obd5av1OT7w _H0NM8nt0Ed2obd5av1OT7w" optionalInput="_LIaIoXt0Ed2obd5av1OT7w" output="_ac8CoXt0Ed2obd5av1OT7w _ac8Cont0Ed2obd5av1OT7w _ac8Co3t0Ed2obd5av1OT7w" performedPrimarilyBy="_Q2X4YXtxEd2tkbw8c1Rm7g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ac8CoHt0Ed2obd5av1OT7w" name="execute_rule_discovery_roadmap" guid="_ac8CoHt0Ed2obd5av1OT7w" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." hasMultipleOccurrences="true" superActivities="_40DokXqkEd2o_5d3MWaNxQ" isRepeatable="true" linkToPredecessor="_a7e_0Ht0Ed2obd5av1OT7w" mandatoryInput="_H0NM83t0Ed2obd5av1OT7w _H0NM8nt0Ed2obd5av1OT7w" optionalInput="_LIaIoXt0Ed2obd5av1OT7w" output="_ac8CoXt0Ed2obd5av1OT7w _ac8Cont0Ed2obd5av1OT7w _ac8Co3t0Ed2obd5av1OT7w">
+ <presentation xmi:id="-00teH0OUZQu5a2dSdjcT0g" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-00teH0OUZQu5a2dSdjcT0g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
@@ -66,16 +95,37 @@
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_a7e_0Ht0Ed2obd5av1OT7w" guid="_a7e_0Ht0Ed2obd5av1OT7w" pred="_LIaIoHt0Ed2obd5av1OT7w"/>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ac8CoXt0Ed2obd5av1OT7w" name="business_terms_glossary" guid="_ac8CoXt0Ed2obd5av1OT7w" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ac8CoXt0Ed2obd5av1OT7w" name="business_terms_glossary" guid="_ac8CoXt0Ed2obd5av1OT7w" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <presentation xmi:id="-oMh2j3Q0H1ko6v__BoxY0Q" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-oMh2j3Q0H1ko6v__BoxY0Q"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ac8Cont0Ed2obd5av1OT7w" name="rule_description_doc" guid="_ac8Cont0Ed2obd5av1OT7w" presentationName="Rule Description Document" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ac8Cont0Ed2obd5av1OT7w" name="rule_description_doc" guid="_ac8Cont0Ed2obd5av1OT7w" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <presentation xmi:id="-WnGCuUFJzEEm0quNf1yoRg" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-WnGCuUFJzEEm0quNf1yoRg"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ac8Co3t0Ed2obd5av1OT7w" name="conceptual_data_model" guid="_ac8Co3t0Ed2obd5av1OT7w" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <presentation xmi:id="-TyRUd1xh4OgmE7l9ZXFTCg" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-TyRUd1xh4OgmE7l9ZXFTCg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_40DokXqkEd2o_5d3MWaNxQ" name="discover_business_rules" guid="_40DokXqkEd2o_5d3MWaNxQ" presentationName="Discover Business Rules" breakdownElements="_Q2X4YXtxEd2tkbw8c1Rm7g _Q2X4YntxEd2tkbw8c1Rm7g _Q2X4ZHtxEd2tkbw8c1Rm7g _ELiLsD3hEd-rQL4FfV6WbQ _H0NM8Ht0Ed2obd5av1OT7w _H0NM8Xt0Ed2obd5av1OT7w _H0NM8nt0Ed2obd5av1OT7w _H0NM83t0Ed2obd5av1OT7w _JbeFsHt0Ed2obd5av1OT7w _JbeFsXt0Ed2obd5av1OT7w _JbeFsnt0Ed2obd5av1OT7w _LIaIoHt0Ed2obd5av1OT7w _LIaIoXt0Ed2obd5av1OT7w _ac8CoHt0Ed2obd5av1OT7w _ac8CoXt0Ed2obd5av1OT7w _ac8Cont0Ed2obd5av1OT7w _ac8Co3t0Ed2obd5av1OT7w">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_h4FMVlmSEeCcpdiAcH0w-w" name="business_event_description" guid="_h4FMVlmSEeCcpdiAcH0w-w" presentationName="Business Event Description" briefDescription="Logging the business events source of business process execution helps to drive rule discovery." isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <methodElementProperty xmi:id="_h4FMV1mSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-dUUjRXpEQ7U-x2t9WG3nXg" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-dUUjRXpEQ7U-x2t9WG3nXg"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_HSrrgGhiEd-FVuzXjnvIWA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_h4FMWVmSEeCcpdiAcH0w-w" name="use_case" guid="_h4FMWVmSEeCcpdiAcH0w-w" presentationName="Use Case" briefDescription="This artifact captures the system behavior to yield an observable result of value to those who interact with the system." isPlanned="false" superActivities="_40DokXqkEd2o_5d3MWaNxQ">
+ <methodElementProperty xmi:id="_h4FMWlmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kNwINk1Edq2Q8qZoWbvGA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_JLOiIMNvEdu2IdAIaWZyAw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_3Y3XUI5fEdyO5aWob1UGDA"/>
+ <WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_40DokXqkEd2o_5d3MWaNxQ" name="discover_business_rules" guid="_40DokXqkEd2o_5d3MWaNxQ" presentationName="Discover Business Rules" breakdownElements="_Q2X4ZHtxEd2tkbw8c1Rm7g _ELiLsD3hEd-rQL4FfV6WbQ _H0NM8Ht0Ed2obd5av1OT7w _H0NM8nt0Ed2obd5av1OT7w _H0NM83t0Ed2obd5av1OT7w _JbeFsHt0Ed2obd5av1OT7w _JbeFsnt0Ed2obd5av1OT7w _LIaIoHt0Ed2obd5av1OT7w _LIaIoXt0Ed2obd5av1OT7w _ac8CoHt0Ed2obd5av1OT7w _ac8CoXt0Ed2obd5av1OT7w _ac8Cont0Ed2obd5av1OT7w _ac8Co3t0Ed2obd5av1OT7w _h4FMVlmSEeCcpdiAcH0w-w _h4FMWVmSEeCcpdiAcH0w-w">
<presentation xmi:id="-z9VrO6XKxLBPsLPbkRNDlg" href="uma://-z9VrO6XKxLBPsLPbkRNDlg#-z9VrO6XKxLBPsLPbkRNDlg"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.abrd.base/deliveryprocesses/abrd_process/content.xmi b/epf_prac_151/process.abrd.base/deliveryprocesses/abrd_process/content.xmi
index ca74fbd..b9b7d6d 100644
--- a/epf_prac_151/process.abrd.base/deliveryprocesses/abrd_process/content.xmi
+++ b/epf_prac_151/process.abrd.base/deliveryprocesses/abrd_process/content.xmi
@@ -23,4 +23,7749 @@
<mainDescription>Agile Business Rule Development main process</mainDescription>
<purpose>Develop a business application&nbsp;using the business rules approach and agile iterative development.</purpose>
</org.eclipse.epf.uma:DeliveryProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-hSvA_8i1JXnAg_ktO4yhVw" name="identify_decision_point,_QYBzMD3gEd-rQL4FfV6WbQ" guid="-hSvA_8i1JXnAg_ktO4yhVw">
+ <refinedDescription><p>
+ A <a class="elementLink" href="./../../practice.tech.abrd.base/guidances/termdefinitions/decision_point_B1C5EFE2.html"
+ guid="_XUyFIEb1EdySHMdInS9eGA">Decision point</a>&nbsp;represents an activity in a business process where decisions are
+ done. When looking at a task description it is important to search for mental thinking verb, most of the time there is
+ a set of knowledge to apply to execute this task, which leads to decision. This could be human knowledge or business
+ logic implementation in a software component. The type of decision will most likely be a reject or accept of the
+ business event or flag it for future processing downstream in the business process. The decision may also include some
+ computational expressions to assign value to attribute of the business transaction. Therefore to find decision point in
+ a business process or use case description start by searching for mental, action verb like analyze, check, validate,
+ evaluate, verify, assess, ...
+</p>
+<p>
+ In a BPMN process diagram a business process analyst and/ or a rule analyst can annotate the process to highlight
+ decision point in the process.
+</p>
+<p>
+ <img height="363" alt="" src="resources/FindDecisionPoint.bmp" width="1572" />
+</p>
+<p>
+ The search for decision point, attached to a business process description (done with use case or with BPMN does not
+ matter), helps to drive the rule analysis, and helps the business to focus at the business rule&nbsp;enforcement.
+ If&nbsp;the business team misses where the rule should be enforced, he can spend months defining business rules which
+ IT does not understand where to deploy them. The decision point can help drive the discovery of the business policies
+ and rules, for an implementation point of view, as well as a way to organize the top down approach. A decision point
+ support multiple rules, and if implemented with a rule engine, the rules are packaged as rule set.
+</p>
+<p>
+ Also finding the decision points involves studying<br />
+ • Which use cases/scenarios represent decisions - At what steps in the use case is a decision made?<br />
+ • Which requirements constitute rich set of decisions?<br />
+ • Which steps/cases/requirements represent significant complexity?<br />
+ • Which steps/cases/requirements are most subject to change?<br />
+ • Look for decision diamonds in the flow charts and activity diagrams, the gateway by itself route the data to the next
+ activity, but the activity before the gateway should be rich in decisions.
+</p>
+<p>
+ The documentation of the decision point can be done in table format.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-EyvRETbaInP9YwVRsjUmpg" name="review_decision_point_table,_nIvp2MVVEd2pfdXgw7I2qQ" guid="-EyvRETbaInP9YwVRsjUmpg">
+ <refinedDescription><a id="XE_decision_point_table__review" name="XE_decision_point_table__review"></a>See the step description&nbsp;below.</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-7Qhv3MVOtdt02aO-ujeUXQ" name="decision_point_table,_nIvp2cVVEd2pfdXgw7I2qQ" guid="-7Qhv3MVOtdt02aO-ujeUXQ">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-wn8vCP9iknXfxQNa_Gt3Zg" name="business_process_map,_nIvp1sVVEd2pfdXgw7I2qQ" guid="-wn8vCP9iknXfxQNa_Gt3Zg">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-SZIhc8oXvpac5M1fKbXgTA" name="define_discovery_roadmap,_nIvp3MVVEd2pfdXgw7I2qQ" guid="-SZIhc8oXvpac5M1fKbXgTA">
+ <refinedDescription><p>
+ There are two dimensions to consider when preparing the rule discovery activi-ties or roadmap:
+</p>
+<ul>
+ <li>
+ The type of source for rule harvesting
+ </li>
+ <li>
+ The type of analysis used by the project team: use case approach, busi-ness process modeling, mission policies
+ analysis
+ </li>
+</ul>
+<p>
+ Tony Morgan in his book "Business Rules and Information Systems: Aligning IT with Business Goals" proposes the
+ following discovery processed according to the different source above:
+</p>
+<ul>
+ <li>
+ The static analysis process uses reading and highlighting the rules within documentation. The elicitation is based
+ on reading session completed with Question / Answer workshop sessions
+ </li>
+ <li>
+ Interactive involves a Subject Matter Expert who has the knowledge of the business process and the decisions to
+ take to process a given business event.The process will be done by using elicitation workshop
+ </li>
+ <li>
+ Automated involve using a computer and special application to search for rule statement within procedure code, SQL
+ procedures, code listing... Code review should always be complemented by workshop sessions for Q&amp;A.<br />
+ </li>
+</ul>
+<p>
+ So for each decision point within the DP table do the following steps&nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-z6-Qx7OJfj-Yq25AioSjCg" name="rule_discovery_roadmap,_nIvp1MVVEd2pfdXgw7I2qQ" guid="-z6-Qx7OJfj-Yq25AioSjCg">
+ <refinedDescription><a id="XE_rule_discovery__roadmap" name="XE_rule_discovery__roadmap"></a>For each decision point we can complete the
+information about the discovery roadmap and plan. The following table format can be used as template.<br
+class="ISISGuidance" style="MARGIN: 3pt 0cm 3pt 36pt" /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-FbRsIZayJhCaFmbyRB96Cg" name="organise_workshop,_nIvp4MVVEd2pfdXgw7I2qQ" guid="-FbRsIZayJhCaFmbyRB96Cg">
+ <refinedDescription><a id="XE_workshop__organize" name="XE_workshop__organize"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ To make the better use of the development and business team's time it is important to plan in advance the workshop
+ sessions and to clearly state what is in the agenda. We recommend organizing the day in two parts:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Do morning discovery workshop using elicitation techniques with the project stakeholders and subject matter expert.
+ During the&nbsp;rule harvesting phase the analyst team may want to use the rule template document to enter the rule
+ description and use some simple diagramming techniques to define the business entities (A good tool is the UML
+ class diagram but without the details of the methods)
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Second part of the day is used by&nbsp;the analyst and development team to perform analysis activities and later on
+ to author the rules.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ As explained in <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/concepts/cycle_approach_7FA44D8F.html"
+ guid="_ftAoIAjrEdyj5bYZ0eCR5g">Cycle Approach to Rules Development</a> the discovery workshops are in phase 1, 2, and
+ 3, but with different frequency of occurrence. Phase 1 and 2, the workshops can be set every morning, but starting on
+ phase 3 it could happen every two days or more (but never more than a week to keep the focus and efficiency in the
+ process).<br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The team should verify to have access to a dedicated meeting room with white boards, pencils, paper; post it, and
+ potentially a UML tool to quickly develop diagrams..
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-G5nrokl8FZiZW26GR8U4Fg" name="discovery_workshop_itinerary,_nIvp48VVEd2pfdXgw7I2qQ" guid="-G5nrokl8FZiZW26GR8U4Fg">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-rQeo3KBsjTpEofLhWWoCHg" name="execute_rule_discovery_roadmap,_nIvp1cVVEd2pfdXgw7I2qQ" guid="-rQeo3KBsjTpEofLhWWoCHg">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-SVG8fBamP9jI0gLGSNQYPg" name="business_terms_glossary,_nIvp18VVEd2pfdXgw7I2qQ" guid="-SVG8fBamP9jI0gLGSNQYPg">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Ol-Ismqi_vwu93DuUULISw" name="rule_description_doc,_nIvp58VVEd2pfdXgw7I2qQ" guid="-Ol-Ismqi_vwu93DuUULISw">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-xywJ9rs6yDU3S-RR7R6DHw" name="conceptual_data_model,_nIvp08VVEd2pfdXgw7I2qQ" guid="-xywJ9rs6yDU3S-RR7R6DHw">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-nWwIrDx_rgbWN_dCjIPeGg" name="business_event_description,_uJON1FmSEeCcpdiAcH0w-w" guid="-nWwIrDx_rgbWN_dCjIPeGg">
+ <refinedDescription><p>
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 9.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">Trigger
+ for the execution of a business process.</span> The processing of a business event can be done manually or using
+ software products and applications. Some decisions need to be done on the event for example to accept/ reject it or to
+ initiate some business processes. Those decisions can be implemented using a rule engine technology.
+</p>
+<p>
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 9.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">The
+ following list gives some examples of business event:</span>
+</p>
+<ul>
+ <li>
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Claim is received</span>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Tax
+ form is filled</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Loan
+ application is received</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Car
+ is out of the chain</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Train
+ wheel goes in front of infrared sensor</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">RFID
+ read</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Wafer
+ is started within the Fab</span>
+ </div>
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Zgt8ljNbGXKcbU4gzUCQrg" name="extract_rule_meaning,_s37aOcVVEd2pfdXgw7I2qQ" guid="-Zgt8ljNbGXKcbU4gzUCQrg">
+ <refinedDescription><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">During the elicitation activity the raw description of the rule uses business terms as used in common
+ language used by the people. This presents what the business users think about the way things are done in the company.
+ They are linking words with statements with all the different semantic attached to them. The first activity focuses on
+ analyzing this rule description&nbsp;to extract&nbsp;the business entities and terms used in a formal non ambiguous
+ fashion.&nbsp;</font></span>
+</p>
+<p>
+ We are discussing about Business Term here, as reference to a business concept used in daily business operations.They
+ are often found in different departments or refer to the same business concept from a different perspective: they are
+ synonyms. A term may describe business concept which will be mapped to a Class, a characteristic of a business entity
+ which will be mapped to attribute of a class, and sometime a term may describe the way a business object behave, in
+ that last case it will be mapped within method of a final state machine.
+</p>
+<p>
+ The second concept presented in the analysis of rule is the Fact. Fact is a combination of terms that describes what
+ business people know about their business. It connects terms into sensible business relevant observations.<br
+ style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple" />
+ As stated by the SBVR specification meaning is built of concepts, questions and propositions. the concepts will build
+ our underlying data model used by the executable rules, and the proposition will structure the data model and can also
+ be mapped to rules.<br />
+</p>
+<p
+style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple">
+ All these informations&nbsp;help to build a&nbsp;first logical data model used to build the underlying object
+ model&nbsp;used by the rules. We can use UML tool to design a class diagram, generates java code and import such code
+ in the rule IDE.<br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-NjDm5kyrlZVxH1HwaGoVFA" name="rule_description_doc,_s37aOMVVEd2pfdXgw7I2qQ" guid="-NjDm5kyrlZVxH1HwaGoVFA">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-LZfO28SzpOMkRDb62aUppg" name="fact_model,_s3yQQcVVEd2pfdXgw7I2qQ" guid="-LZfO28SzpOMkRDb62aUppg">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-cAqcd_rDIyDggEFNkpOafA" name="logical_data_model,_s37aMcVVEd2pfdXgw7I2qQ" guid="-cAqcd_rDIyDggEFNkpOafA">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-TMElbWb1oCm06CVVbtGziA" name="transform_rules,_s37aOsVVEd2pfdXgw7I2qQ" guid="-TMElbWb1oCm06CVVbtGziA">
+ <keyConsiderations>This activity will also be done during the implementation of the rule set, but it is started during the analysis, so we are
+detailing it in this context.</keyConsiderations>
+ <refinedDescription><p>
+ Rule Analyst has to study the rule discovered and try to transform it so that the implementation and the management of
+ the rule will be more easy. This includes transforming the rule in atomic element using a syntax without ambiguity,
+ remove redundant rules, conflicting rules, and finally try to redefine the scope of the rule by searching by
+ non-handled cases.&nbsp;
+</p>
+<p>
+ At this stage rule analyst can build some rule template which&nbsp;are built from rules that have the same set of
+ conditions with some little variations: adding new value in test condition, or new condition.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-cldFzj8jYSiyDtkZGFpjQQ" name="build_test_scenario,_s37aO8VVEd2pfdXgw7I2qQ" guid="-cldFzj8jYSiyDtkZGFpjQQ">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-JMP5iTEzmgde5KqHrptXyA" name="synchronize_data_model,_s37aNcVVEd2pfdXgw7I2qQ" guid="-JMP5iTEzmgde5KqHrptXyA">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst needs to continuously verify that business terms used in rule statements are part of the logical data
+ model (classes/ attributes) and physical data model (PDM). The model exposed to the rule needs to get data from data
+ sources. If a concept is not in the data it has to be quickly handled and managed by the application architect.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst should be in continuous communication with the data model developer, responsible to develop the XML
+ schema or java model (or .Net), and the physical mapping to database.<br />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Part of most of the business application are the list of code, enumerated date or domain values. It is important to
+ well design how those data are defined, accessed by the application, and the rule authoring environment.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ It can be helpful for some major business term to define a mapping to a class-attribute, and if the BRMS supports this
+ function it is recommended to detail the "verbalization" of the business term.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<div align="center">
+ <table class="MsoNormalTable" style="WIDTH: 351pt; BORDER-COLLAPSE: collapse; mso-padding-alt: 0in 0in 0in 0in"
+ cellspacing="0" cellpadding="0" width="468" border="0">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes">
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: gray 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Business Term</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">OO mapping</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Verbalization</span></i>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LTV</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LoanApplication.ltv</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">The loan to value ratio</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in left 3.0in" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-f3XkJ0vY-f93Cugh2hUPag" name="decision_point_table,_z0dHecVVEd2pfdXgw7I2qQ" guid="-f3XkJ0vY-f93Cugh2hUPag">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-XJgsI3tf1RyfJOE8nXKyfA" name="business_process_map,_z0dHdsVVEd2pfdXgw7I2qQ" guid="-XJgsI3tf1RyfJOE8nXKyfA">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-FYiTjOVLhDDFiks9REzbWw" name="discovery_workshop_itinerary,_z0dHg8VVEd2pfdXgw7I2qQ" guid="-FYiTjOVLhDDFiks9REzbWw">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-I69B91Gv39Hsf4q9QC8gdw" name="execute_rule_discovery_roadmap,_z0dHdcVVEd2pfdXgw7I2qQ" guid="-I69B91Gv39Hsf4q9QC8gdw">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="--xaKhVngfn0TG7AUCYDE2Q" name="business_terms_glossary,_z0dHd8VVEd2pfdXgw7I2qQ" guid="--xaKhVngfn0TG7AUCYDE2Q">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ZxuH1YXgB-PGC8KKf8SqMA" name="rule_description_doc,_z0dHh8VVEd2pfdXgw7I2qQ" guid="-ZxuH1YXgB-PGC8KKf8SqMA">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-cQYuDYNpIetEa-A0wc2rMA" name="conceptual_data_model,_z0dHc8VVEd2pfdXgw7I2qQ" guid="-cQYuDYNpIetEa-A0wc2rMA">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-NBqg7ns9nlUev0xlKSBKVg" name="extract_rule_meaning,_9s4lK8VVEd2pfdXgw7I2qQ" guid="-NBqg7ns9nlUev0xlKSBKVg">
+ <refinedDescription><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">During the elicitation activity the raw description of the rule uses business terms as used in common
+ language used by the people. This presents what the business users think about the way things are done in the company.
+ They are linking words with statements with all the different semantic attached to them. The first activity focuses on
+ analyzing this rule description&nbsp;to extract&nbsp;the business entities and terms used in a formal non ambiguous
+ fashion.&nbsp;</font></span>
+</p>
+<p>
+ We are discussing about Business Term here, as reference to a business concept used in daily business operations.They
+ are often found in different departments or refer to the same business concept from a different perspective: they are
+ synonyms. A term may describe business concept which will be mapped to a Class, a characteristic of a business entity
+ which will be mapped to attribute of a class, and sometime a term may describe the way a business object behave, in
+ that last case it will be mapped within method of a final state machine.
+</p>
+<p>
+ The second concept presented in the analysis of rule is the Fact. Fact is a combination of terms that describes what
+ business people know about their business. It connects terms into sensible business relevant observations.<br
+ style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple" />
+ As stated by the SBVR specification meaning is built of concepts, questions and propositions. the concepts will build
+ our underlying data model used by the executable rules, and the proposition will structure the data model and can also
+ be mapped to rules.<br />
+</p>
+<p
+style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple">
+ All these informations&nbsp;help to build a&nbsp;first logical data model used to build the underlying object
+ model&nbsp;used by the rules. We can use UML tool to design a class diagram, generates java code and import such code
+ in the rule IDE.<br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-1EFb1j163vesKIPD-WKc_A" name="rule_description_doc,_9s4lKsVVEd2pfdXgw7I2qQ" guid="-1EFb1j163vesKIPD-WKc_A">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-30jW7XM9GTETWwegnerK-g" name="fact_model,_9s4lIcVVEd2pfdXgw7I2qQ" guid="-30jW7XM9GTETWwegnerK-g">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-QosjoU1KKqxnanfXEHADUQ" name="logical_data_model,_9s4lI8VVEd2pfdXgw7I2qQ" guid="-QosjoU1KKqxnanfXEHADUQ">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Jkw-vxUJt3NMdOu_yUsNgw" name="transform_rules,_9s4lLMVVEd2pfdXgw7I2qQ" guid="-Jkw-vxUJt3NMdOu_yUsNgw">
+ <keyConsiderations>This activity will also be done during the implementation of the rule set, but it is started during the analysis, so we are
+detailing it in this context.</keyConsiderations>
+ <refinedDescription><p>
+ Rule Analyst has to study the rule discovered and try to transform it so that the implementation and the management of
+ the rule will be more easy. This includes transforming the rule in atomic element using a syntax without ambiguity,
+ remove redundant rules, conflicting rules, and finally try to redefine the scope of the rule by searching by
+ non-handled cases.&nbsp;
+</p>
+<p>
+ At this stage rule analyst can build some rule template which&nbsp;are built from rules that have the same set of
+ conditions with some little variations: adding new value in test condition, or new condition.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-jD0SjTGEVGjAXwk-96CnBw" name="build_test_scenario,_9s4lLcVVEd2pfdXgw7I2qQ" guid="-jD0SjTGEVGjAXwk-96CnBw">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-pxSSUK3yjMwpuFplEiArVA" name="synchronize_data_model,_9s4lJ8VVEd2pfdXgw7I2qQ" guid="-pxSSUK3yjMwpuFplEiArVA">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst needs to continuously verify that business terms used in rule statements are part of the logical data
+ model (classes/ attributes) and physical data model (PDM). The model exposed to the rule needs to get data from data
+ sources. If a concept is not in the data it has to be quickly handled and managed by the application architect.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst should be in continuous communication with the data model developer, responsible to develop the XML
+ schema or java model (or .Net), and the physical mapping to database.<br />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Part of most of the business application are the list of code, enumerated date or domain values. It is important to
+ well design how those data are defined, accessed by the application, and the rule authoring environment.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ It can be helpful for some major business term to define a mapping to a class-attribute, and if the BRMS supports this
+ function it is recommended to detail the "verbalization" of the business term.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<div align="center">
+ <table class="MsoNormalTable" style="WIDTH: 351pt; BORDER-COLLAPSE: collapse; mso-padding-alt: 0in 0in 0in 0in"
+ cellspacing="0" cellpadding="0" width="468" border="0">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes">
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: gray 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Business Term</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">OO mapping</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Verbalization</span></i>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LTV</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LoanApplication.ltv</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">The loan to value ratio</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in left 3.0in" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-1hKEhTu7zfbuOyxxSBfTVA" name="determine_rule_implementation,_9s4lQMVVEd2pfdXgw7I2qQ" guid="-1hKEhTu7zfbuOyxxSBfTVA">
+ <refinedDescription><a id="XE_rule__determine_implementation" name="XE_rule__determine_implementation"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Project teams involved in BRMS deployment are often asking the following type of questions:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus a&nbsp;BPM?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ How do I decide what decisions should I put into a BRE?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus code?&nbsp;
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ There are definitively multiple variables which could influence the decision on where to implement rules. We can start
+ by looking at the BRMS value propositions, it should help to get a first set of variables:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Adaptability – Measure the ability to change the business logic easily. The motivation can be due to short deadline
+ constraint, or frequent small changes or important change that may occur every month or quarter.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Transparency – Represents the need to clearly implement the business logic as what was agreed upon the business
+ unit and the IT team, in a way that every parties understand the logic. This is leading to express the logic in
+ natural or close to natural language.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Auditability – Represents the ability to trace from the business motivation to the execution of the policy to
+ better understand what was the logic behind a decision.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Reusability – Need to share business logic across processes or applications and stay . consistent across
+ applications/transactions
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Manageability- This variable addresses the life cycle management of the business logic. Who writes what, and when,
+ and all the questions related to maintenance and evolutions of the rule-based service.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The purpose here is not to say it is not possible to support those variables in standard software development
+ practices, but more to find some good patterns on how to decide on where to implement the business logic.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ When looking at a business rules statement software engineer can see different possible choices of implementation like:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Data model: designing an object oriented object model involves supporting a lot of business rules. A statement like
+ a mortgage application can have a primary and a secondary borrower, will be supported by two classes and a 1 to 2
+ relationship. At the instantiation of those classes the control of the cardinality can be done in the application
+ logic, or the database, or the GUI structure.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Application code: implementing the logic in function, procedural code or methods in service layer or business
+ objects.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ BPM process flow, tasks or links: BPM tools are addressing business process efficiency issue specifically on "who
+ is involved", "when they should be involved". "what they need to do". BPM supports manual human and automated
+ actors. At a glance the business logic to implement in BPM is linked to people, task, and data to process within a
+ task. When supporting purely automated tasks BPM is orchestrating the application logic and services (BPEL engine).
+ BRMS complements BPM by adding the why to a BPM task, why it behaves a certain way, why this decision is done.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Rule engine: <span style="mso-spacerun: yes">&nbsp;</span>using predefined structure like if then else statement or
+ decision table, rule flow, decision tree, function, rule template or other high level language...
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Graphical user interface: <span style="mso-spacerun: yes">&nbsp;</span>using scripting language or server side code
+ in controller class it is possible to implement data validation type of business rules.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In the following paragraphs address each of different choices with their impact on the variables
+</p><br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in Data Model</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Rule which is controlling the structure of the model and the reference integrity
+ should be in the physical data model, the O/R mapping layer or on the domain object model.</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule setting constraint on relationship -
+ <span style="mso-spacerun: yes">&nbsp;</span>like a loan application could only have two borrowers</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule on the structure of the business
+ entities - like this attribute is part of this object</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following facts are based on a simple
+ user authentication problem, are well implemented in an object model and the supporting application code which
+ create the instance from the data (O/R mapping layer or DAO or service layer):</span>
+ </li>
+</ul>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of users who can login to the application</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of groups of user</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A User is part of a group</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group includes a list of Users</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group has one user reference who is the creator of the group</span>
+</p>
+<p>
+ Terms and facts and derived attributes&nbsp;are the primary constituents of data models and are represented in a UML
+ class diagram, and logical data model (entities/relationship model), or a physical data model.
+</p>
+<p>
+ <span style="mso-bidi-language: HE">The following table lists the impact of this implementation on the previously
+ defined variables</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 221.4pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very static implementation. A change in the constraints of the object model
+ impact, data persistence, logical data model, service and presentation layers. Change is managed on
+ a monthly or yearly basis</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Data model represented as UML classes diagram is doing a poor job to
+ communicate to business. Entities diagram represents a more high level representation of the domain
+ model, but forces the team to maintain the link between the implementation and the business
+ representation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tool, with a strict development process and
+ disciplines can help to trace back to the business motivation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Domain Object model can be designed as reusable. But in the reality each
+ application needs a view of the core business object model, and so part of the implemented
+ application will be to build those view.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tools and strict discipline can help maintain the
+ business logic.</font></span>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in application code</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Implementing business rule in application code is
+ currently the most common way the IT developer is doing it. The major justifications are performance and flexibility of
+ the coding language. Using hard coded if/then/else statements isn't too flexible, but in the hands of a top notch
+ programmer it can be very fast and arguably as fast as or faster than a rule engine. Assuming the programmer has
+ unlimited time to optimize the execution for a fixed set of rules. If the ruleset changes frequently and the system
+ can't tolerate a big drop in performance, than a rule engine is the solution.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following example of business rules may be
+ easily implemented in code:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span class="ISISCodeParagraphChar"><font face="Courier">verify in each items the customer bought since he is customer
+ with us there is at least one article of type T so that we can propose the new product Y with X % of discount, except
+ if the customer is from the state of New York or New Jersey</font></span><span
+ style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">We can implement this in a method which loops on
+ the articles bought by a given customer and do the search. At a first analysis, navigating in a collection of objects
+ and testing multiples conditions on them is easy to implement using the power of programming language.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One thing interesting will be the hard coding of
+ the value of New York, New Jersey... If this logic change we need to add if statements in the code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Other type of rules are related to the control of
+ the execution of a set of "services" to support specific use case. Dispatching, orchestration, data manipulation, … are
+ better candidate to be implemented in application code. Those rules are more static, often more complex, and
+ definitively linked to context of execution. The context may be too complex to expose to a rule engine.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Orchestration are now very well supported by
+ BPM-BPEL engine because the developer needs to add flexibility on the service selection and invocation.<span
+ style="mso-spacerun: yes">&nbsp;</span></span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The evaluation of the important variables
+ is:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 334.25pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">the necessity to change code when a business rule changes is still
+ unpleasant: software build are more efficient and cost less than before but deployment may be
+ expensive depending of the complexity of the production environment. <span
+ style="mso-spacerun: yes">&nbsp;</span></font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Changing code under time pressure usually leads to poor
+ quality</font></span>
+ </p><br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. The logic as defined by the business is split in multiple parts of the
+ code, methods and procedures.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. Only strict use of configuration management tools with a strict
+ development process may help.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">If the logic is implemented in a service layer with defined interface it may
+ be possible to reuse part of the methods.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Developer is
+ responsible to implement the change, and use configuration management tools and strict development
+ disciplines.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in process map</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Business process automation is the technology components substituting and/or
+ supplementing manual processes to manage information flow within an organization to lower costs, reduce risk, and
+ increase consistency. In this context Business rules describe the structure, operation, and strategy of an
+ organization's business process. The business process definition can be seen as a business rule. Typically a rule
+ involving routing of transactional data to a queue, a task, or a sub process will be most likely implemented in a
+ process map. Defined at the link level business rules are linked to the structure of the process flow. Once designed
+ and implemented there is few chance those rule will change. Changing a business process is most of the time risky: we
+ do not want to change thing working and involving a lot of parties and stakeholders. In fact</span> new policies,
+ regulations or business strategies may affect the rules without changing the core business processes.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">A rule like: "<i style="mso-bidi-font-style: normal">if there is an exception in
+ the claim processing we want a supervisor to study the claim and the accumulated reasons extracted by the process so
+ far"</i> will most likely finish as guard on a process map link:</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <img height="348" alt="" src="resources/BRinBPM.bmp" width="313" />
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Task 1 will most of the time call a rule engine to take decision on the claim. One of the pattern is to accumulate all
+ the possible reasons in a list. If the list include an exception or high priority reason, the process map will route to
+ the "Process Exception" task. This task can queue the work item to a supervisor queues.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There are a lot tasks in a business process that are decision rich, so with a lot
+ of business rule to execute before completing the task. Those rules can be executed by a rule engine. The integration
+ Rule Engine – BPM will bring the value to support those cases. But as good practice it is always possible to try to
+ re-arrange an activity diagram of a use case or a process map so that some activities are purely automatically executed
+ in a rule engine mapped as a rule flow.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Business rules hardly coded in using BPM notation is not efficient and lead
+ to complex map. The real design implementation is to mix BPM map and business rules-decision
+ delegated in a process task. In this type of implementation we can leverage the best of both
+ worlds, and the adaptability is excellent.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: when the integration of BPMS and BRMS is done perfectly, the
+ business and IT team have a clear understanding of the process execution and the decision done by a
+ task by studying the rules attached to the task.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: both tools has version control, and it is possible to link
+ process map version to rule set version.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rules defined in a task should be expose to the other application as a
+ service. So reusability can be achieved. Rules in a BPM map are not really reusable.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Process logic will
+ have a more stable life cycle, and it is managed in the BPMS. <span
+ style="mso-spacerun: yes">&nbsp;</span></span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a rule engine</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Any type of rule using a forward chaining approach will best fit in any RETE rule
+ engine. To avoid long explanation a rule engine will perform very efficiently the following rules which are more
+ complex to implement in code:</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Set parameter = A / (B ^ 2)</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If parameter is above 30 then the risk is<span
+ style="mso-spacerun: yes">&nbsp;</span> medium</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If the risk is medium then alert the manager</span>
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><span style="mso-spacerun: yes">&nbsp;</span>If we enter a new value for A all the
+ depend rules will be fired. Rules can be entered in any order we want, it is less declarative than procedural
+ code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Backward chaining rule pattern can also been supported by a rule engine. The rule
+ system works down the tree to find the data that it requires. It will ask question to be able to infer decisions. It is
+ possible to implement backward chaining with product using pure inference by&nbsp;using a goal object.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">As we already stated one of the key factor is flexibility. We already encounter the
+ following decision: "This rule will not change"... but in fact it will do in the future or some of related one"
+ .</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">We can for example take a simple example of a static rule defined as</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 1.9pt 0cm 0pt 18pt; TEXT-ALIGN: justify">
+ <span class="ISISCodeParagraphChar"><font face="Courier">If the status of the customer is gold and the product is
+ &lt;&gt; then apply &lt;&gt; % discount</font></span><span style="mso-bidi-language: HE">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">This rule can be implemented within application code using some tables in a
+ database that link the product, the category of possible status and the discount to apply. But when discussing with the
+ business user to understand what is a gold customer? We can get other conditions that definitively will change over
+ time: "A customer who spend more than &lt;&gt; the amount of money... during the last 6 months ...No !<span
+ style="mso-spacerun: yes">&nbsp;</span> during the last four month only for the product X because it was only available
+ for 4 months!, … Okay but customer in the states {,,,,} could not be part of the gold status... Ah I forgot, ... A
+ customer must have 18 years old, and by the way customer working for our company or subsidiaries could not be part of
+ the gold...</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Excellent, rule can change quickly and be deployed quickly too</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: by adding meta data to implemented rule we can clearly link rule
+ to business strategies and policies</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent and most of the rule engine has log mechanism to trace what were
+ the rules executed on a given transaction.</font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rule reports are important to the business as part of
+ documentation</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very good if the BRMS use rule repository and the rule analyst designed a
+ rule sharing approach</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Excellent as rules
+ are externalized and managed as a standalone artifact. Rule configuration management is complex,
+ and integrity between rule life cycle and rule set versioning is not a simple
+ practice.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a graphical user interface</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ We will base the integration on the Model-View-Controller (MVC) design pattern. The presentation tier handles the
+ client interaction by abstracting the low-level protocol details into an event-based mechanism. The view's main
+ requirement is synchronization with the model so that data displayed to the user is up to date. The controller is
+ responsible to prepare the data and manage the view flow and content. Delegating the creation of content to a rule
+ engine is possible but need to be done synchronously.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The business rule will be related to control the list of widget the GUI will present. A typical pattern is around
+ product catalog application or dynamic questionnaire. The rule pattern to control the content looks like:
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the selection on this page was &lt;&gt; then add this &lt;&gt; to the model
+ used in view &lt;&gt;</i>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ A rule to control the flow of page looks like
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the user visited page &lt;&gt; (and | or page &lt;&gt;) then next page is
+ &lt;&gt;</i>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Both rules may be enriched with business type decision based on data of the model.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In these pattern it is clear we need to keep the previous context of decision, and events the user created.<span
+ style="mso-spacerun: yes">&nbsp;</span> So most of the current applications are putting the business rule in the
+ controller class or in the java script of the view, but it is possible to design the controller to use a rule engine,
+ as soon as the decision needs to change. This is particularly true for e-commerce web site, where marketing campaign
+ can quickly be put in place by proposing product or product feature more dynamically.<span
+ style="mso-spacerun: yes">&nbsp;</span>
+</p><br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ujEcUPK8pFeN7wqLRcSB9A" name="define_ruleset,_9s4lO8VVEd2pfdXgw7I2qQ" guid="-ujEcUPK8pFeN7wqLRcSB9A">
+ <refinedDescription><a id="XE_rule_set__define" name="XE_rule_set__define"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">When designing an application using one BRE and a simple rule set this activity
+ will be done quickly. The rule developer still needs to think about the parameters the exception management, <span
+ style="mso-spacerun: yes">&nbsp;</span>what are the rule part of the rule set, and how they are executed.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">So for a simple unique rule set the following information needs to be designed and
+ documented:</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Input, output parameters</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Type of data model</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Rule execution flow using a rule flow. But it is still possible with modern BRE
+ to use re-entrant rule set, so executing a rule flow from a rule task or rule package.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Exception management</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Inference objects like a result object which may be used to control the future
+ execution of the caller application or the BRE.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">What are the rule part of the rule set</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">What is their execution order. It is recommended to avoid using a ordering
+ mechanism like the rule priority, but some time at a rule task level it is needed to use sorting mechanism</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">When does a rule is not candidate to enter in a rule set. This is linked to the
+ rule life cycle.</span>
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-GSA2k4CiOuK856zbdHf6bw" name="build_object_models,_9s4lSsVVEd2pfdXgw7I2qQ" guid="-GSA2k4CiOuK856zbdHf6bw">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">Depending of the technology used there is different approach to this task. The
+ domain object model at the enterprise level will represent a complex data model a rule architect does not want to
+ expose as-is to the rule engine and the rule authoring environment. Navigating a complex graph of objects will bring
+ unnecessary complexity for the rule writer. So we recommend to always try to use a view of the enterprise domain object
+ model. For example in Financial Industry the business domain&nbsp;data model defined in MISMO (<a
+ href="http://www.mismo.org/"><font color="#005DA0">www.mismo.org</font></a>), brings a lot of value for an enterprise
+ willing to define a common ontology for their data models. But exposing the MISMO model as it is within a BRMS rule
+ authoring IDE will put too much complexity. As the Architect is responsible to design decision service reusable cross
+ application, it may make sense to consider view of this object model in the context of the service.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">For the application the view can be defined in two entities:</span>
+</p>
+<ul style="MARGIN-TOP: 0in" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in">
+ <span style="mso-bidi-language: HE">the Domain Object Model using java or xml schema as the underling
+ technology</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in">
+ <span style="mso-bidi-language: HE">or out of the box object view, like ILOG-Business Object Model element. The BOM
+ is mandatory to write rule on, but it&nbsp;can be created from an existing java model or XSD or created
+ top-down.</span>
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">If the model does not exist in the application, or at the enterprise level we still
+ recommend to develop the domain model, using an UML designer and code generation tools.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-font-weight: bold; mso-bidi-font-style: italic">It is also important to consider designing a java
+ model or XSD schema which is closed to the business concepts used by the rule but built as a view of the domain object
+ model (We called that the Rule Business Object Pattern or RBO): in the example of standard object model like MISMO or
+ ACORD, it makes sense to do not expose all the class definition, attributes and enumerated to avoid exposing a complex
+ rule language to the business user. This view will be instantiated by the application business logic in the context of
+ preparing the data for the rule services</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ When designing a Domain Object model one of the challenges is to determine what should be an entity and what should be
+ an attribute of the entity.<span style="mso-spacerun: yes">&nbsp;</span> This is why knowledge engineers like the
+ Enterprise Ontology as a start point for developing these concepts.<span style="mso-spacerun: yes">&nbsp;</span> The
+ Enterprise Ontology describes the major entities and concepts that apply to all enterprises and it provides a very good
+ starting point for the establishment of static object models and data models.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The difference between a class and an entity type is that classes have both data and behaviors whereas entity types
+ just have data. A normal entity depicts one concept.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Use multiple different UML class diagram to represent entities and their relations. Then enhance them to have a
+ complete class diagram from which you should be able to generate java code or XSD.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Capture Meta data about each entity: business name, business definition, super type or subtype, number of occurrences,
+ primary key, and alternate keys.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">It is possible to consider designing a Domain Model using Interface, and then apply
+ different type of implementation according to different execution pattern or platforms. For example we can design
+ a;</span>
+</p>
+<ul style="MARGIN-TOP: 0in" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030902" name="1030902"><span style="mso-bidi-language: HE">Staged deployment with different execution
+ classes</span></a>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030906" name="1030906"><span style="mso-bidi-language: HE">Dynamic model (XML based or dynamic classes)
+ versus static model</span></a>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030907" name="1030907"><span style="mso-bidi-language: HE">Production/test models (active objects versus
+ mock objects)</span></a>
+ </li>
+</ul><a id="XE_object_model__build" name="XE_object_model__build"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-A69eNZMgOD-TmrIh98RJsg" name="build_rule_project_structure,_9s4lPsVVEd2pfdXgw7I2qQ" guid="-A69eNZMgOD-TmrIh98RJsg">
+ <refinedDescription><a id="XE_rule_project__build_structure" name="XE_rule_project__build_structure"></a><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; TEXT-ALIGN: justify; mso-list: l0 level1 lfo1; tab-stops: list .25in" />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><span style="mso-bidi-language: HE">This activity is linked to the tool used. There
+ is still some considerations when designing the project structure for the rules and application:</span></span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Apply good design practice of implementing the application using a n-tier
+ approach. The service layer includes the interfaces of the rule decision service entries.</span><br
+ class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 18pt" />
+ <br />
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><img height="491" alt="" src="resources/projStruct.bmp" width="515" /></span>
+</p>
+<div style="MARGIN-TOP: 0cm; MARGIN-LEFT: 2em" type="disc">
+ <ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE"><span style="mso-bidi-language: HE">Organize rule project so that a few
+ person can concurrently work on&nbsp;rule artifact at the same time.</span></span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Organize rule project so that they are manageable in term of performance at
+ the execution and at the rule authoring level.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ Separate representation of the domain object model in java project.
+ </li>
+ </ul>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-7KXY0dEtZ02k-zR2uSgrLw" name="prototype_rules,_9s4lQcVVEd2pfdXgw7I2qQ" guid="-7KXY0dEtZ02k-zR2uSgrLw">
+ <refinedDescription><a id="XE_rule__prototyping" name="XE_rule__prototyping"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The goal of the Rule Analysis activity is to prepare the rules for the
+ implementation. The rule analyst and the rule writer will analyze the rules discovered in a disjointed way into a
+ complete and coherent set. From the rule description, the glossary of business terms and may be from a first version of
+ the logical data model (LDM), the discovery team needs to transform the rules using the terms of the business to
+ elements that will be implemented by the rule writers. The rule analyst executes a set of iterative tasks to reach rule
+ implementation.</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-DLOZ9q9zKzqSH02qulirKQ" name="decision_point_table,_9s4lPMVVEd2pfdXgw7I2qQ" guid="-DLOZ9q9zKzqSH02qulirKQ">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-WpMajOrHlIGWS4oIiTfIgQ" name="rule_description_doc,_9s4lRsVVEd2pfdXgw7I2qQ" guid="-WpMajOrHlIGWS4oIiTfIgQ">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-mw3UMRnpZKKJ1HXl4Tx2GA" name="ruleset,_9s4lP8VVEd2pfdXgw7I2qQ" guid="-mw3UMRnpZKKJ1HXl4Tx2GA">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-TzodlLaSF7x8Ox7OmJmUyg" name="define_ruleset_testing,_HSAXQGh8Ed-FVuzXjnvIWA" guid="-TzodlLaSF7x8Ox7OmJmUyg">
+ <refinedDescription><p>
+ The recommended approach is to consider a rule-set as a unit piece of functionality that gets exposed to the rest of
+ the application as a decision service (SOA pattern). Therefore it should be tested using the same strategy as for any
+ other function in the system. One criterion of rule testing lies in the level of user friendliness that should be built
+ into the test harness. Indeed, empowering business analysts with the ability to change the rules also means they should
+ be tested with their changes. Typically developers code fixtures and do automated testing using JUnit. Business
+ analysts should not write code, but should be able to put together fixtures to be tested against the rules.
+</p>
+<p>
+ How much effort should be spent on the rule test harness really depends on the application, and also importantly on the
+ IT-level of business analyst. Sometimes capturing test data in XML and having business analysts edit them is enough and
+ very cost effective. Sometimes business analysts will feel more comfortable with Excel spreadsheets, or with a full GUI
+ which would need a larger development effort to be facilitated.<br />
+ It is usually a good idea whenever possible to keep individual test case data in files that can be put under source
+ code management. This way the code base, the rules and the test cases can be kept in sync. This becomes important when
+ multiple versions of a business rule are being worked on at different stages such as active development stage, test
+ stage or production stage.<br />
+ BRMS testing fits perfectly into this strategy due to its ability to produce the same sort of test fixtures as the
+ other environments. Utilizing a tool such as JUnit as the test controller, test fixtures are stored in a test fixture
+ repository for which the JUnit can access.
+</p>
+<h5>
+ Testing Levels<br />
+</h5>
+<p>
+ The following levels of testing are usually applied during the application construction:<br />
+</p>
+<ul>
+ <li>
+ Unit Test: applied to test classes and other application elements as developers build them. In the context of a
+ BRMS, the goal of unit testing is to make sure that a rule is actually fired when expected, against the expect
+ object instances and performs the expected working memory updates.
+ </li>
+ <li>
+ Component Test: applied to test a group of elements (e.g. classes) which together represent a significant
+ application component. In the context of a BRMS, a component is typically a rule service.
+ </li>
+ <li>
+ System Test: applied to test the system performs the right business functions correctly.
+ </li>
+ <li>
+ Acceptance Test: applied to ensure users are satisfied with the system. The last stages of acceptance testing are
+ the alpha testing (testing performed internally by the company) and beta testing (testing performed by a limited
+ audience outside of the company).
+ </li>
+ <li>
+ The scope of this section is limited to unit-test (usually performed by rule developers) and component test
+ (performed by both rule developers and rule authors), where components are understood as the rule services
+ implemented by a rule engine.
+ </li>
+</ul>
+<p>
+ Once the rule service components are tested, the next levels can follow the general application testing process
+ followed by the client's QA department, who are considering the rule services as black boxes.<br />
+</p>
+<h5>
+ Testing Activities
+</h5>
+<p>
+ This section relates to why testing is performed, that is what we are trying to get out of it. The goal of testing the
+ decision service components is first and foremost to ensure the correctness of the decision rendered by the service
+ with respect to the requirements.<br />
+ Key Performance Indicators (KPIs) are used to measure how close the actual test results are from the expectations. The
+ focus of KPIs vary depending on the type of testing performed: for performance testing, the KPIs will obviously be
+ interested in the time taken to execute the rules or tasks in the rule-set, for coverage, the focus will be on the set
+ of rule fired and the set of tasks executed, and for more business-oriented testing of correctness, the focus will be
+ on the accuracy of the response.<br />
+</p>
+<h5>
+ Correctness<br />
+</h5>
+<p>
+ For a decision-rich type of application, this is where most of the testing time and effort will be spent, using all
+ types of resources from developers, to business analysts, to business rule writers and subject matter experts.<br />
+ The goal here is to ensure that for a given request configuration, the system renders a response that conforms to the
+ company business goals and policies, contractual obligations and possibly to compliance rules imposed by external
+ agencies (laws and regulations). The impact of an incorrect decision can be profound, from lawsuits for non-compliance
+ to risky financial commitments.<br />
+ Testing the correctness of a business rules application necessarily involves the participation of SMEs, who will write
+ test cases and manually produce the expected response. This is a very time and resource consuming activity which should
+ be carefully taken into account when designing the test plan for an application.<br />
+ Alternatively, some test cases can be extracted from a legacy system database. The benefit here is obvious: the
+ database provides the number and the variety of test cases needed, and also guarantees the validity of the test
+ cases.<br />
+</p>
+<h5>
+ Regression<br />
+</h5>
+<p>
+ The goal of regression testing is to uncover regression problems, that is, problems which were not present in the
+ previous version of the application but appeared in the new version after a change was introduced. Regression testing
+ for rules is used to make sure that after fixing, or updating a rule service, the functionalities which were working
+ before are still working as expected. For example, after implementing a business change request which lowers the rates
+ in the state of California, regression testing should be applied to ensure that rates remained unchanged in all other
+ states.<br />
+ Besides verifying that correctness is conserved from one version to another, regression testing is also used to verify
+ that quality (for example, execution performance) is conserved.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-3TEm3EjK2B_3xvMAHjQHWw" name="develop_unit_tests,_9s4lNcVVEd2pfdXgw7I2qQ" guid="-3TEm3EjK2B_3xvMAHjQHWw">
+ <refinedDescription><a id="XE_unit_tests__develop" name="XE_unit_tests__develop"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Rule Unit Testing is the process of testing a specific rule in the context of the rule set in which it is deployed.
+ Rule Unit Testing allows rule writers to:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Validate each rule in the context of its rule set
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Control the rule set quality
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Conduct some impact analysis when rules are in conflict
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Helps to have non-regression tests
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There is a major difference between testing a code, and a rule. A rule engine per
+ design may not put a rule in the agenda if the conditions are not matched. This means that when the rule writer write a
+ new rule, even if the data are sent to trigger the execution of this new rule it is possible that a rule fired before
+ the new one, with change the condition of the data so that this new rule will never be eligible. Developing a complete
+ set of unit test is an efficient way to see this problem, and to improve the rule set design. Some powerful BRMS
+ platform has rules consistency checking which helps to do some static analysis of those potential conflict by analyzing
+ the conditions and the actions of the rules. For sure real test cases will complete the picture.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<span
+style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Using
+a Test Driven Development approach rule writer can develop the test script preparing the data to trigger each rule,
+depending of the BRMS platform used, the script generation can be done automatically or not. What is important is develop
+reusable test case organized in test suite which include assertion statement to validate the expected results. This is
+efficient tool to put in place automatic non regression tests.</span></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-wUfIZbnlisjRJ7z3OjFsUQ" name="develop_rules,_9s4lN8VVEd2pfdXgw7I2qQ" guid="-wUfIZbnlisjRJ7z3OjFsUQ">
+ <refinedDescription><a id="XE_rule__develop" name="XE_rule__develop"></a>
+<p>
+ Programming using rule approach enforces to know how a rule engine is working. This is not a complex skill, rue author
+ needs to understand&nbsp; the concepts of asserting, retracting object into working memory and modifying them. It is
+ recommended to read what a <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_engine_A66B71B3.html"
+ guid="_QQcSoEXXEdy14e5PT9v3HQ">Rule engine</a>&nbsp;is to get those concepts.
+</p>
+<p>
+ Rule development can follow a test driven development approach: the developer can develop the test cases to trigger the
+ rule execution and then write the rules. Once done the new rules are extracted with the other rules in the rule set,
+ deployed to the unit test environment and the test executes. When designing with interface the unit test uses the
+ facade to access the rule engine for&nbsp;the execution.
+</p>
+<p>
+ When rules are complex and include a lot of conditions it may make sense to add condition by steps. It may be easy to
+ make error by using a wrong boolean operator. When the rue language support navigating into collection the testing may
+ include test around the presence and not presence of element in the collection.
+</p>
+<p>
+ It is always interesting once the rule is developed to perform rule analysis if the BRMS product has this capability.
+ The analysis helps to see if the current rule is in conflict with existing rules.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-bLL0Fi0p_lu2XVXfO4Bmng" name="ruleset,_9s4lNMVVEd2pfdXgw7I2qQ" guid="-bLL0Fi0p_lu2XVXfO4Bmng">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-pk5as0BVClbnn3B7FhmN3A" name="enhance_object_models,_9s4lMMVVEd2pfdXgw7I2qQ" guid="-pk5as0BVClbnn3B7FhmN3A">
+ <refinedDescription>Typically the developer adds helper methods in the data model to facilitate the rule writing. Develop utility classes. The
+data elements should not have persistence logic in it. For example in Java do not put JDBC code in the Customer object. Let
+try to stick to the Java bean specification for all the&nbsp;business objects, and leverage a service layer, with service
+facades objects to help gathering and process data.&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-9bcuy4Hs_gwTKjG8NyKAPw" name="execute_rule_set,_9s4lM8VVEd2pfdXgw7I2qQ" guid="-9bcuy4Hs_gwTKjG8NyKAPw">
+ <refinedDescription><a id="XE_rule_set__execute" name="XE_rule_set__execute"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-oYF8elqKsD5hfhKlCij3xQ" name="log_issue,_9s4lMsVVEd2pfdXgw7I2qQ" guid="-oYF8elqKsD5hfhKlCij3xQ">
+ <refinedDescription><ul>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Formally log any issues and decisions done during the rule
+ analysis and the rule authoring activities.</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The issue
+ log is used to manage feedbacks, and to improve the rule set quality.</span></span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-weight: bold">As a social process, people will
+ change their mind, it is a good practice to log decision on a timely manner.</span>
+ </div>
+ </li>
+</ul><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-OJ8H_2tSlsUq645zMbm48Q" name="develop_architecture,_9s4lTsVVEd2pfdXgw7I2qQ" guid="-OJ8H_2tSlsUq645zMbm48Q">
+ <keyConsiderations><p class="MsoNormal" style="MARGIN: 0in 0in 10pt">
+ <span style="mso-bidi-language: HE">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.</span>
+</p></keyConsiderations>
+ <refinedDescription><p>
+ The architect has to address as soon as possible in the project life cycle:
+</p>
+<ul>
+ <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.
+ </li>
+ <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.<br />
+ </li>
+</ul>
+<p>
+ For a BRMS deployment architect needs to integrate the following components within the IT architecture:
+</p>
+<ul>
+ <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.&nbsp;<br />
+ </li>
+ <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.<br />
+ </li>
+ <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.<br />
+ </li>
+ <li>
+ A Web based Rule management platform to let business users and analysts being able to maintain the rules.<br />
+ </li>
+ <li>
+ A Rule testing framework to support functional testing of the rule set and non-regression tests.
+ </li>
+</ul>
+<p>
+ <img height="376" alt="" src="resources/BRMScomponents.bmp" width="487" />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-AG5WgBy68mLoQW6HqHTusQ" name="decision_service_architecture,_9s4lT8VVEd2pfdXgw7I2qQ" guid="-AG5WgBy68mLoQW6HqHTusQ">
+ <refinedDescription><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 /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-VLRdP6iYek0zEo_rHnIppw" name="design_reference_data_integration,_9s4lTcVVEd2pfdXgw7I2qQ" guid="-VLRdP6iYek0zEo_rHnIppw">
+ <refinedDescription><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.
+</p>
+<p>
+ The following diagram highlights a high level architecture&nbsp;architect can leverage to design&nbsp;his own solution.
+</p><br />
+<p>
+ <img height="499" alt="" src="resources/MDM.bmp" width="557" /><br />
+</p>
+<p>
+ The master data are centralized in a repository, and technology as Master Data Management product can be&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&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.
+</p>
+<p>
+ The same applies for the rule authoring environment: The&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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-BBnqXNX3L83SEuYSuaMdxw" name="design_models_for_bre,_9s4lUMVVEd2pfdXgw7I2qQ" guid="-BBnqXNX3L83SEuYSuaMdxw">
+ <refinedDescription><p>
+ This is an important activity as we do not expose an enterprise model or a physical model as&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.
+</p>
+<p>
+ In any cases&nbsp;&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.&nbsp;
+</p>
+<p>
+ Developing such models is done by iterations.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ZBEhisTrkRvWYQ7SWQP4eg" name="integrate_bre,_9s4lUcVVEd2pfdXgw7I2qQ" guid="-ZBEhisTrkRvWYQ7SWQP4eg">
+ <refinedDescription><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.
+</p>
+<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:
+</p>
+<ul>
+ <li>
+ the service definition: one or more operations linked to the same data semantic
+ </li>
+ <li>
+ the operation call approach: synchronous/ asynchronous, stateless/stateful, header based or carrying payload, use
+ of faults or not
+ </li>
+ <li>
+ the exception reporting
+ </li>
+</ul>
+<p>
+ The service implementation using a rule engine has to look at:
+</p>
+<ul>
+ <li>
+ the transaction propagation
+ </li>
+ <li>
+ the reference data caching
+ </li>
+ <li>
+ the parsing of input message: the claim data
+ </li>
+ <li>
+ the loading of the related data: the policy related to the claim, or the insured person profile
+ </li>
+ <li>
+ the preparation of the output message: the result and may be some other technical data
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-rH1vUc8rldU1_AKYYx9dBA" name="logical_data_model,_vxYecVmSEeCcpdiAcH0w-w" guid="-rH1vUc8rldU1_AKYYx9dBA">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-bvUOgHIu3fluB7VANjXFJg" name="decision_point_table,_vxYedFmSEeCcpdiAcH0w-w" guid="-bvUOgHIu3fluB7VANjXFJg">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ewbo32yGFGXgBOLZ6El0qQ" name="fact_model,_vxYeelmSEeCcpdiAcH0w-w" guid="-ewbo32yGFGXgBOLZ6El0qQ">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-c8q_v1s1n7aK-0miFaupPw" name="decision_point_table,_RkSNlMVWEd2pfdXgw7I2qQ" guid="-c8q_v1s1n7aK-0miFaupPw">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-yaB5VmxyoNnFc5KAKx87uw" name="business_process_map,_RkSNkcVWEd2pfdXgw7I2qQ" guid="-yaB5VmxyoNnFc5KAKx87uw">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-jiPE4qjhy0-GvsHSu8k4hw" name="discovery_workshop_itinerary,_RkSNnsVWEd2pfdXgw7I2qQ" guid="-jiPE4qjhy0-GvsHSu8k4hw">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-N9JRT0YykF7mF_nPmGpEig" name="execute_rule_discovery_roadmap,_RkSNkMVWEd2pfdXgw7I2qQ" guid="-N9JRT0YykF7mF_nPmGpEig">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-wKyQQHGWKPhxgDMava9lMA" name="business_terms_glossary,_RkSNksVWEd2pfdXgw7I2qQ" guid="-wKyQQHGWKPhxgDMava9lMA">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-bN3NfZ3WOIrkhDKHWDPKkA" name="rule_description_doc,_RkSNosVWEd2pfdXgw7I2qQ" guid="-bN3NfZ3WOIrkhDKHWDPKkA">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-l1seeyWf2ab1M7_-vwsRiQ" name="conceptual_data_model,_RkSNjsVWEd2pfdXgw7I2qQ" guid="-l1seeyWf2ab1M7_-vwsRiQ">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-teqRVFQdfi3M0E_2hPt2OA" name="rule_description_doc,_RkSNasVWEd2pfdXgw7I2qQ" guid="-teqRVFQdfi3M0E_2hPt2OA">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-7obhtj52BKnAGY2bh-MvLw" name="fact_model,_RkSNYcVWEd2pfdXgw7I2qQ" guid="-7obhtj52BKnAGY2bh-MvLw">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-KnXTyJRJlBDBK68DXO57Uw" name="logical_data_model,_RkSNY8VWEd2pfdXgw7I2qQ" guid="-KnXTyJRJlBDBK68DXO57Uw">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-sMysBcAYtIvVDmB57oo8sA" name="transform_rules,_RkSNbMVWEd2pfdXgw7I2qQ" guid="-sMysBcAYtIvVDmB57oo8sA">
+ <keyConsiderations>This activity will also be done during the implementation of the rule set, but it is started during the analysis, so we are
+detailing it in this context.</keyConsiderations>
+ <refinedDescription><p>
+ Rule Analyst has to study the rule discovered and try to transform it so that the implementation and the management of
+ the rule will be more easy. This includes transforming the rule in atomic element using a syntax without ambiguity,
+ remove redundant rules, conflicting rules, and finally try to redefine the scope of the rule by searching by
+ non-handled cases.&nbsp;
+</p>
+<p>
+ At this stage rule analyst can build some rule template which&nbsp;are built from rules that have the same set of
+ conditions with some little variations: adding new value in test condition, or new condition.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-bcOPKdssk4qvaJmaJ82Wdg" name="build_test_scenario,_RkSNbcVWEd2pfdXgw7I2qQ" guid="-bcOPKdssk4qvaJmaJ82Wdg">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-D86vI3p-CJqtaGHovLIH3A" name="synchronize_data_model,_RkSNZ8VWEd2pfdXgw7I2qQ" guid="-D86vI3p-CJqtaGHovLIH3A">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst needs to continuously verify that business terms used in rule statements are part of the logical data
+ model (classes/ attributes) and physical data model (PDM). The model exposed to the rule needs to get data from data
+ sources. If a concept is not in the data it has to be quickly handled and managed by the application architect.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst should be in continuous communication with the data model developer, responsible to develop the XML
+ schema or java model (or .Net), and the physical mapping to database.<br />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Part of most of the business application are the list of code, enumerated date or domain values. It is important to
+ well design how those data are defined, accessed by the application, and the rule authoring environment.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ It can be helpful for some major business term to define a mapping to a class-attribute, and if the BRMS supports this
+ function it is recommended to detail the "verbalization" of the business term.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<div align="center">
+ <table class="MsoNormalTable" style="WIDTH: 351pt; BORDER-COLLAPSE: collapse; mso-padding-alt: 0in 0in 0in 0in"
+ cellspacing="0" cellpadding="0" width="468" border="0">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes">
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: gray 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Business Term</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">OO mapping</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Verbalization</span></i>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LTV</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LoanApplication.ltv</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">The loan to value ratio</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in left 3.0in" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Qy_wVwt9Qh9iVf4FyNvOag" name="determine_rule_implementation,_DbIE5MVXEd2pfdXgw7I2qQ" guid="-Qy_wVwt9Qh9iVf4FyNvOag">
+ <refinedDescription><a id="XE_rule__determine_implementation" name="XE_rule__determine_implementation"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Project teams involved in BRMS deployment are often asking the following type of questions:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus a&nbsp;BPM?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ How do I decide what decisions should I put into a BRE?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus code?&nbsp;
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ There are definitively multiple variables which could influence the decision on where to implement rules. We can start
+ by looking at the BRMS value propositions, it should help to get a first set of variables:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Adaptability – Measure the ability to change the business logic easily. The motivation can be due to short deadline
+ constraint, or frequent small changes or important change that may occur every month or quarter.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Transparency – Represents the need to clearly implement the business logic as what was agreed upon the business
+ unit and the IT team, in a way that every parties understand the logic. This is leading to express the logic in
+ natural or close to natural language.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Auditability – Represents the ability to trace from the business motivation to the execution of the policy to
+ better understand what was the logic behind a decision.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Reusability – Need to share business logic across processes or applications and stay . consistent across
+ applications/transactions
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Manageability- This variable addresses the life cycle management of the business logic. Who writes what, and when,
+ and all the questions related to maintenance and evolutions of the rule-based service.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The purpose here is not to say it is not possible to support those variables in standard software development
+ practices, but more to find some good patterns on how to decide on where to implement the business logic.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ When looking at a business rules statement software engineer can see different possible choices of implementation like:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Data model: designing an object oriented object model involves supporting a lot of business rules. A statement like
+ a mortgage application can have a primary and a secondary borrower, will be supported by two classes and a 1 to 2
+ relationship. At the instantiation of those classes the control of the cardinality can be done in the application
+ logic, or the database, or the GUI structure.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Application code: implementing the logic in function, procedural code or methods in service layer or business
+ objects.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ BPM process flow, tasks or links: BPM tools are addressing business process efficiency issue specifically on "who
+ is involved", "when they should be involved". "what they need to do". BPM supports manual human and automated
+ actors. At a glance the business logic to implement in BPM is linked to people, task, and data to process within a
+ task. When supporting purely automated tasks BPM is orchestrating the application logic and services (BPEL engine).
+ BRMS complements BPM by adding the why to a BPM task, why it behaves a certain way, why this decision is done.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Rule engine: <span style="mso-spacerun: yes">&nbsp;</span>using predefined structure like if then else statement or
+ decision table, rule flow, decision tree, function, rule template or other high level language...
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Graphical user interface: <span style="mso-spacerun: yes">&nbsp;</span>using scripting language or server side code
+ in controller class it is possible to implement data validation type of business rules.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In the following paragraphs address each of different choices with their impact on the variables
+</p><br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in Data Model</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Rule which is controlling the structure of the model and the reference integrity
+ should be in the physical data model, the O/R mapping layer or on the domain object model.</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule setting constraint on relationship -
+ <span style="mso-spacerun: yes">&nbsp;</span>like a loan application could only have two borrowers</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule on the structure of the business
+ entities - like this attribute is part of this object</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following facts are based on a simple
+ user authentication problem, are well implemented in an object model and the supporting application code which
+ create the instance from the data (O/R mapping layer or DAO or service layer):</span>
+ </li>
+</ul>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of users who can login to the application</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of groups of user</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A User is part of a group</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group includes a list of Users</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group has one user reference who is the creator of the group</span>
+</p>
+<p>
+ Terms and facts and derived attributes&nbsp;are the primary constituents of data models and are represented in a UML
+ class diagram, and logical data model (entities/relationship model), or a physical data model.
+</p>
+<p>
+ <span style="mso-bidi-language: HE">The following table lists the impact of this implementation on the previously
+ defined variables</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 221.4pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very static implementation. A change in the constraints of the object model
+ impact, data persistence, logical data model, service and presentation layers. Change is managed on
+ a monthly or yearly basis</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Data model represented as UML classes diagram is doing a poor job to
+ communicate to business. Entities diagram represents a more high level representation of the domain
+ model, but forces the team to maintain the link between the implementation and the business
+ representation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tool, with a strict development process and
+ disciplines can help to trace back to the business motivation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Domain Object model can be designed as reusable. But in the reality each
+ application needs a view of the core business object model, and so part of the implemented
+ application will be to build those view.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tools and strict discipline can help maintain the
+ business logic.</font></span>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in application code</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Implementing business rule in application code is
+ currently the most common way the IT developer is doing it. The major justifications are performance and flexibility of
+ the coding language. Using hard coded if/then/else statements isn't too flexible, but in the hands of a top notch
+ programmer it can be very fast and arguably as fast as or faster than a rule engine. Assuming the programmer has
+ unlimited time to optimize the execution for a fixed set of rules. If the ruleset changes frequently and the system
+ can't tolerate a big drop in performance, than a rule engine is the solution.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following example of business rules may be
+ easily implemented in code:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span class="ISISCodeParagraphChar"><font face="Courier">verify in each items the customer bought since he is customer
+ with us there is at least one article of type T so that we can propose the new product Y with X % of discount, except
+ if the customer is from the state of New York or New Jersey</font></span><span
+ style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">We can implement this in a method which loops on
+ the articles bought by a given customer and do the search. At a first analysis, navigating in a collection of objects
+ and testing multiples conditions on them is easy to implement using the power of programming language.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One thing interesting will be the hard coding of
+ the value of New York, New Jersey... If this logic change we need to add if statements in the code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Other type of rules are related to the control of
+ the execution of a set of "services" to support specific use case. Dispatching, orchestration, data manipulation, … are
+ better candidate to be implemented in application code. Those rules are more static, often more complex, and
+ definitively linked to context of execution. The context may be too complex to expose to a rule engine.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Orchestration are now very well supported by
+ BPM-BPEL engine because the developer needs to add flexibility on the service selection and invocation.<span
+ style="mso-spacerun: yes">&nbsp;</span></span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The evaluation of the important variables
+ is:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 334.25pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">the necessity to change code when a business rule changes is still
+ unpleasant: software build are more efficient and cost less than before but deployment may be
+ expensive depending of the complexity of the production environment. <span
+ style="mso-spacerun: yes">&nbsp;</span></font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Changing code under time pressure usually leads to poor
+ quality</font></span>
+ </p><br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. The logic as defined by the business is split in multiple parts of the
+ code, methods and procedures.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. Only strict use of configuration management tools with a strict
+ development process may help.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">If the logic is implemented in a service layer with defined interface it may
+ be possible to reuse part of the methods.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Developer is
+ responsible to implement the change, and use configuration management tools and strict development
+ disciplines.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in process map</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Business process automation is the technology components substituting and/or
+ supplementing manual processes to manage information flow within an organization to lower costs, reduce risk, and
+ increase consistency. In this context Business rules describe the structure, operation, and strategy of an
+ organization's business process. The business process definition can be seen as a business rule. Typically a rule
+ involving routing of transactional data to a queue, a task, or a sub process will be most likely implemented in a
+ process map. Defined at the link level business rules are linked to the structure of the process flow. Once designed
+ and implemented there is few chance those rule will change. Changing a business process is most of the time risky: we
+ do not want to change thing working and involving a lot of parties and stakeholders. In fact</span> new policies,
+ regulations or business strategies may affect the rules without changing the core business processes.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">A rule like: "<i style="mso-bidi-font-style: normal">if there is an exception in
+ the claim processing we want a supervisor to study the claim and the accumulated reasons extracted by the process so
+ far"</i> will most likely finish as guard on a process map link:</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <img height="348" alt="" src="resources/BRinBPM.bmp" width="313" />
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Task 1 will most of the time call a rule engine to take decision on the claim. One of the pattern is to accumulate all
+ the possible reasons in a list. If the list include an exception or high priority reason, the process map will route to
+ the "Process Exception" task. This task can queue the work item to a supervisor queues.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There are a lot tasks in a business process that are decision rich, so with a lot
+ of business rule to execute before completing the task. Those rules can be executed by a rule engine. The integration
+ Rule Engine – BPM will bring the value to support those cases. But as good practice it is always possible to try to
+ re-arrange an activity diagram of a use case or a process map so that some activities are purely automatically executed
+ in a rule engine mapped as a rule flow.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Business rules hardly coded in using BPM notation is not efficient and lead
+ to complex map. The real design implementation is to mix BPM map and business rules-decision
+ delegated in a process task. In this type of implementation we can leverage the best of both
+ worlds, and the adaptability is excellent.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: when the integration of BPMS and BRMS is done perfectly, the
+ business and IT team have a clear understanding of the process execution and the decision done by a
+ task by studying the rules attached to the task.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: both tools has version control, and it is possible to link
+ process map version to rule set version.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rules defined in a task should be expose to the other application as a
+ service. So reusability can be achieved. Rules in a BPM map are not really reusable.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Process logic will
+ have a more stable life cycle, and it is managed in the BPMS. <span
+ style="mso-spacerun: yes">&nbsp;</span></span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a rule engine</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Any type of rule using a forward chaining approach will best fit in any RETE rule
+ engine. To avoid long explanation a rule engine will perform very efficiently the following rules which are more
+ complex to implement in code:</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Set parameter = A / (B ^ 2)</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If parameter is above 30 then the risk is<span
+ style="mso-spacerun: yes">&nbsp;</span> medium</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If the risk is medium then alert the manager</span>
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><span style="mso-spacerun: yes">&nbsp;</span>If we enter a new value for A all the
+ depend rules will be fired. Rules can be entered in any order we want, it is less declarative than procedural
+ code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Backward chaining rule pattern can also been supported by a rule engine. The rule
+ system works down the tree to find the data that it requires. It will ask question to be able to infer decisions. It is
+ possible to implement backward chaining with product using pure inference by&nbsp;using a goal object.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">As we already stated one of the key factor is flexibility. We already encounter the
+ following decision: "This rule will not change"... but in fact it will do in the future or some of related one"
+ .</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">We can for example take a simple example of a static rule defined as</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 1.9pt 0cm 0pt 18pt; TEXT-ALIGN: justify">
+ <span class="ISISCodeParagraphChar"><font face="Courier">If the status of the customer is gold and the product is
+ &lt;&gt; then apply &lt;&gt; % discount</font></span><span style="mso-bidi-language: HE">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">This rule can be implemented within application code using some tables in a
+ database that link the product, the category of possible status and the discount to apply. But when discussing with the
+ business user to understand what is a gold customer? We can get other conditions that definitively will change over
+ time: "A customer who spend more than &lt;&gt; the amount of money... during the last 6 months ...No !<span
+ style="mso-spacerun: yes">&nbsp;</span> during the last four month only for the product X because it was only available
+ for 4 months!, … Okay but customer in the states {,,,,} could not be part of the gold status... Ah I forgot, ... A
+ customer must have 18 years old, and by the way customer working for our company or subsidiaries could not be part of
+ the gold...</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Excellent, rule can change quickly and be deployed quickly too</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: by adding meta data to implemented rule we can clearly link rule
+ to business strategies and policies</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent and most of the rule engine has log mechanism to trace what were
+ the rules executed on a given transaction.</font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rule reports are important to the business as part of
+ documentation</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very good if the BRMS use rule repository and the rule analyst designed a
+ rule sharing approach</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Excellent as rules
+ are externalized and managed as a standalone artifact. Rule configuration management is complex,
+ and integrity between rule life cycle and rule set versioning is not a simple
+ practice.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a graphical user interface</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ We will base the integration on the Model-View-Controller (MVC) design pattern. The presentation tier handles the
+ client interaction by abstracting the low-level protocol details into an event-based mechanism. The view's main
+ requirement is synchronization with the model so that data displayed to the user is up to date. The controller is
+ responsible to prepare the data and manage the view flow and content. Delegating the creation of content to a rule
+ engine is possible but need to be done synchronously.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The business rule will be related to control the list of widget the GUI will present. A typical pattern is around
+ product catalog application or dynamic questionnaire. The rule pattern to control the content looks like:
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the selection on this page was &lt;&gt; then add this &lt;&gt; to the model
+ used in view &lt;&gt;</i>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ A rule to control the flow of page looks like
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the user visited page &lt;&gt; (and | or page &lt;&gt;) then next page is
+ &lt;&gt;</i>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Both rules may be enriched with business type decision based on data of the model.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In these pattern it is clear we need to keep the previous context of decision, and events the user created.<span
+ style="mso-spacerun: yes">&nbsp;</span> So most of the current applications are putting the business rule in the
+ controller class or in the java script of the view, but it is possible to design the controller to use a rule engine,
+ as soon as the decision needs to change. This is particularly true for e-commerce web site, where marketing campaign
+ can quickly be put in place by proposing product or product feature more dynamically.<span
+ style="mso-spacerun: yes">&nbsp;</span>
+</p><br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-7BTHzZPiw1v_S2Ts1aJNBA" name="decision_point_table,_DbIE58VXEd2pfdXgw7I2qQ" guid="-7BTHzZPiw1v_S2Ts1aJNBA">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="--tH7_LHDMrDWKm6h9JBFsA" name="rule_description_doc,_DbIE4sVXEd2pfdXgw7I2qQ" guid="--tH7_LHDMrDWKm6h9JBFsA">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-yPcK13A7M5bOTTJG-OiLTQ" name="develop_unit_tests,_RkSNdcVWEd2pfdXgw7I2qQ" guid="-yPcK13A7M5bOTTJG-OiLTQ">
+ <refinedDescription><a id="XE_unit_tests__develop" name="XE_unit_tests__develop"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Rule Unit Testing is the process of testing a specific rule in the context of the rule set in which it is deployed.
+ Rule Unit Testing allows rule writers to:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Validate each rule in the context of its rule set
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Control the rule set quality
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Conduct some impact analysis when rules are in conflict
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Helps to have non-regression tests
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There is a major difference between testing a code, and a rule. A rule engine per
+ design may not put a rule in the agenda if the conditions are not matched. This means that when the rule writer write a
+ new rule, even if the data are sent to trigger the execution of this new rule it is possible that a rule fired before
+ the new one, with change the condition of the data so that this new rule will never be eligible. Developing a complete
+ set of unit test is an efficient way to see this problem, and to improve the rule set design. Some powerful BRMS
+ platform has rules consistency checking which helps to do some static analysis of those potential conflict by analyzing
+ the conditions and the actions of the rules. For sure real test cases will complete the picture.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<span
+style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Using
+a Test Driven Development approach rule writer can develop the test script preparing the data to trigger each rule,
+depending of the BRMS platform used, the script generation can be done automatically or not. What is important is develop
+reusable test case organized in test suite which include assertion statement to validate the expected results. This is
+efficient tool to put in place automatic non regression tests.</span></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-z_nnzuHQecgXrHgcz9F0qw" name="develop_rules,_RkSNd8VWEd2pfdXgw7I2qQ" guid="-z_nnzuHQecgXrHgcz9F0qw">
+ <refinedDescription><a id="XE_rule__develop" name="XE_rule__develop"></a>
+<p>
+ Programming using rule approach enforces to know how a rule engine is working. This is not a complex skill, rue author
+ needs to understand&nbsp; the concepts of asserting, retracting object into working memory and modifying them. It is
+ recommended to read what a <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_engine_A66B71B3.html"
+ guid="_QQcSoEXXEdy14e5PT9v3HQ">Rule engine</a>&nbsp;is to get those concepts.
+</p>
+<p>
+ Rule development can follow a test driven development approach: the developer can develop the test cases to trigger the
+ rule execution and then write the rules. Once done the new rules are extracted with the other rules in the rule set,
+ deployed to the unit test environment and the test executes. When designing with interface the unit test uses the
+ facade to access the rule engine for&nbsp;the execution.
+</p>
+<p>
+ When rules are complex and include a lot of conditions it may make sense to add condition by steps. It may be easy to
+ make error by using a wrong boolean operator. When the rue language support navigating into collection the testing may
+ include test around the presence and not presence of element in the collection.
+</p>
+<p>
+ It is always interesting once the rule is developed to perform rule analysis if the BRMS product has this capability.
+ The analysis helps to see if the current rule is in conflict with existing rules.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="--__8DYtnVs9eZArH2GikBg" name="ruleset,_RkSNdMVWEd2pfdXgw7I2qQ" guid="--__8DYtnVs9eZArH2GikBg">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-xrmI1p-ME165PzMiVzJ8Sw" name="enhance_object_models,_RkSNcMVWEd2pfdXgw7I2qQ" guid="-xrmI1p-ME165PzMiVzJ8Sw">
+ <refinedDescription>Typically the developer adds helper methods in the data model to facilitate the rule writing. Develop utility classes. The
+data elements should not have persistence logic in it. For example in Java do not put JDBC code in the Customer object. Let
+try to stick to the Java bean specification for all the&nbsp;business objects, and leverage a service layer, with service
+facades objects to help gathering and process data.&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-uuWfS5EV0FimZ5_4aRVtjA" name="execute_rule_set,_RkSNc8VWEd2pfdXgw7I2qQ" guid="-uuWfS5EV0FimZ5_4aRVtjA">
+ <refinedDescription><a id="XE_rule_set__execute" name="XE_rule_set__execute"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-zUb0cau__Hfq13SvkX5QLw" name="log_issue,_RkSNcsVWEd2pfdXgw7I2qQ" guid="-zUb0cau__Hfq13SvkX5QLw">
+ <refinedDescription><ul>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Formally log any issues and decisions done during the rule
+ analysis and the rule authoring activities.</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The issue
+ log is used to manage feedbacks, and to improve the rule set quality.</span></span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-weight: bold">As a social process, people will
+ change their mind, it is a good practice to log decision on a timely manner.</span>
+ </div>
+ </li>
+</ul><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-xZmMlKJ2ELDM5ehTI5-ouA" name="define_ruleset_testing,_xxBFkGh8Ed-9y9wL8auvhA" guid="-xZmMlKJ2ELDM5ehTI5-ouA">
+ <refinedDescription><p>
+ The recommended approach is to consider a rule-set as a unit piece of functionality that gets exposed to the rest of
+ the application as a decision service (SOA pattern). Therefore it should be tested using the same strategy as for any
+ other function in the system. One criterion of rule testing lies in the level of user friendliness that should be built
+ into the test harness. Indeed, empowering business analysts with the ability to change the rules also means they should
+ be tested with their changes. Typically developers code fixtures and do automated testing using JUnit. Business
+ analysts should not write code, but should be able to put together fixtures to be tested against the rules.
+</p>
+<p>
+ How much effort should be spent on the rule test harness really depends on the application, and also importantly on the
+ IT-level of business analyst. Sometimes capturing test data in XML and having business analysts edit them is enough and
+ very cost effective. Sometimes business analysts will feel more comfortable with Excel spreadsheets, or with a full GUI
+ which would need a larger development effort to be facilitated.<br />
+ It is usually a good idea whenever possible to keep individual test case data in files that can be put under source
+ code management. This way the code base, the rules and the test cases can be kept in sync. This becomes important when
+ multiple versions of a business rule are being worked on at different stages such as active development stage, test
+ stage or production stage.<br />
+ BRMS testing fits perfectly into this strategy due to its ability to produce the same sort of test fixtures as the
+ other environments. Utilizing a tool such as JUnit as the test controller, test fixtures are stored in a test fixture
+ repository for which the JUnit can access.
+</p>
+<h5>
+ Testing Levels<br />
+</h5>
+<p>
+ The following levels of testing are usually applied during the application construction:<br />
+</p>
+<ul>
+ <li>
+ Unit Test: applied to test classes and other application elements as developers build them. In the context of a
+ BRMS, the goal of unit testing is to make sure that a rule is actually fired when expected, against the expect
+ object instances and performs the expected working memory updates.
+ </li>
+ <li>
+ Component Test: applied to test a group of elements (e.g. classes) which together represent a significant
+ application component. In the context of a BRMS, a component is typically a rule service.
+ </li>
+ <li>
+ System Test: applied to test the system performs the right business functions correctly.
+ </li>
+ <li>
+ Acceptance Test: applied to ensure users are satisfied with the system. The last stages of acceptance testing are
+ the alpha testing (testing performed internally by the company) and beta testing (testing performed by a limited
+ audience outside of the company).
+ </li>
+ <li>
+ The scope of this section is limited to unit-test (usually performed by rule developers) and component test
+ (performed by both rule developers and rule authors), where components are understood as the rule services
+ implemented by a rule engine.
+ </li>
+</ul>
+<p>
+ Once the rule service components are tested, the next levels can follow the general application testing process
+ followed by the client's QA department, who are considering the rule services as black boxes.<br />
+</p>
+<h5>
+ Testing Activities
+</h5>
+<p>
+ This section relates to why testing is performed, that is what we are trying to get out of it. The goal of testing the
+ decision service components is first and foremost to ensure the correctness of the decision rendered by the service
+ with respect to the requirements.<br />
+ Key Performance Indicators (KPIs) are used to measure how close the actual test results are from the expectations. The
+ focus of KPIs vary depending on the type of testing performed: for performance testing, the KPIs will obviously be
+ interested in the time taken to execute the rules or tasks in the rule-set, for coverage, the focus will be on the set
+ of rule fired and the set of tasks executed, and for more business-oriented testing of correctness, the focus will be
+ on the accuracy of the response.<br />
+</p>
+<h5>
+ Correctness<br />
+</h5>
+<p>
+ For a decision-rich type of application, this is where most of the testing time and effort will be spent, using all
+ types of resources from developers, to business analysts, to business rule writers and subject matter experts.<br />
+ The goal here is to ensure that for a given request configuration, the system renders a response that conforms to the
+ company business goals and policies, contractual obligations and possibly to compliance rules imposed by external
+ agencies (laws and regulations). The impact of an incorrect decision can be profound, from lawsuits for non-compliance
+ to risky financial commitments.<br />
+ Testing the correctness of a business rules application necessarily involves the participation of SMEs, who will write
+ test cases and manually produce the expected response. This is a very time and resource consuming activity which should
+ be carefully taken into account when designing the test plan for an application.<br />
+ Alternatively, some test cases can be extracted from a legacy system database. The benefit here is obvious: the
+ database provides the number and the variety of test cases needed, and also guarantees the validity of the test
+ cases.<br />
+</p>
+<h5>
+ Regression<br />
+</h5>
+<p>
+ The goal of regression testing is to uncover regression problems, that is, problems which were not present in the
+ previous version of the application but appeared in the new version after a change was introduced. Regression testing
+ for rules is used to make sure that after fixing, or updating a rule service, the functionalities which were working
+ before are still working as expected. For example, after implementing a business change request which lowers the rates
+ in the state of California, regression testing should be applied to ensure that rates remained unchanged in all other
+ states.<br />
+ Besides verifying that correctness is conserved from one version to another, regression testing is also used to verify
+ that quality (for example, execution performance) is conserved.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-QGPmaN2xy-Wgo3ltSi79iA" name="define_data_scenario,_RkSNq8VWEd2pfdXgw7I2qQ" guid="-QGPmaN2xy-Wgo3ltSi79iA">
+ <refinedDescription>This task is initiated during the rule harvesting phase, and completed over the development life cycle. Developing the data
+model used by the rules enforces to adopt a test driven development approach which define the&nbsp;data with the project
+model. Extracting the terms and the facts used by the rules helps to define the conceptual&nbsp;data model, this model can
+be unit tested with framework like Junit. Data defined in these test cases&nbsp;should come&nbsp;from the rule discovery
+session. Rule discovery is easily facilitate when concrete example is used to drive understanding of the
+business&nbsp;intent for each rule. The concrete example is used to populate data for test.&nbsp;&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-I90uzl3ItrvAQBeMg-l9pw" name="execute_ruleset_functional_test,_RkSNrsVWEd2pfdXgw7I2qQ" guid="-I90uzl3ItrvAQBeMg-l9pw">
+ <refinedDescription><a id="XE_rule_set__execute_functional_tests" name="XE_rule_set__execute_functional_tests"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-h_Q4rpmMhckmEL3epy5j4Q" name="get_rule_set_reports,_RkSNqcVWEd2pfdXgw7I2qQ" guid="-h_Q4rpmMhckmEL3epy5j4Q">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-JkOVgFn0THaQU3V_LciXbg" name="get_sme_feedback,_RkSNr8VWEd2pfdXgw7I2qQ" guid="-JkOVgFn0THaQU3V_LciXbg">
+ <refinedDescription><a id="XE_SME__get_feedback" name="XE_SME__get_feedback"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-LGCZRD2iL1EzFH3_LqlAJg" name="test_analysis,_RkSNrcVWEd2pfdXgw7I2qQ" guid="-LGCZRD2iL1EzFH3_LqlAJg">
+ <refinedDescription><a id="XE_test_analysis" name="XE_test_analysis"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-UbMVWUVbdTcZeO_raP_Zmg" name="ruleset,_RkSNp8VWEd2pfdXgw7I2qQ" guid="-UbMVWUVbdTcZeO_raP_Zmg">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-fwowC3JkpIga2H7YGyHA4Q" name="rule_report,_RkSNqMVWEd2pfdXgw7I2qQ" guid="-fwowC3JkpIga2H7YGyHA4Q">
+ <refinedDescription><a id="XE_rule_report" name="XE_rule_report"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-G84F_WKYJbQh1mymVCWgxw" name="sme_recommendations,_RkSNqsVWEd2pfdXgw7I2qQ" guid="-G84F_WKYJbQh1mymVCWgxw">
+ <refinedDescription><a id="XE_SME__recommendations" name="XE_SME__recommendations"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-1PQWVqDq_1c_uYCcAzXPjQ" name="rsm_report,_RkSNrMVWEd2pfdXgw7I2qQ" guid="-1PQWVqDq_1c_uYCcAzXPjQ">
+ <refinedDescription><a id="XE_RSM_report" name="XE_RSM_report"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-tlugq7LmqmrzFCxoFyR-AQ" name="deploy_rules,_0xrvQsVWEd2pfdXgw7I2qQ" guid="-tlugq7LmqmrzFCxoFyR-AQ">
+ <refinedDescription><a id="XE_rule__deploy" name="XE_rule__deploy"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-TpaFFyf36HQMpZFFFgj0Cg" name="ruleset,_0xrvQ8VWEd2pfdXgw7I2qQ" guid="-TpaFFyf36HQMpZFFFgj0Cg">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-f6gTOIuqcTE7Bo6RKZ0TqQ" name="synchronize_with_wrms,_0xrvQcVWEd2pfdXgw7I2qQ" guid="-f6gTOIuqcTE7Bo6RKZ0TqQ">
+ <refinedDescription><a id="XE_web-based_brms__synchronize" name="XE_web-based_brms__synchronize"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-2plISeUo4TFYeepdm0sd9g" name="rule_repository_in_db,_0xrvRcVWEd2pfdXgw7I2qQ" guid="-2plISeUo4TFYeepdm0sd9g">
+ <refinedDescription><a id="XE_rule_repository__in_db" name="XE_rule_repository__in_db"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-MfK3a42-JVFgfXFrlgKVCg" name="decision_point_table,_6r4dDMVWEd2pfdXgw7I2qQ" guid="-MfK3a42-JVFgfXFrlgKVCg">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-eUCZh9-TGhKseTixKaMrHg" name="business_process_map,_6r4dCcVWEd2pfdXgw7I2qQ" guid="-eUCZh9-TGhKseTixKaMrHg">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-iQtEn6D9iqYBMMYBWuVKBw" name="discovery_workshop_itinerary,_6r4dFsVWEd2pfdXgw7I2qQ" guid="-iQtEn6D9iqYBMMYBWuVKBw">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-lgSFuLT3lWbTwunMCMdGzA" name="execute_rule_discovery_roadmap,_6r4dCMVWEd2pfdXgw7I2qQ" guid="-lgSFuLT3lWbTwunMCMdGzA">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-jDcrhnRAGpNy9F3lmDQh9A" name="business_terms_glossary,_6r4dCsVWEd2pfdXgw7I2qQ" guid="-jDcrhnRAGpNy9F3lmDQh9A">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Ya6ew2cXy0t86scG8NYWbA" name="rule_description_doc,_6r4dGsVWEd2pfdXgw7I2qQ" guid="-Ya6ew2cXy0t86scG8NYWbA">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-_HXi3XetHAIsFYblsTtTcg" name="conceptual_data_model,_6r4dBsVWEd2pfdXgw7I2qQ" guid="-_HXi3XetHAIsFYblsTtTcg">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-HRHCQT3_ksQap5yLiPUDqg" name="extract_rule_meaning,_6r4c28VWEd2pfdXgw7I2qQ" guid="-HRHCQT3_ksQap5yLiPUDqg">
+ <refinedDescription><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">During the elicitation activity the raw description of the rule uses business terms as used in common
+ language used by the people. This presents what the business users think about the way things are done in the company.
+ They are linking words with statements with all the different semantic attached to them. The first activity focuses on
+ analyzing this rule description&nbsp;to extract&nbsp;the business entities and terms used in a formal non ambiguous
+ fashion.&nbsp;</font></span>
+</p>
+<p>
+ We are discussing about Business Term here, as reference to a business concept used in daily business operations.They
+ are often found in different departments or refer to the same business concept from a different perspective: they are
+ synonyms. A term may describe business concept which will be mapped to a Class, a characteristic of a business entity
+ which will be mapped to attribute of a class, and sometime a term may describe the way a business object behave, in
+ that last case it will be mapped within method of a final state machine.
+</p>
+<p>
+ The second concept presented in the analysis of rule is the Fact. Fact is a combination of terms that describes what
+ business people know about their business. It connects terms into sensible business relevant observations.<br
+ style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple" />
+ As stated by the SBVR specification meaning is built of concepts, questions and propositions. the concepts will build
+ our underlying data model used by the executable rules, and the proposition will structure the data model and can also
+ be mapped to rules.<br />
+</p>
+<p
+style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple">
+ All these informations&nbsp;help to build a&nbsp;first logical data model used to build the underlying object
+ model&nbsp;used by the rules. We can use UML tool to design a class diagram, generates java code and import such code
+ in the rule IDE.<br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Mp1iTCY_ZxvmhCU0pK1B4A" name="rule_description_doc,_6r4c2sVWEd2pfdXgw7I2qQ" guid="-Mp1iTCY_ZxvmhCU0pK1B4A">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Oycd-mszF0ZsLk-8ZeJWHg" name="fact_model,_6r4c0cVWEd2pfdXgw7I2qQ" guid="-Oycd-mszF0ZsLk-8ZeJWHg">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-CqnB4S0O3gkfIdcDYQrDPQ" name="logical_data_model,_6r4c08VWEd2pfdXgw7I2qQ" guid="-CqnB4S0O3gkfIdcDYQrDPQ">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-i-o-ix2w6ehxgG6NXqzYnQ" name="transform_rules,_6r4c3MVWEd2pfdXgw7I2qQ" guid="-i-o-ix2w6ehxgG6NXqzYnQ">
+ <keyConsiderations>This activity will also be done during the implementation of the rule set, but it is started during the analysis, so we are
+detailing it in this context.</keyConsiderations>
+ <refinedDescription><p>
+ Rule Analyst has to study the rule discovered and try to transform it so that the implementation and the management of
+ the rule will be more easy. This includes transforming the rule in atomic element using a syntax without ambiguity,
+ remove redundant rules, conflicting rules, and finally try to redefine the scope of the rule by searching by
+ non-handled cases.&nbsp;
+</p>
+<p>
+ At this stage rule analyst can build some rule template which&nbsp;are built from rules that have the same set of
+ conditions with some little variations: adding new value in test condition, or new condition.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Vw7w7CdsiPTvpIJJdjf1NA" name="build_test_scenario,_6r4c3cVWEd2pfdXgw7I2qQ" guid="-Vw7w7CdsiPTvpIJJdjf1NA">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-lohL0MczQsZKJLN8EUe8IQ" name="synchronize_data_model,_6r4c18VWEd2pfdXgw7I2qQ" guid="-lohL0MczQsZKJLN8EUe8IQ">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst needs to continuously verify that business terms used in rule statements are part of the logical data
+ model (classes/ attributes) and physical data model (PDM). The model exposed to the rule needs to get data from data
+ sources. If a concept is not in the data it has to be quickly handled and managed by the application architect.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst should be in continuous communication with the data model developer, responsible to develop the XML
+ schema or java model (or .Net), and the physical mapping to database.<br />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Part of most of the business application are the list of code, enumerated date or domain values. It is important to
+ well design how those data are defined, accessed by the application, and the rule authoring environment.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ It can be helpful for some major business term to define a mapping to a class-attribute, and if the BRMS supports this
+ function it is recommended to detail the "verbalization" of the business term.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<div align="center">
+ <table class="MsoNormalTable" style="WIDTH: 351pt; BORDER-COLLAPSE: collapse; mso-padding-alt: 0in 0in 0in 0in"
+ cellspacing="0" cellpadding="0" width="468" border="0">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes">
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: gray 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Business Term</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">OO mapping</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Verbalization</span></i>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LTV</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LoanApplication.ltv</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">The loan to value ratio</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in left 3.0in" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-NmUNzIfRKfaj1Arf585V3A" name="determine_rule_implementation,_6r4c-MVWEd2pfdXgw7I2qQ" guid="-NmUNzIfRKfaj1Arf585V3A">
+ <refinedDescription><a id="XE_rule__determine_implementation" name="XE_rule__determine_implementation"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Project teams involved in BRMS deployment are often asking the following type of questions:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus a&nbsp;BPM?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ How do I decide what decisions should I put into a BRE?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus code?&nbsp;
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ There are definitively multiple variables which could influence the decision on where to implement rules. We can start
+ by looking at the BRMS value propositions, it should help to get a first set of variables:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Adaptability – Measure the ability to change the business logic easily. The motivation can be due to short deadline
+ constraint, or frequent small changes or important change that may occur every month or quarter.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Transparency – Represents the need to clearly implement the business logic as what was agreed upon the business
+ unit and the IT team, in a way that every parties understand the logic. This is leading to express the logic in
+ natural or close to natural language.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Auditability – Represents the ability to trace from the business motivation to the execution of the policy to
+ better understand what was the logic behind a decision.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Reusability – Need to share business logic across processes or applications and stay . consistent across
+ applications/transactions
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Manageability- This variable addresses the life cycle management of the business logic. Who writes what, and when,
+ and all the questions related to maintenance and evolutions of the rule-based service.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The purpose here is not to say it is not possible to support those variables in standard software development
+ practices, but more to find some good patterns on how to decide on where to implement the business logic.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ When looking at a business rules statement software engineer can see different possible choices of implementation like:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Data model: designing an object oriented object model involves supporting a lot of business rules. A statement like
+ a mortgage application can have a primary and a secondary borrower, will be supported by two classes and a 1 to 2
+ relationship. At the instantiation of those classes the control of the cardinality can be done in the application
+ logic, or the database, or the GUI structure.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Application code: implementing the logic in function, procedural code or methods in service layer or business
+ objects.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ BPM process flow, tasks or links: BPM tools are addressing business process efficiency issue specifically on "who
+ is involved", "when they should be involved". "what they need to do". BPM supports manual human and automated
+ actors. At a glance the business logic to implement in BPM is linked to people, task, and data to process within a
+ task. When supporting purely automated tasks BPM is orchestrating the application logic and services (BPEL engine).
+ BRMS complements BPM by adding the why to a BPM task, why it behaves a certain way, why this decision is done.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Rule engine: <span style="mso-spacerun: yes">&nbsp;</span>using predefined structure like if then else statement or
+ decision table, rule flow, decision tree, function, rule template or other high level language...
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Graphical user interface: <span style="mso-spacerun: yes">&nbsp;</span>using scripting language or server side code
+ in controller class it is possible to implement data validation type of business rules.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In the following paragraphs address each of different choices with their impact on the variables
+</p><br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in Data Model</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Rule which is controlling the structure of the model and the reference integrity
+ should be in the physical data model, the O/R mapping layer or on the domain object model.</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule setting constraint on relationship -
+ <span style="mso-spacerun: yes">&nbsp;</span>like a loan application could only have two borrowers</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule on the structure of the business
+ entities - like this attribute is part of this object</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following facts are based on a simple
+ user authentication problem, are well implemented in an object model and the supporting application code which
+ create the instance from the data (O/R mapping layer or DAO or service layer):</span>
+ </li>
+</ul>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of users who can login to the application</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of groups of user</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A User is part of a group</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group includes a list of Users</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group has one user reference who is the creator of the group</span>
+</p>
+<p>
+ Terms and facts and derived attributes&nbsp;are the primary constituents of data models and are represented in a UML
+ class diagram, and logical data model (entities/relationship model), or a physical data model.
+</p>
+<p>
+ <span style="mso-bidi-language: HE">The following table lists the impact of this implementation on the previously
+ defined variables</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 221.4pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very static implementation. A change in the constraints of the object model
+ impact, data persistence, logical data model, service and presentation layers. Change is managed on
+ a monthly or yearly basis</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Data model represented as UML classes diagram is doing a poor job to
+ communicate to business. Entities diagram represents a more high level representation of the domain
+ model, but forces the team to maintain the link between the implementation and the business
+ representation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tool, with a strict development process and
+ disciplines can help to trace back to the business motivation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Domain Object model can be designed as reusable. But in the reality each
+ application needs a view of the core business object model, and so part of the implemented
+ application will be to build those view.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tools and strict discipline can help maintain the
+ business logic.</font></span>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in application code</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Implementing business rule in application code is
+ currently the most common way the IT developer is doing it. The major justifications are performance and flexibility of
+ the coding language. Using hard coded if/then/else statements isn't too flexible, but in the hands of a top notch
+ programmer it can be very fast and arguably as fast as or faster than a rule engine. Assuming the programmer has
+ unlimited time to optimize the execution for a fixed set of rules. If the ruleset changes frequently and the system
+ can't tolerate a big drop in performance, than a rule engine is the solution.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following example of business rules may be
+ easily implemented in code:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span class="ISISCodeParagraphChar"><font face="Courier">verify in each items the customer bought since he is customer
+ with us there is at least one article of type T so that we can propose the new product Y with X % of discount, except
+ if the customer is from the state of New York or New Jersey</font></span><span
+ style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">We can implement this in a method which loops on
+ the articles bought by a given customer and do the search. At a first analysis, navigating in a collection of objects
+ and testing multiples conditions on them is easy to implement using the power of programming language.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One thing interesting will be the hard coding of
+ the value of New York, New Jersey... If this logic change we need to add if statements in the code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Other type of rules are related to the control of
+ the execution of a set of "services" to support specific use case. Dispatching, orchestration, data manipulation, … are
+ better candidate to be implemented in application code. Those rules are more static, often more complex, and
+ definitively linked to context of execution. The context may be too complex to expose to a rule engine.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Orchestration are now very well supported by
+ BPM-BPEL engine because the developer needs to add flexibility on the service selection and invocation.<span
+ style="mso-spacerun: yes">&nbsp;</span></span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The evaluation of the important variables
+ is:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 334.25pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">the necessity to change code when a business rule changes is still
+ unpleasant: software build are more efficient and cost less than before but deployment may be
+ expensive depending of the complexity of the production environment. <span
+ style="mso-spacerun: yes">&nbsp;</span></font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Changing code under time pressure usually leads to poor
+ quality</font></span>
+ </p><br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. The logic as defined by the business is split in multiple parts of the
+ code, methods and procedures.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. Only strict use of configuration management tools with a strict
+ development process may help.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">If the logic is implemented in a service layer with defined interface it may
+ be possible to reuse part of the methods.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Developer is
+ responsible to implement the change, and use configuration management tools and strict development
+ disciplines.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in process map</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Business process automation is the technology components substituting and/or
+ supplementing manual processes to manage information flow within an organization to lower costs, reduce risk, and
+ increase consistency. In this context Business rules describe the structure, operation, and strategy of an
+ organization's business process. The business process definition can be seen as a business rule. Typically a rule
+ involving routing of transactional data to a queue, a task, or a sub process will be most likely implemented in a
+ process map. Defined at the link level business rules are linked to the structure of the process flow. Once designed
+ and implemented there is few chance those rule will change. Changing a business process is most of the time risky: we
+ do not want to change thing working and involving a lot of parties and stakeholders. In fact</span> new policies,
+ regulations or business strategies may affect the rules without changing the core business processes.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">A rule like: "<i style="mso-bidi-font-style: normal">if there is an exception in
+ the claim processing we want a supervisor to study the claim and the accumulated reasons extracted by the process so
+ far"</i> will most likely finish as guard on a process map link:</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <img height="348" alt="" src="resources/BRinBPM.bmp" width="313" />
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Task 1 will most of the time call a rule engine to take decision on the claim. One of the pattern is to accumulate all
+ the possible reasons in a list. If the list include an exception or high priority reason, the process map will route to
+ the "Process Exception" task. This task can queue the work item to a supervisor queues.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There are a lot tasks in a business process that are decision rich, so with a lot
+ of business rule to execute before completing the task. Those rules can be executed by a rule engine. The integration
+ Rule Engine – BPM will bring the value to support those cases. But as good practice it is always possible to try to
+ re-arrange an activity diagram of a use case or a process map so that some activities are purely automatically executed
+ in a rule engine mapped as a rule flow.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Business rules hardly coded in using BPM notation is not efficient and lead
+ to complex map. The real design implementation is to mix BPM map and business rules-decision
+ delegated in a process task. In this type of implementation we can leverage the best of both
+ worlds, and the adaptability is excellent.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: when the integration of BPMS and BRMS is done perfectly, the
+ business and IT team have a clear understanding of the process execution and the decision done by a
+ task by studying the rules attached to the task.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: both tools has version control, and it is possible to link
+ process map version to rule set version.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rules defined in a task should be expose to the other application as a
+ service. So reusability can be achieved. Rules in a BPM map are not really reusable.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Process logic will
+ have a more stable life cycle, and it is managed in the BPMS. <span
+ style="mso-spacerun: yes">&nbsp;</span></span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a rule engine</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Any type of rule using a forward chaining approach will best fit in any RETE rule
+ engine. To avoid long explanation a rule engine will perform very efficiently the following rules which are more
+ complex to implement in code:</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Set parameter = A / (B ^ 2)</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If parameter is above 30 then the risk is<span
+ style="mso-spacerun: yes">&nbsp;</span> medium</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If the risk is medium then alert the manager</span>
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><span style="mso-spacerun: yes">&nbsp;</span>If we enter a new value for A all the
+ depend rules will be fired. Rules can be entered in any order we want, it is less declarative than procedural
+ code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Backward chaining rule pattern can also been supported by a rule engine. The rule
+ system works down the tree to find the data that it requires. It will ask question to be able to infer decisions. It is
+ possible to implement backward chaining with product using pure inference by&nbsp;using a goal object.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">As we already stated one of the key factor is flexibility. We already encounter the
+ following decision: "This rule will not change"... but in fact it will do in the future or some of related one"
+ .</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">We can for example take a simple example of a static rule defined as</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 1.9pt 0cm 0pt 18pt; TEXT-ALIGN: justify">
+ <span class="ISISCodeParagraphChar"><font face="Courier">If the status of the customer is gold and the product is
+ &lt;&gt; then apply &lt;&gt; % discount</font></span><span style="mso-bidi-language: HE">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">This rule can be implemented within application code using some tables in a
+ database that link the product, the category of possible status and the discount to apply. But when discussing with the
+ business user to understand what is a gold customer? We can get other conditions that definitively will change over
+ time: "A customer who spend more than &lt;&gt; the amount of money... during the last 6 months ...No !<span
+ style="mso-spacerun: yes">&nbsp;</span> during the last four month only for the product X because it was only available
+ for 4 months!, … Okay but customer in the states {,,,,} could not be part of the gold status... Ah I forgot, ... A
+ customer must have 18 years old, and by the way customer working for our company or subsidiaries could not be part of
+ the gold...</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Excellent, rule can change quickly and be deployed quickly too</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: by adding meta data to implemented rule we can clearly link rule
+ to business strategies and policies</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent and most of the rule engine has log mechanism to trace what were
+ the rules executed on a given transaction.</font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rule reports are important to the business as part of
+ documentation</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very good if the BRMS use rule repository and the rule analyst designed a
+ rule sharing approach</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Excellent as rules
+ are externalized and managed as a standalone artifact. Rule configuration management is complex,
+ and integrity between rule life cycle and rule set versioning is not a simple
+ practice.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a graphical user interface</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ We will base the integration on the Model-View-Controller (MVC) design pattern. The presentation tier handles the
+ client interaction by abstracting the low-level protocol details into an event-based mechanism. The view's main
+ requirement is synchronization with the model so that data displayed to the user is up to date. The controller is
+ responsible to prepare the data and manage the view flow and content. Delegating the creation of content to a rule
+ engine is possible but need to be done synchronously.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The business rule will be related to control the list of widget the GUI will present. A typical pattern is around
+ product catalog application or dynamic questionnaire. The rule pattern to control the content looks like:
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the selection on this page was &lt;&gt; then add this &lt;&gt; to the model
+ used in view &lt;&gt;</i>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ A rule to control the flow of page looks like
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the user visited page &lt;&gt; (and | or page &lt;&gt;) then next page is
+ &lt;&gt;</i>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Both rules may be enriched with business type decision based on data of the model.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In these pattern it is clear we need to keep the previous context of decision, and events the user created.<span
+ style="mso-spacerun: yes">&nbsp;</span> So most of the current applications are putting the business rule in the
+ controller class or in the java script of the view, but it is possible to design the controller to use a rule engine,
+ as soon as the decision needs to change. This is particularly true for e-commerce web site, where marketing campaign
+ can quickly be put in place by proposing product or product feature more dynamically.<span
+ style="mso-spacerun: yes">&nbsp;</span>
+</p><br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-XeTJfes8s01sk2ZVcZ8ORQ" name="decision_point_table,_6r4c9MVWEd2pfdXgw7I2qQ" guid="-XeTJfes8s01sk2ZVcZ8ORQ">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-vseCuvO6sao9pngM_Ax32Q" name="rule_description_doc,_6r4c_sVWEd2pfdXgw7I2qQ" guid="-vseCuvO6sao9pngM_Ax32Q">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ppaJma4emmmK-5NP1JKfEA" name="develop_unit_tests,_6r4c5cVWEd2pfdXgw7I2qQ" guid="-ppaJma4emmmK-5NP1JKfEA">
+ <refinedDescription><a id="XE_unit_tests__develop" name="XE_unit_tests__develop"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Rule Unit Testing is the process of testing a specific rule in the context of the rule set in which it is deployed.
+ Rule Unit Testing allows rule writers to:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Validate each rule in the context of its rule set
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Control the rule set quality
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Conduct some impact analysis when rules are in conflict
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Helps to have non-regression tests
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There is a major difference between testing a code, and a rule. A rule engine per
+ design may not put a rule in the agenda if the conditions are not matched. This means that when the rule writer write a
+ new rule, even if the data are sent to trigger the execution of this new rule it is possible that a rule fired before
+ the new one, with change the condition of the data so that this new rule will never be eligible. Developing a complete
+ set of unit test is an efficient way to see this problem, and to improve the rule set design. Some powerful BRMS
+ platform has rules consistency checking which helps to do some static analysis of those potential conflict by analyzing
+ the conditions and the actions of the rules. For sure real test cases will complete the picture.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<span
+style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Using
+a Test Driven Development approach rule writer can develop the test script preparing the data to trigger each rule,
+depending of the BRMS platform used, the script generation can be done automatically or not. What is important is develop
+reusable test case organized in test suite which include assertion statement to validate the expected results. This is
+efficient tool to put in place automatic non regression tests.</span></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-VRP7bY43MhKouOQxpD791Q" name="develop_rules,_6r4c58VWEd2pfdXgw7I2qQ" guid="-VRP7bY43MhKouOQxpD791Q">
+ <refinedDescription><a id="XE_rule__develop" name="XE_rule__develop"></a>
+<p>
+ Programming using rule approach enforces to know how a rule engine is working. This is not a complex skill, rue author
+ needs to understand&nbsp; the concepts of asserting, retracting object into working memory and modifying them. It is
+ recommended to read what a <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_engine_A66B71B3.html"
+ guid="_QQcSoEXXEdy14e5PT9v3HQ">Rule engine</a>&nbsp;is to get those concepts.
+</p>
+<p>
+ Rule development can follow a test driven development approach: the developer can develop the test cases to trigger the
+ rule execution and then write the rules. Once done the new rules are extracted with the other rules in the rule set,
+ deployed to the unit test environment and the test executes. When designing with interface the unit test uses the
+ facade to access the rule engine for&nbsp;the execution.
+</p>
+<p>
+ When rules are complex and include a lot of conditions it may make sense to add condition by steps. It may be easy to
+ make error by using a wrong boolean operator. When the rue language support navigating into collection the testing may
+ include test around the presence and not presence of element in the collection.
+</p>
+<p>
+ It is always interesting once the rule is developed to perform rule analysis if the BRMS product has this capability.
+ The analysis helps to see if the current rule is in conflict with existing rules.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-mU2cfiy9SzQO2aBAKn6lEQ" name="ruleset,_6r4c5MVWEd2pfdXgw7I2qQ" guid="-mU2cfiy9SzQO2aBAKn6lEQ">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Q0OitIPVg9I1Oq_g9_XCiw" name="enhance_object_models,_6r4c4MVWEd2pfdXgw7I2qQ" guid="-Q0OitIPVg9I1Oq_g9_XCiw">
+ <refinedDescription>Typically the developer adds helper methods in the data model to facilitate the rule writing. Develop utility classes. The
+data elements should not have persistence logic in it. For example in Java do not put JDBC code in the Customer object. Let
+try to stick to the Java bean specification for all the&nbsp;business objects, and leverage a service layer, with service
+facades objects to help gathering and process data.&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-gmJa6dJF634bZnYGdnthtw" name="execute_rule_set,_6r4c48VWEd2pfdXgw7I2qQ" guid="-gmJa6dJF634bZnYGdnthtw">
+ <refinedDescription><a id="XE_rule_set__execute" name="XE_rule_set__execute"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-TunYKZqNMaMlNqp73EpPgA" name="log_issue,_6r4c4sVWEd2pfdXgw7I2qQ" guid="-TunYKZqNMaMlNqp73EpPgA">
+ <refinedDescription><ul>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Formally log any issues and decisions done during the rule
+ analysis and the rule authoring activities.</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The issue
+ log is used to manage feedbacks, and to improve the rule set quality.</span></span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-weight: bold">As a social process, people will
+ change their mind, it is a good practice to log decision on a timely manner.</span>
+ </div>
+ </li>
+</ul><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-y4Aw5AGHiDwN62DoU72gvw" name="execute_ruleset_functional_test,_6r4dJsVWEd2pfdXgw7I2qQ" guid="-y4Aw5AGHiDwN62DoU72gvw">
+ <refinedDescription><a id="XE_rule_set__execute_functional_tests" name="XE_rule_set__execute_functional_tests"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-5G8CfPgnZh36ji0ZlYzYXQ" name="get_rule_set_reports,_6r4dIcVWEd2pfdXgw7I2qQ" guid="-5G8CfPgnZh36ji0ZlYzYXQ">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-aGsq4sRPoN9Rg2zOy4BOaQ" name="get_sme_feedback,_6r4dJ8VWEd2pfdXgw7I2qQ" guid="-aGsq4sRPoN9Rg2zOy4BOaQ">
+ <refinedDescription><a id="XE_SME__get_feedback" name="XE_SME__get_feedback"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ndrhF3xLLIGB3LyVVM1-Lg" name="test_analysis,_6r4dJcVWEd2pfdXgw7I2qQ" guid="-ndrhF3xLLIGB3LyVVM1-Lg">
+ <refinedDescription><a id="XE_test_analysis" name="XE_test_analysis"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-1bBmUUB5_pPRA1-9EE-g7A" name="ruleset,_6r4dH8VWEd2pfdXgw7I2qQ" guid="-1bBmUUB5_pPRA1-9EE-g7A">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-z7C-L5MyFxgpQP2wmgkaCg" name="rule_report,_6r4dIMVWEd2pfdXgw7I2qQ" guid="-z7C-L5MyFxgpQP2wmgkaCg">
+ <refinedDescription><a id="XE_rule_report" name="XE_rule_report"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-IM6GVp0gm8GpDQQHu1JTzA" name="sme_recommendations,_6r4dIsVWEd2pfdXgw7I2qQ" guid="-IM6GVp0gm8GpDQQHu1JTzA">
+ <refinedDescription><a id="XE_SME__recommendations" name="XE_SME__recommendations"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-EuY3fQmZi-sssGgLCoGwqw" name="rsm_report,_6r4dJMVWEd2pfdXgw7I2qQ" guid="-EuY3fQmZi-sssGgLCoGwqw">
+ <refinedDescription><a id="XE_RSM_report" name="XE_RSM_report"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-x18L5UZxvP6LBzZCJekP0g" name="deploy_rules,_6r4c68VWEd2pfdXgw7I2qQ" guid="-x18L5UZxvP6LBzZCJekP0g">
+ <refinedDescription><a id="XE_rule__deploy" name="XE_rule__deploy"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-VIexLG3fR5IHNPWD53_k-w" name="ruleset,_6r4c7MVWEd2pfdXgw7I2qQ" guid="-VIexLG3fR5IHNPWD53_k-w">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-yhAuH0Pn0YnmJPGHNdA4nA" name="synchronize_with_wrms,_6r4c6sVWEd2pfdXgw7I2qQ" guid="-yhAuH0Pn0YnmJPGHNdA4nA">
+ <refinedDescription><a id="XE_web-based_brms__synchronize" name="XE_web-based_brms__synchronize"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-92jwAW4UkB6tPCOwNbvKuw" name="rule_repository_in_db,_6r4c7sVWEd2pfdXgw7I2qQ" guid="-92jwAW4UkB6tPCOwNbvKuw">
+ <refinedDescription><a id="XE_rule_repository__in_db" name="XE_rule_repository__in_db"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/deliveryprocesses/abrd_process/model.xmi b/epf_prac_151/process.abrd.base/deliveryprocesses/abrd_process/model.xmi
index d1cb1f6..a1718a2 100644
--- a/epf_prac_151/process.abrd.base/deliveryprocesses/abrd_process/model.xmi
+++ b/epf_prac_151/process.abrd.base/deliveryprocesses/abrd_process/model.xmi
@@ -21,26 +21,161 @@
<resourceDescriptors xmi:id="__bLXgrekEd-D7YZN9NgldQ" id="-fxBunH2zP8bxL0NEj54ptA" uri="content.xmi"/>
<resourceDescriptors xmi:id="__bUhcLekEd-D7YZN9NgldQ" id="-UobSWGrKBmEhg8A39R5yLg" uri="content.xmi"/>
<resourceDescriptors xmi:id="__bUhcbekEd-D7YZN9NgldQ" id="-Ui61NyVqm4OfNM8QodL5rQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9fzWQFmSEeCcpdiAcH0w-w" id="-hSvA_8i1JXnAg_ktO4yhVw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9fzWQVmSEeCcpdiAcH0w-w" id="-EyvRETbaInP9YwVRsjUmpg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9fzWQlmSEeCcpdiAcH0w-w" id="-7Qhv3MVOtdt02aO-ujeUXQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9f9HQFmSEeCcpdiAcH0w-w" id="-wn8vCP9iknXfxQNa_Gt3Zg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9f9HQVmSEeCcpdiAcH0w-w" id="-SZIhc8oXvpac5M1fKbXgTA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9f9HQlmSEeCcpdiAcH0w-w" id="-z6-Qx7OJfj-Yq25AioSjCg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9gGRMFmSEeCcpdiAcH0w-w" id="-FbRsIZayJhCaFmbyRB96Cg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9gGRMVmSEeCcpdiAcH0w-w" id="-G5nrokl8FZiZW26GR8U4Fg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9gQCMFmSEeCcpdiAcH0w-w" id="-rQeo3KBsjTpEofLhWWoCHg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9gQCMVmSEeCcpdiAcH0w-w" id="-SVG8fBamP9jI0gLGSNQYPg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9gZzMFmSEeCcpdiAcH0w-w" id="-Ol-Ismqi_vwu93DuUULISw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9gi9IFmSEeCcpdiAcH0w-w" id="-xywJ9rs6yDU3S-RR7R6DHw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9gi9IVmSEeCcpdiAcH0w-w" id="-nWwIrDx_rgbWN_dCjIPeGg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9gsuIFmSEeCcpdiAcH0w-w" id="-Zgt8ljNbGXKcbU4gzUCQrg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9g_pEFmSEeCcpdiAcH0w-w" id="-NjDm5kyrlZVxH1HwaGoVFA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9g_pEVmSEeCcpdiAcH0w-w" id="-LZfO28SzpOMkRDb62aUppg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9hJaEFmSEeCcpdiAcH0w-w" id="-cAqcd_rDIyDggEFNkpOafA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9hJaEVmSEeCcpdiAcH0w-w" id="-TMElbWb1oCm06CVVbtGziA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9hSkAFmSEeCcpdiAcH0w-w" id="-cldFzj8jYSiyDtkZGFpjQQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9hSkAlmSEeCcpdiAcH0w-w" id="-JMP5iTEzmgde5KqHrptXyA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9hvP8VmSEeCcpdiAcH0w-w" id="-f3XkJ0vY-f93Cugh2hUPag" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9hvP8lmSEeCcpdiAcH0w-w" id="-XJgsI3tf1RyfJOE8nXKyfA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9h5A8FmSEeCcpdiAcH0w-w" id="-FYiTjOVLhDDFiks9REzbWw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9h5A8VmSEeCcpdiAcH0w-w" id="-I69B91Gv39Hsf4q9QC8gdw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9iCK4FmSEeCcpdiAcH0w-w" id="--xaKhVngfn0TG7AUCYDE2Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9iCK4VmSEeCcpdiAcH0w-w" id="-ZxuH1YXgB-PGC8KKf8SqMA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9iL74FmSEeCcpdiAcH0w-w" id="-cQYuDYNpIetEa-A0wc2rMA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9iL74VmSEeCcpdiAcH0w-w" id="-NBqg7ns9nlUev0xlKSBKVg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ion0VmSEeCcpdiAcH0w-w" id="-1EFb1j163vesKIPD-WKc_A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9iyY0FmSEeCcpdiAcH0w-w" id="-30jW7XM9GTETWwegnerK-g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9iyY0VmSEeCcpdiAcH0w-w" id="-QosjoU1KKqxnanfXEHADUQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9i7iwFmSEeCcpdiAcH0w-w" id="-Jkw-vxUJt3NMdOu_yUsNgw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9i7iwVmSEeCcpdiAcH0w-w" id="-jD0SjTGEVGjAXwk-96CnBw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9jFTwVmSEeCcpdiAcH0w-w" id="-pxSSUK3yjMwpuFplEiArVA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9jOdsFmSEeCcpdiAcH0w-w" id="-1hKEhTu7zfbuOyxxSBfTVA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9jh_sFmSEeCcpdiAcH0w-w" id="-ujEcUPK8pFeN7wqLRcSB9A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9jh_sVmSEeCcpdiAcH0w-w" id="-GSA2k4CiOuK856zbdHf6bw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9jrJoFmSEeCcpdiAcH0w-w" id="-A69eNZMgOD-TmrIh98RJsg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9jrJoVmSEeCcpdiAcH0w-w" id="-7KXY0dEtZ02k-zR2uSgrLw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9j06oVmSEeCcpdiAcH0w-w" id="-DLOZ9q9zKzqSH02qulirKQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9j-roFmSEeCcpdiAcH0w-w" id="-WpMajOrHlIGWS4oIiTfIgQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9j-roVmSEeCcpdiAcH0w-w" id="-mw3UMRnpZKKJ1HXl4Tx2GA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9kH1kFmSEeCcpdiAcH0w-w" id="-TzodlLaSF7x8Ox7OmJmUyg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9kRmkFmSEeCcpdiAcH0w-w" id="-3TEm3EjK2B_3xvMAHjQHWw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9kRmkVmSEeCcpdiAcH0w-w" id="-wUfIZbnlisjRJ7z3OjFsUQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9kawgVmSEeCcpdiAcH0w-w" id="-bLL0Fi0p_lu2XVXfO4Bmng" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9kkhgFmSEeCcpdiAcH0w-w" id="-pk5as0BVClbnn3B7FhmN3A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9kuSgFmSEeCcpdiAcH0w-w" id="-9bcuy4Hs_gwTKjG8NyKAPw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9kuSgVmSEeCcpdiAcH0w-w" id="-oYF8elqKsD5hfhKlCij3xQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9k3ccFmSEeCcpdiAcH0w-w" id="-OJ8H_2tSlsUq645zMbm48Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9lBNcVmSEeCcpdiAcH0w-w" id="-AG5WgBy68mLoQW6HqHTusQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9lK-cFmSEeCcpdiAcH0w-w" id="-VLRdP6iYek0zEo_rHnIppw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9lK-cVmSEeCcpdiAcH0w-w" id="-BBnqXNX3L83SEuYSuaMdxw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9lUIYFmSEeCcpdiAcH0w-w" id="-ZBEhisTrkRvWYQ7SWQP4eg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ld5YFmSEeCcpdiAcH0w-w" id="-rH1vUc8rldU1_AKYYx9dBA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ld5YVmSEeCcpdiAcH0w-w" id="-bvUOgHIu3fluB7VANjXFJg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9lnDUFmSEeCcpdiAcH0w-w" id="-ewbo32yGFGXgBOLZ6El0qQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9mDvQFmSEeCcpdiAcH0w-w" id="-c8q_v1s1n7aK-0miFaupPw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9mDvQVmSEeCcpdiAcH0w-w" id="-yaB5VmxyoNnFc5KAKx87uw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9mNgQFmSEeCcpdiAcH0w-w" id="-jiPE4qjhy0-GvsHSu8k4hw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9mXRQFmSEeCcpdiAcH0w-w" id="-N9JRT0YykF7mF_nPmGpEig" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9mXRQVmSEeCcpdiAcH0w-w" id="-wKyQQHGWKPhxgDMava9lMA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9mgbMFmSEeCcpdiAcH0w-w" id="-bN3NfZ3WOIrkhDKHWDPKkA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9mqMMFmSEeCcpdiAcH0w-w" id="-l1seeyWf2ab1M7_-vwsRiQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9m9HIFmSEeCcpdiAcH0w-w" id="-teqRVFQdfi3M0E_2hPt2OA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9nG4IFmSEeCcpdiAcH0w-w" id="-7obhtj52BKnAGY2bh-MvLw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9nG4IVmSEeCcpdiAcH0w-w" id="-KnXTyJRJlBDBK68DXO57Uw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9nQCEFmSEeCcpdiAcH0w-w" id="-sMysBcAYtIvVDmB57oo8sA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9nZzEFmSEeCcpdiAcH0w-w" id="-bcOPKdssk4qvaJmaJ82Wdg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9nsuAFmSEeCcpdiAcH0w-w" id="-D86vI3p-CJqtaGHovLIH3A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9nsuAVmSEeCcpdiAcH0w-w" id="-Qy_wVwt9Qh9iVf4FyNvOag" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9oJZ8FmSEeCcpdiAcH0w-w" id="-7BTHzZPiw1v_S2Ts1aJNBA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9oTK8FmSEeCcpdiAcH0w-w" id="--tH7_LHDMrDWKm6h9JBFsA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ocU4FmSEeCcpdiAcH0w-w" id="-yPcK13A7M5bOTTJG-OiLTQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ocU4VmSEeCcpdiAcH0w-w" id="-z_nnzuHQecgXrHgcz9F0qw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ov24FmSEeCcpdiAcH0w-w" id="--__8DYtnVs9eZArH2GikBg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9o5A0FmSEeCcpdiAcH0w-w" id="-xrmI1p-ME165PzMiVzJ8Sw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9pCx0FmSEeCcpdiAcH0w-w" id="-uuWfS5EV0FimZ5_4aRVtjA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9pL7wFmSEeCcpdiAcH0w-w" id="-zUb0cau__Hfq13SvkX5QLw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9pVswFmSEeCcpdiAcH0w-w" id="-xZmMlKJ2ELDM5ehTI5-ouA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9pfdwFmSEeCcpdiAcH0w-w" id="-QGPmaN2xy-Wgo3ltSi79iA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9qYOkFmSEeCcpdiAcH0w-w" id="-I90uzl3ItrvAQBeMg-l9pw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9qh_kFmSEeCcpdiAcH0w-w" id="-h_Q4rpmMhckmEL3epy5j4Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9qrwkFmSEeCcpdiAcH0w-w" id="-JkOVgFn0THaQU3V_LciXbg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9q06gFmSEeCcpdiAcH0w-w" id="-LGCZRD2iL1EzFH3_LqlAJg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9q-rgFmSEeCcpdiAcH0w-w" id="-UbMVWUVbdTcZeO_raP_Zmg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9rIcgFmSEeCcpdiAcH0w-w" id="-fwowC3JkpIga2H7YGyHA4Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9rRmcFmSEeCcpdiAcH0w-w" id="-G84F_WKYJbQh1mymVCWgxw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9rbXcFmSEeCcpdiAcH0w-w" id="-1PQWVqDq_1c_uYCcAzXPjQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9rkhYFmSEeCcpdiAcH0w-w" id="-tlugq7LmqmrzFCxoFyR-AQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ruSYFmSEeCcpdiAcH0w-w" id="-TpaFFyf36HQMpZFFFgj0Cg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ruSYVmSEeCcpdiAcH0w-w" id="-f6gTOIuqcTE7Bo6RKZ0TqQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9sK-UFmSEeCcpdiAcH0w-w" id="-2plISeUo4TFYeepdm0sd9g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9snqQFmSEeCcpdiAcH0w-w" id="-MfK3a42-JVFgfXFrlgKVCg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9sw0MFmSEeCcpdiAcH0w-w" id="-eUCZh9-TGhKseTixKaMrHg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9s6lMFmSEeCcpdiAcH0w-w" id="-iQtEn6D9iqYBMMYBWuVKBw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9tEWMFmSEeCcpdiAcH0w-w" id="-lgSFuLT3lWbTwunMCMdGzA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9tNgIFmSEeCcpdiAcH0w-w" id="-jDcrhnRAGpNy9F3lmDQh9A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9tNgIVmSEeCcpdiAcH0w-w" id="-Ya6ew2cXy0t86scG8NYWbA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9tXRIFmSEeCcpdiAcH0w-w" id="-_HXi3XetHAIsFYblsTtTcg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9thCIFmSEeCcpdiAcH0w-w" id="-HRHCQT3_ksQap5yLiPUDqg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9t9HAFmSEeCcpdiAcH0w-w" id="-Mp1iTCY_ZxvmhCU0pK1B4A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9uG4AFmSEeCcpdiAcH0w-w" id="-Oycd-mszF0ZsLk-8ZeJWHg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9uG4AVmSEeCcpdiAcH0w-w" id="-CqnB4S0O3gkfIdcDYQrDPQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9uQpAFmSEeCcpdiAcH0w-w" id="-i-o-ix2w6ehxgG6NXqzYnQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9uZy8FmSEeCcpdiAcH0w-w" id="-Vw7w7CdsiPTvpIJJdjf1NA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9utU8FmSEeCcpdiAcH0w-w" id="-lohL0MczQsZKJLN8EUe8IQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9u2e4FmSEeCcpdiAcH0w-w" id="-NmUNzIfRKfaj1Arf585V3A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9vTK0FmSEeCcpdiAcH0w-w" id="-XeTJfes8s01sk2ZVcZ8ORQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9vc70FmSEeCcpdiAcH0w-w" id="-vseCuvO6sao9pngM_Ax32Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9vmFwFmSEeCcpdiAcH0w-w" id="-ppaJma4emmmK-5NP1JKfEA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9vv2wFmSEeCcpdiAcH0w-w" id="-VRP7bY43MhKouOQxpD791Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9wCxsFmSEeCcpdiAcH0w-w" id="-mU2cfiy9SzQO2aBAKn6lEQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9wMisFmSEeCcpdiAcH0w-w" id="-Q0OitIPVg9I1Oq_g9_XCiw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9wVsoFmSEeCcpdiAcH0w-w" id="-gmJa6dJF634bZnYGdnthtw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9wfdoFmSEeCcpdiAcH0w-w" id="-TunYKZqNMaMlNqp73EpPgA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9wpOoFmSEeCcpdiAcH0w-w" id="-y4Aw5AGHiDwN62DoU72gvw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9wyYkFmSEeCcpdiAcH0w-w" id="-5G8CfPgnZh36ji0ZlYzYXQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9w8JkFmSEeCcpdiAcH0w-w" id="-aGsq4sRPoN9Rg2zOy4BOaQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9xF6kFmSEeCcpdiAcH0w-w" id="-ndrhF3xLLIGB3LyVVM1-Lg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9xPEgFmSEeCcpdiAcH0w-w" id="-1bBmUUB5_pPRA1-9EE-g7A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9xh_cFmSEeCcpdiAcH0w-w" id="-z7C-L5MyFxgpQP2wmgkaCg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9xrwcFmSEeCcpdiAcH0w-w" id="-IM6GVp0gm8GpDQQHu1JTzA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9x1hcFmSEeCcpdiAcH0w-w" id="-EuY3fQmZi-sssGgLCoGwqw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9x-rYFmSEeCcpdiAcH0w-w" id="-x18L5UZxvP6LBzZCJekP0g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9yIcYFmSEeCcpdiAcH0w-w" id="-VIexLG3fR5IHNPWD53_k-w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9ySNYFmSEeCcpdiAcH0w-w" id="-yhAuH0Pn0YnmJPGHNdA4nA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_9yuSQFmSEeCcpdiAcH0w-w" id="-92jwAW4UkB6tPCOwNbvKuw" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_2EcLMHqlEd2o_5d3MWaNxQ" name="abrd_process" guid="_2EcLMHqlEd2o_5d3MWaNxQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWjybekEd-D7YZN9NgldQ" name="Harvesting" guid="_9tWjybekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWjyrekEd-D7YZN9NgldQ" name="discover_business_rules" guid="_9tWjyrekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_nIvp5cVVEd2pfdXgw7I2qQ" name="discover_business_rules" guid="_nIvp5cVVEd2pfdXgw7I2qQ" presentationName="Discover Business Rules" superActivities="_CryGMHqmEd2o_5d3MWaNxQ" breakdownElements="_nIvp4cVVEd2pfdXgw7I2qQ _nIvp28VVEd2pfdXgw7I2qQ _nIvp6cVVEd2pfdXgw7I2qQ _QYBzMD3gEd-rQL4FfV6WbQ _nIvp2MVVEd2pfdXgw7I2qQ _nIvp0sVVEd2pfdXgw7I2qQ _nIvp2cVVEd2pfdXgw7I2qQ _nIvp1sVVEd2pfdXgw7I2qQ _nIvp3MVVEd2pfdXgw7I2qQ _nIvp4sVVEd2pfdXgw7I2qQ _nIvp1MVVEd2pfdXgw7I2qQ _nIvp4MVVEd2pfdXgw7I2qQ _nIvp48VVEd2pfdXgw7I2qQ _nIvp1cVVEd2pfdXgw7I2qQ _nIvp18VVEd2pfdXgw7I2qQ _nIvp58VVEd2pfdXgw7I2qQ _nIvp08VVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_nIvp5cVVEd2pfdXgw7I2qQ" name="discover_business_rules" guid="_nIvp5cVVEd2pfdXgw7I2qQ" presentationName="Discover Business Rules" superActivities="_CryGMHqmEd2o_5d3MWaNxQ" breakdownElements="_nIvp6cVVEd2pfdXgw7I2qQ _QYBzMD3gEd-rQL4FfV6WbQ _nIvp2MVVEd2pfdXgw7I2qQ _nIvp2cVVEd2pfdXgw7I2qQ _nIvp1sVVEd2pfdXgw7I2qQ _nIvp3MVVEd2pfdXgw7I2qQ _nIvp1MVVEd2pfdXgw7I2qQ _nIvp4MVVEd2pfdXgw7I2qQ _nIvp48VVEd2pfdXgw7I2qQ _nIvp1cVVEd2pfdXgw7I2qQ _nIvp18VVEd2pfdXgw7I2qQ _nIvp58VVEd2pfdXgw7I2qQ _nIvp08VVEd2pfdXgw7I2qQ _uJON1FmSEeCcpdiAcH0w-w _uJXXwVmSEeCcpdiAcH0w-w">
<presentation xmi:id="-Nbe8Rdqjq4lgoQ95Y0ot9g" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Nbe8Rdqjq4lgoQ95Y0ot9g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_nIvp4cVVEd2pfdXgw7I2qQ" name="rule_analyst" guid="_nIvp4cVVEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" modifies="_nIvp2cVVEd2pfdXgw7I2qQ _nIvp1MVVEd2pfdXgw7I2qQ _nIvp18VVEd2pfdXgw7I2qQ _nIvp58VVEd2pfdXgw7I2qQ _nIvp08VVEd2pfdXgw7I2qQ" responsibleFor="_nIvp6cVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_nIvp28VVEd2pfdXgw7I2qQ" name="business_analyst" guid="_nIvp28VVEd2pfdXgw7I2qQ" presentationName="Business Analyst" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" responsibleFor="_nIvp6cVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp6cVVEd2pfdXgw7I2qQ" name="use_case_model" guid="_nIvp6cVVEd2pfdXgw7I2qQ" presentationName="Use-Case Model" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp6cVVEd2pfdXgw7I2qQ" name="use_case_model" guid="_nIvp6cVVEd2pfdXgw7I2qQ" presentationName="Use-Case Model" briefDescription="This artifact captures a model of the intended functions and environment of the system and serves as a contract between the customer and the team." isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_QYBzMD3gEd-rQL4FfV6WbQ" name="Identify Decision Point" guid="_QYBzMD3gEd-rQL4FfV6WbQ" presentationName="Identify Decision Point" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_QYBzMD3gEd-rQL4FfV6WbQ" name="identify_decision_point" guid="_QYBzMD3gEd-rQL4FfV6WbQ" presentationName="Identify Decision Points" briefDescription="Decision points are points of variability and decision in a business process. The goal of this task is to list the potential decision points in scope for the project." superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" output="_nIvp2cVVEd2pfdXgw7I2qQ _uJON1FmSEeCcpdiAcH0w-w">
+ <presentation xmi:id="-hSvA_8i1JXnAg_ktO4yhVw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-hSvA_8i1JXnAg_ktO4yhVw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yNUigIMUEd-68ahhmSUqHw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_A2d5sCyQEd-ER8gMc_Ftrw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nIvp2MVVEd2pfdXgw7I2qQ" name="review_decision_point_table" guid="_nIvp2MVVEd2pfdXgw7I2qQ" presentationName="Review decision point table, business process map, use case model" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" linkToPredecessor="_ZJ870D3gEd-rQL4FfV6WbQ" isSynchronizedWithSource="false" additionallyPerformedBy="_nIvp0sVVEd2pfdXgw7I2qQ _nIvp28VVEd2pfdXgw7I2qQ" mandatoryInput="_nIvp2cVVEd2pfdXgw7I2qQ" optionalInput="_nIvp1sVVEd2pfdXgw7I2qQ _nIvp6cVVEd2pfdXgw7I2qQ" output="_nIvp2cVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_nIvp4cVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nIvp2MVVEd2pfdXgw7I2qQ" name="review_decision_point_table" guid="_nIvp2MVVEd2pfdXgw7I2qQ" presentationName="Review Decision Point Table, Business Process Map, Use Case Model" briefDescription="After the business modeling activity of the Inception Phase the project team should have a decision point table document as a source for the rule discovery phase. A review of each decision point is needed. If this table is not present the team can start by the current business process description and then layouts this DP table." superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" linkToPredecessor="_ZJ870D3gEd-rQL4FfV6WbQ" isSynchronizedWithSource="false" mandatoryInput="_nIvp1sVVEd2pfdXgw7I2qQ" optionalInput="_nIvp6cVVEd2pfdXgw7I2qQ _nIvp2cVVEd2pfdXgw7I2qQ" output="_nIvp2cVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-EyvRETbaInP9YwVRsjUmpg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-EyvRETbaInP9YwVRsjUmpg"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Fpgz4HqsEd2o_5d3MWaNxQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWzAjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_sruWzQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_XA_IIHrPEd2o_5d3MWaNxQ"/>
@@ -50,28 +185,33 @@
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_sruWzgjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_ZJ870D3gEd-rQL4FfV6WbQ" guid="_ZJ870D3gEd-rQL4FfV6WbQ" pred="_QYBzMD3gEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_nIvp0sVVEd2pfdXgw7I2qQ" name="subject_matter_expert" guid="_nIvp0sVVEd2pfdXgw7I2qQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp2cVVEd2pfdXgw7I2qQ" name="decision_point_table" guid="_nIvp2cVVEd2pfdXgw7I2qQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-7Qhv3MVOtdt02aO-ujeUXQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-7Qhv3MVOtdt02aO-ujeUXQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp1sVVEd2pfdXgw7I2qQ" name="business_process_map" guid="_nIvp1sVVEd2pfdXgw7I2qQ" presentationName="Business Process Map" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp1sVVEd2pfdXgw7I2qQ" name="business_process_map" guid="_nIvp1sVVEd2pfdXgw7I2qQ" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-wn8vCP9iknXfxQNa_Gt3Zg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-wn8vCP9iknXfxQNa_Gt3Zg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nIvp3MVVEd2pfdXgw7I2qQ" name="define_discovery_roadmap" guid="_nIvp3MVVEd2pfdXgw7I2qQ" presentationName="Define discovery roadmap" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" linkToPredecessor="_nIvp3cVVEd2pfdXgw7I2qQ" additionallyPerformedBy="_nIvp4sVVEd2pfdXgw7I2qQ _nIvp28VVEd2pfdXgw7I2qQ" mandatoryInput="_nIvp2cVVEd2pfdXgw7I2qQ" optionalInput="_nIvp6cVVEd2pfdXgw7I2qQ _nIvp1sVVEd2pfdXgw7I2qQ" output="_nIvp1MVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_nIvp4cVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nIvp3MVVEd2pfdXgw7I2qQ" name="define_discovery_roadmap" guid="_nIvp3MVVEd2pfdXgw7I2qQ" presentationName="Define Discovery Roadmap" briefDescription="The definition of the discovery roadmap is an important step to understand how the development team will extract the rules from the different kind of sources. There are multiple types of roadmaps according to the different starting points and rule sources." superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" linkToPredecessor="_nIvp3cVVEd2pfdXgw7I2qQ" mandatoryInput="_nIvp2cVVEd2pfdXgw7I2qQ" optionalInput="_nIvp6cVVEd2pfdXgw7I2qQ _nIvp1sVVEd2pfdXgw7I2qQ _uJXXwVmSEeCcpdiAcH0w-w" output="_nIvp1MVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-SZIhc8oXvpac5M1fKbXgTA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-SZIhc8oXvpac5M1fKbXgTA"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWygjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxgjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-Ak_E6i3qbz4NMG7ynyf4DA#_srklyQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-Ak_E6i3qbz4NMG7ynyf4DA#_srklxwjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_nIvp3cVVEd2pfdXgw7I2qQ" guid="_nIvp3cVVEd2pfdXgw7I2qQ" pred="_nIvp2MVVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_nIvp4sVVEd2pfdXgw7I2qQ" name="project_manager" guid="_nIvp4sVVEd2pfdXgw7I2qQ" presentationName="Project Manager" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" modifies="_nIvp48VVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp1MVVEd2pfdXgw7I2qQ" name="rule_discovery_roadmap" guid="_nIvp1MVVEd2pfdXgw7I2qQ" presentationName="Rule discovery roadmap" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp1MVVEd2pfdXgw7I2qQ" name="rule_discovery_roadmap" guid="_nIvp1MVVEd2pfdXgw7I2qQ" presentationName="Rule Discovery Roadmap" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-z6-Qx7OJfj-Yq25AioSjCg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-z6-Qx7OJfj-Yq25AioSjCg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWygjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2QjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1QjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nIvp4MVVEd2pfdXgw7I2qQ" name="organise_workshop" guid="_nIvp4MVVEd2pfdXgw7I2qQ" presentationName="Organize workshop" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" linkToPredecessor="_nIvp38VVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" additionallyPerformedBy="_nIvp28VVEd2pfdXgw7I2qQ _nIvp4cVVEd2pfdXgw7I2qQ" mandatoryInput="_nIvp1MVVEd2pfdXgw7I2qQ" output="_nIvp48VVEd2pfdXgw7I2qQ" performedPrimarilyBy="_nIvp4sVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nIvp4MVVEd2pfdXgw7I2qQ" name="organise_workshop" guid="_nIvp4MVVEd2pfdXgw7I2qQ" presentationName="Organize Workshop" briefDescription="In case of human source for the rule the team needs to organize elicitation workshops" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" linkToPredecessor="_nIvp38VVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" mandatoryInput="_nIvp1MVVEd2pfdXgw7I2qQ" output="_nIvp48VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-FbRsIZayJhCaFmbyRB96Cg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-FbRsIZayJhCaFmbyRB96Cg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0QjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWxAjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-ffYBUOhR5mZssG9eZxktmg#_sruWyQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-ffYBUOhR5mZssG9eZxktmg#_sruWxwjqEdyj5bYZ0eCR5g"/>
@@ -81,9 +221,13 @@
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_nIvp38VVEd2pfdXgw7I2qQ" guid="_nIvp38VVEd2pfdXgw7I2qQ" pred="_nIvp3MVVEd2pfdXgw7I2qQ"/>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp48VVEd2pfdXgw7I2qQ" name="discovery_workshop_itinerary" guid="_nIvp48VVEd2pfdXgw7I2qQ" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-G5nrokl8FZiZW26GR8U4Fg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-G5nrokl8FZiZW26GR8U4Fg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nIvp1cVVEd2pfdXgw7I2qQ" name="execute_rule_discovery_roadmap" guid="_nIvp1cVVEd2pfdXgw7I2qQ" presentationName="Execute rule discovery roadmap" hasMultipleOccurrences="true" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" isRepeatable="true" linkToPredecessor="_nIvp5sVVEd2pfdXgw7I2qQ" additionallyPerformedBy="_nIvp28VVEd2pfdXgw7I2qQ _nIvp0sVVEd2pfdXgw7I2qQ" mandatoryInput="_nIvp1sVVEd2pfdXgw7I2qQ _nIvp2cVVEd2pfdXgw7I2qQ" optionalInput="_nIvp48VVEd2pfdXgw7I2qQ" output="_nIvp18VVEd2pfdXgw7I2qQ _nIvp58VVEd2pfdXgw7I2qQ _nIvp08VVEd2pfdXgw7I2qQ" performedPrimarilyBy="_nIvp4cVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nIvp1cVVEd2pfdXgw7I2qQ" name="execute_rule_discovery_roadmap" guid="_nIvp1cVVEd2pfdXgw7I2qQ" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." hasMultipleOccurrences="true" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ" isRepeatable="true" linkToPredecessor="_nIvp5sVVEd2pfdXgw7I2qQ" mandatoryInput="_nIvp1sVVEd2pfdXgw7I2qQ _nIvp2cVVEd2pfdXgw7I2qQ" optionalInput="_nIvp48VVEd2pfdXgw7I2qQ" output="_nIvp18VVEd2pfdXgw7I2qQ _nIvp58VVEd2pfdXgw7I2qQ _nIvp08VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-rQeo3KBsjTpEofLhWWoCHg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-rQeo3KBsjTpEofLhWWoCHg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
@@ -91,40 +235,69 @@
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_nIvp5sVVEd2pfdXgw7I2qQ" guid="_nIvp5sVVEd2pfdXgw7I2qQ" pred="_nIvp4MVVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp18VVEd2pfdXgw7I2qQ" name="business_terms_glossary" guid="_nIvp18VVEd2pfdXgw7I2qQ" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp18VVEd2pfdXgw7I2qQ" name="business_terms_glossary" guid="_nIvp18VVEd2pfdXgw7I2qQ" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-SVG8fBamP9jI0gLGSNQYPg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-SVG8fBamP9jI0gLGSNQYPg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp58VVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_nIvp58VVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp58VVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_nIvp58VVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Ol-Ismqi_vwu93DuUULISw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Ol-Ismqi_vwu93DuUULISw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_nIvp08VVEd2pfdXgw7I2qQ" name="conceptual_data_model" guid="_nIvp08VVEd2pfdXgw7I2qQ" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-xywJ9rs6yDU3S-RR7R6DHw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-xywJ9rs6yDU3S-RR7R6DHw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_uJON1FmSEeCcpdiAcH0w-w" name="business_event_description" guid="_uJON1FmSEeCcpdiAcH0w-w" presentationName="Business Event Description" briefDescription="Logging the business events source of business process execution helps to drive rule discovery." isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <methodElementProperty xmi:id="_uJON1VmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-nWwIrDx_rgbWN_dCjIPeGg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-nWwIrDx_rgbWN_dCjIPeGg"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_HSrrgGhiEd-FVuzXjnvIWA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_uJXXwVmSEeCcpdiAcH0w-w" name="use_case" guid="_uJXXwVmSEeCcpdiAcH0w-w" presentationName="Use Case" briefDescription="This artifact captures the system behavior to yield an observable result of value to those who interact with the system." isPlanned="false" superActivities="_nIvp5cVVEd2pfdXgw7I2qQ">
+ <methodElementProperty xmi:id="_uJXXwlmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kNwINk1Edq2Q8qZoWbvGA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_JLOiIMNvEdu2IdAIaWZyAw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_3Y3XUI5fEdyO5aWob1UGDA"/>
+ <WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWjz7ekEd-D7YZN9NgldQ" name="analyze_business_rules" guid="_9tWjz7ekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_s37aM8VVEd2pfdXgw7I2qQ" name="analyze_business_rules" guid="_s37aM8VVEd2pfdXgw7I2qQ" presentationName="Analyze Business Rules" superActivities="_CryGMHqmEd2o_5d3MWaNxQ" breakdownElements="_s37aOcVVEd2pfdXgw7I2qQ _s37aNsVVEd2pfdXgw7I2qQ _s37aNMVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ _s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOsVVEd2pfdXgw7I2qQ _s37aO8VVEd2pfdXgw7I2qQ _s37aN8VVEd2pfdXgw7I2qQ _s37aNcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_s37aM8VVEd2pfdXgw7I2qQ" name="analyze_business_rules" guid="_s37aM8VVEd2pfdXgw7I2qQ" presentationName="Analyze Business Rules" superActivities="_CryGMHqmEd2o_5d3MWaNxQ" breakdownElements="_s37aOcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ _s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOsVVEd2pfdXgw7I2qQ _s37aO8VVEd2pfdXgw7I2qQ _s37aNcVVEd2pfdXgw7I2qQ">
<presentation xmi:id="-4RpjINOc4rCESRAYiXaR1w" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-4RpjINOc4rCESRAYiXaR1w"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_s37aOcVVEd2pfdXgw7I2qQ" name="extract_rule_meaning" guid="_s37aOcVVEd2pfdXgw7I2qQ" presentationName="Extract rule meaning" superActivities="_s37aM8VVEd2pfdXgw7I2qQ" linkToPredecessor="_v9YIMMVVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" mandatoryInput="_s37aOMVVEd2pfdXgw7I2qQ" output="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_s37aNsVVEd2pfdXgw7I2qQ _s37aNMVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_s37aOcVVEd2pfdXgw7I2qQ" name="extract_rule_meaning" guid="_s37aOcVVEd2pfdXgw7I2qQ" presentationName="Extract Rule Meaning" briefDescription="Extract the semantic of the rule to prepare for a data model and to remove any ambiguity and redundancy." superActivities="_s37aM8VVEd2pfdXgw7I2qQ" linkToPredecessor="_v9YIMMVVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" mandatoryInput="_s37aOMVVEd2pfdXgw7I2qQ" output="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Zgt8ljNbGXKcbU4gzUCQrg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Zgt8ljNbGXKcbU4gzUCQrg"/>
+ <concepts href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_gPfSoIpzEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8_mWgH3GEd2sJcA0evSBQw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_o19QgF2BEd2T6cNSe41mOg"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_v9YIMMVVEd2pfdXgw7I2qQ" guid="_v9YIMMVVEd2pfdXgw7I2qQ" pred="_nIvp1cVVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_s37aNsVVEd2pfdXgw7I2qQ" name="business_analyst" guid="_s37aNsVVEd2pfdXgw7I2qQ" presentationName="Business Analyst" isPlanned="false" superActivities="_s37aM8VVEd2pfdXgw7I2qQ" modifies="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_s37aNMVVEd2pfdXgw7I2qQ" name="rule_analyst" guid="_s37aNMVVEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_s37aM8VVEd2pfdXgw7I2qQ" modifies="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ" responsibleFor="_s3yQQcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_s37aOMVVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_s37aOMVVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_s37aM8VVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_s37aOMVVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_s37aOMVVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_s37aM8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-NjDm5kyrlZVxH1HwaGoVFA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-NjDm5kyrlZVxH1HwaGoVFA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_s3yQQcVVEd2pfdXgw7I2qQ" name="fact_model" guid="_s3yQQcVVEd2pfdXgw7I2qQ" presentationName="Fact Model" isPlanned="false" superActivities="_s37aM8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-LZfO28SzpOMkRDb62aUppg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-LZfO28SzpOMkRDb62aUppg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_s37aMcVVEd2pfdXgw7I2qQ" name="logical_data_model" guid="_s37aMcVVEd2pfdXgw7I2qQ" presentationName="Logical Data Model" isPlanned="false" superActivities="_s37aM8VVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_s37aMcVVEd2pfdXgw7I2qQ" name="logical_data_model" guid="_s37aMcVVEd2pfdXgw7I2qQ" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_s37aM8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-cAqcd_rDIyDggEFNkpOafA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-cAqcd_rDIyDggEFNkpOafA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_s37aOsVVEd2pfdXgw7I2qQ" name="transform_rules" guid="_s37aOsVVEd2pfdXgw7I2qQ" presentationName="Transform rules" superActivities="_s37aM8VVEd2pfdXgw7I2qQ" linkToPredecessor="_s37aMMVVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" mandatoryInput="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ" output="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_s37aNMVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_s37aOsVVEd2pfdXgw7I2qQ" name="transform_rules" guid="_s37aOsVVEd2pfdXgw7I2qQ" presentationName="Transform Rules" briefDescription="Transform the rule to avoid ambiguity and make them more atomic" superActivities="_s37aM8VVEd2pfdXgw7I2qQ" linkToPredecessor="_s37aMMVVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" mandatoryInput="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ" output="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-TMElbWb1oCm06CVVbtGziA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-TMElbWb1oCm06CVVbtGziA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_K6-3kDmnEdy8N6BRpa8ByQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x_5XgH9iEd26h9j0X6pKmw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8mZw8DmhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_7HEPsDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_tFwpYDmoEdy8N6BRpa8ByQ"/>
@@ -134,14 +307,15 @@
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_0-T6ADmoEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_s37aMMVVEd2pfdXgw7I2qQ" guid="_s37aMMVVEd2pfdXgw7I2qQ" pred="_s37aOcVVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_s37aO8VVEd2pfdXgw7I2qQ" name="build_test_scenario" guid="_s37aO8VVEd2pfdXgw7I2qQ" presentationName="Build test scenarios" superActivities="_s37aM8VVEd2pfdXgw7I2qQ" linkToPredecessor="_s37aMsVVEd2pfdXgw7I2qQ" additionallyPerformedBy="_s37aN8VVEd2pfdXgw7I2qQ _s37aNsVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_s37aNMVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_s37aO8VVEd2pfdXgw7I2qQ" name="build_test_scenario" guid="_s37aO8VVEd2pfdXgw7I2qQ" presentationName="Build Test Scenarios" briefDescription="Work with analysis team to define concrete scenario with real data so that we can later on test the process and the rules." superActivities="_s37aM8VVEd2pfdXgw7I2qQ" linkToPredecessor="_s37aMsVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-cldFzj8jYSiyDtkZGFpjQQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-cldFzj8jYSiyDtkZGFpjQQ"/>
+ <guidelines href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <supportingMaterials href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_vLvAUGjFEd2PJ-nlV-86WA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1dlWkH3GEd2sJcA0evSBQw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_s37aMsVVEd2pfdXgw7I2qQ" guid="_s37aMsVVEd2pfdXgw7I2qQ" pred="_s37aOsVVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_s37aN8VVEd2pfdXgw7I2qQ" name="subject_matter_expert" guid="_s37aN8VVEd2pfdXgw7I2qQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_s37aM8VVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_s37aNcVVEd2pfdXgw7I2qQ" name="synchronize_data_model" guid="_s37aNcVVEd2pfdXgw7I2qQ" presentationName="Synchronize data models" superActivities="_s37aM8VVEd2pfdXgw7I2qQ" linkToPredecessor="_s37aPMVVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" mandatoryInput="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ" output="_s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_s37aNMVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_s37aNcVVEd2pfdXgw7I2qQ" name="synchronize_data_model" guid="_s37aNcVVEd2pfdXgw7I2qQ" presentationName="Synchronize Data Models" briefDescription="Ensure the terms and entities used in the rule march element in the different date models used by the IT components" superActivities="_s37aM8VVEd2pfdXgw7I2qQ" linkToPredecessor="_s37aPMVVEd2pfdXgw7I2qQ" isSynchronizedWithSource="false" mandatoryInput="_s3yQQcVVEd2pfdXgw7I2qQ _s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ" output="_s37aMcVVEd2pfdXgw7I2qQ _s37aOMVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-JMP5iTEzmgde5KqHrptXyA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-JMP5iTEzmgde5KqHrptXyA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_prtzIDmiEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_s37aPMVVEd2pfdXgw7I2qQ" guid="_s37aPMVVEd2pfdXgw7I2qQ" pred="_s37aO8VVEd2pfdXgw7I2qQ"/>
@@ -150,31 +324,35 @@
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj1LekEd-D7YZN9NgldQ" name="prototyping" guid="_9tWj1LekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj1bekEd-D7YZN9NgldQ" name="discover_business_rules" guid="_9tWj1bekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_z0dHhcVVEd2pfdXgw7I2qQ" name="discover_business_rules" guid="_z0dHhcVVEd2pfdXgw7I2qQ" presentationName="Discover Business Rules" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_z0dHgcVVEd2pfdXgw7I2qQ _z0dHe8VVEd2pfdXgw7I2qQ _z0dHicVVEd2pfdXgw7I2qQ _z0dHcsVVEd2pfdXgw7I2qQ _z0dHecVVEd2pfdXgw7I2qQ _z0dHdsVVEd2pfdXgw7I2qQ _z0dHg8VVEd2pfdXgw7I2qQ _z0dHdcVVEd2pfdXgw7I2qQ _z0dHd8VVEd2pfdXgw7I2qQ _z0dHh8VVEd2pfdXgw7I2qQ _z0dHc8VVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_z0dHhcVVEd2pfdXgw7I2qQ" name="discover_business_rules" guid="_z0dHhcVVEd2pfdXgw7I2qQ" presentationName="Discover Business Rules" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_z0dHicVVEd2pfdXgw7I2qQ _z0dHecVVEd2pfdXgw7I2qQ _z0dHdsVVEd2pfdXgw7I2qQ _z0dHg8VVEd2pfdXgw7I2qQ _z0dHdcVVEd2pfdXgw7I2qQ _z0dHd8VVEd2pfdXgw7I2qQ _z0dHh8VVEd2pfdXgw7I2qQ _z0dHc8VVEd2pfdXgw7I2qQ">
<presentation xmi:id="-GhJfLtRP5ADWO_NtIImqUw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-GhJfLtRP5ADWO_NtIImqUw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_z0dHgcVVEd2pfdXgw7I2qQ" name="rule_analyst" guid="_z0dHgcVVEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ" modifies="_z0dHd8VVEd2pfdXgw7I2qQ _z0dHh8VVEd2pfdXgw7I2qQ _z0dHc8VVEd2pfdXgw7I2qQ" responsibleFor="_z0dHicVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_z0dHe8VVEd2pfdXgw7I2qQ" name="business_analyst" guid="_z0dHe8VVEd2pfdXgw7I2qQ" presentationName="Business Analyst" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ" responsibleFor="_z0dHicVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHicVVEd2pfdXgw7I2qQ" name="use_case_model" guid="_z0dHicVVEd2pfdXgw7I2qQ" presentationName="Use-Case Model" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHicVVEd2pfdXgw7I2qQ" name="use_case_model" guid="_z0dHicVVEd2pfdXgw7I2qQ" presentationName="Use-Case Model" briefDescription="This artifact captures a model of the intended functions and environment of the system and serves as a contract between the customer and the team." isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_z0dHcsVVEd2pfdXgw7I2qQ" name="subject_matter_expert" guid="_z0dHcsVVEd2pfdXgw7I2qQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHecVVEd2pfdXgw7I2qQ" name="decision_point_table" guid="_z0dHecVVEd2pfdXgw7I2qQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-f3XkJ0vY-f93Cugh2hUPag" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-f3XkJ0vY-f93Cugh2hUPag"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHdsVVEd2pfdXgw7I2qQ" name="business_process_map" guid="_z0dHdsVVEd2pfdXgw7I2qQ" presentationName="Business Process Map" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHdsVVEd2pfdXgw7I2qQ" name="business_process_map" guid="_z0dHdsVVEd2pfdXgw7I2qQ" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-XJgsI3tf1RyfJOE8nXKyfA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-XJgsI3tf1RyfJOE8nXKyfA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHg8VVEd2pfdXgw7I2qQ" name="discovery_workshop_itinerary" guid="_z0dHg8VVEd2pfdXgw7I2qQ" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-FYiTjOVLhDDFiks9REzbWw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-FYiTjOVLhDDFiks9REzbWw"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_z0dHdcVVEd2pfdXgw7I2qQ" name="execute_rule_discovery_roadmap" guid="_z0dHdcVVEd2pfdXgw7I2qQ" presentationName="Execute rule discovery roadmap" hasMultipleOccurrences="true" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ" isRepeatable="true" linkToPredecessor="_z0dHhsVVEd2pfdXgw7I2qQ" additionallyPerformedBy="_z0dHe8VVEd2pfdXgw7I2qQ _z0dHcsVVEd2pfdXgw7I2qQ" mandatoryInput="_z0dHdsVVEd2pfdXgw7I2qQ _z0dHecVVEd2pfdXgw7I2qQ" optionalInput="_z0dHg8VVEd2pfdXgw7I2qQ" output="_z0dHd8VVEd2pfdXgw7I2qQ _z0dHh8VVEd2pfdXgw7I2qQ _z0dHc8VVEd2pfdXgw7I2qQ" performedPrimarilyBy="_z0dHgcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_z0dHdcVVEd2pfdXgw7I2qQ" name="execute_rule_discovery_roadmap" guid="_z0dHdcVVEd2pfdXgw7I2qQ" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." hasMultipleOccurrences="true" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ" isRepeatable="true" linkToPredecessor="_z0dHhsVVEd2pfdXgw7I2qQ" mandatoryInput="_z0dHdsVVEd2pfdXgw7I2qQ _z0dHecVVEd2pfdXgw7I2qQ" optionalInput="_z0dHg8VVEd2pfdXgw7I2qQ" output="_z0dHd8VVEd2pfdXgw7I2qQ _z0dHh8VVEd2pfdXgw7I2qQ _z0dHc8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-I69B91Gv39Hsf4q9QC8gdw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-I69B91Gv39Hsf4q9QC8gdw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
@@ -182,39 +360,55 @@
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_z0dHhsVVEd2pfdXgw7I2qQ" guid="_z0dHhsVVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHd8VVEd2pfdXgw7I2qQ" name="business_terms_glossary" guid="_z0dHd8VVEd2pfdXgw7I2qQ" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHd8VVEd2pfdXgw7I2qQ" name="business_terms_glossary" guid="_z0dHd8VVEd2pfdXgw7I2qQ" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="--xaKhVngfn0TG7AUCYDE2Q" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#--xaKhVngfn0TG7AUCYDE2Q"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHh8VVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_z0dHh8VVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHh8VVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_z0dHh8VVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-ZxuH1YXgB-PGC8KKf8SqMA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-ZxuH1YXgB-PGC8KKf8SqMA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_z0dHc8VVEd2pfdXgw7I2qQ" name="conceptual_data_model" guid="_z0dHc8VVEd2pfdXgw7I2qQ" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_z0dHhcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-cQYuDYNpIetEa-A0wc2rMA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-cQYuDYNpIetEa-A0wc2rMA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj17ekEd-D7YZN9NgldQ" name="analyze_business_rules" guid="_9tWj17ekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_9s4lJcVVEd2pfdXgw7I2qQ" name="analyze_business_rules" guid="_9s4lJcVVEd2pfdXgw7I2qQ" presentationName="Analyze Business Rules" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_9s4lK8VVEd2pfdXgw7I2qQ _9s4lKMVVEd2pfdXgw7I2qQ _9s4lJsVVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ _9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lLMVVEd2pfdXgw7I2qQ _9s4lLcVVEd2pfdXgw7I2qQ _9s4lKcVVEd2pfdXgw7I2qQ _9s4lJ8VVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_9s4lJcVVEd2pfdXgw7I2qQ" name="analyze_business_rules" guid="_9s4lJcVVEd2pfdXgw7I2qQ" presentationName="Analyze Business Rules" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_9s4lK8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ _9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lLMVVEd2pfdXgw7I2qQ _9s4lLcVVEd2pfdXgw7I2qQ _9s4lJ8VVEd2pfdXgw7I2qQ">
<presentation xmi:id="-wWls41lEy2zA_NkxhOnoDg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-wWls41lEy2zA_NkxhOnoDg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lK8VVEd2pfdXgw7I2qQ" name="extract_rule_meaning" guid="_9s4lK8VVEd2pfdXgw7I2qQ" presentationName="Extract the meaning of the rule" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" mandatoryInput="_9s4lKsVVEd2pfdXgw7I2qQ" output="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lKMVVEd2pfdXgw7I2qQ _9s4lJsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lK8VVEd2pfdXgw7I2qQ" name="extract_rule_meaning" guid="_9s4lK8VVEd2pfdXgw7I2qQ" presentationName="Extract Rule Meaning" briefDescription="Extract the semantic of the rule to prepare for a data model and to remove any ambiguity and redundancy." superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" mandatoryInput="_9s4lKsVVEd2pfdXgw7I2qQ" output="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-NBqg7ns9nlUev0xlKSBKVg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-NBqg7ns9nlUev0xlKSBKVg"/>
+ <concepts href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_gPfSoIpzEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8_mWgH3GEd2sJcA0evSBQw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_o19QgF2BEd2T6cNSe41mOg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lKMVVEd2pfdXgw7I2qQ" name="business_analyst" guid="_9s4lKMVVEd2pfdXgw7I2qQ" presentationName="Business Analyst" isPlanned="false" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" modifies="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lJsVVEd2pfdXgw7I2qQ" name="rule_analyst" guid="_9s4lJsVVEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" modifies="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ" responsibleFor="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lKsVVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_9s4lKsVVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lKsVVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_9s4lKsVVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-1EFb1j163vesKIPD-WKc_A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-1EFb1j163vesKIPD-WKc_A"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lIcVVEd2pfdXgw7I2qQ" name="fact_model" guid="_9s4lIcVVEd2pfdXgw7I2qQ" presentationName="Fact Model" isPlanned="false" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-30jW7XM9GTETWwegnerK-g" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-30jW7XM9GTETWwegnerK-g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lI8VVEd2pfdXgw7I2qQ" name="logical_data_model" guid="_9s4lI8VVEd2pfdXgw7I2qQ" presentationName="Logical Data Model" isPlanned="false" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lI8VVEd2pfdXgw7I2qQ" name="logical_data_model" guid="_9s4lI8VVEd2pfdXgw7I2qQ" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-QosjoU1KKqxnanfXEHADUQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-QosjoU1KKqxnanfXEHADUQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lLMVVEd2pfdXgw7I2qQ" name="transform_rules" guid="_9s4lLMVVEd2pfdXgw7I2qQ" presentationName="Transform Rules" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lIsVVEd2pfdXgw7I2qQ" mandatoryInput="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ" output="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lJsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lLMVVEd2pfdXgw7I2qQ" name="transform_rules" guid="_9s4lLMVVEd2pfdXgw7I2qQ" presentationName="Transform Rules" briefDescription="Transform the rule to avoid ambiguity and make them more atomic" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lIsVVEd2pfdXgw7I2qQ" mandatoryInput="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ" output="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Jkw-vxUJt3NMdOu_yUsNgw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Jkw-vxUJt3NMdOu_yUsNgw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_K6-3kDmnEdy8N6BRpa8ByQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x_5XgH9iEd26h9j0X6pKmw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8mZw8DmhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_7HEPsDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_tFwpYDmoEdy8N6BRpa8ByQ"/>
@@ -224,32 +418,29 @@
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_0-T6ADmoEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9s4lIsVVEd2pfdXgw7I2qQ" guid="_9s4lIsVVEd2pfdXgw7I2qQ" pred="_9s4lK8VVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lLcVVEd2pfdXgw7I2qQ" name="build_test_scenario" guid="_9s4lLcVVEd2pfdXgw7I2qQ" presentationName="Build test scenarios" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lJMVVEd2pfdXgw7I2qQ" additionallyPerformedBy="_9s4lKcVVEd2pfdXgw7I2qQ _9s4lKMVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lJsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lLcVVEd2pfdXgw7I2qQ" name="build_test_scenario" guid="_9s4lLcVVEd2pfdXgw7I2qQ" presentationName="Build Test Scenarios" briefDescription="Work with analysis team to define concrete scenario with real data so that we can later on test the process and the rules." superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lJMVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-jD0SjTGEVGjAXwk-96CnBw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-jD0SjTGEVGjAXwk-96CnBw"/>
+ <guidelines href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <supportingMaterials href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_vLvAUGjFEd2PJ-nlV-86WA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1dlWkH3GEd2sJcA0evSBQw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9s4lJMVVEd2pfdXgw7I2qQ" guid="_9s4lJMVVEd2pfdXgw7I2qQ" pred="_9s4lLMVVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lKcVVEd2pfdXgw7I2qQ" name="subject_matter_expert" guid="_9s4lKcVVEd2pfdXgw7I2qQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lJ8VVEd2pfdXgw7I2qQ" name="synchronize_data_model" guid="_9s4lJ8VVEd2pfdXgw7I2qQ" presentationName="Synchronize Data Models" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lLsVVEd2pfdXgw7I2qQ" mandatoryInput="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ" output="_9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lJsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lJ8VVEd2pfdXgw7I2qQ" name="synchronize_data_model" guid="_9s4lJ8VVEd2pfdXgw7I2qQ" presentationName="Synchronize Data Models" briefDescription="Ensure the terms and entities used in the rule march element in the different date models used by the IT components" superActivities="_9s4lJcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lLsVVEd2pfdXgw7I2qQ" mandatoryInput="_9s4lIcVVEd2pfdXgw7I2qQ _9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ" output="_9s4lI8VVEd2pfdXgw7I2qQ _9s4lKsVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-pxSSUK3yjMwpuFplEiArVA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-pxSSUK3yjMwpuFplEiArVA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_prtzIDmiEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9s4lLsVVEd2pfdXgw7I2qQ" guid="_9s4lLsVVEd2pfdXgw7I2qQ" pred="_9s4lLcVVEd2pfdXgw7I2qQ"/>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj27ekEd-D7YZN9NgldQ" name="design_bre_integration" guid="_9tWj27ekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_9s4lPcVVEd2pfdXgw7I2qQ" name="design_bre_integration" guid="_9s4lPcVVEd2pfdXgw7I2qQ" presentationName="Design BRMS Integration" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_9s4lQMVVEd2pfdXgw7I2qQ _9s4lSMVVEd2pfdXgw7I2qQ _9s4lQsVVEd2pfdXgw7I2qQ _9s4lO8VVEd2pfdXgw7I2qQ _9s4lSsVVEd2pfdXgw7I2qQ _9s4lPsVVEd2pfdXgw7I2qQ _9s4lQcVVEd2pfdXgw7I2qQ _9s4lScVVEd2pfdXgw7I2qQ _9s4lPMVVEd2pfdXgw7I2qQ _9s4lRsVVEd2pfdXgw7I2qQ _9s4lP8VVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_9s4lPcVVEd2pfdXgw7I2qQ" name="design_bre_integration" guid="_9s4lPcVVEd2pfdXgw7I2qQ" presentationName="Design BRMS Integration" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_9s4lQMVVEd2pfdXgw7I2qQ _9s4lO8VVEd2pfdXgw7I2qQ _9s4lSsVVEd2pfdXgw7I2qQ _9s4lPsVVEd2pfdXgw7I2qQ _9s4lQcVVEd2pfdXgw7I2qQ _9s4lPMVVEd2pfdXgw7I2qQ _9s4lRsVVEd2pfdXgw7I2qQ _9s4lP8VVEd2pfdXgw7I2qQ">
<presentation xmi:id="-Vy5EjgkTkzCMhrts0Aczlg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Vy5EjgkTkzCMhrts0Aczlg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lQMVVEd2pfdXgw7I2qQ" name="determine_rule_implementation" guid="_9s4lQMVVEd2pfdXgw7I2qQ" presentationName="Determine Rule Implementation" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lSMVVEd2pfdXgw7I2qQ _9s4lQsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lQMVVEd2pfdXgw7I2qQ" name="determine_rule_implementation" guid="_9s4lQMVVEd2pfdXgw7I2qQ" presentationName="Determine Rule Implementation" briefDescription="This task tries to answer the question of where to implement the business rules that have been discovered." superActivities="_9s4lPcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-1hKEhTu7zfbuOyxxSBfTVA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-1hKEhTu7zfbuOyxxSBfTVA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_qzveUBk5Edyoe_hnDlTB5A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lSMVVEd2pfdXgw7I2qQ" name="rule_analyst" guid="_9s4lSMVVEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ" responsibleFor="_9s4lRsVVEd2pfdXgw7I2qQ _9s4lPMVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lQsVVEd2pfdXgw7I2qQ" name="rule_architect" guid="_9s4lQsVVEd2pfdXgw7I2qQ" presentationName="Rule Architect" isPlanned="false" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lO8VVEd2pfdXgw7I2qQ" name="define_ruleset" guid="_9s4lO8VVEd2pfdXgw7I2qQ" presentationName="Define Rule Set" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lRcVVEd2pfdXgw7I2qQ" mandatoryInput="_9s4lPMVVEd2pfdXgw7I2qQ _9s4lRsVVEd2pfdXgw7I2qQ" output="_9s4lP8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-ujEcUPK8pFeN7wqLRcSB9A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-ujEcUPK8pFeN7wqLRcSB9A"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_7L2MIDyOEdyA6a_I80swHw"/>
<selectedSteps href="uma://-gt8CaPXz6HldH1v7OnThvg#_uGtsEErrEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-gt8CaPXz6HldH1v7OnThvg#_pIE9sEafEdySHMdInS9eGA"/>
@@ -259,10 +450,12 @@
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9s4lRcVVEd2pfdXgw7I2qQ" guid="_9s4lRcVVEd2pfdXgw7I2qQ" pred="_9s4lQMVVEd2pfdXgw7I2qQ"/>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lSsVVEd2pfdXgw7I2qQ" name="build_object_models" guid="_9s4lSsVVEd2pfdXgw7I2qQ" presentationName="Build Object Models" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lR8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-GSA2k4CiOuK856zbdHf6bw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-GSA2k4CiOuK856zbdHf6bw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZffcIDmiEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9s4lR8VVEd2pfdXgw7I2qQ" guid="_9s4lR8VVEd2pfdXgw7I2qQ" pred="_9s4lO8VVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lPsVVEd2pfdXgw7I2qQ" name="build_rule_project_structure" guid="_9s4lPsVVEd2pfdXgw7I2qQ" presentationName="Build Rule Project Structure" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lOsVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lSMVVEd2pfdXgw7I2qQ _9s4lQsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lPsVVEd2pfdXgw7I2qQ" name="build_rule_project_structure" guid="_9s4lPsVVEd2pfdXgw7I2qQ" presentationName="Build Rule Project Structure" briefDescription="Designing and building how the rule will be managed is an important activity of a BRMS project. This task describes how to build the set of rule and non rules projects that support the business application." superActivities="_9s4lPcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lOsVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-A69eNZMgOD-TmrIh98RJsg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-A69eNZMgOD-TmrIh98RJsg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_O92DQDV5EdyTBtGu8YeFfg"/>
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_OBfOkDuhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_RVoYoDyNEdyA6a_I80swHw"/>
@@ -271,7 +464,9 @@
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_94ET8DugEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9s4lOsVVEd2pfdXgw7I2qQ" guid="_9s4lOsVVEd2pfdXgw7I2qQ" pred="_9s4lO8VVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lQcVVEd2pfdXgw7I2qQ" name="prototype_rules" guid="_9s4lQcVVEd2pfdXgw7I2qQ" presentationName="Prototype Rules" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lRMVVEd2pfdXgw7I2qQ _9s4lQ8VVEd2pfdXgw7I2qQ" additionallyPerformedBy="_9s4lScVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lSMVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lQcVVEd2pfdXgw7I2qQ" name="prototype_rules" guid="_9s4lQcVVEd2pfdXgw7I2qQ" presentationName="Prototype Rules" briefDescription="Prototyping rules is an important step of the rule analysis, as it is when we are really coding that issues arrived. Paper work is fine, but working rules is far better." superActivities="_9s4lPcVVEd2pfdXgw7I2qQ" linkToPredecessor="_9s4lRMVVEd2pfdXgw7I2qQ _9s4lQ8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-7KXY0dEtZ02k-zR2uSgrLw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-7KXY0dEtZ02k-zR2uSgrLw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x-GVQIsqEd2gksNyFVJN4g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_dds-IDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_tA5YEDyIEdyA6a_I80swHw"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_usf-QDyIEdyA6a_I80swHw"/>
@@ -281,30 +476,40 @@
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9s4lRMVVEd2pfdXgw7I2qQ" guid="_9s4lRMVVEd2pfdXgw7I2qQ" pred="_9s4lSsVVEd2pfdXgw7I2qQ"/>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9s4lQ8VVEd2pfdXgw7I2qQ" guid="_9s4lQ8VVEd2pfdXgw7I2qQ" pred="_9s4lPsVVEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lScVVEd2pfdXgw7I2qQ" name="rule_writer" guid="_9s4lScVVEd2pfdXgw7I2qQ" presentationName="Rule Writer" isPlanned="false" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lPMVVEd2pfdXgw7I2qQ" name="decision_point_table" guid="_9s4lPMVVEd2pfdXgw7I2qQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-DLOZ9q9zKzqSH02qulirKQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-DLOZ9q9zKzqSH02qulirKQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lRsVVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_9s4lRsVVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lRsVVEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_9s4lRsVVEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-WpMajOrHlIGWS4oIiTfIgQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-WpMajOrHlIGWS4oIiTfIgQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lP8VVEd2pfdXgw7I2qQ" name="ruleset" guid="_9s4lP8VVEd2pfdXgw7I2qQ" presentationName="Rule Set" isPlanned="false" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lP8VVEd2pfdXgw7I2qQ" name="ruleset" guid="_9s4lP8VVEd2pfdXgw7I2qQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_9s4lPcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-mw3UMRnpZKKJ1HXl4Tx2GA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-mw3UMRnpZKKJ1HXl4Tx2GA"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj4bekEd-D7YZN9NgldQ" name="author_business_rules" guid="_9tWj4bekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_9s4lMcVVEd2pfdXgw7I2qQ" name="author_business_rules" guid="_9s4lMcVVEd2pfdXgw7I2qQ" presentationName="Author Business Rules" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_HSAXQGh8Ed-FVuzXjnvIWA _9s4lNcVVEd2pfdXgw7I2qQ _9s4lN8VVEd2pfdXgw7I2qQ _9s4lNsVVEd2pfdXgw7I2qQ _9s4lNMVVEd2pfdXgw7I2qQ _9s4lOMVVEd2pfdXgw7I2qQ _9s4lMMVVEd2pfdXgw7I2qQ _9s4lM8VVEd2pfdXgw7I2qQ _9s4lMsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_9s4lMcVVEd2pfdXgw7I2qQ" name="author_business_rules" guid="_9s4lMcVVEd2pfdXgw7I2qQ" presentationName="Author Business Rules" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_HSAXQGh8Ed-FVuzXjnvIWA _9s4lNcVVEd2pfdXgw7I2qQ _9s4lN8VVEd2pfdXgw7I2qQ _9s4lNMVVEd2pfdXgw7I2qQ _9s4lMMVVEd2pfdXgw7I2qQ _9s4lM8VVEd2pfdXgw7I2qQ _9s4lMsVVEd2pfdXgw7I2qQ">
<presentation xmi:id="-hpPbI7yoU4KI3IBgzkYMOw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-hpPbI7yoU4KI3IBgzkYMOw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_HSAXQGh8Ed-FVuzXjnvIWA" name="define_ruleset_testing" guid="_HSAXQGh8Ed-FVuzXjnvIWA" presentationName="Define Rule Testing Approach" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_HSAXQGh8Ed-FVuzXjnvIWA" name="define_ruleset_testing" guid="_HSAXQGh8Ed-FVuzXjnvIWA" presentationName="Define Rule Testing Approach" briefDescription="Rule testing has been a crucial and intensive task within rule development, due to the nature of a lot of business rules working together." superActivities="_9s4lMcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-TzodlLaSF7x8Ox7OmJmUyg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-TzodlLaSF7x8Ox7OmJmUyg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mDL5YGhkEd-FVuzXjnvIWA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lNcVVEd2pfdXgw7I2qQ" name="develop_unit_tests" guid="_9s4lNcVVEd2pfdXgw7I2qQ" presentationName="Develop Unit Tests for rule" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lOMVVEd2pfdXgw7I2qQ _9s4lNsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lNcVVEd2pfdXgw7I2qQ" name="develop_unit_tests" guid="_9s4lNcVVEd2pfdXgw7I2qQ" presentationName="Develop Rule Unit Tests" briefDescription="The goal of this task is to track down anomalies in the rules such as conflicts, redundancies or overlaps.
" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-3TEm3EjK2B_3xvMAHjQHWw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-3TEm3EjK2B_3xvMAHjQHWw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ioCPkDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lN8VVEd2pfdXgw7I2qQ" name="develop_rules" guid="_9s4lN8VVEd2pfdXgw7I2qQ" presentationName="Develop Rules" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ" output="_9s4lNMVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lNsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lN8VVEd2pfdXgw7I2qQ" name="develop_rules" guid="_9s4lN8VVEd2pfdXgw7I2qQ" presentationName="Develop Rules" briefDescription="This task is about developing each rule in the rule project." superActivities="_9s4lMcVVEd2pfdXgw7I2qQ" output="_9s4lNMVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-wUfIZbnlisjRJ7z3OjFsUQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-wUfIZbnlisjRJ7z3OjFsUQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Y2CxEDzEEdyA6a_I80swHw"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_bsPp8ErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_qfzk4ErtEdyEE-k1R6LmOA"/>
@@ -312,84 +517,118 @@
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_zAvrMErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_GvK9oEruEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lNsVVEd2pfdXgw7I2qQ" name="rule_writer" guid="_9s4lNsVVEd2pfdXgw7I2qQ" presentationName="Rule Writer" isPlanned="false" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ" modifies="_9s4lNMVVEd2pfdXgw7I2qQ" responsibleFor="_9s4lNMVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lNMVVEd2pfdXgw7I2qQ" name="ruleset" guid="_9s4lNMVVEd2pfdXgw7I2qQ" presentationName="Rule Set" isPlanned="false" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lNMVVEd2pfdXgw7I2qQ" name="ruleset" guid="_9s4lNMVVEd2pfdXgw7I2qQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-bLL0Fi0p_lu2XVXfO4Bmng" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-bLL0Fi0p_lu2XVXfO4Bmng"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lOMVVEd2pfdXgw7I2qQ" name="developer" guid="_9s4lOMVVEd2pfdXgw7I2qQ" presentationName="Developer" isPlanned="false" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lMMVVEd2pfdXgw7I2qQ" name="enhance_object_models" guid="_9s4lMMVVEd2pfdXgw7I2qQ" presentationName="Enhance Object Models" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lOMVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lMMVVEd2pfdXgw7I2qQ" name="enhance_object_models" guid="_9s4lMMVVEd2pfdXgw7I2qQ" presentationName="Enhance Object Models" briefDescription="The data model is started during the analysis and design tasks. But it will involve over time. So this activity supports the enhancement of the object models." superActivities="_9s4lMcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-pk5as0BVClbnn3B7FhmN3A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-pk5as0BVClbnn3B7FhmN3A"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_UXrv8Eb3EdySHMdInS9eGA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lM8VVEd2pfdXgw7I2qQ" name="execute_rule_set" guid="_9s4lM8VVEd2pfdXgw7I2qQ" presentationName="Execute Rule Set" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ" output="_9s4lNMVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lNsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lM8VVEd2pfdXgw7I2qQ" name="execute_rule_set" guid="_9s4lM8VVEd2pfdXgw7I2qQ" presentationName="Execute Rule Set" briefDescription="Execute the tests to trigger the rule execution. Analyze the output logs. Report issues." superActivities="_9s4lMcVVEd2pfdXgw7I2qQ" output="_9s4lNMVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-9bcuy4Hs_gwTKjG8NyKAPw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-9bcuy4Hs_gwTKjG8NyKAPw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_JCHfMEXhEdy14e5PT9v3HQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lMsVVEd2pfdXgw7I2qQ" name="log_issue" guid="_9s4lMsVVEd2pfdXgw7I2qQ" presentationName="Log issue" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lNsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lMsVVEd2pfdXgw7I2qQ" name="log_issue" guid="_9s4lMsVVEd2pfdXgw7I2qQ" presentationName="Log Issue" superActivities="_9s4lMcVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-oYF8elqKsD5hfhKlCij3xQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-oYF8elqKsD5hfhKlCij3xQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yGbYIEb0EdySHMdInS9eGA"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj4rekEd-D7YZN9NgldQ" name="develop__bre_architecture" guid="_9tWj4rekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_9s4lTMVVEd2pfdXgw7I2qQ" name="develop__bre_architecture" guid="_9s4lTMVVEd2pfdXgw7I2qQ" presentationName="Develop BRMS Integration Architecture" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_9s4lTsVVEd2pfdXgw7I2qQ _9s4lUsVVEd2pfdXgw7I2qQ _9s4lT8VVEd2pfdXgw7I2qQ _9s4lTcVVEd2pfdXgw7I2qQ _9s4lUMVVEd2pfdXgw7I2qQ _9s4lUcVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_9s4lTMVVEd2pfdXgw7I2qQ" name="develop__bre_architecture" guid="_9s4lTMVVEd2pfdXgw7I2qQ" presentationName="Develop BRMS Integration Architecture" superActivities="_zPFMAXrDEd2o_5d3MWaNxQ" breakdownElements="_9s4lTsVVEd2pfdXgw7I2qQ _9s4lT8VVEd2pfdXgw7I2qQ _9s4lTcVVEd2pfdXgw7I2qQ _9s4lUMVVEd2pfdXgw7I2qQ _9s4lUcVVEd2pfdXgw7I2qQ _vxYecVmSEeCcpdiAcH0w-w _vxYedFmSEeCcpdiAcH0w-w _vxYed1mSEeCcpdiAcH0w-w _vxYeelmSEeCcpdiAcH0w-w">
<presentation xmi:id="-qptRZHxVnbhlR7Ycjbxb9A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-qptRZHxVnbhlR7Ycjbxb9A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lTsVVEd2pfdXgw7I2qQ" name="develop_architecture" guid="_9s4lTsVVEd2pfdXgw7I2qQ" presentationName="Develop Business Rule Application Architecture" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ" output="_9s4lT8VVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lUsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lTsVVEd2pfdXgw7I2qQ" name="develop_architecture" guid="_9s4lTsVVEd2pfdXgw7I2qQ" presentationName="Develop Business Rule Application Architecture" briefDescription="The purpose of the architecture activities is to support the following major items:
•	Integrate the Rule Engine into the business application
•	Deploy Business Rules Management System into the business and IT organizations." superActivities="_9s4lTMVVEd2pfdXgw7I2qQ" mandatoryInput="_vxYecVmSEeCcpdiAcH0w-w _vxYedFmSEeCcpdiAcH0w-w" output="_9s4lT8VVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-OJ8H_2tSlsUq645zMbm48Q" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-OJ8H_2tSlsUq645zMbm48Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_O1kAANvfEduv2KOT-Teh6w"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gjdYMlgEdmt3adZL5Dmdw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_nOQHsAp6EdyPCr4G1Tb79A"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_RMRccChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_yIEJ4Ap6EdyPCr4G1Tb79A"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_r5SRoChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_venZkChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_yFzeQChaEd2bfOOTyXGWkw"/>
+ <selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_HDD68Im5Ed2cL6yqw-_-uA"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_04xVIChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_27c-kChaEd2bfOOTyXGWkw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_9s4lUsVVEd2pfdXgw7I2qQ" name="rule_architect" guid="_9s4lUsVVEd2pfdXgw7I2qQ" presentationName="Rule Architect" isPlanned="false" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ" modifies="_9s4lT8VVEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lT8VVEd2pfdXgw7I2qQ" name="decision_service_architecture" guid="_9s4lT8VVEd2pfdXgw7I2qQ" presentationName="Decision Service Architecture" isPlanned="false" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_9s4lT8VVEd2pfdXgw7I2qQ" name="decision_service_architecture" guid="_9s4lT8VVEd2pfdXgw7I2qQ" presentationName="Decision Service Architecture" briefDescription="A decision service is a piece of logic which uses a decision engine like a rule engine in order to infer actions on the input data." isPlanned="false" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-AG5WgBy68mLoQW6HqHTusQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-AG5WgBy68mLoQW6HqHTusQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YRiuIItDEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_6BE7QAp_EdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lTcVVEd2pfdXgw7I2qQ" name="design_reference_data_integration" guid="_9s4lTcVVEd2pfdXgw7I2qQ" presentationName="Design Integration to Reference Data" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lTcVVEd2pfdXgw7I2qQ" name="design_reference_data_integration" guid="_9s4lTcVVEd2pfdXgw7I2qQ" presentationName="Design Integration to Reference Data" briefDescription="Reference data are everywhere in business application, from basic enumeration value like the US sates to business codes with business meaning (like medical code). Those references data should be managed in a central Data Base or repository. The Rule engine needs to access them at execution but also during the authoring phase." superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-VLRdP6iYek0zEo_rHnIppw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-VLRdP6iYek0zEo_rHnIppw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_HMQasGDFEdyKlZvvtnMrMg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lUMVVEd2pfdXgw7I2qQ" name="design_models_for_bre" guid="_9s4lUMVVEd2pfdXgw7I2qQ" presentationName="Design Business Object Models for Rule Engine Processing" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lUsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lUMVVEd2pfdXgw7I2qQ" name="design_models_for_bre" guid="_9s4lUMVVEd2pfdXgw7I2qQ" presentationName="Design Business Object Models for Rule Engine Processing" briefDescription="Design the object model to be processed by the rule engine. " superActivities="_9s4lTMVVEd2pfdXgw7I2qQ" mandatoryInput="_vxYeelmSEeCcpdiAcH0w-w _vxYecVmSEeCcpdiAcH0w-w" output="_vxYed1mSEeCcpdiAcH0w-w">
+ <presentation xmi:id="-BBnqXNX3L83SEuYSuaMdxw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-BBnqXNX3L83SEuYSuaMdxw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_lYC2IGDAEdyKlZvvtnMrMg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lUcVVEd2pfdXgw7I2qQ" name="integrate_bre" guid="_9s4lUcVVEd2pfdXgw7I2qQ" presentationName="Integrate BRE with service layer" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ" performedPrimarilyBy="_9s4lUsVVEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_9s4lUcVVEd2pfdXgw7I2qQ" name="integrate_bre" guid="_9s4lUcVVEd2pfdXgw7I2qQ" presentationName="Integrate BRE within Service Layer" briefDescription="The integration of the rule engine can be done in different approaches depending of the type of application, and architecture." superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-ZBEhisTrkRvWYQ7SWQP4eg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-ZBEhisTrkRvWYQ7SWQP4eg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_IuFgEIm-Ed2dvb7--2nAHw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YRiuIItDEd2gksNyFVJN4g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_6-p2EH_BEd2YWI_0AZcMOA"/>
</processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_vxYecVmSEeCcpdiAcH0w-w" name="logical_data_model" guid="_vxYecVmSEeCcpdiAcH0w-w" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <methodElementProperty xmi:id="_vxYeclmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-rH1vUc8rldU1_AKYYx9dBA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-rH1vUc8rldU1_AKYYx9dBA"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_vxYedFmSEeCcpdiAcH0w-w" name="decision_point_table" guid="_vxYedFmSEeCcpdiAcH0w-w" presentationName="Decision Point Table" isPlanned="false" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <methodElementProperty xmi:id="_vxYedVmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-bvUOgHIu3fluB7VANjXFJg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-bvUOgHIu3fluB7VANjXFJg"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_vxYed1mSEeCcpdiAcH0w-w" name="executable_object_model" guid="_vxYed1mSEeCcpdiAcH0w-w" presentationName="Executable Object Model" briefDescription="A Java, .Net or XML schema implementation of the logical data model" isPlanned="false" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <methodElementProperty xmi:id="_vxYeeFmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_U003IIm4Ed2cL6yqw-_-uA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_vxYeelmSEeCcpdiAcH0w-w" name="fact_model" guid="_vxYeelmSEeCcpdiAcH0w-w" presentationName="Fact Model" isPlanned="false" superActivities="_9s4lTMVVEd2pfdXgw7I2qQ">
+ <methodElementProperty xmi:id="_vxYee1mSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-ewbo32yGFGXgBOLZ6El0qQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-ewbo32yGFGXgBOLZ6El0qQ"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
+ </processElements>
</childPackages>
<processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_zPFMAXrDEd2o_5d3MWaNxQ" name="prototyping" guid="_zPFMAXrDEd2o_5d3MWaNxQ" presentationName="Cycle 2- Prototyping" superActivities="_2EcLMXqlEd2o_5d3MWaNxQ" breakdownElements="_z0dHhcVVEd2pfdXgw7I2qQ _9s4lJcVVEd2pfdXgw7I2qQ _9s4lPcVVEd2pfdXgw7I2qQ _9s4lMcVVEd2pfdXgw7I2qQ _9s4lTMVVEd2pfdXgw7I2qQ"/>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj47ekEd-D7YZN9NgldQ" name="Cycle3- Building" guid="_9tWj47ekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj5LekEd-D7YZN9NgldQ" name="discover_business_rules" guid="_9tWj5LekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_RkSNoMVWEd2pfdXgw7I2qQ" name="discover_business_rules" guid="_RkSNoMVWEd2pfdXgw7I2qQ" presentationName="Discover Business Rules" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_RkSNnMVWEd2pfdXgw7I2qQ _RkSNlsVWEd2pfdXgw7I2qQ _RkSNpMVWEd2pfdXgw7I2qQ _RkSNjcVWEd2pfdXgw7I2qQ _RkSNlMVWEd2pfdXgw7I2qQ _RkSNkcVWEd2pfdXgw7I2qQ _RkSNnsVWEd2pfdXgw7I2qQ _RkSNkMVWEd2pfdXgw7I2qQ _RkSNksVWEd2pfdXgw7I2qQ _RkSNosVWEd2pfdXgw7I2qQ _RkSNjsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_RkSNoMVWEd2pfdXgw7I2qQ" name="discover_business_rules" guid="_RkSNoMVWEd2pfdXgw7I2qQ" presentationName="Discover Business Rules" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_RkSNpMVWEd2pfdXgw7I2qQ _RkSNlMVWEd2pfdXgw7I2qQ _RkSNkcVWEd2pfdXgw7I2qQ _RkSNnsVWEd2pfdXgw7I2qQ _RkSNkMVWEd2pfdXgw7I2qQ _RkSNksVWEd2pfdXgw7I2qQ _RkSNosVWEd2pfdXgw7I2qQ _RkSNjsVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-zxa-baDc1KSYzHLYLZLONQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-zxa-baDc1KSYzHLYLZLONQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_RkSNnMVWEd2pfdXgw7I2qQ" name="rule_analyst" guid="_RkSNnMVWEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ" modifies="_RkSNksVWEd2pfdXgw7I2qQ _RkSNosVWEd2pfdXgw7I2qQ _RkSNjsVWEd2pfdXgw7I2qQ" responsibleFor="_RkSNpMVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_RkSNlsVWEd2pfdXgw7I2qQ" name="business_analyst" guid="_RkSNlsVWEd2pfdXgw7I2qQ" presentationName="Business Analyst" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ" responsibleFor="_RkSNpMVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNpMVWEd2pfdXgw7I2qQ" name="use_case_model" guid="_RkSNpMVWEd2pfdXgw7I2qQ" presentationName="Use-Case Model" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNpMVWEd2pfdXgw7I2qQ" name="use_case_model" guid="_RkSNpMVWEd2pfdXgw7I2qQ" presentationName="Use-Case Model" briefDescription="This artifact captures a model of the intended functions and environment of the system and serves as a contract between the customer and the team." isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_RkSNjcVWEd2pfdXgw7I2qQ" name="subject_matter_expert" guid="_RkSNjcVWEd2pfdXgw7I2qQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNlMVWEd2pfdXgw7I2qQ" name="decision_point_table" guid="_RkSNlMVWEd2pfdXgw7I2qQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-c8q_v1s1n7aK-0miFaupPw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-c8q_v1s1n7aK-0miFaupPw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNkcVWEd2pfdXgw7I2qQ" name="business_process_map" guid="_RkSNkcVWEd2pfdXgw7I2qQ" presentationName="Business Process Map" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNkcVWEd2pfdXgw7I2qQ" name="business_process_map" guid="_RkSNkcVWEd2pfdXgw7I2qQ" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-yaB5VmxyoNnFc5KAKx87uw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-yaB5VmxyoNnFc5KAKx87uw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNnsVWEd2pfdXgw7I2qQ" name="discovery_workshop_itinerary" guid="_RkSNnsVWEd2pfdXgw7I2qQ" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-jiPE4qjhy0-GvsHSu8k4hw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-jiPE4qjhy0-GvsHSu8k4hw"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNkMVWEd2pfdXgw7I2qQ" name="execute_rule_discovery_roadmap" guid="_RkSNkMVWEd2pfdXgw7I2qQ" presentationName="Execute rule discovery roadmap" hasMultipleOccurrences="true" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ" isRepeatable="true" linkToPredecessor="_RkSNocVWEd2pfdXgw7I2qQ" additionallyPerformedBy="_RkSNlsVWEd2pfdXgw7I2qQ _RkSNjcVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNkcVWEd2pfdXgw7I2qQ _RkSNlMVWEd2pfdXgw7I2qQ" optionalInput="_RkSNnsVWEd2pfdXgw7I2qQ" output="_RkSNksVWEd2pfdXgw7I2qQ _RkSNosVWEd2pfdXgw7I2qQ _RkSNjsVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNnMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNkMVWEd2pfdXgw7I2qQ" name="execute_rule_discovery_roadmap" guid="_RkSNkMVWEd2pfdXgw7I2qQ" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." hasMultipleOccurrences="true" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ" isRepeatable="true" linkToPredecessor="_RkSNocVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNkcVWEd2pfdXgw7I2qQ _RkSNlMVWEd2pfdXgw7I2qQ" optionalInput="_RkSNnsVWEd2pfdXgw7I2qQ" output="_RkSNksVWEd2pfdXgw7I2qQ _RkSNosVWEd2pfdXgw7I2qQ _RkSNjsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-N9JRT0YykF7mF_nPmGpEig" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-N9JRT0YykF7mF_nPmGpEig"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
@@ -397,36 +636,48 @@
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_RkSNocVWEd2pfdXgw7I2qQ" guid="_RkSNocVWEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNksVWEd2pfdXgw7I2qQ" name="business_terms_glossary" guid="_RkSNksVWEd2pfdXgw7I2qQ" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNksVWEd2pfdXgw7I2qQ" name="business_terms_glossary" guid="_RkSNksVWEd2pfdXgw7I2qQ" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-wKyQQHGWKPhxgDMava9lMA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-wKyQQHGWKPhxgDMava9lMA"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNosVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_RkSNosVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNosVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_RkSNosVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-bN3NfZ3WOIrkhDKHWDPKkA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-bN3NfZ3WOIrkhDKHWDPKkA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNjsVWEd2pfdXgw7I2qQ" name="conceptual_data_model" guid="_RkSNjsVWEd2pfdXgw7I2qQ" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_RkSNoMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-l1seeyWf2ab1M7_-vwsRiQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-l1seeyWf2ab1M7_-vwsRiQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj5rekEd-D7YZN9NgldQ" name="analyze_business_rules" guid="_9tWj5rekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_RkSNZcVWEd2pfdXgw7I2qQ" name="analyze_business_rules" guid="_RkSNZcVWEd2pfdXgw7I2qQ" presentationName="Analyze Business Rules" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_RkSNaMVWEd2pfdXgw7I2qQ _RkSNZsVWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ _RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNbMVWEd2pfdXgw7I2qQ _RkSNbcVWEd2pfdXgw7I2qQ _RkSNacVWEd2pfdXgw7I2qQ _RkSNZ8VWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_RkSNZcVWEd2pfdXgw7I2qQ" name="analyze_business_rules" guid="_RkSNZcVWEd2pfdXgw7I2qQ" presentationName="Analyze Business Rules" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_RkSNasVWEd2pfdXgw7I2qQ _RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNbMVWEd2pfdXgw7I2qQ _RkSNbcVWEd2pfdXgw7I2qQ _RkSNZ8VWEd2pfdXgw7I2qQ">
<presentation xmi:id="-I6NaNeD6vtJcfSCfyJ2e1Q" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-I6NaNeD6vtJcfSCfyJ2e1Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_RkSNaMVWEd2pfdXgw7I2qQ" name="business_analyst" guid="_RkSNaMVWEd2pfdXgw7I2qQ" presentationName="Business Analyst" isPlanned="false" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_RkSNZsVWEd2pfdXgw7I2qQ" name="rule_analyst" guid="_RkSNZsVWEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ" modifies="_RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ" responsibleFor="_RkSNYcVWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNasVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_RkSNasVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNasVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_RkSNasVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-teqRVFQdfi3M0E_2hPt2OA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-teqRVFQdfi3M0E_2hPt2OA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNYcVWEd2pfdXgw7I2qQ" name="fact_model" guid="_RkSNYcVWEd2pfdXgw7I2qQ" presentationName="Fact Model" isPlanned="false" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-7obhtj52BKnAGY2bh-MvLw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-7obhtj52BKnAGY2bh-MvLw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNY8VWEd2pfdXgw7I2qQ" name="logical_data_model" guid="_RkSNY8VWEd2pfdXgw7I2qQ" presentationName="Logical Data Model" isPlanned="false" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNY8VWEd2pfdXgw7I2qQ" name="logical_data_model" guid="_RkSNY8VWEd2pfdXgw7I2qQ" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-KnXTyJRJlBDBK68DXO57Uw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-KnXTyJRJlBDBK68DXO57Uw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNbMVWEd2pfdXgw7I2qQ" name="transform_rules" guid="_RkSNbMVWEd2pfdXgw7I2qQ" presentationName="Transform Rules" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ" linkToPredecessor="_RkSNYsVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ" output="_RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNZsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNbMVWEd2pfdXgw7I2qQ" name="transform_rules" guid="_RkSNbMVWEd2pfdXgw7I2qQ" presentationName="Transform Rules" briefDescription="Transform the rule to avoid ambiguity and make them more atomic" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ" linkToPredecessor="_RkSNYsVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ" output="_RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-sMysBcAYtIvVDmB57oo8sA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-sMysBcAYtIvVDmB57oo8sA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_K6-3kDmnEdy8N6BRpa8ByQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x_5XgH9iEd26h9j0X6pKmw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8mZw8DmhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_7HEPsDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_tFwpYDmoEdy8N6BRpa8ByQ"/>
@@ -436,46 +687,52 @@
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_0-T6ADmoEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_RkSNYsVWEd2pfdXgw7I2qQ" guid="_RkSNYsVWEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNbcVWEd2pfdXgw7I2qQ" name="build_test_scenario" guid="_RkSNbcVWEd2pfdXgw7I2qQ" presentationName="Build test scenarios" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ" linkToPredecessor="_RkSNZMVWEd2pfdXgw7I2qQ" additionallyPerformedBy="_RkSNacVWEd2pfdXgw7I2qQ _RkSNaMVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNZsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNbcVWEd2pfdXgw7I2qQ" name="build_test_scenario" guid="_RkSNbcVWEd2pfdXgw7I2qQ" presentationName="Build Test Scenarios" briefDescription="Work with analysis team to define concrete scenario with real data so that we can later on test the process and the rules." superActivities="_RkSNZcVWEd2pfdXgw7I2qQ" linkToPredecessor="_RkSNZMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-bcOPKdssk4qvaJmaJ82Wdg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-bcOPKdssk4qvaJmaJ82Wdg"/>
+ <guidelines href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <supportingMaterials href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_vLvAUGjFEd2PJ-nlV-86WA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1dlWkH3GEd2sJcA0evSBQw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_RkSNZMVWEd2pfdXgw7I2qQ" guid="_RkSNZMVWEd2pfdXgw7I2qQ" pred="_RkSNbMVWEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_RkSNacVWEd2pfdXgw7I2qQ" name="subject_matter_expert" guid="_RkSNacVWEd2pfdXgw7I2qQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNZ8VWEd2pfdXgw7I2qQ" name="synchronize_data_model" guid="_RkSNZ8VWEd2pfdXgw7I2qQ" presentationName="Synchronize Data Models" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ" linkToPredecessor="_RkSNbsVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ" output="_RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNZsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNZ8VWEd2pfdXgw7I2qQ" name="synchronize_data_model" guid="_RkSNZ8VWEd2pfdXgw7I2qQ" presentationName="Synchronize Data Models" briefDescription="Ensure the terms and entities used in the rule march element in the different date models used by the IT components" superActivities="_RkSNZcVWEd2pfdXgw7I2qQ" linkToPredecessor="_RkSNbsVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNYcVWEd2pfdXgw7I2qQ _RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ" output="_RkSNY8VWEd2pfdXgw7I2qQ _RkSNasVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-D86vI3p-CJqtaGHovLIH3A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-D86vI3p-CJqtaGHovLIH3A"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_prtzIDmiEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_RkSNbsVWEd2pfdXgw7I2qQ" guid="_RkSNbsVWEd2pfdXgw7I2qQ" pred="_RkSNbcVWEd2pfdXgw7I2qQ"/>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj6rekEd-D7YZN9NgldQ" name="design_bre_integration" guid="_9tWj6rekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_DbIE48VXEd2pfdXgw7I2qQ" name="design_bre_integration" guid="_DbIE48VXEd2pfdXgw7I2qQ" presentationName="Design BRMS Integration" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_DbIE5MVXEd2pfdXgw7I2qQ _DbIE6cVXEd2pfdXgw7I2qQ _DbIE68VXEd2pfdXgw7I2qQ _DbIE58VXEd2pfdXgw7I2qQ _DbIE4sVXEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_DbIE48VXEd2pfdXgw7I2qQ" name="design_bre_integration" guid="_DbIE48VXEd2pfdXgw7I2qQ" presentationName="Design BRMS Integration" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_DbIE5MVXEd2pfdXgw7I2qQ _DbIE58VXEd2pfdXgw7I2qQ _DbIE4sVXEd2pfdXgw7I2qQ">
<presentation xmi:id="-iDrjgGg0EofrciITbayiaA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-iDrjgGg0EofrciITbayiaA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_DbIE5MVXEd2pfdXgw7I2qQ" name="determine_rule_implementation" guid="_DbIE5MVXEd2pfdXgw7I2qQ" presentationName="Determine Rule Implementation" superActivities="_DbIE48VXEd2pfdXgw7I2qQ" performedPrimarilyBy="_DbIE6cVXEd2pfdXgw7I2qQ _DbIE68VXEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_DbIE5MVXEd2pfdXgw7I2qQ" name="determine_rule_implementation" guid="_DbIE5MVXEd2pfdXgw7I2qQ" presentationName="Determine Rule Implementation" briefDescription="This task tries to answer the question of where to implement the business rules that have been discovered." superActivities="_DbIE48VXEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Qy_wVwt9Qh9iVf4FyNvOag" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Qy_wVwt9Qh9iVf4FyNvOag"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_qzveUBk5Edyoe_hnDlTB5A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_DbIE6cVXEd2pfdXgw7I2qQ" name="rule_analyst" guid="_DbIE6cVXEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_DbIE48VXEd2pfdXgw7I2qQ" responsibleFor="_DbIE4sVXEd2pfdXgw7I2qQ _DbIE58VXEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_DbIE68VXEd2pfdXgw7I2qQ" name="rule_architect" guid="_DbIE68VXEd2pfdXgw7I2qQ" presentationName="Rule Architect" isPlanned="false" superActivities="_DbIE48VXEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_DbIE58VXEd2pfdXgw7I2qQ" name="decision_point_table" guid="_DbIE58VXEd2pfdXgw7I2qQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_DbIE48VXEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-7BTHzZPiw1v_S2Ts1aJNBA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-7BTHzZPiw1v_S2Ts1aJNBA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_DbIE4sVXEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_DbIE4sVXEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_DbIE48VXEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_DbIE4sVXEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_DbIE4sVXEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_DbIE48VXEd2pfdXgw7I2qQ">
+ <presentation xmi:id="--tH7_LHDMrDWKm6h9JBFsA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#--tH7_LHDMrDWKm6h9JBFsA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj67ekEd-D7YZN9NgldQ" name="author_business_rules" guid="_9tWj67ekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_RkSNccVWEd2pfdXgw7I2qQ" name="author_business_rules" guid="_RkSNccVWEd2pfdXgw7I2qQ" presentationName="Author Business Rules" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_RkSNdcVWEd2pfdXgw7I2qQ _RkSNd8VWEd2pfdXgw7I2qQ _RkSNdsVWEd2pfdXgw7I2qQ _RkSNdMVWEd2pfdXgw7I2qQ _RkSNeMVWEd2pfdXgw7I2qQ _RkSNcMVWEd2pfdXgw7I2qQ _RkSNc8VWEd2pfdXgw7I2qQ _RkSNcsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_RkSNccVWEd2pfdXgw7I2qQ" name="author_business_rules" guid="_RkSNccVWEd2pfdXgw7I2qQ" presentationName="Author Business Rules" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_RkSNdcVWEd2pfdXgw7I2qQ _RkSNd8VWEd2pfdXgw7I2qQ _RkSNdMVWEd2pfdXgw7I2qQ _RkSNcMVWEd2pfdXgw7I2qQ _RkSNc8VWEd2pfdXgw7I2qQ _RkSNcsVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-8tHTcrgK1fmquEli5euXbQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-8tHTcrgK1fmquEli5euXbQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNdcVWEd2pfdXgw7I2qQ" name="develop_unit_tests" guid="_RkSNdcVWEd2pfdXgw7I2qQ" presentationName="Develop Unit Tests for rule" superActivities="_RkSNccVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNeMVWEd2pfdXgw7I2qQ _RkSNdsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNdcVWEd2pfdXgw7I2qQ" name="develop_unit_tests" guid="_RkSNdcVWEd2pfdXgw7I2qQ" presentationName="Develop Rule Unit Tests" briefDescription="The goal of this task is to track down anomalies in the rules such as conflicts, redundancies or overlaps.
" superActivities="_RkSNccVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-yPcK13A7M5bOTTJG-OiLTQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-yPcK13A7M5bOTTJG-OiLTQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ioCPkDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNd8VWEd2pfdXgw7I2qQ" name="develop_rules" guid="_RkSNd8VWEd2pfdXgw7I2qQ" presentationName="Develop Rules" superActivities="_RkSNccVWEd2pfdXgw7I2qQ" output="_RkSNdMVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNdsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNd8VWEd2pfdXgw7I2qQ" name="develop_rules" guid="_RkSNd8VWEd2pfdXgw7I2qQ" presentationName="Develop Rules" briefDescription="This task is about developing each rule in the rule project." superActivities="_RkSNccVWEd2pfdXgw7I2qQ" output="_RkSNdMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-z_nnzuHQecgXrHgcz9F0qw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-z_nnzuHQecgXrHgcz9F0qw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Y2CxEDzEEdyA6a_I80swHw"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_bsPp8ErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_qfzk4ErtEdyEE-k1R6LmOA"/>
@@ -483,22 +740,21 @@
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_zAvrMErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_GvK9oEruEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_RkSNdsVWEd2pfdXgw7I2qQ" name="rule_writer" guid="_RkSNdsVWEd2pfdXgw7I2qQ" presentationName="Rule Writer" isPlanned="false" superActivities="_RkSNccVWEd2pfdXgw7I2qQ" modifies="_RkSNdMVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNdMVWEd2pfdXgw7I2qQ" name="ruleset" guid="_RkSNdMVWEd2pfdXgw7I2qQ" presentationName="Rule Set" isPlanned="false" superActivities="_RkSNccVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNdMVWEd2pfdXgw7I2qQ" name="ruleset" guid="_RkSNdMVWEd2pfdXgw7I2qQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_RkSNccVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="--__8DYtnVs9eZArH2GikBg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#--__8DYtnVs9eZArH2GikBg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_RkSNeMVWEd2pfdXgw7I2qQ" name="developer" guid="_RkSNeMVWEd2pfdXgw7I2qQ" presentationName="Developer" isPlanned="false" superActivities="_RkSNccVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNcMVWEd2pfdXgw7I2qQ" name="enhance_object_models" guid="_RkSNcMVWEd2pfdXgw7I2qQ" presentationName="Enhance Object Models" superActivities="_RkSNccVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNeMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNcMVWEd2pfdXgw7I2qQ" name="enhance_object_models" guid="_RkSNcMVWEd2pfdXgw7I2qQ" presentationName="Enhance Object Models" briefDescription="The data model is started during the analysis and design tasks. But it will involve over time. So this activity supports the enhancement of the object models." superActivities="_RkSNccVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-xrmI1p-ME165PzMiVzJ8Sw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-xrmI1p-ME165PzMiVzJ8Sw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_UXrv8Eb3EdySHMdInS9eGA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNc8VWEd2pfdXgw7I2qQ" name="execute_rule_set" guid="_RkSNc8VWEd2pfdXgw7I2qQ" presentationName="Execute Rule Set" superActivities="_RkSNccVWEd2pfdXgw7I2qQ" output="_RkSNdMVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNdsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNc8VWEd2pfdXgw7I2qQ" name="execute_rule_set" guid="_RkSNc8VWEd2pfdXgw7I2qQ" presentationName="Execute Rule Set" briefDescription="Execute the tests to trigger the rule execution. Analyze the output logs. Report issues." superActivities="_RkSNccVWEd2pfdXgw7I2qQ" output="_RkSNdMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-uuWfS5EV0FimZ5_4aRVtjA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-uuWfS5EV0FimZ5_4aRVtjA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_JCHfMEXhEdy14e5PT9v3HQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNcsVWEd2pfdXgw7I2qQ" name="log_issue" guid="_RkSNcsVWEd2pfdXgw7I2qQ" presentationName="Log issue" superActivities="_RkSNccVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_RkSNdsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNcsVWEd2pfdXgw7I2qQ" name="log_issue" guid="_RkSNcsVWEd2pfdXgw7I2qQ" presentationName="Log Issue" superActivities="_RkSNccVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-zUb0cau__Hfq13SvkX5QLw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-zUb0cau__Hfq13SvkX5QLw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yGbYIEb0EdySHMdInS9eGA"/>
</processElements>
</childPackages>
@@ -506,37 +762,49 @@
<processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_RkSNpsVWEd2pfdXgw7I2qQ" name="validate_business_rules" guid="_RkSNpsVWEd2pfdXgw7I2qQ" presentationName="Validate Business Rules" superActivities="_o2AhUXtxEd2tkbw8c1Rm7g" breakdownElements="_xxBFkGh8Ed-9y9wL8auvhA _RkSNq8VWEd2pfdXgw7I2qQ _RkSNrsVWEd2pfdXgw7I2qQ _RkSNqcVWEd2pfdXgw7I2qQ _RkSNr8VWEd2pfdXgw7I2qQ _RkSNrcVWEd2pfdXgw7I2qQ _RkSNp8VWEd2pfdXgw7I2qQ _RkSNqMVWEd2pfdXgw7I2qQ _RkSNqsVWEd2pfdXgw7I2qQ _RkSNrMVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-4WeilgakCQbS1xQ7a54XEg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-4WeilgakCQbS1xQ7a54XEg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_xxBFkGh8Ed-9y9wL8auvhA" name="define_ruleset_testing" guid="_xxBFkGh8Ed-9y9wL8auvhA" presentationName="Define Rule Testing Approach" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_xxBFkGh8Ed-9y9wL8auvhA" name="define_ruleset_testing" guid="_xxBFkGh8Ed-9y9wL8auvhA" presentationName="Define Rule Testing Approach" briefDescription="Rule testing has been a crucial and intensive task within rule development, due to the nature of a lot of business rules working together." superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-xZmMlKJ2ELDM5ehTI5-ouA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-xZmMlKJ2ELDM5ehTI5-ouA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mDL5YGhkEd-FVuzXjnvIWA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNq8VWEd2pfdXgw7I2qQ" name="define_data_scenario" guid="_RkSNq8VWEd2pfdXgw7I2qQ" presentationName="Define Data Scenarios to Test Rule" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNq8VWEd2pfdXgw7I2qQ" name="define_data_scenario" guid="_RkSNq8VWEd2pfdXgw7I2qQ" presentationName="Define Data Scenarios to Test Rule" briefDescription="This task supports the definition of the data used to trigger the rule execution in scope for validating the rule set quality." superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-QGPmaN2xy-Wgo3ltSi79iA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-QGPmaN2xy-Wgo3ltSi79iA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eAWtgFv3EdykEsBjRsVfZw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNrsVWEd2pfdXgw7I2qQ" name="execute_ruleset_functional_test" guid="_RkSNrsVWEd2pfdXgw7I2qQ" presentationName="Execute Rule Set Functional Tests" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNp8VWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNrsVWEd2pfdXgw7I2qQ" name="execute_ruleset_functional_test" guid="_RkSNrsVWEd2pfdXgw7I2qQ" presentationName="Execute Rule Set Functional Tests" briefDescription="Validate the function supported by the rule set with end to end scenarios. This involve client code calling the rule service." superActivities="_RkSNpsVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNp8VWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-I90uzl3ItrvAQBeMg-l9pw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-I90uzl3ItrvAQBeMg-l9pw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_euAb8FtuEdykEsBjRsVfZw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNqcVWEd2pfdXgw7I2qQ" name="get_rule_set_reports" guid="_RkSNqcVWEd2pfdXgw7I2qQ" presentationName="Get Rule Set Reports" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ" output="_RkSNqMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-h_Q4rpmMhckmEL3epy5j4Q" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-h_Q4rpmMhckmEL3epy5j4Q"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_LGd_MFtvEdykEsBjRsVfZw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNr8VWEd2pfdXgw7I2qQ" name="get_sme_feedback" guid="_RkSNr8VWEd2pfdXgw7I2qQ" presentationName="Get SME Feedback" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNqMVWEd2pfdXgw7I2qQ" output="_RkSNqsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-JkOVgFn0THaQU3V_LciXbg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-JkOVgFn0THaQU3V_LciXbg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_CmBe4EtaEdyEE-k1R6LmOA"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_RkSNrcVWEd2pfdXgw7I2qQ" name="test_analysis" guid="_RkSNrcVWEd2pfdXgw7I2qQ" presentationName="Test Analysis" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ" mandatoryInput="_RkSNrMVWEd2pfdXgw7I2qQ _RkSNqMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-LGCZRD2iL1EzFH3_LqlAJg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-LGCZRD2iL1EzFH3_LqlAJg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_OmI3QEtZEdyEE-k1R6LmOA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_cik88EtZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik88UtZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik880tZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik88ktZEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNp8VWEd2pfdXgw7I2qQ" name="ruleset" guid="_RkSNp8VWEd2pfdXgw7I2qQ" presentationName="Rule Set" isPlanned="false" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNp8VWEd2pfdXgw7I2qQ" name="ruleset" guid="_RkSNp8VWEd2pfdXgw7I2qQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-UbMVWUVbdTcZeO_raP_Zmg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-UbMVWUVbdTcZeO_raP_Zmg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNqMVWEd2pfdXgw7I2qQ" name="rule_report" guid="_RkSNqMVWEd2pfdXgw7I2qQ" presentationName="Rule Report" isPlanned="false" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-fwowC3JkpIga2H7YGyHA4Q" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-fwowC3JkpIga2H7YGyHA4Q"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_arqeoUtZEdyEE-k1R6LmOA"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNqsVWEd2pfdXgw7I2qQ" name="sme_recommendations" guid="_RkSNqsVWEd2pfdXgw7I2qQ" presentationName="SME Recommendations" isPlanned="false" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-G84F_WKYJbQh1mymVCWgxw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-G84F_WKYJbQh1mymVCWgxw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_BnlgsEtaEdyEE-k1R6LmOA"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RkSNrMVWEd2pfdXgw7I2qQ" name="rsm_report" guid="_RkSNrMVWEd2pfdXgw7I2qQ" presentationName="RSM Report" isPlanned="false" superActivities="_RkSNpsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-1PQWVqDq_1c_uYCcAzXPjQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-1PQWVqDq_1c_uYCcAzXPjQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_arqeoEtZEdyEE-k1R6LmOA"/>
</processElements>
</childPackages>
@@ -544,25 +812,24 @@
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj7bekEd-D7YZN9NgldQ" name="Cycle 4- Integrating" guid="_9tWj7bekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj7rekEd-D7YZN9NgldQ" name="deploy_business_rules" guid="_9tWj7rekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_0xrvR8VWEd2pfdXgw7I2qQ" name="deploy_business_rules" guid="_0xrvR8VWEd2pfdXgw7I2qQ" presentationName="Deploy Business Rules" superActivities="_3pe8sXtxEd2tkbw8c1Rm7g" breakdownElements="_0xrvQsVWEd2pfdXgw7I2qQ _0xrvQ8VWEd2pfdXgw7I2qQ _0xrvQcVWEd2pfdXgw7I2qQ _0xrvRMVWEd2pfdXgw7I2qQ _0xrvRsVWEd2pfdXgw7I2qQ _0xrvRcVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_0xrvR8VWEd2pfdXgw7I2qQ" name="deploy_business_rules" guid="_0xrvR8VWEd2pfdXgw7I2qQ" presentationName="Deploy Business Rules" superActivities="_3pe8sXtxEd2tkbw8c1Rm7g" breakdownElements="_0xrvQsVWEd2pfdXgw7I2qQ _0xrvQ8VWEd2pfdXgw7I2qQ _0xrvQcVWEd2pfdXgw7I2qQ _0xrvRcVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-CDhw1ZKfzw57sjOszDxNXQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-CDhw1ZKfzw57sjOszDxNXQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0xrvQsVWEd2pfdXgw7I2qQ" name="deploy_rules" guid="_0xrvQsVWEd2pfdXgw7I2qQ" presentationName="Deploy Rules" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ" mandatoryInput="_0xrvQ8VWEd2pfdXgw7I2qQ" output="_0xrvQ8VWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0xrvQsVWEd2pfdXgw7I2qQ" name="deploy_rules" guid="_0xrvQsVWEd2pfdXgw7I2qQ" presentationName="Deploy Rules" briefDescription="Deploy rule set in the integrated core application" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ" mandatoryInput="_0xrvQ8VWEd2pfdXgw7I2qQ" output="_0xrvQ8VWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-tlugq7LmqmrzFCxoFyR-AQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-tlugq7LmqmrzFCxoFyR-AQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_AgQVAD5QEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_0xrvQ8VWEd2pfdXgw7I2qQ" name="ruleset" guid="_0xrvQ8VWEd2pfdXgw7I2qQ" presentationName="Rule Set" isPlanned="false" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_0xrvQ8VWEd2pfdXgw7I2qQ" name="ruleset" guid="_0xrvQ8VWEd2pfdXgw7I2qQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-TpaFFyf36HQMpZFFFgj0Cg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-TpaFFyf36HQMpZFFFgj0Cg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0xrvQcVWEd2pfdXgw7I2qQ" name="synchronize_with_wrms" guid="_0xrvQcVWEd2pfdXgw7I2qQ" presentationName="Synchronize with Web-Based Rule Management System" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ" output="_0xrvRcVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_0xrvRMVWEd2pfdXgw7I2qQ _0xrvRsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0xrvQcVWEd2pfdXgw7I2qQ" name="synchronize_with_wrms" guid="_0xrvQcVWEd2pfdXgw7I2qQ" presentationName="Synchronize with Web-Based Rule Management System" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ" output="_0xrvRcVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-f6gTOIuqcTE7Bo6RKZ0TqQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-f6gTOIuqcTE7Bo6RKZ0TqQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YkGwYFtsEdykEsBjRsVfZw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_0xrvRMVWEd2pfdXgw7I2qQ" name="rule_writer" guid="_0xrvRMVWEd2pfdXgw7I2qQ" presentationName="Rule Writer" isPlanned="false" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ" modifies="_0xrvRcVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_0xrvRsVWEd2pfdXgw7I2qQ" name="rule_administrator" guid="_0xrvRsVWEd2pfdXgw7I2qQ" presentationName="Rule Administrator" isPlanned="false" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ" modifies="_0xrvRcVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4QqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_0xrvRcVWEd2pfdXgw7I2qQ" name="rule_repository_in_db" guid="_0xrvRcVWEd2pfdXgw7I2qQ" presentationName="Rule Repository in DB" isPlanned="false" superActivities="_0xrvR8VWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-2plISeUo4TFYeepdm0sd9g" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-2plISeUo4TFYeepdm0sd9g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_jqxtYFttEdykEsBjRsVfZw"/>
</processElements>
</childPackages>
@@ -570,31 +837,35 @@
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj77ekEd-D7YZN9NgldQ" name="Cycle 5- Enhancing" guid="_9tWj77ekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj8LekEd-D7YZN9NgldQ" name="discover_business_rules" guid="_9tWj8LekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4dGMVWEd2pfdXgw7I2qQ" name="discover_business_rules" guid="_6r4dGMVWEd2pfdXgw7I2qQ" presentationName="Discover Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4dFMVWEd2pfdXgw7I2qQ _6r4dDsVWEd2pfdXgw7I2qQ _6r4dHMVWEd2pfdXgw7I2qQ _6r4dBcVWEd2pfdXgw7I2qQ _6r4dDMVWEd2pfdXgw7I2qQ _6r4dCcVWEd2pfdXgw7I2qQ _6r4dFsVWEd2pfdXgw7I2qQ _6r4dCMVWEd2pfdXgw7I2qQ _6r4dCsVWEd2pfdXgw7I2qQ _6r4dGsVWEd2pfdXgw7I2qQ _6r4dBsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4dGMVWEd2pfdXgw7I2qQ" name="discover_business_rules" guid="_6r4dGMVWEd2pfdXgw7I2qQ" presentationName="Discover Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4dHMVWEd2pfdXgw7I2qQ _6r4dDMVWEd2pfdXgw7I2qQ _6r4dCcVWEd2pfdXgw7I2qQ _6r4dFsVWEd2pfdXgw7I2qQ _6r4dCMVWEd2pfdXgw7I2qQ _6r4dCsVWEd2pfdXgw7I2qQ _6r4dGsVWEd2pfdXgw7I2qQ _6r4dBsVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-TxDZIG3zJyyBuiVvCyxaNQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-TxDZIG3zJyyBuiVvCyxaNQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4dFMVWEd2pfdXgw7I2qQ" name="rule_analyst" guid="_6r4dFMVWEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ" modifies="_6r4dCsVWEd2pfdXgw7I2qQ _6r4dGsVWEd2pfdXgw7I2qQ _6r4dBsVWEd2pfdXgw7I2qQ" responsibleFor="_6r4dHMVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4dDsVWEd2pfdXgw7I2qQ" name="business_analyst" guid="_6r4dDsVWEd2pfdXgw7I2qQ" presentationName="Business Analyst" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ" responsibleFor="_6r4dHMVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dHMVWEd2pfdXgw7I2qQ" name="use_case_model" guid="_6r4dHMVWEd2pfdXgw7I2qQ" presentationName="Use-Case Model" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dHMVWEd2pfdXgw7I2qQ" name="use_case_model" guid="_6r4dHMVWEd2pfdXgw7I2qQ" presentationName="Use-Case Model" briefDescription="This artifact captures a model of the intended functions and environment of the system and serves as a contract between the customer and the team." isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4dBcVWEd2pfdXgw7I2qQ" name="subject_matter_expert" guid="_6r4dBcVWEd2pfdXgw7I2qQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dDMVWEd2pfdXgw7I2qQ" name="decision_point_table" guid="_6r4dDMVWEd2pfdXgw7I2qQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-MfK3a42-JVFgfXFrlgKVCg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-MfK3a42-JVFgfXFrlgKVCg"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dCcVWEd2pfdXgw7I2qQ" name="business_process_map" guid="_6r4dCcVWEd2pfdXgw7I2qQ" presentationName="Business Process Map" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dCcVWEd2pfdXgw7I2qQ" name="business_process_map" guid="_6r4dCcVWEd2pfdXgw7I2qQ" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-eUCZh9-TGhKseTixKaMrHg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-eUCZh9-TGhKseTixKaMrHg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dFsVWEd2pfdXgw7I2qQ" name="discovery_workshop_itinerary" guid="_6r4dFsVWEd2pfdXgw7I2qQ" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-iQtEn6D9iqYBMMYBWuVKBw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-iQtEn6D9iqYBMMYBWuVKBw"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4dCMVWEd2pfdXgw7I2qQ" name="execute_rule_discovery_roadmap" guid="_6r4dCMVWEd2pfdXgw7I2qQ" presentationName="Execute rule discovery roadmap" hasMultipleOccurrences="true" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ" isRepeatable="true" linkToPredecessor="_6r4dGcVWEd2pfdXgw7I2qQ" additionallyPerformedBy="_6r4dDsVWEd2pfdXgw7I2qQ _6r4dBcVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4dCcVWEd2pfdXgw7I2qQ _6r4dDMVWEd2pfdXgw7I2qQ" optionalInput="_6r4dFsVWEd2pfdXgw7I2qQ" output="_6r4dCsVWEd2pfdXgw7I2qQ _6r4dGsVWEd2pfdXgw7I2qQ _6r4dBsVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4dFMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4dCMVWEd2pfdXgw7I2qQ" name="execute_rule_discovery_roadmap" guid="_6r4dCMVWEd2pfdXgw7I2qQ" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." hasMultipleOccurrences="true" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ" isRepeatable="true" linkToPredecessor="_6r4dGcVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4dCcVWEd2pfdXgw7I2qQ _6r4dDMVWEd2pfdXgw7I2qQ" optionalInput="_6r4dFsVWEd2pfdXgw7I2qQ" output="_6r4dCsVWEd2pfdXgw7I2qQ _6r4dGsVWEd2pfdXgw7I2qQ _6r4dBsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-lgSFuLT3lWbTwunMCMdGzA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-lgSFuLT3lWbTwunMCMdGzA"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
@@ -602,39 +873,55 @@
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_6r4dGcVWEd2pfdXgw7I2qQ" guid="_6r4dGcVWEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dCsVWEd2pfdXgw7I2qQ" name="business_terms_glossary" guid="_6r4dCsVWEd2pfdXgw7I2qQ" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dCsVWEd2pfdXgw7I2qQ" name="business_terms_glossary" guid="_6r4dCsVWEd2pfdXgw7I2qQ" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-jDcrhnRAGpNy9F3lmDQh9A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-jDcrhnRAGpNy9F3lmDQh9A"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dGsVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_6r4dGsVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dGsVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_6r4dGsVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Ya6ew2cXy0t86scG8NYWbA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Ya6ew2cXy0t86scG8NYWbA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dBsVWEd2pfdXgw7I2qQ" name="conceptual_data_model" guid="_6r4dBsVWEd2pfdXgw7I2qQ" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_6r4dGMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-_HXi3XetHAIsFYblsTtTcg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-_HXi3XetHAIsFYblsTtTcg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj8rekEd-D7YZN9NgldQ" name="analyze_business_rules" guid="_9tWj8rekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4c1cVWEd2pfdXgw7I2qQ" name="analyze_business_rules" guid="_6r4c1cVWEd2pfdXgw7I2qQ" presentationName="Analyze Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4c28VWEd2pfdXgw7I2qQ _6r4c2MVWEd2pfdXgw7I2qQ _6r4c1sVWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ _6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c3MVWEd2pfdXgw7I2qQ _6r4c3cVWEd2pfdXgw7I2qQ _6r4c2cVWEd2pfdXgw7I2qQ _6r4c18VWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4c1cVWEd2pfdXgw7I2qQ" name="analyze_business_rules" guid="_6r4c1cVWEd2pfdXgw7I2qQ" presentationName="Analyze Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4c28VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ _6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c3MVWEd2pfdXgw7I2qQ _6r4c3cVWEd2pfdXgw7I2qQ _6r4c18VWEd2pfdXgw7I2qQ">
<presentation xmi:id="-z_SeD1bFowOQJTPCHYGiHw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-z_SeD1bFowOQJTPCHYGiHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c28VWEd2pfdXgw7I2qQ" name="extract_rule_meaning" guid="_6r4c28VWEd2pfdXgw7I2qQ" presentationName="Extract the meaning of the rule" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4c2sVWEd2pfdXgw7I2qQ" output="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c2MVWEd2pfdXgw7I2qQ _6r4c1sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c28VWEd2pfdXgw7I2qQ" name="extract_rule_meaning" guid="_6r4c28VWEd2pfdXgw7I2qQ" presentationName="Extract Rule Meaning" briefDescription="Extract the semantic of the rule to prepare for a data model and to remove any ambiguity and redundancy." superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4c2sVWEd2pfdXgw7I2qQ" output="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-HRHCQT3_ksQap5yLiPUDqg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-HRHCQT3_ksQap5yLiPUDqg"/>
+ <concepts href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_gPfSoIpzEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8_mWgH3GEd2sJcA0evSBQw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_o19QgF2BEd2T6cNSe41mOg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4c2MVWEd2pfdXgw7I2qQ" name="business_analyst" guid="_6r4c2MVWEd2pfdXgw7I2qQ" presentationName="Business Analyst" isPlanned="false" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" modifies="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4c1sVWEd2pfdXgw7I2qQ" name="rule_analyst" guid="_6r4c1sVWEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" modifies="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ" responsibleFor="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c2sVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_6r4c2sVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c2sVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_6r4c2sVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Mp1iTCY_ZxvmhCU0pK1B4A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Mp1iTCY_ZxvmhCU0pK1B4A"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c0cVWEd2pfdXgw7I2qQ" name="fact_model" guid="_6r4c0cVWEd2pfdXgw7I2qQ" presentationName="Fact Model" isPlanned="false" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Oycd-mszF0ZsLk-8ZeJWHg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Oycd-mszF0ZsLk-8ZeJWHg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c08VWEd2pfdXgw7I2qQ" name="logical_data_model" guid="_6r4c08VWEd2pfdXgw7I2qQ" presentationName="Logical Data Model" isPlanned="false" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c08VWEd2pfdXgw7I2qQ" name="logical_data_model" guid="_6r4c08VWEd2pfdXgw7I2qQ" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-CqnB4S0O3gkfIdcDYQrDPQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-CqnB4S0O3gkfIdcDYQrDPQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c3MVWEd2pfdXgw7I2qQ" name="transform_rules" guid="_6r4c3MVWEd2pfdXgw7I2qQ" presentationName="Transform Rules" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" linkToPredecessor="_6r4c0sVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ" output="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c1sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c3MVWEd2pfdXgw7I2qQ" name="transform_rules" guid="_6r4c3MVWEd2pfdXgw7I2qQ" presentationName="Transform Rules" briefDescription="Transform the rule to avoid ambiguity and make them more atomic" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" linkToPredecessor="_6r4c0sVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ" output="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-i-o-ix2w6ehxgG6NXqzYnQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-i-o-ix2w6ehxgG6NXqzYnQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_K6-3kDmnEdy8N6BRpa8ByQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x_5XgH9iEd26h9j0X6pKmw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8mZw8DmhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_7HEPsDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_tFwpYDmoEdy8N6BRpa8ByQ"/>
@@ -644,46 +931,52 @@
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_0-T6ADmoEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_6r4c0sVWEd2pfdXgw7I2qQ" guid="_6r4c0sVWEd2pfdXgw7I2qQ" pred="_6r4c28VWEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c3cVWEd2pfdXgw7I2qQ" name="build_test_scenario" guid="_6r4c3cVWEd2pfdXgw7I2qQ" presentationName="Build test scenarios" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" linkToPredecessor="_6r4c1MVWEd2pfdXgw7I2qQ" additionallyPerformedBy="_6r4c2cVWEd2pfdXgw7I2qQ _6r4c2MVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c1sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c3cVWEd2pfdXgw7I2qQ" name="build_test_scenario" guid="_6r4c3cVWEd2pfdXgw7I2qQ" presentationName="Build Test Scenarios" briefDescription="Work with analysis team to define concrete scenario with real data so that we can later on test the process and the rules." superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" linkToPredecessor="_6r4c1MVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Vw7w7CdsiPTvpIJJdjf1NA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Vw7w7CdsiPTvpIJJdjf1NA"/>
+ <guidelines href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <supportingMaterials href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_vLvAUGjFEd2PJ-nlV-86WA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1dlWkH3GEd2sJcA0evSBQw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_6r4c1MVWEd2pfdXgw7I2qQ" guid="_6r4c1MVWEd2pfdXgw7I2qQ" pred="_6r4c3MVWEd2pfdXgw7I2qQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4c2cVWEd2pfdXgw7I2qQ" name="subject_matter_expert" guid="_6r4c2cVWEd2pfdXgw7I2qQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c18VWEd2pfdXgw7I2qQ" name="synchronize_data_model" guid="_6r4c18VWEd2pfdXgw7I2qQ" presentationName="Synchronize Data Models" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" linkToPredecessor="_6r4c3sVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ" output="_6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c1sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c18VWEd2pfdXgw7I2qQ" name="synchronize_data_model" guid="_6r4c18VWEd2pfdXgw7I2qQ" presentationName="Synchronize Data Models" briefDescription="Ensure the terms and entities used in the rule march element in the different date models used by the IT components" superActivities="_6r4c1cVWEd2pfdXgw7I2qQ" linkToPredecessor="_6r4c3sVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4c0cVWEd2pfdXgw7I2qQ _6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ" output="_6r4c08VWEd2pfdXgw7I2qQ _6r4c2sVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-lohL0MczQsZKJLN8EUe8IQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-lohL0MczQsZKJLN8EUe8IQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_prtzIDmiEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_6r4c3sVWEd2pfdXgw7I2qQ" guid="_6r4c3sVWEd2pfdXgw7I2qQ" pred="_6r4c3cVWEd2pfdXgw7I2qQ"/>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tWj9rekEd-D7YZN9NgldQ" name="design_bre_integration" guid="_9tWj9rekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4c9cVWEd2pfdXgw7I2qQ" name="design_bre_integration" guid="_6r4c9cVWEd2pfdXgw7I2qQ" presentationName="Design BRMS Integration" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4c-MVWEd2pfdXgw7I2qQ _6r4dAMVWEd2pfdXgw7I2qQ _6r4c-sVWEd2pfdXgw7I2qQ _6r4c9MVWEd2pfdXgw7I2qQ _6r4c_sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4c9cVWEd2pfdXgw7I2qQ" name="design_bre_integration" guid="_6r4c9cVWEd2pfdXgw7I2qQ" presentationName="Design BRMS Integration" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4c-MVWEd2pfdXgw7I2qQ _6r4c9MVWEd2pfdXgw7I2qQ _6r4c_sVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-MdbP5cTReRekciw_VZz3vQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-MdbP5cTReRekciw_VZz3vQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c-MVWEd2pfdXgw7I2qQ" name="determine_rule_implementation" guid="_6r4c-MVWEd2pfdXgw7I2qQ" presentationName="Determine Rule Implementation" superActivities="_6r4c9cVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4dAMVWEd2pfdXgw7I2qQ _6r4c-sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c-MVWEd2pfdXgw7I2qQ" name="determine_rule_implementation" guid="_6r4c-MVWEd2pfdXgw7I2qQ" presentationName="Determine Rule Implementation" briefDescription="This task tries to answer the question of where to implement the business rules that have been discovered." superActivities="_6r4c9cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-NmUNzIfRKfaj1Arf585V3A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-NmUNzIfRKfaj1Arf585V3A"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_qzveUBk5Edyoe_hnDlTB5A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4dAMVWEd2pfdXgw7I2qQ" name="rule_analyst" guid="_6r4dAMVWEd2pfdXgw7I2qQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_6r4c9cVWEd2pfdXgw7I2qQ" responsibleFor="_6r4c_sVWEd2pfdXgw7I2qQ _6r4c9MVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4c-sVWEd2pfdXgw7I2qQ" name="rule_architect" guid="_6r4c-sVWEd2pfdXgw7I2qQ" presentationName="Rule Architect" isPlanned="false" superActivities="_6r4c9cVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c9MVWEd2pfdXgw7I2qQ" name="decision_point_table" guid="_6r4c9MVWEd2pfdXgw7I2qQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_6r4c9cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-XeTJfes8s01sk2ZVcZ8ORQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-XeTJfes8s01sk2ZVcZ8ORQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c_sVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_6r4c_sVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_6r4c9cVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c_sVWEd2pfdXgw7I2qQ" name="rule_description_doc" guid="_6r4c_sVWEd2pfdXgw7I2qQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_6r4c9cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-vseCuvO6sao9pngM_Ax32Q" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-vseCuvO6sao9pngM_Ax32Q"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUwLekEd-D7YZN9NgldQ" name="author_business_rules" guid="_9tgUwLekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4c4cVWEd2pfdXgw7I2qQ" name="author_business_rules" guid="_6r4c4cVWEd2pfdXgw7I2qQ" presentationName="Author Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4c5cVWEd2pfdXgw7I2qQ _6r4c58VWEd2pfdXgw7I2qQ _6r4c5sVWEd2pfdXgw7I2qQ _6r4c5MVWEd2pfdXgw7I2qQ _6r4c6MVWEd2pfdXgw7I2qQ _6r4c4MVWEd2pfdXgw7I2qQ _6r4c48VWEd2pfdXgw7I2qQ _6r4c4sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4c4cVWEd2pfdXgw7I2qQ" name="author_business_rules" guid="_6r4c4cVWEd2pfdXgw7I2qQ" presentationName="Author Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4c5cVWEd2pfdXgw7I2qQ _6r4c58VWEd2pfdXgw7I2qQ _6r4c5MVWEd2pfdXgw7I2qQ _6r4c4MVWEd2pfdXgw7I2qQ _6r4c48VWEd2pfdXgw7I2qQ _6r4c4sVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-XW78i_C7h9zp23v7_4FynQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-XW78i_C7h9zp23v7_4FynQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c5cVWEd2pfdXgw7I2qQ" name="develop_unit_tests" guid="_6r4c5cVWEd2pfdXgw7I2qQ" presentationName="Develop Unit Tests for rule" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c6MVWEd2pfdXgw7I2qQ _6r4c5sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c5cVWEd2pfdXgw7I2qQ" name="develop_unit_tests" guid="_6r4c5cVWEd2pfdXgw7I2qQ" presentationName="Develop Rule Unit Tests" briefDescription="The goal of this task is to track down anomalies in the rules such as conflicts, redundancies or overlaps.
" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-ppaJma4emmmK-5NP1JKfEA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-ppaJma4emmmK-5NP1JKfEA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ioCPkDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c58VWEd2pfdXgw7I2qQ" name="develop_rules" guid="_6r4c58VWEd2pfdXgw7I2qQ" presentationName="Develop Rules" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ" output="_6r4c5MVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c5sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c58VWEd2pfdXgw7I2qQ" name="develop_rules" guid="_6r4c58VWEd2pfdXgw7I2qQ" presentationName="Develop Rules" briefDescription="This task is about developing each rule in the rule project." superActivities="_6r4c4cVWEd2pfdXgw7I2qQ" output="_6r4c5MVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-VRP7bY43MhKouOQxpD791Q" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-VRP7bY43MhKouOQxpD791Q"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Y2CxEDzEEdyA6a_I80swHw"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_bsPp8ErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_qfzk4ErtEdyEE-k1R6LmOA"/>
@@ -691,22 +984,21 @@
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_zAvrMErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_GvK9oEruEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4c5sVWEd2pfdXgw7I2qQ" name="rule_writer" guid="_6r4c5sVWEd2pfdXgw7I2qQ" presentationName="Rule Writer" isPlanned="false" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ" modifies="_6r4c5MVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c5MVWEd2pfdXgw7I2qQ" name="ruleset" guid="_6r4c5MVWEd2pfdXgw7I2qQ" presentationName="Rule Set" isPlanned="false" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c5MVWEd2pfdXgw7I2qQ" name="ruleset" guid="_6r4c5MVWEd2pfdXgw7I2qQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-mU2cfiy9SzQO2aBAKn6lEQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-mU2cfiy9SzQO2aBAKn6lEQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4c6MVWEd2pfdXgw7I2qQ" name="developer" guid="_6r4c6MVWEd2pfdXgw7I2qQ" presentationName="Developer" isPlanned="false" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c4MVWEd2pfdXgw7I2qQ" name="enhance_object_models" guid="_6r4c4MVWEd2pfdXgw7I2qQ" presentationName="Enhance Object Models" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c6MVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c4MVWEd2pfdXgw7I2qQ" name="enhance_object_models" guid="_6r4c4MVWEd2pfdXgw7I2qQ" presentationName="Enhance Object Models" briefDescription="The data model is started during the analysis and design tasks. But it will involve over time. So this activity supports the enhancement of the object models." superActivities="_6r4c4cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-Q0OitIPVg9I1Oq_g9_XCiw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-Q0OitIPVg9I1Oq_g9_XCiw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_UXrv8Eb3EdySHMdInS9eGA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c48VWEd2pfdXgw7I2qQ" name="execute_rule_set" guid="_6r4c48VWEd2pfdXgw7I2qQ" presentationName="Execute Rule Set" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ" output="_6r4c5MVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c5sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c48VWEd2pfdXgw7I2qQ" name="execute_rule_set" guid="_6r4c48VWEd2pfdXgw7I2qQ" presentationName="Execute Rule Set" briefDescription="Execute the tests to trigger the rule execution. Analyze the output logs. Report issues." superActivities="_6r4c4cVWEd2pfdXgw7I2qQ" output="_6r4c5MVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-gmJa6dJF634bZnYGdnthtw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-gmJa6dJF634bZnYGdnthtw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_JCHfMEXhEdy14e5PT9v3HQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c4sVWEd2pfdXgw7I2qQ" name="log_issue" guid="_6r4c4sVWEd2pfdXgw7I2qQ" presentationName="Log issue" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c5sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c4sVWEd2pfdXgw7I2qQ" name="log_issue" guid="_6r4c4sVWEd2pfdXgw7I2qQ" presentationName="Log Issue" superActivities="_6r4c4cVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-TunYKZqNMaMlNqp73EpPgA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-TunYKZqNMaMlNqp73EpPgA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yGbYIEb0EdySHMdInS9eGA"/>
</processElements>
</childPackages>
@@ -714,54 +1006,63 @@
<processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4dHsVWEd2pfdXgw7I2qQ" name="validate_business_rules" guid="_6r4dHsVWEd2pfdXgw7I2qQ" presentationName="Validate Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4dJsVWEd2pfdXgw7I2qQ _6r4dIcVWEd2pfdXgw7I2qQ _6r4dJ8VWEd2pfdXgw7I2qQ _6r4dJcVWEd2pfdXgw7I2qQ _6r4dH8VWEd2pfdXgw7I2qQ _6r4dIMVWEd2pfdXgw7I2qQ _6r4dIsVWEd2pfdXgw7I2qQ _6r4dJMVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-fxBunH2zP8bxL0NEj54ptA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-fxBunH2zP8bxL0NEj54ptA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4dJsVWEd2pfdXgw7I2qQ" name="execute_ruleset_functional_test" guid="_6r4dJsVWEd2pfdXgw7I2qQ" presentationName="Execute Rule Set Functional Tests" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4dH8VWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4dJsVWEd2pfdXgw7I2qQ" name="execute_ruleset_functional_test" guid="_6r4dJsVWEd2pfdXgw7I2qQ" presentationName="Execute Rule Set Functional Tests" briefDescription="Validate the function supported by the rule set with end to end scenarios. This involve client code calling the rule service." superActivities="_6r4dHsVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4dH8VWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-y4Aw5AGHiDwN62DoU72gvw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-y4Aw5AGHiDwN62DoU72gvw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_euAb8FtuEdykEsBjRsVfZw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4dIcVWEd2pfdXgw7I2qQ" name="get_rule_set_reports" guid="_6r4dIcVWEd2pfdXgw7I2qQ" presentationName="Get Rule Set Reports" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ" output="_6r4dIMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-5G8CfPgnZh36ji0ZlYzYXQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-5G8CfPgnZh36ji0ZlYzYXQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_LGd_MFtvEdykEsBjRsVfZw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4dJ8VWEd2pfdXgw7I2qQ" name="get_sme_feedback" guid="_6r4dJ8VWEd2pfdXgw7I2qQ" presentationName="Get SME Feedback" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4dIMVWEd2pfdXgw7I2qQ" output="_6r4dIsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-aGsq4sRPoN9Rg2zOy4BOaQ" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-aGsq4sRPoN9Rg2zOy4BOaQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_CmBe4EtaEdyEE-k1R6LmOA"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4dJcVWEd2pfdXgw7I2qQ" name="test_analysis" guid="_6r4dJcVWEd2pfdXgw7I2qQ" presentationName="Test Analysis" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4dJMVWEd2pfdXgw7I2qQ _6r4dIMVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-ndrhF3xLLIGB3LyVVM1-Lg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-ndrhF3xLLIGB3LyVVM1-Lg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_OmI3QEtZEdyEE-k1R6LmOA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_cik88EtZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik88UtZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik880tZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik88ktZEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dH8VWEd2pfdXgw7I2qQ" name="ruleset" guid="_6r4dH8VWEd2pfdXgw7I2qQ" presentationName="Rule Set" isPlanned="false" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dH8VWEd2pfdXgw7I2qQ" name="ruleset" guid="_6r4dH8VWEd2pfdXgw7I2qQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-1bBmUUB5_pPRA1-9EE-g7A" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-1bBmUUB5_pPRA1-9EE-g7A"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dIMVWEd2pfdXgw7I2qQ" name="rule_report" guid="_6r4dIMVWEd2pfdXgw7I2qQ" presentationName="Rule Report" isPlanned="false" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-z7C-L5MyFxgpQP2wmgkaCg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-z7C-L5MyFxgpQP2wmgkaCg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_arqeoUtZEdyEE-k1R6LmOA"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dIsVWEd2pfdXgw7I2qQ" name="sme_recommendations" guid="_6r4dIsVWEd2pfdXgw7I2qQ" presentationName="SME Recommendations" isPlanned="false" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-IM6GVp0gm8GpDQQHu1JTzA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-IM6GVp0gm8GpDQQHu1JTzA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_BnlgsEtaEdyEE-k1R6LmOA"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4dJMVWEd2pfdXgw7I2qQ" name="rsm_report" guid="_6r4dJMVWEd2pfdXgw7I2qQ" presentationName="RSM Report" isPlanned="false" superActivities="_6r4dHsVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-EuY3fQmZi-sssGgLCoGwqw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-EuY3fQmZi-sssGgLCoGwqw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_arqeoEtZEdyEE-k1R6LmOA"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUwrekEd-D7YZN9NgldQ" name="deploy_business_rules" guid="_9tgUwrekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4c8MVWEd2pfdXgw7I2qQ" name="deploy_business_rules" guid="_6r4c8MVWEd2pfdXgw7I2qQ" presentationName="Deploy Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4c68VWEd2pfdXgw7I2qQ _6r4c7MVWEd2pfdXgw7I2qQ _6r4c6sVWEd2pfdXgw7I2qQ _6r4c7cVWEd2pfdXgw7I2qQ _6r4c78VWEd2pfdXgw7I2qQ _6r4c7sVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_6r4c8MVWEd2pfdXgw7I2qQ" name="deploy_business_rules" guid="_6r4c8MVWEd2pfdXgw7I2qQ" presentationName="Deploy Business Rules" superActivities="_53V7YXtxEd2tkbw8c1Rm7g" breakdownElements="_6r4c68VWEd2pfdXgw7I2qQ _6r4c7MVWEd2pfdXgw7I2qQ _6r4c6sVWEd2pfdXgw7I2qQ _6r4c7sVWEd2pfdXgw7I2qQ">
<presentation xmi:id="-UobSWGrKBmEhg8A39R5yLg" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-UobSWGrKBmEhg8A39R5yLg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c68VWEd2pfdXgw7I2qQ" name="deploy_rules" guid="_6r4c68VWEd2pfdXgw7I2qQ" presentationName="Deploy Rules" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4c7MVWEd2pfdXgw7I2qQ" output="_6r4c7MVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c68VWEd2pfdXgw7I2qQ" name="deploy_rules" guid="_6r4c68VWEd2pfdXgw7I2qQ" presentationName="Deploy Rules" briefDescription="Deploy rule set in the integrated core application" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ" mandatoryInput="_6r4c7MVWEd2pfdXgw7I2qQ" output="_6r4c7MVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-x18L5UZxvP6LBzZCJekP0g" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-x18L5UZxvP6LBzZCJekP0g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_AgQVAD5QEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c7MVWEd2pfdXgw7I2qQ" name="ruleset" guid="_6r4c7MVWEd2pfdXgw7I2qQ" presentationName="Rule Set" isPlanned="false" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c7MVWEd2pfdXgw7I2qQ" name="ruleset" guid="_6r4c7MVWEd2pfdXgw7I2qQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-VIexLG3fR5IHNPWD53_k-w" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-VIexLG3fR5IHNPWD53_k-w"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c6sVWEd2pfdXgw7I2qQ" name="synchronize_with_wrms" guid="_6r4c6sVWEd2pfdXgw7I2qQ" presentationName="Synchronize with Web-Based Rule Management System" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ" output="_6r4c7sVWEd2pfdXgw7I2qQ" performedPrimarilyBy="_6r4c7cVWEd2pfdXgw7I2qQ _6r4c78VWEd2pfdXgw7I2qQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6r4c6sVWEd2pfdXgw7I2qQ" name="synchronize_with_wrms" guid="_6r4c6sVWEd2pfdXgw7I2qQ" presentationName="Synchronize with Web-Based Rule Management System" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ" output="_6r4c7sVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-yhAuH0Pn0YnmJPGHNdA4nA" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-yhAuH0Pn0YnmJPGHNdA4nA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YkGwYFtsEdykEsBjRsVfZw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4c7cVWEd2pfdXgw7I2qQ" name="rule_writer" guid="_6r4c7cVWEd2pfdXgw7I2qQ" presentationName="Rule Writer" isPlanned="false" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ" modifies="_6r4c7sVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6r4c78VWEd2pfdXgw7I2qQ" name="rule_administrator" guid="_6r4c78VWEd2pfdXgw7I2qQ" presentationName="Rule Administrator" isPlanned="false" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ" modifies="_6r4c7sVWEd2pfdXgw7I2qQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4QqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6r4c7sVWEd2pfdXgw7I2qQ" name="rule_repository_in_db" guid="_6r4c7sVWEd2pfdXgw7I2qQ" presentationName="Rule Repository in DB" isPlanned="false" superActivities="_6r4c8MVWEd2pfdXgw7I2qQ">
+ <presentation xmi:id="-92jwAW4UkB6tPCOwNbvKuw" href="uma://-Nbe8Rdqjq4lgoQ95Y0ot9g#-92jwAW4UkB6tPCOwNbvKuw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_jqxtYFttEdykEsBjRsVfZw"/>
</processElements>
</childPackages>
diff --git a/epf_prac_151/process.abrd.base/deliveryprocesses/openUp_abrd/content.xmi b/epf_prac_151/process.abrd.base/deliveryprocesses/openUp_abrd/content.xmi
index 26a62bb..ceb02f2 100644
--- a/epf_prac_151/process.abrd.base/deliveryprocesses/openUp_abrd/content.xmi
+++ b/epf_prac_151/process.abrd.base/deliveryprocesses/openUp_abrd/content.xmi
@@ -2,4 +2,5226 @@
<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="-qwh4CuVnjaLX6IHR9ARntQ" name="governance,_2o6S8X_DEd2YWI_0AZcMOA" guid="-qwh4CuVnjaLX6IHR9ARntQ"/>
<org.eclipse.epf.uma:DeliveryProcessDescription xmi:id="-zmO9iNLv1qeo2tvrSUooQw" name="rup_abrd,_iVgFYT3gEd-rQL4FfV6WbQ" guid="-zmO9iNLv1qeo2tvrSUooQw"/>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-prjAV1fmvfmd2Zg_NkMweQ" name="identify_decision_point,_-wL9UD3gEd-rQL4FfV6WbQ" guid="-prjAV1fmvfmd2Zg_NkMweQ">
+ <refinedDescription><p>
+ A <a class="elementLink" href="./../../practice.tech.abrd.base/guidances/termdefinitions/decision_point_B1C5EFE2.html"
+ guid="_XUyFIEb1EdySHMdInS9eGA">Decision point</a>&nbsp;represents an activity in a business process where decisions are
+ done. When looking at a task description it is important to search for mental thinking verb, most of the time there is
+ a set of knowledge to apply to execute this task, which leads to decision. This could be human knowledge or business
+ logic implementation in a software component. The type of decision will most likely be a reject or accept of the
+ business event or flag it for future processing downstream in the business process. The decision may also include some
+ computational expressions to assign value to attribute of the business transaction. Therefore to find decision point in
+ a business process or use case description start by searching for mental, action verb like analyze, check, validate,
+ evaluate, verify, assess, ...
+</p>
+<p>
+ In a BPMN process diagram a business process analyst and/ or a rule analyst can annotate the process to highlight
+ decision point in the process.
+</p>
+<p>
+ <img height="363" alt="" src="resources/FindDecisionPoint.bmp" width="1572" />
+</p>
+<p>
+ The search for decision point, attached to a business process description (done with use case or with BPMN does not
+ matter), helps to drive the rule analysis, and helps the business to focus at the business rule&nbsp;enforcement.
+ If&nbsp;the business team misses where the rule should be enforced, he can spend months defining business rules which
+ IT does not understand where to deploy them. The decision point can help drive the discovery of the business policies
+ and rules, for an implementation point of view, as well as a way to organize the top down approach. A decision point
+ support multiple rules, and if implemented with a rule engine, the rules are packaged as rule set.
+</p>
+<p>
+ Also finding the decision points involves studying<br />
+ • Which use cases/scenarios represent decisions - At what steps in the use case is a decision made?<br />
+ • Which requirements constitute rich set of decisions?<br />
+ • Which steps/cases/requirements represent significant complexity?<br />
+ • Which steps/cases/requirements are most subject to change?<br />
+ • Look for decision diamonds in the flow charts and activity diagrams, the gateway by itself route the data to the next
+ activity, but the activity before the gateway should be rich in decisions.
+</p>
+<p>
+ The documentation of the decision point can be done in table format.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-IuPwmyFj6cPxKh7va58BBg" name="review_decision_point_table,_cj-9QD3hEd-rQL4FfV6WbQ" guid="-IuPwmyFj6cPxKh7va58BBg">
+ <refinedDescription><a id="XE_decision_point_table__review" name="XE_decision_point_table__review"></a>See the step description&nbsp;below.</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-dZH2mwKP_HVhAcRXF625-g" name="define_discovery_roadmap,_dS7G4D3hEd-rQL4FfV6WbQ" guid="-dZH2mwKP_HVhAcRXF625-g">
+ <refinedDescription><p>
+ There are two dimensions to consider when preparing the rule discovery activi-ties or roadmap:
+</p>
+<ul>
+ <li>
+ The type of source for rule harvesting
+ </li>
+ <li>
+ The type of analysis used by the project team: use case approach, busi-ness process modeling, mission policies
+ analysis
+ </li>
+</ul>
+<p>
+ Tony Morgan in his book "Business Rules and Information Systems: Aligning IT with Business Goals" proposes the
+ following discovery processed according to the different source above:
+</p>
+<ul>
+ <li>
+ The static analysis process uses reading and highlighting the rules within documentation. The elicitation is based
+ on reading session completed with Question / Answer workshop sessions
+ </li>
+ <li>
+ Interactive involves a Subject Matter Expert who has the knowledge of the business process and the decisions to
+ take to process a given business event.The process will be done by using elicitation workshop
+ </li>
+ <li>
+ Automated involve using a computer and special application to search for rule statement within procedure code, SQL
+ procedures, code listing... Code review should always be complemented by workshop sessions for Q&amp;A.<br />
+ </li>
+</ul>
+<p>
+ So for each decision point within the DP table do the following steps&nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-k9x6Q4vmGjn5pz_YPmFOSQ" name="organise_workshop,_d88UQD3hEd-rQL4FfV6WbQ" guid="-k9x6Q4vmGjn5pz_YPmFOSQ">
+ <refinedDescription><a id="XE_workshop__organize" name="XE_workshop__organize"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ To make the better use of the development and business team's time it is important to plan in advance the workshop
+ sessions and to clearly state what is in the agenda. We recommend organizing the day in two parts:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Do morning discovery workshop using elicitation techniques with the project stakeholders and subject matter expert.
+ During the&nbsp;rule harvesting phase the analyst team may want to use the rule template document to enter the rule
+ description and use some simple diagramming techniques to define the business entities (A good tool is the UML
+ class diagram but without the details of the methods)
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Second part of the day is used by&nbsp;the analyst and development team to perform analysis activities and later on
+ to author the rules.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ As explained in <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/concepts/cycle_approach_7FA44D8F.html"
+ guid="_ftAoIAjrEdyj5bYZ0eCR5g">Cycle Approach to Rules Development</a> the discovery workshops are in phase 1, 2, and
+ 3, but with different frequency of occurrence. Phase 1 and 2, the workshops can be set every morning, but starting on
+ phase 3 it could happen every two days or more (but never more than a week to keep the focus and efficiency in the
+ process).<br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The team should verify to have access to a dedicated meeting room with white boards, pencils, paper; post it, and
+ potentially a UML tool to quickly develop diagrams..
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-pFOBrLzvMdSKhPgshdTUmg" name="execute_rule_discovery_roadmap,_eaADsD3hEd-rQL4FfV6WbQ" guid="-pFOBrLzvMdSKhPgshdTUmg">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-klIiZfe42Fb3xkxnrn7s8g" name="business_event_description,_ryHzlFmSEeCcpdiAcH0w-w" guid="-klIiZfe42Fb3xkxnrn7s8g">
+ <refinedDescription><p>
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 9.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">Trigger
+ for the execution of a business process.</span> The processing of a business event can be done manually or using
+ software products and applications. Some decisions need to be done on the event for example to accept/ reject it or to
+ initiate some business processes. Those decisions can be implemented using a rule engine technology.
+</p>
+<p>
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 9.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">The
+ following list gives some examples of business event:</span>
+</p>
+<ul>
+ <li>
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Claim is received</span>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Tax
+ form is filled</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Loan
+ application is received</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Car
+ is out of the chain</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Train
+ wheel goes in front of infrared sensor</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">RFID
+ read</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Wafer
+ is started within the Fab</span>
+ </div>
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-dvJXCSep8C4BgXVKBdqzWw" name="business_process_map,_ryHzplmSEeCcpdiAcH0w-w" guid="-dvJXCSep8C4BgXVKBdqzWw">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-l3HNcE1exbebFi_vHnSlng" name="decision_point_table,_ryHzqVmSEeCcpdiAcH0w-w" guid="-l3HNcE1exbebFi_vHnSlng">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-iJdVDnhIv3mdPxGvKtIQTQ" name="decision_point_table,_-wL9Uz3gEd-rQL4FfV6WbQ" guid="-iJdVDnhIv3mdPxGvKtIQTQ">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-VciLFpBjLKj1Gg5oGyKV2w" name="business_process_map,_ckIuQD3hEd-rQL4FfV6WbQ" guid="-VciLFpBjLKj1Gg5oGyKV2w">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-97voq1CnhjuPRUVjP8vvHQ" name="rule_discovery_roadmap,_dTE34T3hEd-rQL4FfV6WbQ" guid="-97voq1CnhjuPRUVjP8vvHQ">
+ <refinedDescription><a id="XE_rule_discovery__roadmap" name="XE_rule_discovery__roadmap"></a>For each decision point we can complete the
+information about the discovery roadmap and plan. The following table format can be used as template.<br
+class="ISISGuidance" style="MARGIN: 3pt 0cm 3pt 36pt" /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-qe6GN8mPPfm5owdB98DzBw" name="discovery_workshop_itinerary,_d88UQT3hEd-rQL4FfV6WbQ" guid="-qe6GN8mPPfm5owdB98DzBw">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-C1-wtv51AzfuS54DlC_z7w" name="business_terms_glossary,_eaADsT3hEd-rQL4FfV6WbQ" guid="-C1-wtv51AzfuS54DlC_z7w">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="--peqPcPE-E86pPKWX9cwLg" name="rule_description_doc,_eaADsj3hEd-rQL4FfV6WbQ" guid="--peqPcPE-E86pPKWX9cwLg">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-l8K8ZTTtZ7_u4YFVAyYZWg" name="conceptual_data_model,_eaADsz3hEd-rQL4FfV6WbQ" guid="-l8K8ZTTtZ7_u4YFVAyYZWg">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-rpwuTxNm209KUwlswmH8HQ" name="execute_rule_discovery_roadmap,_e2UMQD3hEd-rQL4FfV6WbQ" guid="-rpwuTxNm209KUwlswmH8HQ">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-9vl1UQ_4DObTvAkwNa9kEQ" name="extract_rule_meaning,_geBw8D3hEd-rQL4FfV6WbQ" guid="-9vl1UQ_4DObTvAkwNa9kEQ">
+ <refinedDescription><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">During the elicitation activity the raw description of the rule uses business terms as used in common
+ language used by the people. This presents what the business users think about the way things are done in the company.
+ They are linking words with statements with all the different semantic attached to them. The first activity focuses on
+ analyzing this rule description&nbsp;to extract&nbsp;the business entities and terms used in a formal non ambiguous
+ fashion.&nbsp;</font></span>
+</p>
+<p>
+ We are discussing about Business Term here, as reference to a business concept used in daily business operations.They
+ are often found in different departments or refer to the same business concept from a different perspective: they are
+ synonyms. A term may describe business concept which will be mapped to a Class, a characteristic of a business entity
+ which will be mapped to attribute of a class, and sometime a term may describe the way a business object behave, in
+ that last case it will be mapped within method of a final state machine.
+</p>
+<p>
+ The second concept presented in the analysis of rule is the Fact. Fact is a combination of terms that describes what
+ business people know about their business. It connects terms into sensible business relevant observations.<br
+ style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple" />
+ As stated by the SBVR specification meaning is built of concepts, questions and propositions. the concepts will build
+ our underlying data model used by the executable rules, and the proposition will structure the data model and can also
+ be mapped to rules.<br />
+</p>
+<p
+style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple">
+ All these informations&nbsp;help to build a&nbsp;first logical data model used to build the underlying object
+ model&nbsp;used by the rules. We can use UML tool to design a class diagram, generates java code and import such code
+ in the rule IDE.<br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-E243hD2whycztF2dFXEwkA" name="transform_rules,_g1t4MD3hEd-rQL4FfV6WbQ" guid="-E243hD2whycztF2dFXEwkA">
+ <keyConsiderations>This activity will also be done during the implementation of the rule set, but it is started during the analysis, so we are
+detailing it in this context.</keyConsiderations>
+ <refinedDescription><p>
+ Rule Analyst has to study the rule discovered and try to transform it so that the implementation and the management of
+ the rule will be more easy. This includes transforming the rule in atomic element using a syntax without ambiguity,
+ remove redundant rules, conflicting rules, and finally try to redefine the scope of the rule by searching by
+ non-handled cases.&nbsp;
+</p>
+<p>
+ At this stage rule analyst can build some rule template which&nbsp;are built from rules that have the same set of
+ conditions with some little variations: adding new value in test condition, or new condition.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-99g5YVnMANjm-DUauKZXWg" name="build_test_scenario,_hOwDQD3hEd-rQL4FfV6WbQ" guid="-99g5YVnMANjm-DUauKZXWg">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-tIAbTEFRB78mlG35hRD9zQ" name="synchronize_data_model,_h2_H8D3hEd-rQL4FfV6WbQ" guid="-tIAbTEFRB78mlG35hRD9zQ">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst needs to continuously verify that business terms used in rule statements are part of the logical data
+ model (classes/ attributes) and physical data model (PDM). The model exposed to the rule needs to get data from data
+ sources. If a concept is not in the data it has to be quickly handled and managed by the application architect.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst should be in continuous communication with the data model developer, responsible to develop the XML
+ schema or java model (or .Net), and the physical mapping to database.<br />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Part of most of the business application are the list of code, enumerated date or domain values. It is important to
+ well design how those data are defined, accessed by the application, and the rule authoring environment.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ It can be helpful for some major business term to define a mapping to a class-attribute, and if the BRMS supports this
+ function it is recommended to detail the "verbalization" of the business term.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<div align="center">
+ <table class="MsoNormalTable" style="WIDTH: 351pt; BORDER-COLLAPSE: collapse; mso-padding-alt: 0in 0in 0in 0in"
+ cellspacing="0" cellpadding="0" width="468" border="0">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes">
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: gray 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Business Term</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">OO mapping</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Verbalization</span></i>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LTV</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LoanApplication.ltv</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">The loan to value ratio</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in left 3.0in" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Hh7gh2SK9tvxwdrSoTk3tg" name="develop_architecture,_EI4q4D3iEd-rQL4FfV6WbQ" guid="-Hh7gh2SK9tvxwdrSoTk3tg">
+ <keyConsiderations><p class="MsoNormal" style="MARGIN: 0in 0in 10pt">
+ <span style="mso-bidi-language: HE">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.</span>
+</p></keyConsiderations>
+ <refinedDescription><p>
+ The architect has to address as soon as possible in the project life cycle:
+</p>
+<ul>
+ <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.
+ </li>
+ <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.<br />
+ </li>
+</ul>
+<p>
+ For a BRMS deployment architect needs to integrate the following components within the IT architecture:
+</p>
+<ul>
+ <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.&nbsp;<br />
+ </li>
+ <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.<br />
+ </li>
+ <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.<br />
+ </li>
+ <li>
+ A Web based Rule management platform to let business users and analysts being able to maintain the rules.<br />
+ </li>
+ <li>
+ A Rule testing framework to support functional testing of the rule set and non-regression tests.
+ </li>
+</ul>
+<p>
+ <img height="376" alt="" src="resources/BRMScomponents.bmp" width="487" />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Bs-Oyk_niHDCHWUI80V5qw" name="logical_data_model,_EI4q4j3iEd-rQL4FfV6WbQ" guid="-Bs-Oyk_niHDCHWUI80V5qw">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-QinOsfSXNHdry4crJjAWWw" name="decision_point_table,_EI4q4z3iEd-rQL4FfV6WbQ" guid="-QinOsfSXNHdry4crJjAWWw">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-_773MJ887tp2r2fn24vH9Q" name="decision_service_architecture,_EI4q5D3iEd-rQL4FfV6WbQ" guid="-_773MJ887tp2r2fn24vH9Q">
+ <refinedDescription><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 /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-OgvhvvxDv6DTP9JkppFgpw" name="define_data_scenario,_WZA94D3jEd-rQL4FfV6WbQ" guid="-OgvhvvxDv6DTP9JkppFgpw">
+ <refinedDescription>This task is initiated during the rule harvesting phase, and completed over the development life cycle. Developing the data
+model used by the rules enforces to adopt a test driven development approach which define the&nbsp;data with the project
+model. Extracting the terms and the facts used by the rules helps to define the conceptual&nbsp;data model, this model can
+be unit tested with framework like Junit. Data defined in these test cases&nbsp;should come&nbsp;from the rule discovery
+session. Rule discovery is easily facilitate when concrete example is used to drive understanding of the
+business&nbsp;intent for each rule. The concrete example is used to populate data for test.&nbsp;&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-VVUx-pgzq9QqwpY7eyCQug" name="determine_rule_implementation,_0hT5ED3hEd-rQL4FfV6WbQ" guid="-VVUx-pgzq9QqwpY7eyCQug">
+ <refinedDescription><a id="XE_rule__determine_implementation" name="XE_rule__determine_implementation"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Project teams involved in BRMS deployment are often asking the following type of questions:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus a&nbsp;BPM?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ How do I decide what decisions should I put into a BRE?
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l4 level1 lfo5; tab-stops: list 36.0pt">
+ When should I use BRMS versus code?&nbsp;
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ There are definitively multiple variables which could influence the decision on where to implement rules. We can start
+ by looking at the BRMS value propositions, it should help to get a first set of variables:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Adaptability – Measure the ability to change the business logic easily. The motivation can be due to short deadline
+ constraint, or frequent small changes or important change that may occur every month or quarter.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Transparency – Represents the need to clearly implement the business logic as what was agreed upon the business
+ unit and the IT team, in a way that every parties understand the logic. This is leading to express the logic in
+ natural or close to natural language.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Auditability – Represents the ability to trace from the business motivation to the execution of the policy to
+ better understand what was the logic behind a decision.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Reusability – Need to share business logic across processes or applications and stay . consistent across
+ applications/transactions
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo6; tab-stops: list 36.0pt">
+ Manageability- This variable addresses the life cycle management of the business logic. Who writes what, and when,
+ and all the questions related to maintenance and evolutions of the rule-based service.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The purpose here is not to say it is not possible to support those variables in standard software development
+ practices, but more to find some good patterns on how to decide on where to implement the business logic.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ When looking at a business rules statement software engineer can see different possible choices of implementation like:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Data model: designing an object oriented object model involves supporting a lot of business rules. A statement like
+ a mortgage application can have a primary and a secondary borrower, will be supported by two classes and a 1 to 2
+ relationship. At the instantiation of those classes the control of the cardinality can be done in the application
+ logic, or the database, or the GUI structure.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Application code: implementing the logic in function, procedural code or methods in service layer or business
+ objects.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ BPM process flow, tasks or links: BPM tools are addressing business process efficiency issue specifically on "who
+ is involved", "when they should be involved". "what they need to do". BPM supports manual human and automated
+ actors. At a glance the business logic to implement in BPM is linked to people, task, and data to process within a
+ task. When supporting purely automated tasks BPM is orchestrating the application logic and services (BPEL engine).
+ BRMS complements BPM by adding the why to a BPM task, why it behaves a certain way, why this decision is done.
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Rule engine: <span style="mso-spacerun: yes">&nbsp;</span>using predefined structure like if then else statement or
+ decision table, rule flow, decision tree, function, rule template or other high level language...
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo7; tab-stops: list 36.0pt">
+ Graphical user interface: <span style="mso-spacerun: yes">&nbsp;</span>using scripting language or server side code
+ in controller class it is possible to implement data validation type of business rules.
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In the following paragraphs address each of different choices with their impact on the variables
+</p><br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in Data Model</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Rule which is controlling the structure of the model and the reference integrity
+ should be in the physical data model, the O/R mapping layer or on the domain object model.</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule setting constraint on relationship -
+ <span style="mso-spacerun: yes">&nbsp;</span>like a loan application could only have two borrowers</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Rule on the structure of the business
+ entities - like this attribute is part of this object</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo2; tab-stops: list 36.0pt">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following facts are based on a simple
+ user authentication problem, are well implemented in an object model and the supporting application code which
+ create the instance from the data (O/R mapping layer or DAO or service layer):</span>
+ </li>
+</ul>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of users who can login to the application</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A Company has a list of groups of user</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A User is part of a group</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group includes a list of Users</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 3pt 0cm 3pt 54pt; TEXT-INDENT: -18pt; mso-list: l5 level1 lfo3; tab-stops: list 54.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-language: HE; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span> <span
+ style="mso-bidi-language: HE">A group has one user reference who is the creator of the group</span>
+</p>
+<p>
+ Terms and facts and derived attributes&nbsp;are the primary constituents of data models and are represented in a UML
+ class diagram, and logical data model (entities/relationship model), or a physical data model.
+</p>
+<p>
+ <span style="mso-bidi-language: HE">The following table lists the impact of this implementation on the previously
+ defined variables</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 221.4pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very static implementation. A change in the constraints of the object model
+ impact, data persistence, logical data model, service and presentation layers. Change is managed on
+ a monthly or yearly basis</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Data model represented as UML classes diagram is doing a poor job to
+ communicate to business. Entities diagram represents a more high level representation of the domain
+ model, but forces the team to maintain the link between the implementation and the business
+ representation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tool, with a strict development process and
+ disciplines can help to trace back to the business motivation.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Domain Object model can be designed as reusable. But in the reality each
+ application needs a view of the core business object model, and so part of the implemented
+ application will be to build those view.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 221.4pt; 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"
+ valign="top" width="295">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Configuration management tools and strict discipline can help maintain the
+ business logic.</font></span>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in application code</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Implementing business rule in application code is
+ currently the most common way the IT developer is doing it. The major justifications are performance and flexibility of
+ the coding language. Using hard coded if/then/else statements isn't too flexible, but in the hands of a top notch
+ programmer it can be very fast and arguably as fast as or faster than a rule engine. Assuming the programmer has
+ unlimited time to optimize the execution for a fixed set of rules. If the ruleset changes frequently and the system
+ can't tolerate a big drop in performance, than a rule engine is the solution.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following example of business rules may be
+ easily implemented in code:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span class="ISISCodeParagraphChar"><font face="Courier">verify in each items the customer bought since he is customer
+ with us there is at least one article of type T so that we can propose the new product Y with X % of discount, except
+ if the customer is from the state of New York or New Jersey</font></span><span
+ style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">We can implement this in a method which loops on
+ the articles bought by a given customer and do the search. At a first analysis, navigating in a collection of objects
+ and testing multiples conditions on them is easy to implement using the power of programming language.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One thing interesting will be the hard coding of
+ the value of New York, New Jersey... If this logic change we need to add if statements in the code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Other type of rules are related to the control of
+ the execution of a set of "services" to support specific use case. Dispatching, orchestration, data manipulation, … are
+ better candidate to be implemented in application code. Those rules are more static, often more complex, and
+ definitively linked to context of execution. The context may be too complex to expose to a rule engine.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Orchestration are now very well supported by
+ BPM-BPEL engine because the developer needs to add flexibility on the service selection and invocation.<span
+ style="mso-spacerun: yes">&nbsp;</span></span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The evaluation of the important variables
+ is:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 334.25pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">the necessity to change code when a business rule changes is still
+ unpleasant: software build are more efficient and cost less than before but deployment may be
+ expensive depending of the complexity of the production environment. <span
+ style="mso-spacerun: yes">&nbsp;</span></font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Changing code under time pressure usually leads to poor
+ quality</font></span>
+ </p><br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. The logic as defined by the business is split in multiple parts of the
+ code, methods and procedures.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Poor. Only strict use of configuration management tools with a strict
+ development process may help.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">If the logic is implemented in a service layer with defined interface it may
+ be possible to reuse part of the methods.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 334.25pt; 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"
+ valign="top" width="446">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Developer is
+ responsible to implement the change, and use configuration management tools and strict development
+ disciplines.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in process map</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Business process automation is the technology components substituting and/or
+ supplementing manual processes to manage information flow within an organization to lower costs, reduce risk, and
+ increase consistency. In this context Business rules describe the structure, operation, and strategy of an
+ organization's business process. The business process definition can be seen as a business rule. Typically a rule
+ involving routing of transactional data to a queue, a task, or a sub process will be most likely implemented in a
+ process map. Defined at the link level business rules are linked to the structure of the process flow. Once designed
+ and implemented there is few chance those rule will change. Changing a business process is most of the time risky: we
+ do not want to change thing working and involving a lot of parties and stakeholders. In fact</span> new policies,
+ regulations or business strategies may affect the rules without changing the core business processes.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">A rule like: "<i style="mso-bidi-font-style: normal">if there is an exception in
+ the claim processing we want a supervisor to study the claim and the accumulated reasons extracted by the process so
+ far"</i> will most likely finish as guard on a process map link:</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <img height="348" alt="" src="resources/BRinBPM.bmp" width="313" />
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Task 1 will most of the time call a rule engine to take decision on the claim. One of the pattern is to accumulate all
+ the possible reasons in a list. If the list include an exception or high priority reason, the process map will route to
+ the "Process Exception" task. This task can queue the work item to a supervisor queues.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There are a lot tasks in a business process that are decision rich, so with a lot
+ of business rule to execute before completing the task. Those rules can be executed by a rule engine. The integration
+ Rule Engine – BPM will bring the value to support those cases. But as good practice it is always possible to try to
+ re-arrange an activity diagram of a use case or a process map so that some activities are purely automatically executed
+ in a rule engine mapped as a rule flow.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Business rules hardly coded in using BPM notation is not efficient and lead
+ to complex map. The real design implementation is to mix BPM map and business rules-decision
+ delegated in a process task. In this type of implementation we can leverage the best of both
+ worlds, and the adaptability is excellent.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: when the integration of BPMS and BRMS is done perfectly, the
+ business and IT team have a clear understanding of the process execution and the decision done by a
+ task by studying the rules attached to the task.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: both tools has version control, and it is possible to link
+ process map version to rule set version.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rules defined in a task should be expose to the other application as a
+ service. So reusability can be achieved. Rules in a BPM map are not really reusable.</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Process logic will
+ have a more stable life cycle, and it is managed in the BPMS. <span
+ style="mso-spacerun: yes">&nbsp;</span></span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a rule engine</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Any type of rule using a forward chaining approach will best fit in any RETE rule
+ engine. To avoid long explanation a rule engine will perform very efficiently the following rules which are more
+ complex to implement in code:</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Set parameter = A / (B ^ 2)</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If parameter is above 30 then the risk is<span
+ style="mso-spacerun: yes">&nbsp;</span> medium</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l2 level1 lfo4; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">If the risk is medium then alert the manager</span>
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><span style="mso-spacerun: yes">&nbsp;</span>If we enter a new value for A all the
+ depend rules will be fired. Rules can be entered in any order we want, it is less declarative than procedural
+ code.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">Backward chaining rule pattern can also been supported by a rule engine. The rule
+ system works down the tree to find the data that it requires. It will ask question to be able to infer decisions. It is
+ possible to implement backward chaining with product using pure inference by&nbsp;using a goal object.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">As we already stated one of the key factor is flexibility. We already encounter the
+ following decision: "This rule will not change"... but in fact it will do in the future or some of related one"
+ .</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">We can for example take a simple example of a static rule defined as</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 1.9pt 0cm 0pt 18pt; TEXT-ALIGN: justify">
+ <span class="ISISCodeParagraphChar"><font face="Courier">If the status of the customer is gold and the product is
+ &lt;&gt; then apply &lt;&gt; % discount</font></span><span style="mso-bidi-language: HE">.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">This rule can be implemented within application code using some tables in a
+ database that link the product, the category of possible status and the discount to apply. But when discussing with the
+ business user to understand what is a gold customer? We can get other conditions that definitively will change over
+ time: "A customer who spend more than &lt;&gt; the amount of money... during the last 6 months ...No !<span
+ style="mso-spacerun: yes">&nbsp;</span> during the last four month only for the product X because it was only available
+ for 4 months!, … Okay but customer in the states {,,,,} could not be part of the gold status... Ah I forgot, ... A
+ customer must have 18 years old, and by the way customer working for our company or subsidiaries could not be part of
+ the gold...</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The variables evaluation:</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-padding-alt: 0cm 5.4pt 0cm 5.4pt; mso-border-alt: solid silver 1.0pt; mso-yfti-tbllook: 480; mso-border-insideh: 1.0pt solid silver; mso-border-insidev: 1.0pt solid silver"
+ cellspacing="0" cellpadding="0" border="1">
+ <thead>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Variables</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 344.65pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE"><font size="3"><font
+ face="Times New Roman">Evaluation</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ </thead>
+ <tbody>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Adaptability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt"><font
+ face="Times New Roman">Excellent, rule can change quickly and be deployed quickly too</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Transparency</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent: by adding meta data to implemented rule we can clearly link rule
+ to business strategies and policies</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Auditability</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Excellent and most of the rule engine has log mechanism to trace what were
+ the rules executed on a given transaction.</font></span>
+ </p>
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Rule reports are important to the business as part of
+ documentation</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Reusability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Very good if the BRMS use rule repository and the rule analyst designed a
+ rule sharing approach</font></span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 4; mso-yfti-lastrow: yes">
+ <td
+ style="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: 4cm; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="151">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt"><font
+ face="Times New Roman">Manageability</font></span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 344.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"
+ valign="top" width="460">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span
+ style="FONT-SIZE: 8pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">Excellent as rules
+ are externalized and managed as a standalone artifact. Rule configuration management is complex,
+ and integrity between rule life cycle and rule set versioning is not a simple
+ practice.</span></font>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <a><font color="#0066B2"><em><font size="3">Rule in a graphical user interface</font></em></font></a>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ We will base the integration on the Model-View-Controller (MVC) design pattern. The presentation tier handles the
+ client interaction by abstracting the low-level protocol details into an event-based mechanism. The view's main
+ requirement is synchronization with the model so that data displayed to the user is up to date. The controller is
+ responsible to prepare the data and manage the view flow and content. Delegating the creation of content to a rule
+ engine is possible but need to be done synchronously.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ The business rule will be related to control the list of widget the GUI will present. A typical pattern is around
+ product catalog application or dynamic questionnaire. The rule pattern to control the content looks like:
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the selection on this page was &lt;&gt; then add this &lt;&gt; to the model
+ used in view &lt;&gt;</i>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ A rule to control the flow of page looks like
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 36pt">
+ <i style="mso-bidi-font-style: normal">If the user visited page &lt;&gt; (and | or page &lt;&gt;) then next page is
+ &lt;&gt;</i>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Both rules may be enriched with business type decision based on data of the model.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In these pattern it is clear we need to keep the previous context of decision, and events the user created.<span
+ style="mso-spacerun: yes">&nbsp;</span> So most of the current applications are putting the business rule in the
+ controller class or in the java script of the view, but it is possible to design the controller to use a rule engine,
+ as soon as the decision needs to change. This is particularly true for e-commerce web site, where marketing campaign
+ can quickly be put in place by proposing product or product feature more dynamically.<span
+ style="mso-spacerun: yes">&nbsp;</span>
+</p><br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-XQBNNrNBrtaxuEo4q-lUBA" name="define_ruleset,_24aTUD3hEd-rQL4FfV6WbQ" guid="-XQBNNrNBrtaxuEo4q-lUBA">
+ <refinedDescription><a id="XE_rule_set__define" name="XE_rule_set__define"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">When designing an application using one BRE and a simple rule set this activity
+ will be done quickly. The rule developer still needs to think about the parameters the exception management, <span
+ style="mso-spacerun: yes">&nbsp;</span>what are the rule part of the rule set, and how they are executed.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">So for a simple unique rule set the following information needs to be designed and
+ documented:</span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Input, output parameters</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Type of data model</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Rule execution flow using a rule flow. But it is still possible with modern BRE
+ to use re-entrant rule set, so executing a rule flow from a rule task or rule package.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Exception management</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Inference objects like a result object which may be used to control the future
+ execution of the caller application or the BRE.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">What are the rule part of the rule set</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">What is their execution order. It is recommended to avoid using a ordering
+ mechanism like the rule priority, but some time at a rule task level it is needed to use sorting mechanism</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">When does a rule is not candidate to enter in a rule set. This is linked to the
+ rule life cycle.</span>
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-tAu2iMCzVIgP4_Al4Lw8ww" name="build_rule_project_structure,_1Qi9oD3hEd-rQL4FfV6WbQ" guid="-tAu2iMCzVIgP4_Al4Lw8ww">
+ <refinedDescription><a id="XE_rule_project__build_structure" name="XE_rule_project__build_structure"></a><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; TEXT-ALIGN: justify; mso-list: l0 level1 lfo1; tab-stops: list .25in" />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><span style="mso-bidi-language: HE">This activity is linked to the tool used. There
+ is still some considerations when designing the project structure for the rules and application:</span></span>
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Apply good design practice of implementing the application using a n-tier
+ approach. The service layer includes the interfaces of the rule decision service entries.</span><br
+ class="MsoNormal" style="MARGIN: 3pt 0cm 3pt 18pt" />
+ <br />
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE"><img height="491" alt="" src="resources/projStruct.bmp" width="515" /></span>
+</p>
+<div style="MARGIN-TOP: 0cm; MARGIN-LEFT: 2em" type="disc">
+ <ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE"><span style="mso-bidi-language: HE">Organize rule project so that a few
+ person can concurrently work on&nbsp;rule artifact at the same time.</span></span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ <span style="mso-bidi-language: HE">Organize rule project so that they are manageable in term of performance at
+ the execution and at the rule authoring level.</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l1 level1 lfo1; tab-stops: list 36.0pt">
+ Separate representation of the domain object model in java project.
+ </li>
+ </ul>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-VHCrUwUFMiDFHcwq5Epk8g" name="build_object_models,_05dTUD3hEd-rQL4FfV6WbQ" guid="-VHCrUwUFMiDFHcwq5Epk8g">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">Depending of the technology used there is different approach to this task. The
+ domain object model at the enterprise level will represent a complex data model a rule architect does not want to
+ expose as-is to the rule engine and the rule authoring environment. Navigating a complex graph of objects will bring
+ unnecessary complexity for the rule writer. So we recommend to always try to use a view of the enterprise domain object
+ model. For example in Financial Industry the business domain&nbsp;data model defined in MISMO (<a
+ href="http://www.mismo.org/"><font color="#005DA0">www.mismo.org</font></a>), brings a lot of value for an enterprise
+ willing to define a common ontology for their data models. But exposing the MISMO model as it is within a BRMS rule
+ authoring IDE will put too much complexity. As the Architect is responsible to design decision service reusable cross
+ application, it may make sense to consider view of this object model in the context of the service.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">For the application the view can be defined in two entities:</span>
+</p>
+<ul style="MARGIN-TOP: 0in" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in">
+ <span style="mso-bidi-language: HE">the Domain Object Model using java or xml schema as the underling
+ technology</span>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in">
+ <span style="mso-bidi-language: HE">or out of the box object view, like ILOG-Business Object Model element. The BOM
+ is mandatory to write rule on, but it&nbsp;can be created from an existing java model or XSD or created
+ top-down.</span>
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">If the model does not exist in the application, or at the enterprise level we still
+ recommend to develop the domain model, using an UML designer and code generation tools.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-font-weight: bold; mso-bidi-font-style: italic">It is also important to consider designing a java
+ model or XSD schema which is closed to the business concepts used by the rule but built as a view of the domain object
+ model (We called that the Rule Business Object Pattern or RBO): in the example of standard object model like MISMO or
+ ACORD, it makes sense to do not expose all the class definition, attributes and enumerated to avoid exposing a complex
+ rule language to the business user. This view will be instantiated by the application business logic in the context of
+ preparing the data for the rule services</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ When designing a Domain Object model one of the challenges is to determine what should be an entity and what should be
+ an attribute of the entity.<span style="mso-spacerun: yes">&nbsp;</span> This is why knowledge engineers like the
+ Enterprise Ontology as a start point for developing these concepts.<span style="mso-spacerun: yes">&nbsp;</span> The
+ Enterprise Ontology describes the major entities and concepts that apply to all enterprises and it provides a very good
+ starting point for the establishment of static object models and data models.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The difference between a class and an entity type is that classes have both data and behaviors whereas entity types
+ just have data. A normal entity depicts one concept.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Use multiple different UML class diagram to represent entities and their relations. Then enhance them to have a
+ complete class diagram from which you should be able to generate java code or XSD.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Capture Meta data about each entity: business name, business definition, super type or subtype, number of occurrences,
+ primary key, and alternate keys.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ <span style="mso-bidi-language: HE">It is possible to consider designing a Domain Model using Interface, and then apply
+ different type of implementation according to different execution pattern or platforms. For example we can design
+ a;</span>
+</p>
+<ul style="MARGIN-TOP: 0in" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030902" name="1030902"><span style="mso-bidi-language: HE">Staged deployment with different execution
+ classes</span></a>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030906" name="1030906"><span style="mso-bidi-language: HE">Dynamic model (XML based or dynamic classes)
+ versus static model</span></a>
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in">
+ <a id="1030907" name="1030907"><span style="mso-bidi-language: HE">Production/test models (active objects versus
+ mock objects)</span></a>
+ </li>
+</ul><a id="XE_object_model__build" name="XE_object_model__build"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-gb3qcxiSIOyJyQwNdA3I4w" name="prototype_rules,_2WcOsD3hEd-rQL4FfV6WbQ" guid="-gb3qcxiSIOyJyQwNdA3I4w">
+ <refinedDescription><a id="XE_rule__prototyping" name="XE_rule__prototyping"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The goal of the Rule Analysis activity is to prepare the rules for the
+ implementation. The rule analyst and the rule writer will analyze the rules discovered in a disjointed way into a
+ complete and coherent set. From the rule description, the glossary of business terms and may be from a first version of
+ the logical data model (LDM), the discovery team needs to transform the rules using the terms of the business to
+ elements that will be implemented by the rule writers. The rule analyst executes a set of iterative tasks to reach rule
+ implementation.</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-T-jJKt0EZ1lzBKB62eWRPw" name="decision_point_table,_24aTUT3hEd-rQL4FfV6WbQ" guid="-T-jJKt0EZ1lzBKB62eWRPw">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-a7ZnDzkb1A4WCd8v9E7D9A" name="rule_description_doc,_24aTUj3hEd-rQL4FfV6WbQ" guid="-a7ZnDzkb1A4WCd8v9E7D9A">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-OIYF_QKHkcHCdu5yP2EbPQ" name="ruleset,_24aTUz3hEd-rQL4FfV6WbQ" guid="-OIYF_QKHkcHCdu5yP2EbPQ">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-aPrVfOB6lpcDjCUvFFqQqA" name="execute_rule_discovery_roadmap,_8oxIYD3hEd-rQL4FfV6WbQ" guid="-aPrVfOB6lpcDjCUvFFqQqA">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-KRk9ZEALe8Zga5TYVVmNHw" name="business_process_map,_8oxIYz3hEd-rQL4FfV6WbQ" guid="-KRk9ZEALe8Zga5TYVVmNHw">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-VuBFXGbVPgtiGX9pA2G0_A" name="discovery_workshop_itinerary,_8oxIZD3hEd-rQL4FfV6WbQ" guid="-VuBFXGbVPgtiGX9pA2G0_A">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-49ndVIE5XgQJeRgW7VSm5A" name="business_terms_glossary,_8oxIZT3hEd-rQL4FfV6WbQ" guid="-49ndVIE5XgQJeRgW7VSm5A">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-cKCbpL8wmUvXw1Nz87Gw4w" name="conceptual_data_model,_8oxIZj3hEd-rQL4FfV6WbQ" guid="-cKCbpL8wmUvXw1Nz87Gw4w">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-zKTKc4iLlSGe2ryzPTiX5A" name="transform_rules,_-VGHUD3hEd-rQL4FfV6WbQ" guid="-zKTKc4iLlSGe2ryzPTiX5A">
+ <keyConsiderations>This activity will also be done during the implementation of the rule set, but it is started during the analysis, so we are
+detailing it in this context.</keyConsiderations>
+ <refinedDescription><p>
+ Rule Analyst has to study the rule discovered and try to transform it so that the implementation and the management of
+ the rule will be more easy. This includes transforming the rule in atomic element using a syntax without ambiguity,
+ remove redundant rules, conflicting rules, and finally try to redefine the scope of the rule by searching by
+ non-handled cases.&nbsp;
+</p>
+<p>
+ At this stage rule analyst can build some rule template which&nbsp;are built from rules that have the same set of
+ conditions with some little variations: adding new value in test condition, or new condition.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-I3nwk9ceAWBch8vvQbHHQg" name="fact_model,_-VGHUT3hEd-rQL4FfV6WbQ" guid="-I3nwk9ceAWBch8vvQbHHQg">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-FcKKMUfPt3EWzE4_ZOTsnA" name="logical_data_model,_-VGHUj3hEd-rQL4FfV6WbQ" guid="-FcKKMUfPt3EWzE4_ZOTsnA">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-OXURYcVJKojeI03hChFCsQ" name="build_test_scenario,__LyewD3hEd-rQL4FfV6WbQ" guid="-OXURYcVJKojeI03hChFCsQ">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Du2R_k7pqLRr3WzfdFVfWA" name="synchronize_data_model,__wS6AD3hEd-rQL4FfV6WbQ" guid="-Du2R_k7pqLRr3WzfdFVfWA">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst needs to continuously verify that business terms used in rule statements are part of the logical data
+ model (classes/ attributes) and physical data model (PDM). The model exposed to the rule needs to get data from data
+ sources. If a concept is not in the data it has to be quickly handled and managed by the application architect.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ The rule analyst should be in continuous communication with the data model developer, responsible to develop the XML
+ schema or java model (or .Net), and the physical mapping to database.<br />
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ Part of most of the business application are the list of code, enumerated date or domain values. It is important to
+ well design how those data are defined, accessed by the application, and the rule authoring environment.
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0in">
+ It can be helpful for some major business term to define a mapping to a class-attribute, and if the BRMS supports this
+ function it is recommended to detail the "verbalization" of the business term.
+</p><br class="MsoNormal" style="MARGIN: 3pt 0in" />
+<br />
+<div align="center">
+ <table class="MsoNormalTable" style="WIDTH: 351pt; BORDER-COLLAPSE: collapse; mso-padding-alt: 0in 0in 0in 0in"
+ cellspacing="0" cellpadding="0" width="468" border="0">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes">
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: gray 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Business Term</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">OO mapping</span></i>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: gray 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: gray 1pt solid; PADDING-LEFT: 5.4pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <i><span style="COLOR: #005da0">Verbalization</span></i>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LTV</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">LoanApplication.ltv</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <p class="msonormalcxspmiddle" style="MARGIN: auto 0in">
+ <span style="FONT-SIZE: 8pt">The loan to value ratio</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: silver 1pt solid; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: #ece9d8; WIDTH: 117pt; PADDING-TOP: 0in; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent"
+ valign="top" width="156">
+ <br class="msonormalcxspmiddle" style="MARGIN: auto 0in" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in left 3.0in" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-dYuef8izMNil6scNfR1Dsg" name="design_models_for_bre,_FOBuAD3iEd-rQL4FfV6WbQ" guid="-dYuef8izMNil6scNfR1Dsg">
+ <refinedDescription><p>
+ This is an important activity as we do not expose an enterprise model or a physical model as&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.
+</p>
+<p>
+ In any cases&nbsp;&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.&nbsp;
+</p>
+<p>
+ Developing such models is done by iterations.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-mVHqO6S50kezALZgP08etA" name="design_reference_data_integration,_G9L-gD3iEd-rQL4FfV6WbQ" guid="-mVHqO6S50kezALZgP08etA">
+ <refinedDescription><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.
+</p>
+<p>
+ The following diagram highlights a high level architecture&nbsp;architect can leverage to design&nbsp;his own solution.
+</p><br />
+<p>
+ <img height="499" alt="" src="resources/MDM.bmp" width="557" /><br />
+</p>
+<p>
+ The master data are centralized in a repository, and technology as Master Data Management product can be&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&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.
+</p>
+<p>
+ The same applies for the rule authoring environment: The&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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-iYlO6aUGnY1vebmXAhABKA" name="execute_rule_discovery_roadmap,_Wzz48D3iEd-rQL4FfV6WbQ" guid="-iYlO6aUGnY1vebmXAhABKA">
+ <refinedDescription><p>
+ Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
+ critical. They will change their minds as the project proceeds and that's perfectly fine.
+</p>
+<p>
+ The documentation of the rule may be done using different language. The natural language is initially used during
+ business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
+ ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
+ unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
+ terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
+</p>
+<p>
+ Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
+</p>
+<p>
+ A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
+ imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
+ semantically. We use the rule description template to log the rule.
+</p>
+<p>
+ The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
+ refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
+ Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
+ representations of concepts, definitions, instances, and rules&nbsp;in natural language.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-2gR5Uv4Dg17eMzBEYhAfEg" name="business_process_map,_Wzz49D3iEd-rQL4FfV6WbQ" guid="-2gR5Uv4Dg17eMzBEYhAfEg">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-av1HXdO41OcHPsHpp8yBzg" name="decision_point_table,_Wzz49T3iEd-rQL4FfV6WbQ" guid="-av1HXdO41OcHPsHpp8yBzg">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Kcs9trmpnkNOX4TveXHX1g" name="discovery_workshop_itinerary,_Wzz49j3iEd-rQL4FfV6WbQ" guid="-Kcs9trmpnkNOX4TveXHX1g">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Ht-F7YiTjgYImbeM8j5V_Q" name="business_terms_glossary,_Wzz49z3iEd-rQL4FfV6WbQ" guid="-Ht-F7YiTjgYImbeM8j5V_Q">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-1lp43bPxm97SeyOxlld5Ag" name="rule_description_doc,_Wzz4-D3iEd-rQL4FfV6WbQ" guid="-1lp43bPxm97SeyOxlld5Ag">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-vG3KWcPkjzvhkK3yNX7dhA" name="conceptual_data_model,_Wzz4-T3iEd-rQL4FfV6WbQ" guid="-vG3KWcPkjzvhkK3yNX7dhA">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-KITSfYrioY198dVTPssPvg" name="extract_rule_meaning,_ZdreMD3iEd-rQL4FfV6WbQ" guid="-KITSfYrioY198dVTPssPvg">
+ <refinedDescription><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">During the elicitation activity the raw description of the rule uses business terms as used in common
+ language used by the people. This presents what the business users think about the way things are done in the company.
+ They are linking words with statements with all the different semantic attached to them. The first activity focuses on
+ analyzing this rule description&nbsp;to extract&nbsp;the business entities and terms used in a formal non ambiguous
+ fashion.&nbsp;</font></span>
+</p>
+<p>
+ We are discussing about Business Term here, as reference to a business concept used in daily business operations.They
+ are often found in different departments or refer to the same business concept from a different perspective: they are
+ synonyms. A term may describe business concept which will be mapped to a Class, a characteristic of a business entity
+ which will be mapped to attribute of a class, and sometime a term may describe the way a business object behave, in
+ that last case it will be mapped within method of a final state machine.
+</p>
+<p>
+ The second concept presented in the analysis of rule is the Fact. Fact is a combination of terms that describes what
+ business people know about their business. It connects terms into sensible business relevant observations.<br
+ style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple" />
+ As stated by the SBVR specification meaning is built of concepts, questions and propositions. the concepts will build
+ our underlying data model used by the executable rules, and the proposition will structure the data model and can also
+ be mapped to rules.<br />
+</p>
+<p
+style="MARGIN-TOP: 4.32pt; MARGIN-BOTTOM: 0pt; VERTICAL-ALIGN: baseline; DIRECTION: ltr; unicode-bidi: embed; TEXT-ALIGN: left; language: en-US; mso-line-break-override: restrictions; punctuation-wrap: simple">
+ All these informations&nbsp;help to build a&nbsp;first logical data model used to build the underlying object
+ model&nbsp;used by the rules. We can use UML tool to design a class diagram, generates java code and import such code
+ in the rule IDE.<br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-eDpZ1oHsWw_cx-CCwn_Uww" name="fact_model,_ZdreMT3iEd-rQL4FfV6WbQ" guid="-eDpZ1oHsWw_cx-CCwn_Uww">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-qJLlsHiPcRs5jWYwmFql7A" name="logical_data_model,_ZdreMj3iEd-rQL4FfV6WbQ" guid="-qJLlsHiPcRs5jWYwmFql7A">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Toq2oNaIeiDkWe6DYjZU8A" name="transform_rules,_Z4M3AD3iEd-rQL4FfV6WbQ" guid="-Toq2oNaIeiDkWe6DYjZU8A">
+ <keyConsiderations>This activity will also be done during the implementation of the rule set, but it is started during the analysis, so we are
+detailing it in this context.</keyConsiderations>
+ <refinedDescription><p>
+ Rule Analyst has to study the rule discovered and try to transform it so that the implementation and the management of
+ the rule will be more easy. This includes transforming the rule in atomic element using a syntax without ambiguity,
+ remove redundant rules, conflicting rules, and finally try to redefine the scope of the rule by searching by
+ non-handled cases.&nbsp;
+</p>
+<p>
+ At this stage rule analyst can build some rule template which&nbsp;are built from rules that have the same set of
+ conditions with some little variations: adding new value in test condition, or new condition.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-zj5wWJIbnJrzTsbw9RkoQw" name="prototype_rules,_a8TYUD3iEd-rQL4FfV6WbQ" guid="-zj5wWJIbnJrzTsbw9RkoQw">
+ <refinedDescription><a id="XE_rule__prototyping" name="XE_rule__prototyping"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">The goal of the Rule Analysis activity is to prepare the rules for the
+ implementation. The rule analyst and the rule writer will analyze the rules discovered in a disjointed way into a
+ complete and coherent set. From the rule description, the glossary of business terms and may be from a first version of
+ the logical data model (LDM), the discovery team needs to transform the rules using the terms of the business to
+ elements that will be implemented by the rule writers. The rule analyst executes a set of iterative tasks to reach rule
+ implementation.</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-rTl3lsevKBV4DoNtHb85Rw" name="develop_unit_tests,_dWrwED3iEd-rQL4FfV6WbQ" guid="-rTl3lsevKBV4DoNtHb85Rw">
+ <refinedDescription><a id="XE_unit_tests__develop" name="XE_unit_tests__develop"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Rule Unit Testing is the process of testing a specific rule in the context of the rule set in which it is deployed.
+ Rule Unit Testing allows rule writers to:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Validate each rule in the context of its rule set
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Control the rule set quality
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Conduct some impact analysis when rules are in conflict
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Helps to have non-regression tests
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There is a major difference between testing a code, and a rule. A rule engine per
+ design may not put a rule in the agenda if the conditions are not matched. This means that when the rule writer write a
+ new rule, even if the data are sent to trigger the execution of this new rule it is possible that a rule fired before
+ the new one, with change the condition of the data so that this new rule will never be eligible. Developing a complete
+ set of unit test is an efficient way to see this problem, and to improve the rule set design. Some powerful BRMS
+ platform has rules consistency checking which helps to do some static analysis of those potential conflict by analyzing
+ the conditions and the actions of the rules. For sure real test cases will complete the picture.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<span
+style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Using
+a Test Driven Development approach rule writer can develop the test script preparing the data to trigger each rule,
+depending of the BRMS platform used, the script generation can be done automatically or not. What is important is develop
+reusable test case organized in test suite which include assertion statement to validate the expected results. This is
+efficient tool to put in place automatic non regression tests.</span></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-urGvDzu_Rw1bMkZ4dV3VBw" name="develop_rules,_dqy-4D3iEd-rQL4FfV6WbQ" guid="-urGvDzu_Rw1bMkZ4dV3VBw">
+ <refinedDescription><a id="XE_rule__develop" name="XE_rule__develop"></a>
+<p>
+ Programming using rule approach enforces to know how a rule engine is working. This is not a complex skill, rue author
+ needs to understand&nbsp; the concepts of asserting, retracting object into working memory and modifying them. It is
+ recommended to read what a <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_engine_A66B71B3.html"
+ guid="_QQcSoEXXEdy14e5PT9v3HQ">Rule engine</a>&nbsp;is to get those concepts.
+</p>
+<p>
+ Rule development can follow a test driven development approach: the developer can develop the test cases to trigger the
+ rule execution and then write the rules. Once done the new rules are extracted with the other rules in the rule set,
+ deployed to the unit test environment and the test executes. When designing with interface the unit test uses the
+ facade to access the rule engine for&nbsp;the execution.
+</p>
+<p>
+ When rules are complex and include a lot of conditions it may make sense to add condition by steps. It may be easy to
+ make error by using a wrong boolean operator. When the rue language support navigating into collection the testing may
+ include test around the presence and not presence of element in the collection.
+</p>
+<p>
+ It is always interesting once the rule is developed to perform rule analysis if the BRMS product has this capability.
+ The analysis helps to see if the current rule is in conflict with existing rules.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-OFG1oHaKBSeEnVNZHIOO6w" name="ruleset,_dqy-4T3iEd-rQL4FfV6WbQ" guid="-OFG1oHaKBSeEnVNZHIOO6w">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-mKbOrvuons9rChmJPeFspg" name="enhance_object_models,_eEuh0D3iEd-rQL4FfV6WbQ" guid="-mKbOrvuons9rChmJPeFspg">
+ <refinedDescription>Typically the developer adds helper methods in the data model to facilitate the rule writing. Develop utility classes. The
+data elements should not have persistence logic in it. For example in Java do not put JDBC code in the Customer object. Let
+try to stick to the Java bean specification for all the&nbsp;business objects, and leverage a service layer, with service
+facades objects to help gathering and process data.&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Nv1ViqClCaa8E7xNjuhsPA" name="execute_rule_set,_ecapED3iEd-rQL4FfV6WbQ" guid="-Nv1ViqClCaa8E7xNjuhsPA">
+ <refinedDescription><a id="XE_rule_set__execute" name="XE_rule_set__execute"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Fm2vVPiLcQvfC10FPmT-ag" name="log_issue,_fYUQoD3iEd-rQL4FfV6WbQ" guid="-Fm2vVPiLcQvfC10FPmT-ag">
+ <refinedDescription><ul>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Formally log any issues and decisions done during the rule
+ analysis and the rule authoring activities.</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The issue
+ log is used to manage feedbacks, and to improve the rule set quality.</span></span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-weight: bold">As a social process, people will
+ change their mind, it is a good practice to log decision on a timely manner.</span>
+ </div>
+ </li>
+</ul><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-QPBL2a8vAJa9K6CCLq9_hA" name="business_process_map,_e2UMRD3hEd-rQL4FfV6WbQ" guid="-QPBL2a8vAJa9K6CCLq9_hA">
+ <refinedDescription><a id="XE_business_process_map" name="XE_business_process_map"></a>
+<p>
+ A Business Process is a collection of interrelated tasks, which solve a particular business problem or process a
+ business event: a claim is received and needs to be processed within 15 days.
+</p>
+<p>
+ A business process can be decomposed into several sub-processes, which have their own attributes, but also contribute
+ to achieving the goal of the super-process.
+</p>
+<p>
+ The following process map is done using BPMN 1.2 (2..0 soon)&nbsp;and illustrates a loan underwriting process. The
+ entry point is a mail with the loan application received, then the process follow a set of activities to decide if the
+ loan is eligible and what kind of loan product we can offer to the borrower and at what financial condition. This
+ process as described here is not taking into account the actors of the process. Swim lanes can be added&nbsp;to group
+ tasks per actors.
+</p>
+<p>
+ <img height="600" alt="" src="resources/LoanApplicationBPM.bmp" width="357" /><br />
+ <br />
+ &nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-4N-ksyL2jIp6fJQXV1HcBQ" name="decision_point_table,_e2UMRT3hEd-rQL4FfV6WbQ" guid="-4N-ksyL2jIp6fJQXV1HcBQ">
+ <refinedDescription><a id="XE_decision_point_table" name="XE_decision_point_table"></a>
+<p>
+ <span
+ style="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">Groups
+ together all potential rules that determine one decision.</span> <a id="XE_decision_point" name="XE_decision_point">It
+ can be found in a use case description or in a Business Process Map task description.</a>&nbsp;Presented in table
+ format the project team can use the following template:
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="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"
+ cellspacing="0" cellpadding="0" width="662" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Decision Point<span style="mso-spacerun: yes">&nbsp;</span>
+ Name</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Description</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Source for Rule Discovery</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><font face="Times New Roman"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">Current</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; mso-bidi-language: HE">State</span></i></b> <b><i
+ style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE">of
+ Automation</span></i></b></font></font>
+ </p>
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">Rule Owner -</font></font></span></i></b>
+ </p>
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span style="COLOR: #005da0; mso-bidi-language: HE"><font
+ size="3"><font face="Times New Roman">SME</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1; mso-yfti-lastrow: yes">
+ <td
+ style="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"
+ valign="top" width="95">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="198">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="142">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="126">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="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"
+ valign="top" width="100">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div><br />
+<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 "claim data review", or "loan eligibility"...
+</p>
+<p>
+ The source for rule discovery describes the main sources of rule harvesting like human, code, database, book, policies,
+ legal&nbsp;manual...
+</p>
+<p>
+ The current state of automation is optional and just list&nbsp;if for this given decision point we can have tools which
+ can migrate the business rules&nbsp;from one format to another.&nbsp;
+</p>
+<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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-OC5WAbX5mDyrbpG0WkMsTQ" name="discovery_workshop_itinerary,_e2UMRj3hEd-rQL4FfV6WbQ" guid="-OC5WAbX5mDyrbpG0WkMsTQ">
+ <refinedDescription><a id="XE_rule_discovery__workshop_itinerary" name="XE_rule_discovery__workshop_itinerary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Goal:</b> <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">These
+ series of Rule discovery workshops</span> are very important for the &lt;&gt; application, it will help:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To separate a rule as a manageable artifact
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To trace rules from the origin to deployment
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To link rules to business context
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To develop the rule description using business term and natural business
+ language.
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To involve business user in the future ownership of the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare for for the logical data model
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the for the rule set implementation
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Duration</b>: 2 hours per session
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Facilities</b>: white board, pencil, paper; post it, UML tool like Enterprise
+ Architect, ISIS rule templates
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Agenda</b>:
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To formalize the rules using templates and business term and language
+ understood by the business user
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To prepare the tests for the rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> To define the object model for the rule
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Define the different types of rules, rule writing standards, structure rules
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt 47.35pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1; tab-stops: list 47.35pt">
+ <span style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> Address the rule management requirements around rule ownership, and rule
+ change requirements
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Output:</b> rule set definition, logical data model
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Invitees</b>:
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <strong><em><font face="Times New Roman" color="#005DA0"
+ size="3">Business</font></em></strong>&nbsp;
+ </p>
+ </td>
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font face="Times New Roman">IT</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Business Analyst</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule analyst</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">SME</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Rule writer</span>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <p class="MsoNormalCxSpMiddle">
+ <span style="FONT-SIZE: 8pt; mso-bidi-font-size: 12.0pt">Lead developer</span>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <p>
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ &nbsp;
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 241.55pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: auto auto auto 36pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 241.55pt; 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"
+ valign="top" width="322">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <b style="mso-bidi-font-weight: normal">Pre-requisites</b>: Decision point table, rule discovery roadmap, conceptual
+ data model
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-lOo0xOaMfy6RMxOmeK1ntQ" name="business_terms_glossary,_e2UMRz3hEd-rQL4FfV6WbQ" guid="-lOo0xOaMfy6RMxOmeK1ntQ">
+ <refinedDescription><a id="XE_business_terms_glossary" name="XE_business_terms_glossary"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">One of the positive feedbacks&nbsp;received from
+ the business and IT team&nbsp;is the&nbsp;business term glossary document. Some organization has already defined this
+ kind of glossary, and even it is possible to use some industry standard. But standard are always adapted by the
+ organization so it is important to work on such&nbsp;glossary during the early phase of the project.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">
+ <span style="mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt">The following template can be used for logging
+ the business vocabulary. The acronyms are not mandatory. The ownership column describes when a term is under the
+ responsibility of&nbsp;a team.</span>
+</p>
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; 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; mso-table-layout-alt: fixed"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="HEIGHT: 15.75pt; mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt"
+ valign="top" width="104">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Term</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 2cm; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE"><font
+ size="3">Acronym</font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 318.9pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="425">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Definition</span></i></b></font>
+ </p>
+ </td>
+ <td
+ style="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: 56.75pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; HEIGHT: 15.75pt; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="76">
+ <p class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center; mso-add-space: auto; mso-yfti-cnfc: 1" align="center">
+ <font size="3"><b><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-language: HE">Owner</span></i></b></font>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 1">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 2">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes">
+ <td
+ style="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: 77.95pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="104">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 2cm; 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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 318.9pt; 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"
+ valign="top" width="425">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 56.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"
+ valign="top" width="76">
+ <br class="MsoNormalCxSpMiddle" style="MARGIN: 0cm 0cm 0pt; mso-add-space: auto" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="--uzQTSOVvRvz9DVCsqCzcw" name="rule_description_doc,_e2UMSD3hEd-rQL4FfV6WbQ" guid="--uzQTSOVvRvz9DVCsqCzcw">
+ <refinedDescription><a id="XE_rule_description__document" name="XE_rule_description__document"></a>
+<p>
+ The rule description document is used during the discovery phase, and during the first iterations for building a rule
+ set. It is not mandatory to complete it up front with all the rules in it. The complement is done during the Rule
+ Authoring phase.
+</p>
+<p>
+ It is also interesting to leverage SBVR to document the rule.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-qKEGOsD8R1M8vTodG0VI9Q" name="conceptual_data_model,_e2UMST3hEd-rQL4FfV6WbQ" guid="-qKEGOsD8R1M8vTodG0VI9Q">
+ <refinedDescription><p>
+ A conceptual data model describes the things important for an organization as entity classes and characteristics of the
+ things as attributes, and using&nbsp;associations between things. By 'thing'&nbsp;we mean anything perceivable or
+ conceivable and used in a day to day conversation.
+</p>
+<p>
+ Conceptual data model is used to explore domain concepts&nbsp;as a communication vehicle&nbsp;between the analysts and
+ the business team members.
+</p>
+<p>
+ With&nbsp;an&nbsp;Agile approach CDMs are used to explore the high-level static business structures and concepts, and
+ are described during the initial requirements iterations. In our approach conceptual data model are the first version
+ of the logical data model. So we use different level of&nbsp;a class diagram to represent the CDM.&nbsp;&nbsp;The rule
+ elicitation phase is most of the time leveraging the diagrams of&nbsp;the CDMs, but once we progress into the
+ iterations the CDMs are replaced by the LDMs.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-2-4sXJWybjPUMo76gsxUrA" name="fact_model,_geBw8T3hEd-rQL4FfV6WbQ" guid="-2-4sXJWybjPUMo76gsxUrA">
+ <refinedDescription><p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">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.</span> We prefer using UML class diagram showing just the entities, the associations and may be some
+ characteristic as attributes of class.
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A Fact Model should always include elementary
+ (atomic) fact type:</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Noun:&nbsp; Customer, Order, Product</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt">
+ <span style="FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt">•</span><span
+ style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Verb:&nbsp; places, briefs</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-2tm2IktmluDUboGJIcLDSQ" name="logical_data_model,_geBw8j3hEd-rQL4FfV6WbQ" guid="-2tm2IktmluDUboGJIcLDSQ">
+ <refinedDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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&nbsp;as a communication vehicle for the business
+ analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">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.&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.</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
+ a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
+ models, it is possible to use other diagrams.</span>
+</p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
+ relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
+ entire enterprise.&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.</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ &nbsp;
+</p>
+<p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
+ 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.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-SPRTmKcOY8uhXSYUElJD_A" name="integrate_bre,_iSlpYD3iEd-rQL4FfV6WbQ" guid="-SPRTmKcOY8uhXSYUElJD_A">
+ <refinedDescription><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.
+</p>
+<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:
+</p>
+<ul>
+ <li>
+ the service definition: one or more operations linked to the same data semantic
+ </li>
+ <li>
+ the operation call approach: synchronous/ asynchronous, stateless/stateful, header based or carrying payload, use
+ of faults or not
+ </li>
+ <li>
+ the exception reporting
+ </li>
+</ul>
+<p>
+ The service implementation using a rule engine has to look at:
+</p>
+<ul>
+ <li>
+ the transaction propagation
+ </li>
+ <li>
+ the reference data caching
+ </li>
+ <li>
+ the parsing of input message: the claim data
+ </li>
+ <li>
+ the loading of the related data: the policy related to the claim, or the insured person profile
+ </li>
+ <li>
+ the preparation of the output message: the result and may be some other technical data
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-xGdRIdwQIVt3-32feera7A" name="develop_unit_tests,_lXSJcD3iEd-rQL4FfV6WbQ" guid="-xGdRIdwQIVt3-32feera7A">
+ <refinedDescription><a id="XE_unit_tests__develop" name="XE_unit_tests__develop"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Rule Unit Testing is the process of testing a specific rule in the context of the rule set in which it is deployed.
+ Rule Unit Testing allows rule writers to:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Validate each rule in the context of its rule set
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Control the rule set quality
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Conduct some impact analysis when rules are in conflict
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Helps to have non-regression tests
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There is a major difference between testing a code, and a rule. A rule engine per
+ design may not put a rule in the agenda if the conditions are not matched. This means that when the rule writer write a
+ new rule, even if the data are sent to trigger the execution of this new rule it is possible that a rule fired before
+ the new one, with change the condition of the data so that this new rule will never be eligible. Developing a complete
+ set of unit test is an efficient way to see this problem, and to improve the rule set design. Some powerful BRMS
+ platform has rules consistency checking which helps to do some static analysis of those potential conflict by analyzing
+ the conditions and the actions of the rules. For sure real test cases will complete the picture.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<span
+style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Using
+a Test Driven Development approach rule writer can develop the test script preparing the data to trigger each rule,
+depending of the BRMS platform used, the script generation can be done automatically or not. What is important is develop
+reusable test case organized in test suite which include assertion statement to validate the expected results. This is
+efficient tool to put in place automatic non regression tests.</span></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-K9no0Y8fd2qLSwFy6snYnw" name="develop_rules,_lXSJcT3iEd-rQL4FfV6WbQ" guid="-K9no0Y8fd2qLSwFy6snYnw">
+ <refinedDescription><a id="XE_rule__develop" name="XE_rule__develop"></a>
+<p>
+ Programming using rule approach enforces to know how a rule engine is working. This is not a complex skill, rue author
+ needs to understand&nbsp; the concepts of asserting, retracting object into working memory and modifying them. It is
+ recommended to read what a <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_engine_A66B71B3.html"
+ guid="_QQcSoEXXEdy14e5PT9v3HQ">Rule engine</a>&nbsp;is to get those concepts.
+</p>
+<p>
+ Rule development can follow a test driven development approach: the developer can develop the test cases to trigger the
+ rule execution and then write the rules. Once done the new rules are extracted with the other rules in the rule set,
+ deployed to the unit test environment and the test executes. When designing with interface the unit test uses the
+ facade to access the rule engine for&nbsp;the execution.
+</p>
+<p>
+ When rules are complex and include a lot of conditions it may make sense to add condition by steps. It may be easy to
+ make error by using a wrong boolean operator. When the rue language support navigating into collection the testing may
+ include test around the presence and not presence of element in the collection.
+</p>
+<p>
+ It is always interesting once the rule is developed to perform rule analysis if the BRMS product has this capability.
+ The analysis helps to see if the current rule is in conflict with existing rules.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-dbVJh3-7KeKo_CdIOQGj5Q" name="enhance_object_models,_lXSJcj3iEd-rQL4FfV6WbQ" guid="-dbVJh3-7KeKo_CdIOQGj5Q">
+ <refinedDescription>Typically the developer adds helper methods in the data model to facilitate the rule writing. Develop utility classes. The
+data elements should not have persistence logic in it. For example in Java do not put JDBC code in the Customer object. Let
+try to stick to the Java bean specification for all the&nbsp;business objects, and leverage a service layer, with service
+facades objects to help gathering and process data.&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-DSGeVrVTJjT0MRy0TvuDSw" name="execute_rule_set,_lXSJcz3iEd-rQL4FfV6WbQ" guid="-DSGeVrVTJjT0MRy0TvuDSw">
+ <refinedDescription><a id="XE_rule_set__execute" name="XE_rule_set__execute"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-QZu83uvVme58aHkxlEaTmQ" name="log_issue,_lXSJdD3iEd-rQL4FfV6WbQ" guid="-QZu83uvVme58aHkxlEaTmQ">
+ <refinedDescription><ul>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Formally log any issues and decisions done during the rule
+ analysis and the rule authoring activities.</span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The issue
+ log is used to manage feedbacks, and to improve the rule set quality.</span></span>
+ </div>
+ </li>
+ <li>
+ <div class="MsoNormal"
+ style="MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .25in">
+ <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-weight: bold">As a social process, people will
+ change their mind, it is a good practice to log decision on a timely manner.</span>
+ </div>
+ </li>
+</ul><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ebM0psxnCwWPQYF7YFMdWA" name="ruleset,_lXSJdz3iEd-rQL4FfV6WbQ" guid="-ebM0psxnCwWPQYF7YFMdWA">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-fVJV90U2K24PRA6BOiyuTg" name="execute_ruleset_functional_test,_qEITET3iEd-rQL4FfV6WbQ" guid="-fVJV90U2K24PRA6BOiyuTg">
+ <refinedDescription><a id="XE_rule_set__execute_functional_tests" name="XE_rule_set__execute_functional_tests"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-drsUrP20wfWfu6engv0bvA" name="get_rule_set_reports,_qEITEj3iEd-rQL4FfV6WbQ" guid="-drsUrP20wfWfu6engv0bvA">
+ <refinedDescription><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></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-sjX0ZCEDiQdwyXRi2_xwPg" name="get_sme_feedback,_qEITEz3iEd-rQL4FfV6WbQ" guid="-sjX0ZCEDiQdwyXRi2_xwPg">
+ <refinedDescription><a id="XE_SME__get_feedback" name="XE_SME__get_feedback"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-spzcqoK0HWQUSwAvjzoRHQ" name="test_analysis,_qEITFD3iEd-rQL4FfV6WbQ" guid="-spzcqoK0HWQUSwAvjzoRHQ">
+ <refinedDescription><a id="XE_test_analysis" name="XE_test_analysis"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-DepNFUaxj7vgjyQjYJjMOQ" name="rule_report,_qFLb8D3iEd-rQL4FfV6WbQ" guid="-DepNFUaxj7vgjyQjYJjMOQ">
+ <refinedDescription><a id="XE_rule_report" name="XE_rule_report"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-R2JrKH_RtyJIwW3nJszhMg" name="sme_recommendations,_qFLb8T3iEd-rQL4FfV6WbQ" guid="-R2JrKH_RtyJIwW3nJszhMg">
+ <refinedDescription><a id="XE_SME__recommendations" name="XE_SME__recommendations"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-1E7v5wKf27pEV1Pu3M1c1g" name="rsm_report,_qFLb8j3iEd-rQL4FfV6WbQ" guid="-1E7v5wKf27pEV1Pu3M1c1g">
+ <refinedDescription><a id="XE_RSM_report" name="XE_RSM_report"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-barsvSUZoK-B2IRctfkyug" name="define_rule_life_cycle,_59SkIz3iEd-rQL4FfV6WbQ" guid="-barsvSUZoK-B2IRctfkyug">
+ <refinedDescription><a id="XE_life_cycle__define" name="XE_life_cycle__define"></a>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A rule architect has to develop with the business
+ users what will be the <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_life_cycle_B982650C.html"
+ guid="_s5iCsFH7Edy72tV0zV7--Q">rule life cycle</a>. There are a lot of different possibilities for defining this rule
+ life cycle. For the implementation point of view we need to define a</span> <span lang="EN"
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial; mso-ansi-language: EN">"Status" meta property attached
+ to a rule element.</span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">The following states
+ have been identified as a simple but still efficient life cycle:</span>
+</p><br />
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">New</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule is created, and can be modified by its
+ owner</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Defined</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule has been defined and is currently in unit
+ test</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Rejected</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule has been tested un-successfully</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Validated</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule has been tested successfully and can be
+ deployed</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Promoted</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule has been part of a rule set deployed on
+ production platform</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: l0 level1 lfo1; tab-stops: list 27.0pt">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·<span
+ style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>
+ <b style="mso-bidi-font-weight: normal"><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Retired</span></b><span
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">: the rule was deployed or validated on a production
+ platform but no more active.</span>
+</p><br />
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ In the state diagram below the following abbreviations are used:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Rule Writer or Rule Author is the end user of the BRMS application
+ </li>
+ <li class="MsoNormal" style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Rule Admin is an administrator of the rule set.
+ </li>
+ <li class="MsoNormal"
+ style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt; mso-pagination: none; mso-layout-grid-align: none">
+ Rule Tester can be an automatic process or a human.
+ </li>
+</ul>
+<p class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt; mso-pagination: none; mso-layout-grid-align: none">
+ <img height="382" alt="" src="resources/rule_life_cycle.gif" width="409" />
+</p><br class="MsoNormal"
+style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt; mso-pagination: none; mso-layout-grid-align: none" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-zgwCbo2xDbSoVQ6xzPR8Jw" name="define_ruleset_life_cycle,_59SkIj3iEd-rQL4FfV6WbQ" guid="-zgwCbo2xDbSoVQ6xzPR8Jw">
+ <refinedDescription><a id="XE_rule_set__define_life_cycle" name="XE_rule_set__define_life_cycle"></a>
+<p>
+ As it was done for the rule life cycle, it may be needed to complete the rule governance by defining a rule set life
+ cycle.&nbsp;
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-xR_MU1qVIqmI3vD8JwvX1A" name="brms_organization_chart,_59SkIT3iEd-rQL4FfV6WbQ" guid="-xR_MU1qVIqmI3vD8JwvX1A">
+ <refinedDescription><a id="XE_BRMS__organization_chart" name="XE_BRMS__organization_chart"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-0F1JpRACvQlhzf8uibcIKA" name="rule_governance_actors,_59SkMT3iEd-rQL4FfV6WbQ" guid="-0F1JpRACvQlhzf8uibcIKA">
+ <refinedDescription><a id="XE_rule_governance__actors" name="XE_rule_governance__actors"></a>
+<p>
+ The easiest way is to lists the different actors involved in the governance processes within a table format.
+</p><br />
+<div align="center">
+ <table class="ISISTable"
+ style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-table-layout-alt: fixed; 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"
+ cellspacing="0" cellpadding="0" border="1">
+ <tbody>
+ <tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes">
+ <td
+ style="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: 67.5pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid"
+ valign="top" width="90">
+ <p class="MsoNormalCxSpFirst" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font
+ face="Times New Roman">Role</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 62.2pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="83">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font
+ face="Times New Roman">Unit</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 230.3pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="307">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font
+ face="Times New Roman">Role-Responsibilities</font></font></span></i></b>
+ </p>
+ </td>
+ <td
+ style="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: 153pt; PADDING-TOP: 0cm; BORDER-BOTTOM: gray 1pt solid; mso-border-left-alt: solid gray 1.0pt"
+ valign="top" width="204">
+ <p class="MsoNormalCxSpMiddle" style="TEXT-ALIGN: center; mso-yfti-cnfc: 1" align="center">
+ <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal"><span
+ style="COLOR: #005da0"><font size="3"><font
+ face="Times New Roman">Skill</font></font></span></i></b>
+ </p>
+ </td>
+ </tr>
+ <tr style="mso-yfti-irow: 0; mso-yfti-lastrow: yes">
+ <td
+ style="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: 67.5pt; PADDING-TOP: 0cm; BORDER-BOTTOM: silver 1pt solid; BACKGROUND-COLOR: transparent; mso-border-top-alt: solid silver 1.0pt"
+ valign="top" width="90">
+ <br class="MsoNormalCxSpMiddle" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 62.2pt; 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"
+ valign="top" width="83">
+ <p class="MsoNormalCxSpMiddle">
+ <font face="Times New Roman"><span style="FONT-SIZE: 8pt">Business unit</span></font>
+ </p>
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 230.3pt; 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"
+ valign="top" width="307">
+ <br class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt; mso-add-space: auto; mso-list: l0 level1 lfo1; tab-stops: list 18.0pt" />
+ <br />
+ </td>
+ <td
+ style="BORDER-RIGHT: silver 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: #ece9d8; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: #ece9d8; WIDTH: 153pt; 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"
+ valign="top" width="204">
+ <br class="MsoNormalCxSpMiddle"
+ style="MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt; mso-add-space: auto; mso-list: l0 level1 lfo1; tab-stops: list 18.0pt" />
+ <br />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Hc7JvaQ0-snFgiJmpWD2OA" name="rule_life_cycle,_59SkJz3iEd-rQL4FfV6WbQ" guid="-Hc7JvaQ0-snFgiJmpWD2OA">
+ <refinedDescription><a id="XE_rule__life_cycle" name="XE_rule__life_cycle"></a>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; tab-stops: list 27.0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">In the state diagram below the following
+ abbreviations are used:</span>
+</p><br class="MsoNormal" style="MARGIN: 0in 0in 0pt; tab-stops: list 27.0pt" />
+<br />
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Rule
+ Writer or Rule Author is the end user of the BRMS application</span>
+</p>
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Rule
+ Admin is an administrator of the rule set.</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Rule
+ Tester can be an automatic process or a human.</span>
+</p><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none" />
+<br />
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><img alt=""
+ src="resources/rule_life_cycle.gif" /></span>
+</p><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none" />
+<br />
+<p class="MsoNormal" style="MARGIN: 0in 0in 0pt">
+ <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><span lang="EN"
+ style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial; mso-ansi-language: EN">Some complementary
+ guidelines:</span></span>
+</p><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<br />
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 27pt; TEXT-INDENT: -27pt; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">When a
+ rule is created its status is new</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 27pt; TEXT-INDENT: -27pt; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A rule
+ once promoted could not be deleted.</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 27pt; TEXT-INDENT: -27pt; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A rule
+ can be set active or inactive at any state, by using the inactive property</span>
+</p>
+<p class="MsoNormal"
+style="MARGIN: 0in 0in 0pt 27pt; TEXT-INDENT: -27pt; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1">
+ <span
+ style="FONT-FAMILY: Symbol; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span
+ style="mso-list: Ignore">·</span></span> <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">From
+ this life cycle it is important to note that once a rule is promoted the user could not update it. He needs to create a
+ new rule by copy and paste and restart the life cycle up to Validated. Once the rule is ready for deployment a rule
+ administrator will retired the first rule and promote the new one. This is important to follow this process to maintain
+ the integrity of the rule set.</span>
+</p><br class="MsoNormal" style="MARGIN: 0in 0in 0pt" />
+<p class="ISISGuidance" style="MARGIN: 0in 0in 0pt">
+ <span style="COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: Arial">There is a common requirement that may need to
+ be supported to enhance the rule life cycle: "During its life cycle a rule can be deployed only to a specific Test
+ Decision Service, before going to production".</span>
+</p><br class="MsoNormal"
+style="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; tab-stops: list 27.0pt; mso-list: l0 level1 lfo1; mso-pagination: none; mso-layout-grid-align: none" />
+<br /></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-FS7huAe4PXfu1q_QQJGtIA" name="ruleset,_59SkLT3iEd-rQL4FfV6WbQ" guid="-FS7huAe4PXfu1q_QQJGtIA">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-6eacylaMdMYfqb7p28Owqw" name="rule_repository_in_db,_59SkKD3iEd-rQL4FfV6WbQ" guid="-6eacylaMdMYfqb7p28Owqw">
+ <refinedDescription><a id="XE_rule_repository__in_db" name="XE_rule_repository__in_db"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-EQNfnV9bxYjmfZMCotuUHA" name="develop_unit_tests,_Qz1eED3jEd-rQL4FfV6WbQ" guid="-EQNfnV9bxYjmfZMCotuUHA">
+ <refinedDescription><a id="XE_unit_tests__develop" name="XE_unit_tests__develop"></a>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ Rule Unit Testing is the process of testing a specific rule in the context of the rule set in which it is deployed.
+ Rule Unit Testing allows rule writers to:
+</p>
+<ul style="MARGIN-TOP: 0cm" type="disc">
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Validate each rule in the context of its rule set
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Control the rule set quality
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Conduct some impact analysis when rules are in conflict
+ </li>
+ <li class="MsoNormal" style="MARGIN: 3pt 0cm; mso-list: l0 level1 lfo1; tab-stops: list 36.0pt">
+ Helps to have non-regression tests
+ </li>
+</ul>
+<p class="MsoNormal" style="MARGIN: 3pt 0cm">
+ <span style="mso-bidi-language: HE">There is a major difference between testing a code, and a rule. A rule engine per
+ design may not put a rule in the agenda if the conditions are not matched. This means that when the rule writer write a
+ new rule, even if the data are sent to trigger the execution of this new rule it is possible that a rule fired before
+ the new one, with change the condition of the data so that this new rule will never be eligible. Developing a complete
+ set of unit test is an efficient way to see this problem, and to improve the rule set design. Some powerful BRMS
+ platform has rules consistency checking which helps to do some static analysis of those potential conflict by analyzing
+ the conditions and the actions of the rules. For sure real test cases will complete the picture.</span>
+</p><br class="MsoNormal" style="MARGIN: 3pt 0cm" />
+<br />
+<span
+style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-language: HE; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US">Using
+a Test Driven Development approach rule writer can develop the test script preparing the data to trigger each rule,
+depending of the BRMS platform used, the script generation can be done automatically or not. What is important is develop
+reusable test case organized in test suite which include assertion statement to validate the expected results. This is
+efficient tool to put in place automatic non regression tests.</span></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-eivV0I3d5NflWdDxFN11Iw" name="develop_rules,_Qz1eET3jEd-rQL4FfV6WbQ" guid="-eivV0I3d5NflWdDxFN11Iw">
+ <refinedDescription><a id="XE_rule__develop" name="XE_rule__develop"></a>
+<p>
+ Programming using rule approach enforces to know how a rule engine is working. This is not a complex skill, rue author
+ needs to understand&nbsp; the concepts of asserting, retracting object into working memory and modifying them. It is
+ recommended to read what a <a class="elementLink"
+ href="./../../practice.tech.abrd.base/guidances/termdefinitions/rule_engine_A66B71B3.html"
+ guid="_QQcSoEXXEdy14e5PT9v3HQ">Rule engine</a>&nbsp;is to get those concepts.
+</p>
+<p>
+ Rule development can follow a test driven development approach: the developer can develop the test cases to trigger the
+ rule execution and then write the rules. Once done the new rules are extracted with the other rules in the rule set,
+ deployed to the unit test environment and the test executes. When designing with interface the unit test uses the
+ facade to access the rule engine for&nbsp;the execution.
+</p>
+<p>
+ When rules are complex and include a lot of conditions it may make sense to add condition by steps. It may be easy to
+ make error by using a wrong boolean operator. When the rue language support navigating into collection the testing may
+ include test around the presence and not presence of element in the collection.
+</p>
+<p>
+ It is always interesting once the rule is developed to perform rule analysis if the BRMS product has this capability.
+ The analysis helps to see if the current rule is in conflict with existing rules.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-JW1SrN4HN2vfMWdXhwx0ww" name="enhance_object_models,_Qz1eEj3jEd-rQL4FfV6WbQ" guid="-JW1SrN4HN2vfMWdXhwx0ww">
+ <refinedDescription>Typically the developer adds helper methods in the data model to facilitate the rule writing. Develop utility classes. The
+data elements should not have persistence logic in it. For example in Java do not put JDBC code in the Customer object. Let
+try to stick to the Java bean specification for all the&nbsp;business objects, and leverage a service layer, with service
+facades objects to help gathering and process data.&nbsp;</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-sq25iSf421_q4x2ZbYXkKQ" name="execute_rule_set,_Qz1eEz3jEd-rQL4FfV6WbQ" guid="-sq25iSf421_q4x2ZbYXkKQ">
+ <refinedDescription><a id="XE_rule_set__execute" name="XE_rule_set__execute"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-RjvG1D-ZAteachI2o5oCQw" name="ruleset,_Qz1eFj3jEd-rQL4FfV6WbQ" guid="-RjvG1D-ZAteachI2o5oCQw">
+ <refinedDescription><a id="XE_rule_set__work_product" name="XE_rule_set__work_product"></a>
+<p>
+ For more detail see <a class="elementLink" href="./../../abrd/guidances/termdefinitions/rule_set_4D4C8DB1.html"
+ guid="_DdvcwBCQEdyJtJ3PbfdVDw">Rule Set</a>&nbsp;and <a class="elementLink"
+ href="./../../abrd/guidances/termdefinitions/rule_engine_A66B71B3.html" guid="_QQcSoEXXEdy14e5PT9v3HQ">rule engine</a>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-gXDJs-AADHuo-Up6bT4Vow" name="deploy_rules,_SI7BsD3jEd-rQL4FfV6WbQ" guid="-gXDJs-AADHuo-Up6bT4Vow">
+ <refinedDescription><a id="XE_rule__deploy" name="XE_rule__deploy"></a></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
</xmi:XMI>
diff --git a/epf_prac_151/process.abrd.base/deliveryprocesses/openUp_abrd/model.xmi b/epf_prac_151/process.abrd.base/deliveryprocesses/openUp_abrd/model.xmi
index 5868fa7..5e2158d 100644
--- a/epf_prac_151/process.abrd.base/deliveryprocesses/openUp_abrd/model.xmi
+++ b/epf_prac_151/process.abrd.base/deliveryprocesses/openUp_abrd/model.xmi
@@ -3,15 +3,121 @@
<org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="__eme8LekEd-D7YZN9NgldQ" guid="__eme8LekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__eme8bekEd-D7YZN9NgldQ" id="-qwh4CuVnjaLX6IHR9ARntQ" uri="content.xmi"/>
<resourceDescriptors xmi:id="__ewP8LekEd-D7YZN9NgldQ" id="-zmO9iNLv1qeo2tvrSUooQw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Sz2isVmTEeCcpdiAcH0w-w" id="-prjAV1fmvfmd2Zg_NkMweQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Sz2islmTEeCcpdiAcH0w-w" id="-IuPwmyFj6cPxKh7va58BBg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Sz2is1mTEeCcpdiAcH0w-w" id="-dZH2mwKP_HVhAcRXF625-g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Sz2itFmTEeCcpdiAcH0w-w" id="-k9x6Q4vmGjn5pz_YPmFOSQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Sz2itVmTEeCcpdiAcH0w-w" id="-pFOBrLzvMdSKhPgshdTUmg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0ATsFmTEeCcpdiAcH0w-w" id="-klIiZfe42Fb3xkxnrn7s8g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0ATsVmTEeCcpdiAcH0w-w" id="-dvJXCSep8C4BgXVKBdqzWw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0ATslmTEeCcpdiAcH0w-w" id="-l3HNcE1exbebFi_vHnSlng" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0ATs1mTEeCcpdiAcH0w-w" id="-iJdVDnhIv3mdPxGvKtIQTQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0ATtFmTEeCcpdiAcH0w-w" id="-VciLFpBjLKj1Gg5oGyKV2w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0KEsFmTEeCcpdiAcH0w-w" id="-97voq1CnhjuPRUVjP8vvHQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0KEsVmTEeCcpdiAcH0w-w" id="-qe6GN8mPPfm5owdB98DzBw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0KEslmTEeCcpdiAcH0w-w" id="-C1-wtv51AzfuS54DlC_z7w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0KEs1mTEeCcpdiAcH0w-w" id="--peqPcPE-E86pPKWX9cwLg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0KEtFmTEeCcpdiAcH0w-w" id="-l8K8ZTTtZ7_u4YFVAyYZWg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0c_oFmTEeCcpdiAcH0w-w" id="-rpwuTxNm209KUwlswmH8HQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0c_oVmTEeCcpdiAcH0w-w" id="-9vl1UQ_4DObTvAkwNa9kEQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0c_olmTEeCcpdiAcH0w-w" id="-E243hD2whycztF2dFXEwkA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0c_o1mTEeCcpdiAcH0w-w" id="-99g5YVnMANjm-DUauKZXWg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0mJkFmTEeCcpdiAcH0w-w" id="-tIAbTEFRB78mlG35hRD9zQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0mJkVmTEeCcpdiAcH0w-w" id="-Hh7gh2SK9tvxwdrSoTk3tg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0v6kFmTEeCcpdiAcH0w-w" id="-Bs-Oyk_niHDCHWUI80V5qw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0v6kVmTEeCcpdiAcH0w-w" id="-QinOsfSXNHdry4crJjAWWw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S0v6klmTEeCcpdiAcH0w-w" id="-_773MJ887tp2r2fn24vH9Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S05rkFmTEeCcpdiAcH0w-w" id="-OgvhvvxDv6DTP9JkppFgpw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S05rklmTEeCcpdiAcH0w-w" id="-VVUx-pgzq9QqwpY7eyCQug" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1C1glmTEeCcpdiAcH0w-w" id="-XQBNNrNBrtaxuEo4q-lUBA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1MmgFmTEeCcpdiAcH0w-w" id="-tAu2iMCzVIgP4_Al4Lw8ww" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1MmgVmTEeCcpdiAcH0w-w" id="-VHCrUwUFMiDFHcwq5Epk8g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1WXgFmTEeCcpdiAcH0w-w" id="-gb3qcxiSIOyJyQwNdA3I4w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1WXglmTEeCcpdiAcH0w-w" id="-T-jJKt0EZ1lzBKB62eWRPw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1fhcFmTEeCcpdiAcH0w-w" id="-a7ZnDzkb1A4WCd8v9E7D9A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1fhcVmTEeCcpdiAcH0w-w" id="-OIYF_QKHkcHCdu5yP2EbPQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1pScFmTEeCcpdiAcH0w-w" id="-aPrVfOB6lpcDjCUvFFqQqA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1ycYVmTEeCcpdiAcH0w-w" id="-KRk9ZEALe8Zga5TYVVmNHw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S1ycYlmTEeCcpdiAcH0w-w" id="-VuBFXGbVPgtiGX9pA2G0_A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S18NYFmTEeCcpdiAcH0w-w" id="-49ndVIE5XgQJeRgW7VSm5A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S18NYVmTEeCcpdiAcH0w-w" id="-cKCbpL8wmUvXw1Nz87Gw4w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S2F-YFmTEeCcpdiAcH0w-w" id="-zKTKc4iLlSGe2ryzPTiX5A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S2F-YVmTEeCcpdiAcH0w-w" id="-I3nwk9ceAWBch8vvQbHHQg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S2PIUFmTEeCcpdiAcH0w-w" id="-FcKKMUfPt3EWzE4_ZOTsnA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S2PIUVmTEeCcpdiAcH0w-w" id="-OXURYcVJKojeI03hChFCsQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S2Y5UFmTEeCcpdiAcH0w-w" id="-Du2R_k7pqLRr3WzfdFVfWA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S2Y5UVmTEeCcpdiAcH0w-w" id="-dYuef8izMNil6scNfR1Dsg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S2iqUFmTEeCcpdiAcH0w-w" id="-mVHqO6S50kezALZgP08etA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S2iqUVmTEeCcpdiAcH0w-w" id="-iYlO6aUGnY1vebmXAhABKA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S34HEFmTEeCcpdiAcH0w-w" id="-2gR5Uv4Dg17eMzBEYhAfEg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S34HEVmTEeCcpdiAcH0w-w" id="-av1HXdO41OcHPsHpp8yBzg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4B4EFmTEeCcpdiAcH0w-w" id="-Kcs9trmpnkNOX4TveXHX1g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4B4EVmTEeCcpdiAcH0w-w" id="-Ht-F7YiTjgYImbeM8j5V_Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4LCAFmTEeCcpdiAcH0w-w" id="-1lp43bPxm97SeyOxlld5Ag" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4UzAFmTEeCcpdiAcH0w-w" id="-vG3KWcPkjzvhkK3yNX7dhA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4UzAVmTEeCcpdiAcH0w-w" id="-KITSfYrioY198dVTPssPvg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4ekAFmTEeCcpdiAcH0w-w" id="-eDpZ1oHsWw_cx-CCwn_Uww" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4ekAVmTEeCcpdiAcH0w-w" id="-qJLlsHiPcRs5jWYwmFql7A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4nt8FmTEeCcpdiAcH0w-w" id="-Toq2oNaIeiDkWe6DYjZU8A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S4nt8VmTEeCcpdiAcH0w-w" id="-zj5wWJIbnJrzTsbw9RkoQw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S47P8FmTEeCcpdiAcH0w-w" id="-rTl3lsevKBV4DoNtHb85Rw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S47P8VmTEeCcpdiAcH0w-w" id="-urGvDzu_Rw1bMkZ4dV3VBw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S5EZ4FmTEeCcpdiAcH0w-w" id="-OFG1oHaKBSeEnVNZHIOO6w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S5EZ4VmTEeCcpdiAcH0w-w" id="-mKbOrvuons9rChmJPeFspg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S5OK4FmTEeCcpdiAcH0w-w" id="-Nv1ViqClCaa8E7xNjuhsPA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S5XU0FmTEeCcpdiAcH0w-w" id="-Fm2vVPiLcQvfC10FPmT-ag" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S5XU0VmTEeCcpdiAcH0w-w" id="-QPBL2a8vAJa9K6CCLq9_hA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S5hF0FmTEeCcpdiAcH0w-w" id="-4N-ksyL2jIp6fJQXV1HcBQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S5hF0VmTEeCcpdiAcH0w-w" id="-OC5WAbX5mDyrbpG0WkMsTQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S5q20FmTEeCcpdiAcH0w-w" id="-lOo0xOaMfy6RMxOmeK1ntQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S50AwFmTEeCcpdiAcH0w-w" id="--uzQTSOVvRvz9DVCsqCzcw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S50AwVmTEeCcpdiAcH0w-w" id="-qKEGOsD8R1M8vTodG0VI9Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S59xwFmTEeCcpdiAcH0w-w" id="-2-4sXJWybjPUMo76gsxUrA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S6HiwFmTEeCcpdiAcH0w-w" id="-2tm2IktmluDUboGJIcLDSQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S6HiwVmTEeCcpdiAcH0w-w" id="-SPRTmKcOY8uhXSYUElJD_A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S6adsFmTEeCcpdiAcH0w-w" id="-xGdRIdwQIVt3-32feera7A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S6adsVmTEeCcpdiAcH0w-w" id="-K9no0Y8fd2qLSwFy6snYnw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S6jnoFmTEeCcpdiAcH0w-w" id="-dbVJh3-7KeKo_CdIOQGj5Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S6tYoFmTEeCcpdiAcH0w-w" id="-DSGeVrVTJjT0MRy0TvuDSw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S6tYoVmTEeCcpdiAcH0w-w" id="-QZu83uvVme58aHkxlEaTmQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S7ATkFmTEeCcpdiAcH0w-w" id="-ebM0psxnCwWPQYF7YFMdWA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S7KEkFmTEeCcpdiAcH0w-w" id="-fVJV90U2K24PRA6BOiyuTg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S7KEkVmTEeCcpdiAcH0w-w" id="-drsUrP20wfWfu6engv0bvA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S7T1kFmTEeCcpdiAcH0w-w" id="-sjX0ZCEDiQdwyXRi2_xwPg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S7c_gFmTEeCcpdiAcH0w-w" id="-spzcqoK0HWQUSwAvjzoRHQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S7v6cFmTEeCcpdiAcH0w-w" id="-DepNFUaxj7vgjyQjYJjMOQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S7v6cVmTEeCcpdiAcH0w-w" id="-R2JrKH_RtyJIwW3nJszhMg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S75rcFmTEeCcpdiAcH0w-w" id="-1E7v5wKf27pEV1Pu3M1c1g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S8DccFmTEeCcpdiAcH0w-w" id="-barsvSUZoK-B2IRctfkyug" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S8MmYFmTEeCcpdiAcH0w-w" id="-zgwCbo2xDbSoVQ6xzPR8Jw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S88NQFmTEeCcpdiAcH0w-w" id="-xR_MU1qVIqmI3vD8JwvX1A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S88NQVmTEeCcpdiAcH0w-w" id="-0F1JpRACvQlhzf8uibcIKA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S9F-QFmTEeCcpdiAcH0w-w" id="-Hc7JvaQ0-snFgiJmpWD2OA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S9PvQFmTEeCcpdiAcH0w-w" id="-FS7huAe4PXfu1q_QQJGtIA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S9Y5MFmTEeCcpdiAcH0w-w" id="-6eacylaMdMYfqb7p28Owqw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S9Y5MVmTEeCcpdiAcH0w-w" id="-EQNfnV9bxYjmfZMCotuUHA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S9iqMFmTEeCcpdiAcH0w-w" id="-eivV0I3d5NflWdDxFN11Iw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S9sbMFmTEeCcpdiAcH0w-w" id="-JW1SrN4HN2vfMWdXhwx0ww" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S91lIFmTEeCcpdiAcH0w-w" id="-sq25iSf421_q4x2ZbYXkKQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S9_WIFmTEeCcpdiAcH0w-w" id="-RjvG1D-ZAteachI2o5oCQw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_S-IgEFmTEeCcpdiAcH0w-w" id="-gXDJs-AADHuo-Up6bT4Vow" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_iVgFYD3gEd-rQL4FfV6WbQ" name="openUp_abrd" guid="_iVgFYD3gEd-rQL4FfV6WbQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUw7ekEd-D7YZN9NgldQ" name="Inception" guid="_9tgUw7ekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUxLekEd-D7YZN9NgldQ" name="Iteration n" guid="_9tgUxLekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_jFqhkT3hEd-rQL4FfV6WbQ" name="Iteration n" guid="_jFqhkT3hEd-rQL4FfV6WbQ" presentationName="Iteration n" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_-wL9UD3gEd-rQL4FfV6WbQ _cj-9QD3hEd-rQL4FfV6WbQ _dS7G4D3hEd-rQL4FfV6WbQ _d88UQD3hEd-rQL4FfV6WbQ _eaADsD3hEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_-wL9UD3gEd-rQL4FfV6WbQ" name="identify_decision_point" guid="_-wL9UD3gEd-rQL4FfV6WbQ" presentationName="Identify Decision Points" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" output="_-wL9Uz3gEd-rQL4FfV6WbQ" performedPrimarilyBy="_-wL9UT3gEd-rQL4FfV6WbQ _-wL9Uj3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_jFqhkT3hEd-rQL4FfV6WbQ" name="Iteration n" guid="_jFqhkT3hEd-rQL4FfV6WbQ" presentationName="Iteration n" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_-wL9UD3gEd-rQL4FfV6WbQ _cj-9QD3hEd-rQL4FfV6WbQ _dS7G4D3hEd-rQL4FfV6WbQ _d88UQD3hEd-rQL4FfV6WbQ _eaADsD3hEd-rQL4FfV6WbQ _ryHzlFmSEeCcpdiAcH0w-w _ryHzplmSEeCcpdiAcH0w-w _ryHzqVmSEeCcpdiAcH0w-w _ryRkkVmSEeCcpdiAcH0w-w"/>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_-wL9UD3gEd-rQL4FfV6WbQ" name="identify_decision_point" guid="_-wL9UD3gEd-rQL4FfV6WbQ" presentationName="Identify Decision Points" briefDescription="Decision points are points of variability and decision in a business process. The goal of this task is to list the potential decision points in scope for the project." superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" output="_-wL9Uz3gEd-rQL4FfV6WbQ _ryHzlFmSEeCcpdiAcH0w-w">
+ <presentation xmi:id="-prjAV1fmvfmd2Zg_NkMweQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-prjAV1fmvfmd2Zg_NkMweQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yNUigIMUEd-68ahhmSUqHw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_A2d5sCyQEd-ER8gMc_Ftrw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_cj-9QD3hEd-rQL4FfV6WbQ" name="review_decision_point_table" guid="_cj-9QD3hEd-rQL4FfV6WbQ" presentationName="Review Decision Point Table, Business Process Map, Use Case Model" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_cj-9QT3hEd-rQL4FfV6WbQ _-wL9UT3gEd-rQL4FfV6WbQ" mandatoryInput="_-wL9Uz3gEd-rQL4FfV6WbQ" optionalInput="_ckIuQD3hEd-rQL4FfV6WbQ _ckIuQT3hEd-rQL4FfV6WbQ" output="_-wL9Uz3gEd-rQL4FfV6WbQ" performedPrimarilyBy="_-wL9Uj3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_cj-9QD3hEd-rQL4FfV6WbQ" name="review_decision_point_table" guid="_cj-9QD3hEd-rQL4FfV6WbQ" presentationName="Review Decision Point Table, Business Process Map, Use Case Model" briefDescription="After the business modeling activity of the Inception Phase the project team should have a decision point table document as a source for the rule discovery phase. A review of each decision point is needed. If this table is not present the team can start by the current business process description and then layouts this DP table." superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" mandatoryInput="_ryHzplmSEeCcpdiAcH0w-w" optionalInput="_ckIuQT3hEd-rQL4FfV6WbQ _ryHzqVmSEeCcpdiAcH0w-w" output="_-wL9Uz3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-IuPwmyFj6cPxKh7va58BBg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-IuPwmyFj6cPxKh7va58BBg"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Fpgz4HqsEd2o_5d3MWaNxQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWzAjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_sruWzQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_XA_IIHrPEd2o_5d3MWaNxQ"/>
@@ -20,12 +126,16 @@
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_1KxREHrNEd2o_5d3MWaNxQ"/>
<selectedSteps href="uma://-GPF0smZFlAxXRJQwghRiZA#_sruWzgjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_dS7G4D3hEd-rQL4FfV6WbQ" name="define_discovery_roadmap" guid="_dS7G4D3hEd-rQL4FfV6WbQ" presentationName="Define Discovery Roadmap" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_dTE34D3hEd-rQL4FfV6WbQ _-wL9UT3gEd-rQL4FfV6WbQ" mandatoryInput="_-wL9Uz3gEd-rQL4FfV6WbQ" optionalInput="_ckIuQT3hEd-rQL4FfV6WbQ _ckIuQD3hEd-rQL4FfV6WbQ" output="_dTE34T3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_-wL9Uj3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_dS7G4D3hEd-rQL4FfV6WbQ" name="define_discovery_roadmap" guid="_dS7G4D3hEd-rQL4FfV6WbQ" presentationName="Define Discovery Roadmap" briefDescription="The definition of the discovery roadmap is an important step to understand how the development team will extract the rules from the different kind of sources. There are multiple types of roadmaps according to the different starting points and rule sources." superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" mandatoryInput="_-wL9Uz3gEd-rQL4FfV6WbQ" optionalInput="_ckIuQT3hEd-rQL4FfV6WbQ _ckIuQD3hEd-rQL4FfV6WbQ _ryRkkVmSEeCcpdiAcH0w-w" output="_dTE34T3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-dZH2mwKP_HVhAcRXF625-g" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-dZH2mwKP_HVhAcRXF625-g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWygjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxgjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-Ak_E6i3qbz4NMG7ynyf4DA#_srklyQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-Ak_E6i3qbz4NMG7ynyf4DA#_srklxwjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_d88UQD3hEd-rQL4FfV6WbQ" name="organise_workshop" guid="_d88UQD3hEd-rQL4FfV6WbQ" presentationName="Organize Workshop" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_-wL9UT3gEd-rQL4FfV6WbQ _-wL9Uj3gEd-rQL4FfV6WbQ" mandatoryInput="_dTE34T3hEd-rQL4FfV6WbQ" output="_d88UQT3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_dTE34D3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_d88UQD3hEd-rQL4FfV6WbQ" name="organise_workshop" guid="_d88UQD3hEd-rQL4FfV6WbQ" presentationName="Organize Workshop" briefDescription="In case of human source for the rule the team needs to organize elicitation workshops" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" mandatoryInput="_dTE34T3hEd-rQL4FfV6WbQ" output="_d88UQT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-k9x6Q4vmGjn5pz_YPmFOSQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-k9x6Q4vmGjn5pz_YPmFOSQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0QjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWxAjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-ffYBUOhR5mZssG9eZxktmg#_sruWyQjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-ffYBUOhR5mZssG9eZxktmg#_sruWxwjqEdyj5bYZ0eCR5g"/>
@@ -33,75 +143,112 @@
<selectedSteps href="uma://-ffYBUOhR5mZssG9eZxktmg#_sruWyAjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-ffYBUOhR5mZssG9eZxktmg#_sruWxQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_eaADsD3hEd-rQL4FfV6WbQ" name="execute_rule_discovery_roadmap" guid="_eaADsD3hEd-rQL4FfV6WbQ" presentationName="Execute Rule Discovery Roadmap" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_-wL9UT3gEd-rQL4FfV6WbQ _cj-9QT3hEd-rQL4FfV6WbQ" mandatoryInput="_ckIuQD3hEd-rQL4FfV6WbQ _-wL9Uz3gEd-rQL4FfV6WbQ" optionalInput="_d88UQT3hEd-rQL4FfV6WbQ" output="_eaADsT3hEd-rQL4FfV6WbQ _eaADsj3hEd-rQL4FfV6WbQ _eaADsz3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_-wL9Uj3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_eaADsD3hEd-rQL4FfV6WbQ" name="execute_rule_discovery_roadmap" guid="_eaADsD3hEd-rQL4FfV6WbQ" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." superActivities="_jFqhkT3hEd-rQL4FfV6WbQ" mandatoryInput="_ckIuQD3hEd-rQL4FfV6WbQ _-wL9Uz3gEd-rQL4FfV6WbQ" optionalInput="_d88UQT3hEd-rQL4FfV6WbQ" output="_eaADsT3hEd-rQL4FfV6WbQ _eaADsj3hEd-rQL4FfV6WbQ _eaADsz3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-pFOBrLzvMdSKhPgshdTUmg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-pFOBrLzvMdSKhPgshdTUmg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3gjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ryHzlFmSEeCcpdiAcH0w-w" name="business_event_description" guid="_ryHzlFmSEeCcpdiAcH0w-w" presentationName="Business Event Description" briefDescription="Logging the business events source of business process execution helps to drive rule discovery." isPlanned="false" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ">
+ <methodElementProperty xmi:id="_ryHzlVmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-klIiZfe42Fb3xkxnrn7s8g" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-klIiZfe42Fb3xkxnrn7s8g"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_HSrrgGhiEd-FVuzXjnvIWA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ryHzplmSEeCcpdiAcH0w-w" name="business_process_map" guid="_ryHzplmSEeCcpdiAcH0w-w" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ">
+ <methodElementProperty xmi:id="_ryHzp1mSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-dvJXCSep8C4BgXVKBdqzWw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-dvJXCSep8C4BgXVKBdqzWw"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ryHzqVmSEeCcpdiAcH0w-w" name="decision_point_table" guid="_ryHzqVmSEeCcpdiAcH0w-w" presentationName="Decision Point Table" isPlanned="false" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ">
+ <methodElementProperty xmi:id="_ryHzqlmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <presentation xmi:id="-l3HNcE1exbebFi_vHnSlng" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-l3HNcE1exbebFi_vHnSlng"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
+ <WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ryRkkVmSEeCcpdiAcH0w-w" name="use_case" guid="_ryRkkVmSEeCcpdiAcH0w-w" presentationName="Use Case" briefDescription="This artifact captures the system behavior to yield an observable result of value to those who interact with the system." isPlanned="false" superActivities="_jFqhkT3hEd-rQL4FfV6WbQ">
+ <methodElementProperty xmi:id="_ryRkklmSEeCcpdiAcH0w-w" name="descriptor_createdByReference" value="true"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kNwINk1Edq2Q8qZoWbvGA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_JLOiIMNvEdu2IdAIaWZyAw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_3Y3XUI5fEdyO5aWob1UGDA"/>
+ <WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </processElements>
</childPackages>
- <processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_y0zJYT3gEd-rQL4FfV6WbQ" name="Inception" guid="_y0zJYT3gEd-rQL4FfV6WbQ" presentationName="Inception" superActivities="_iVgFYT3gEd-rQL4FfV6WbQ" breakdownElements="_-wL9UT3gEd-rQL4FfV6WbQ _-wL9Uj3gEd-rQL4FfV6WbQ _-wL9Uz3gEd-rQL4FfV6WbQ _cj-9QT3hEd-rQL4FfV6WbQ _ckIuQD3hEd-rQL4FfV6WbQ _ckIuQT3hEd-rQL4FfV6WbQ _dTE34D3hEd-rQL4FfV6WbQ _dTE34T3hEd-rQL4FfV6WbQ _d88UQT3hEd-rQL4FfV6WbQ _eaADsT3hEd-rQL4FfV6WbQ _eaADsj3hEd-rQL4FfV6WbQ _eaADsz3hEd-rQL4FfV6WbQ _jFqhkT3hEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_-wL9UT3gEd-rQL4FfV6WbQ" name="business_analyst" guid="_-wL9UT3gEd-rQL4FfV6WbQ" presentationName="Business Analyst" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ" modifies="_-wL9Uz3gEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_-wL9Uj3gEd-rQL4FfV6WbQ" name="rule_analyst" guid="_-wL9Uj3gEd-rQL4FfV6WbQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ" modifies="_-wL9Uz3gEd-rQL4FfV6WbQ _dTE34T3hEd-rQL4FfV6WbQ _eaADsT3hEd-rQL4FfV6WbQ _eaADsj3hEd-rQL4FfV6WbQ _eaADsz3hEd-rQL4FfV6WbQ" responsibleFor="_eaADsz3hEd-rQL4FfV6WbQ _eaADsj3hEd-rQL4FfV6WbQ _eaADsT3hEd-rQL4FfV6WbQ _d88UQT3hEd-rQL4FfV6WbQ _dTE34T3hEd-rQL4FfV6WbQ _-wL9Uz3gEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_y0zJYT3gEd-rQL4FfV6WbQ" name="Inception" guid="_y0zJYT3gEd-rQL4FfV6WbQ" presentationName="Inception" superActivities="_iVgFYT3gEd-rQL4FfV6WbQ" breakdownElements="_-wL9Uz3gEd-rQL4FfV6WbQ _ckIuQD3hEd-rQL4FfV6WbQ _ckIuQT3hEd-rQL4FfV6WbQ _dTE34T3hEd-rQL4FfV6WbQ _d88UQT3hEd-rQL4FfV6WbQ _eaADsT3hEd-rQL4FfV6WbQ _eaADsj3hEd-rQL4FfV6WbQ _eaADsz3hEd-rQL4FfV6WbQ _jFqhkT3hEd-rQL4FfV6WbQ"/>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_-wL9Uz3gEd-rQL4FfV6WbQ" name="decision_point_table" guid="_-wL9Uz3gEd-rQL4FfV6WbQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-iJdVDnhIv3mdPxGvKtIQTQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-iJdVDnhIv3mdPxGvKtIQTQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_cj-9QT3hEd-rQL4FfV6WbQ" name="subject_matter_expert" guid="_cj-9QT3hEd-rQL4FfV6WbQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ckIuQD3hEd-rQL4FfV6WbQ" name="business_process_map" guid="_ckIuQD3hEd-rQL4FfV6WbQ" presentationName="Business Process Map" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ckIuQD3hEd-rQL4FfV6WbQ" name="business_process_map" guid="_ckIuQD3hEd-rQL4FfV6WbQ" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-VciLFpBjLKj1Gg5oGyKV2w" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-VciLFpBjLKj1Gg5oGyKV2w"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ckIuQT3hEd-rQL4FfV6WbQ" name="use_case_model" guid="_ckIuQT3hEd-rQL4FfV6WbQ" presentationName="Use-Case Model" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ckIuQT3hEd-rQL4FfV6WbQ" name="use_case_model" guid="_ckIuQT3hEd-rQL4FfV6WbQ" presentationName="Use-Case Model" briefDescription="This artifact captures a model of the intended functions and environment of the system and serves as a contract between the customer and the team." isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_dTE34D3hEd-rQL4FfV6WbQ" name="project_manager" guid="_dTE34D3hEd-rQL4FfV6WbQ" presentationName="Project Manager" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ" modifies="_d88UQT3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_dTE34T3hEd-rQL4FfV6WbQ" name="rule_discovery_roadmap" guid="_dTE34T3hEd-rQL4FfV6WbQ" presentationName="Rule Discovery Roadmap" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-97voq1CnhjuPRUVjP8vvHQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-97voq1CnhjuPRUVjP8vvHQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruWygjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2QjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1QjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_d88UQT3hEd-rQL4FfV6WbQ" name="discovery_workshop_itinerary" guid="_d88UQT3hEd-rQL4FfV6WbQ" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-qe6GN8mPPfm5owdB98DzBw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-qe6GN8mPPfm5owdB98DzBw"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_eaADsT3hEd-rQL4FfV6WbQ" name="business_terms_glossary" guid="_eaADsT3hEd-rQL4FfV6WbQ" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_eaADsT3hEd-rQL4FfV6WbQ" name="business_terms_glossary" guid="_eaADsT3hEd-rQL4FfV6WbQ" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-C1-wtv51AzfuS54DlC_z7w" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-C1-wtv51AzfuS54DlC_z7w"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_eaADsj3hEd-rQL4FfV6WbQ" name="rule_description_doc" guid="_eaADsj3hEd-rQL4FfV6WbQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_eaADsj3hEd-rQL4FfV6WbQ" name="rule_description_doc" guid="_eaADsj3hEd-rQL4FfV6WbQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="--peqPcPE-E86pPKWX9cwLg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#--peqPcPE-E86pPKWX9cwLg"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_eaADsz3hEd-rQL4FfV6WbQ" name="conceptual_data_model" guid="_eaADsz3hEd-rQL4FfV6WbQ" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_y0zJYT3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-l8K8ZTTtZ7_u4YFVAyYZWg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-l8K8ZTTtZ7_u4YFVAyYZWg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUxbekEd-D7YZN9NgldQ" name="Elaboration" guid="_9tgUxbekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUxrekEd-D7YZN9NgldQ" name="Iteration E1" guid="_9tgUxrekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_sPbicT3hEd-rQL4FfV6WbQ" name="Iteration E1" guid="_sPbicT3hEd-rQL4FfV6WbQ" presentationName="Iteration E1" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_e2UMQT3hEd-rQL4FfV6WbQ _e2UMQj3hEd-rQL4FfV6WbQ _e2UMQz3hEd-rQL4FfV6WbQ _e2UMQD3hEd-rQL4FfV6WbQ _geBw8D3hEd-rQL4FfV6WbQ _g1t4MD3hEd-rQL4FfV6WbQ _hOwDQD3hEd-rQL4FfV6WbQ _h2_H8D3hEd-rQL4FfV6WbQ _EI4q4D3iEd-rQL4FfV6WbQ _EI4q4T3iEd-rQL4FfV6WbQ _EI4q4j3iEd-rQL4FfV6WbQ _EI4q4z3iEd-rQL4FfV6WbQ _EI4q5D3iEd-rQL4FfV6WbQ _WZA94D3jEd-rQL4FfV6WbQ _WZA94T3jEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_e2UMQT3hEd-rQL4FfV6WbQ" name="rule_analyst" guid="_e2UMQT3hEd-rQL4FfV6WbQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" modifies="_e2UMRz3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ _e2UMST3hEd-rQL4FfV6WbQ _geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ" responsibleFor="_EI4q4z3iEd-rQL4FfV6WbQ _EI4q4j3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_e2UMQj3hEd-rQL4FfV6WbQ" name="business_analyst" guid="_e2UMQj3hEd-rQL4FfV6WbQ" presentationName="Business Analyst" isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" modifies="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_e2UMQz3hEd-rQL4FfV6WbQ" name="subject_matter_expert" guid="_e2UMQz3hEd-rQL4FfV6WbQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_e2UMQD3hEd-rQL4FfV6WbQ" name="execute_rule_discovery_roadmap" guid="_e2UMQD3hEd-rQL4FfV6WbQ" presentationName="Execute Rule Discovery Roadmap" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_e2UMQj3hEd-rQL4FfV6WbQ _e2UMQz3hEd-rQL4FfV6WbQ" mandatoryInput="_e2UMRD3hEd-rQL4FfV6WbQ _e2UMRT3hEd-rQL4FfV6WbQ" optionalInput="_e2UMRj3hEd-rQL4FfV6WbQ" output="_e2UMRz3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ _e2UMST3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_e2UMQT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_sPbicT3hEd-rQL4FfV6WbQ" name="Iteration E1" guid="_sPbicT3hEd-rQL4FfV6WbQ" presentationName="Iteration E1" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_e2UMQD3hEd-rQL4FfV6WbQ _geBw8D3hEd-rQL4FfV6WbQ _g1t4MD3hEd-rQL4FfV6WbQ _hOwDQD3hEd-rQL4FfV6WbQ _h2_H8D3hEd-rQL4FfV6WbQ _EI4q4D3iEd-rQL4FfV6WbQ _EI4q4j3iEd-rQL4FfV6WbQ _EI4q4z3iEd-rQL4FfV6WbQ _EI4q5D3iEd-rQL4FfV6WbQ _WZA94D3jEd-rQL4FfV6WbQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_e2UMQD3hEd-rQL4FfV6WbQ" name="execute_rule_discovery_roadmap" guid="_e2UMQD3hEd-rQL4FfV6WbQ" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_e2UMRD3hEd-rQL4FfV6WbQ _e2UMRT3hEd-rQL4FfV6WbQ" optionalInput="_e2UMRj3hEd-rQL4FfV6WbQ" output="_e2UMRz3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ _e2UMST3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-rpwuTxNm209KUwlswmH8HQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-rpwuTxNm209KUwlswmH8HQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3gjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_geBw8D3hEd-rQL4FfV6WbQ" name="extract_rule_meaning" guid="_geBw8D3hEd-rQL4FfV6WbQ" presentationName="Extract Rule Meaning" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_e2UMSD3hEd-rQL4FfV6WbQ" output="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_e2UMQj3hEd-rQL4FfV6WbQ _e2UMQT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_geBw8D3hEd-rQL4FfV6WbQ" name="extract_rule_meaning" guid="_geBw8D3hEd-rQL4FfV6WbQ" presentationName="Extract Rule Meaning" briefDescription="Extract the semantic of the rule to prepare for a data model and to remove any ambiguity and redundancy." superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_e2UMSD3hEd-rQL4FfV6WbQ" output="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-9vl1UQ_4DObTvAkwNa9kEQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-9vl1UQ_4DObTvAkwNa9kEQ"/>
+ <concepts href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_gPfSoIpzEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8_mWgH3GEd2sJcA0evSBQw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_o19QgF2BEd2T6cNSe41mOg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_g1t4MD3hEd-rQL4FfV6WbQ" name="transform_rules" guid="_g1t4MD3hEd-rQL4FfV6WbQ" presentationName="Transform Rules" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ" output="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_e2UMQT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_g1t4MD3hEd-rQL4FfV6WbQ" name="transform_rules" guid="_g1t4MD3hEd-rQL4FfV6WbQ" presentationName="Transform Rules" briefDescription="Transform the rule to avoid ambiguity and make them more atomic" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ" output="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-E243hD2whycztF2dFXEwkA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-E243hD2whycztF2dFXEwkA"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_K6-3kDmnEdy8N6BRpa8ByQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x_5XgH9iEd26h9j0X6pKmw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8mZw8DmhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_7HEPsDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_tFwpYDmoEdy8N6BRpa8ByQ"/>
@@ -110,13 +257,21 @@
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_w3cyUDmoEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_0-T6ADmoEdy8N6BRpa8ByQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_hOwDQD3hEd-rQL4FfV6WbQ" name="build_test_scenario" guid="_hOwDQD3hEd-rQL4FfV6WbQ" presentationName="Build Test Scenarios" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_e2UMQj3hEd-rQL4FfV6WbQ _e2UMQz3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_e2UMQT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_hOwDQD3hEd-rQL4FfV6WbQ" name="build_test_scenario" guid="_hOwDQD3hEd-rQL4FfV6WbQ" presentationName="Build Test Scenarios" briefDescription="Work with analysis team to define concrete scenario with real data so that we can later on test the process and the rules." superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-99g5YVnMANjm-DUauKZXWg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-99g5YVnMANjm-DUauKZXWg"/>
+ <guidelines href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <supportingMaterials href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_vLvAUGjFEd2PJ-nlV-86WA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1dlWkH3GEd2sJcA0evSBQw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_h2_H8D3hEd-rQL4FfV6WbQ" name="synchronize_data_model" guid="_h2_H8D3hEd-rQL4FfV6WbQ" presentationName="Synchronize Data Models" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ" output="_geBw8j3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_e2UMQT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_h2_H8D3hEd-rQL4FfV6WbQ" name="synchronize_data_model" guid="_h2_H8D3hEd-rQL4FfV6WbQ" presentationName="Synchronize Data Models" briefDescription="Ensure the terms and entities used in the rule march element in the different date models used by the IT components" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ" output="_geBw8j3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-tIAbTEFRB78mlG35hRD9zQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-tIAbTEFRB78mlG35hRD9zQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_prtzIDmiEdy8N6BRpa8ByQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_EI4q4D3iEd-rQL4FfV6WbQ" name="develop_architecture" guid="_EI4q4D3iEd-rQL4FfV6WbQ" presentationName="Develop Business Rule Application Architecture" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_EI4q4j3iEd-rQL4FfV6WbQ _EI4q4z3iEd-rQL4FfV6WbQ" output="_EI4q5D3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_EI4q4T3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_EI4q4D3iEd-rQL4FfV6WbQ" name="develop_architecture" guid="_EI4q4D3iEd-rQL4FfV6WbQ" presentationName="Develop Business Rule Application Architecture" briefDescription="The purpose of the architecture activities is to support the following major items:
•	Integrate the Rule Engine into the business application
•	Deploy Business Rules Management System into the business and IT organizations." superActivities="_sPbicT3hEd-rQL4FfV6WbQ" mandatoryInput="_EI4q4j3iEd-rQL4FfV6WbQ _EI4q4z3iEd-rQL4FfV6WbQ" output="_EI4q5D3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Hh7gh2SK9tvxwdrSoTk3tg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Hh7gh2SK9tvxwdrSoTk3tg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_O1kAANvfEduv2KOT-Teh6w"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gjdYMlgEdmt3adZL5Dmdw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_nOQHsAp6EdyPCr4G1Tb79A"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_RMRccChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_yIEJ4Ap6EdyPCr4G1Tb79A"/>
@@ -127,37 +282,35 @@
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_04xVIChaEd2bfOOTyXGWkw"/>
<selectedSteps href="uma://-AUjqKQk_naPhdZWAQR-Mmg#_27c-kChaEd2bfOOTyXGWkw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EI4q4T3iEd-rQL4FfV6WbQ" name="rule_architect" guid="_EI4q4T3iEd-rQL4FfV6WbQ" presentationName="Rule Architect" isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" modifies="_EI4q5D3iEd-rQL4FfV6WbQ" responsibleFor="_EI4q5D3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EI4q4j3iEd-rQL4FfV6WbQ" name="logical_data_model" guid="_EI4q4j3iEd-rQL4FfV6WbQ" presentationName="Logical Data Model" isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EI4q4j3iEd-rQL4FfV6WbQ" name="logical_data_model" guid="_EI4q4j3iEd-rQL4FfV6WbQ" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Bs-Oyk_niHDCHWUI80V5qw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Bs-Oyk_niHDCHWUI80V5qw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EI4q4z3iEd-rQL4FfV6WbQ" name="decision_point_table" guid="_EI4q4z3iEd-rQL4FfV6WbQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-QinOsfSXNHdry4crJjAWWw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-QinOsfSXNHdry4crJjAWWw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EI4q5D3iEd-rQL4FfV6WbQ" name="decision_service_architecture" guid="_EI4q5D3iEd-rQL4FfV6WbQ" presentationName="Decision Service Architecture" isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EI4q5D3iEd-rQL4FfV6WbQ" name="decision_service_architecture" guid="_EI4q5D3iEd-rQL4FfV6WbQ" presentationName="Decision Service Architecture" briefDescription="A decision service is a piece of logic which uses a decision engine like a rule engine in order to infer actions on the input data." isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-_773MJ887tp2r2fn24vH9Q" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-_773MJ887tp2r2fn24vH9Q"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YRiuIItDEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eORS8GhhEd-FVuzXjnvIWA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_6BE7QAp_EdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_WZA94D3jEd-rQL4FfV6WbQ" name="define_data_scenario" guid="_WZA94D3jEd-rQL4FfV6WbQ" presentationName="Define Data Scenarios to Test Rule" superActivities="_sPbicT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_WZA94T3jEd-rQL4FfV6WbQ" performedPrimarilyBy="_e2UMQT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_WZA94D3jEd-rQL4FfV6WbQ" name="define_data_scenario" guid="_WZA94D3jEd-rQL4FfV6WbQ" presentationName="Define Data Scenarios to Test Rule" briefDescription="This task supports the definition of the data used to trigger the rule execution in scope for validating the rule set quality." superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-OgvhvvxDv6DTP9JkppFgpw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-OgvhvvxDv6DTP9JkppFgpw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_eAWtgFv3EdykEsBjRsVfZw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_WZA94T3jEd-rQL4FfV6WbQ" name="tester" guid="_WZA94T3jEd-rQL4FfV6WbQ" presentationName="Tester" isPlanned="false" superActivities="_sPbicT3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
- </processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUx7ekEd-D7YZN9NgldQ" name="Iteration E2" guid="_9tgUx7ekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_zEeusT3hEd-rQL4FfV6WbQ" name="Iteration E2" guid="_zEeusT3hEd-rQL4FfV6WbQ" presentationName="Iteration E2" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_0hT5ED3hEd-rQL4FfV6WbQ _0hT5ET3hEd-rQL4FfV6WbQ _0hT5Ej3hEd-rQL4FfV6WbQ _24aTUD3hEd-rQL4FfV6WbQ _1Qi9oD3hEd-rQL4FfV6WbQ _05dTUD3hEd-rQL4FfV6WbQ _05dTUT3hEd-rQL4FfV6WbQ _2WcOsD3hEd-rQL4FfV6WbQ _2WcOsT3hEd-rQL4FfV6WbQ _24aTUT3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ _24aTUz3hEd-rQL4FfV6WbQ _8oxIYD3hEd-rQL4FfV6WbQ _8oxIYT3hEd-rQL4FfV6WbQ _8oxIYj3hEd-rQL4FfV6WbQ _8oxIYz3hEd-rQL4FfV6WbQ _8oxIZD3hEd-rQL4FfV6WbQ _8oxIZT3hEd-rQL4FfV6WbQ _8oxIZj3hEd-rQL4FfV6WbQ _-VGHUD3hEd-rQL4FfV6WbQ _-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ __LyewD3hEd-rQL4FfV6WbQ __wS6AD3hEd-rQL4FfV6WbQ _FOBuAD3iEd-rQL4FfV6WbQ _FOBuAT3iEd-rQL4FfV6WbQ _G9L-gD3iEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0hT5ED3hEd-rQL4FfV6WbQ" name="determine_rule_implementation" guid="_0hT5ED3hEd-rQL4FfV6WbQ" presentationName="Determine Rule Implementation" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5ET3hEd-rQL4FfV6WbQ _0hT5Ej3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_zEeusT3hEd-rQL4FfV6WbQ" name="Iteration E2" guid="_zEeusT3hEd-rQL4FfV6WbQ" presentationName="Iteration E2" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_0hT5ED3hEd-rQL4FfV6WbQ _24aTUD3hEd-rQL4FfV6WbQ _1Qi9oD3hEd-rQL4FfV6WbQ _05dTUD3hEd-rQL4FfV6WbQ _2WcOsD3hEd-rQL4FfV6WbQ _24aTUT3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ _24aTUz3hEd-rQL4FfV6WbQ _8oxIYD3hEd-rQL4FfV6WbQ _8oxIYz3hEd-rQL4FfV6WbQ _8oxIZD3hEd-rQL4FfV6WbQ _8oxIZT3hEd-rQL4FfV6WbQ _8oxIZj3hEd-rQL4FfV6WbQ _-VGHUD3hEd-rQL4FfV6WbQ _-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ __LyewD3hEd-rQL4FfV6WbQ __wS6AD3hEd-rQL4FfV6WbQ _FOBuAD3iEd-rQL4FfV6WbQ _FOBuAT3iEd-rQL4FfV6WbQ _G9L-gD3iEd-rQL4FfV6WbQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0hT5ED3hEd-rQL4FfV6WbQ" name="determine_rule_implementation" guid="_0hT5ED3hEd-rQL4FfV6WbQ" presentationName="Determine Rule Implementation" briefDescription="This task tries to answer the question of where to implement the business rules that have been discovered." superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-VVUx-pgzq9QqwpY7eyCQug" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-VVUx-pgzq9QqwpY7eyCQug"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_qzveUBk5Edyoe_hnDlTB5A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_0hT5ET3hEd-rQL4FfV6WbQ" name="rule_analyst" guid="_0hT5ET3hEd-rQL4FfV6WbQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" modifies="_8oxIZT3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ _8oxIZj3hEd-rQL4FfV6WbQ _-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ" responsibleFor="_-VGHUj3hEd-rQL4FfV6WbQ _-VGHUT3hEd-rQL4FfV6WbQ _8oxIZj3hEd-rQL4FfV6WbQ _8oxIZT3hEd-rQL4FfV6WbQ _8oxIZD3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ _24aTUT3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_0hT5Ej3hEd-rQL4FfV6WbQ" name="rule_architect" guid="_0hT5Ej3hEd-rQL4FfV6WbQ" presentationName="Rule Architect" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" modifies="_24aTUz3hEd-rQL4FfV6WbQ _FOBuAT3iEd-rQL4FfV6WbQ" responsibleFor="_FOBuAT3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_24aTUD3hEd-rQL4FfV6WbQ" name="define_ruleset" guid="_24aTUD3hEd-rQL4FfV6WbQ" presentationName="Define Rule Set" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_24aTUT3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ" output="_24aTUz3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5Ej3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_24aTUD3hEd-rQL4FfV6WbQ" name="define_ruleset" guid="_24aTUD3hEd-rQL4FfV6WbQ" presentationName="Define Rule Set" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_24aTUT3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ" output="_24aTUz3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-XQBNNrNBrtaxuEo4q-lUBA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-XQBNNrNBrtaxuEo4q-lUBA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_7L2MIDyOEdyA6a_I80swHw"/>
<selectedSteps href="uma://-gt8CaPXz6HldH1v7OnThvg#_uGtsEErrEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-gt8CaPXz6HldH1v7OnThvg#_pIE9sEafEdySHMdInS9eGA"/>
@@ -165,7 +318,8 @@
<selectedSteps href="uma://-gt8CaPXz6HldH1v7OnThvg#_vYhSMErrEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-gt8CaPXz6HldH1v7OnThvg#_4V6rAErrEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_1Qi9oD3hEd-rQL4FfV6WbQ" name="build_rule_project_structure" guid="_1Qi9oD3hEd-rQL4FfV6WbQ" presentationName="Build Rule Project Structure" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5ET3hEd-rQL4FfV6WbQ _0hT5Ej3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_1Qi9oD3hEd-rQL4FfV6WbQ" name="build_rule_project_structure" guid="_1Qi9oD3hEd-rQL4FfV6WbQ" presentationName="Build Rule Project Structure" briefDescription="Designing and building how the rule will be managed is an important activity of a BRMS project. This task describes how to build the set of rule and non rules projects that support the business application." superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-tAu2iMCzVIgP4_Al4Lw8ww" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-tAu2iMCzVIgP4_Al4Lw8ww"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_O92DQDV5EdyTBtGu8YeFfg"/>
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_OBfOkDuhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_RVoYoDyNEdyA6a_I80swHw"/>
@@ -173,13 +327,13 @@
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_O92DQTV5EdyTBtGu8YeFfg"/>
<selectedSteps href="uma://-FSjG7hFXf5jUyW13bEdakQ#_94ET8DugEdy8N6BRpa8ByQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_05dTUD3hEd-rQL4FfV6WbQ" name="build_object_models" guid="_05dTUD3hEd-rQL4FfV6WbQ" presentationName="Build Object Models" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_05dTUT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_05dTUD3hEd-rQL4FfV6WbQ" name="build_object_models" guid="_05dTUD3hEd-rQL4FfV6WbQ" presentationName="Build Object Models" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-VHCrUwUFMiDFHcwq5Epk8g" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-VHCrUwUFMiDFHcwq5Epk8g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZffcIDmiEdy8N6BRpa8ByQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_05dTUT3hEd-rQL4FfV6WbQ" name="developer" guid="_05dTUT3hEd-rQL4FfV6WbQ" presentationName="Developer" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_2WcOsD3hEd-rQL4FfV6WbQ" name="prototype_rules" guid="_2WcOsD3hEd-rQL4FfV6WbQ" presentationName="Prototype Rules" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_2WcOsT3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5ET3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_2WcOsD3hEd-rQL4FfV6WbQ" name="prototype_rules" guid="_2WcOsD3hEd-rQL4FfV6WbQ" presentationName="Prototype Rules" briefDescription="Prototyping rules is an important step of the rule analysis, as it is when we are really coding that issues arrived. Paper work is fine, but working rules is far better." superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-gb3qcxiSIOyJyQwNdA3I4w" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-gb3qcxiSIOyJyQwNdA3I4w"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x-GVQIsqEd2gksNyFVJN4g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_dds-IDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_tA5YEDyIEdyA6a_I80swHw"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_usf-QDyIEdyA6a_I80swHw"/>
@@ -187,44 +341,56 @@
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_8RaUwDyIEdyA6a_I80swHw"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_-ThWcDyIEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_2WcOsT3hEd-rQL4FfV6WbQ" name="rule_writer" guid="_2WcOsT3hEd-rQL4FfV6WbQ" presentationName="Rule Writer" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" responsibleFor="_24aTUz3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_24aTUT3hEd-rQL4FfV6WbQ" name="decision_point_table" guid="_24aTUT3hEd-rQL4FfV6WbQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-T-jJKt0EZ1lzBKB62eWRPw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-T-jJKt0EZ1lzBKB62eWRPw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_24aTUj3hEd-rQL4FfV6WbQ" name="rule_description_doc" guid="_24aTUj3hEd-rQL4FfV6WbQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_24aTUj3hEd-rQL4FfV6WbQ" name="rule_description_doc" guid="_24aTUj3hEd-rQL4FfV6WbQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-a7ZnDzkb1A4WCd8v9E7D9A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-a7ZnDzkb1A4WCd8v9E7D9A"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_24aTUz3hEd-rQL4FfV6WbQ" name="ruleset" guid="_24aTUz3hEd-rQL4FfV6WbQ" presentationName="Ruleset" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_24aTUz3hEd-rQL4FfV6WbQ" name="ruleset" guid="_24aTUz3hEd-rQL4FfV6WbQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-OIYF_QKHkcHCdu5yP2EbPQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-OIYF_QKHkcHCdu5yP2EbPQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_8oxIYD3hEd-rQL4FfV6WbQ" name="execute_rule_discovery_roadmap" guid="_8oxIYD3hEd-rQL4FfV6WbQ" presentationName="Execute Rule Discovery Roadmap" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_8oxIYT3hEd-rQL4FfV6WbQ _8oxIYj3hEd-rQL4FfV6WbQ" mandatoryInput="_8oxIYz3hEd-rQL4FfV6WbQ _24aTUT3hEd-rQL4FfV6WbQ" optionalInput="_8oxIZD3hEd-rQL4FfV6WbQ" output="_8oxIZT3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ _8oxIZj3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5ET3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_8oxIYD3hEd-rQL4FfV6WbQ" name="execute_rule_discovery_roadmap" guid="_8oxIYD3hEd-rQL4FfV6WbQ" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_8oxIYz3hEd-rQL4FfV6WbQ _24aTUT3hEd-rQL4FfV6WbQ" optionalInput="_8oxIZD3hEd-rQL4FfV6WbQ" output="_8oxIZT3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ _8oxIZj3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-aPrVfOB6lpcDjCUvFFqQqA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-aPrVfOB6lpcDjCUvFFqQqA"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3gjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_8oxIYT3hEd-rQL4FfV6WbQ" name="business_analyst" guid="_8oxIYT3hEd-rQL4FfV6WbQ" presentationName="Business Analyst" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_8oxIYj3hEd-rQL4FfV6WbQ" name="subject_matter_expert" guid="_8oxIYj3hEd-rQL4FfV6WbQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_8oxIYz3hEd-rQL4FfV6WbQ" name="business_process_map" guid="_8oxIYz3hEd-rQL4FfV6WbQ" presentationName="Business Process Map" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_8oxIYz3hEd-rQL4FfV6WbQ" name="business_process_map" guid="_8oxIYz3hEd-rQL4FfV6WbQ" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-KRk9ZEALe8Zga5TYVVmNHw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-KRk9ZEALe8Zga5TYVVmNHw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_8oxIZD3hEd-rQL4FfV6WbQ" name="discovery_workshop_itinerary" guid="_8oxIZD3hEd-rQL4FfV6WbQ" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-VuBFXGbVPgtiGX9pA2G0_A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-VuBFXGbVPgtiGX9pA2G0_A"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_8oxIZT3hEd-rQL4FfV6WbQ" name="business_terms_glossary" guid="_8oxIZT3hEd-rQL4FfV6WbQ" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_8oxIZT3hEd-rQL4FfV6WbQ" name="business_terms_glossary" guid="_8oxIZT3hEd-rQL4FfV6WbQ" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-49ndVIE5XgQJeRgW7VSm5A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-49ndVIE5XgQJeRgW7VSm5A"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_8oxIZj3hEd-rQL4FfV6WbQ" name="conceptual_data_model" guid="_8oxIZj3hEd-rQL4FfV6WbQ" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-cKCbpL8wmUvXw1Nz87Gw4w" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-cKCbpL8wmUvXw1Nz87Gw4w"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_-VGHUD3hEd-rQL4FfV6WbQ" name="transform_rules" guid="_-VGHUD3hEd-rQL4FfV6WbQ" presentationName="Transform Rules" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ" output="_-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5ET3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_-VGHUD3hEd-rQL4FfV6WbQ" name="transform_rules" guid="_-VGHUD3hEd-rQL4FfV6WbQ" presentationName="Transform Rules" briefDescription="Transform the rule to avoid ambiguity and make them more atomic" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ" output="_-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-zKTKc4iLlSGe2ryzPTiX5A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-zKTKc4iLlSGe2ryzPTiX5A"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_K6-3kDmnEdy8N6BRpa8ByQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x_5XgH9iEd26h9j0X6pKmw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8mZw8DmhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_7HEPsDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_tFwpYDmoEdy8N6BRpa8ByQ"/>
@@ -234,73 +400,97 @@
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_0-T6ADmoEdy8N6BRpa8ByQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_-VGHUT3hEd-rQL4FfV6WbQ" name="fact_model" guid="_-VGHUT3hEd-rQL4FfV6WbQ" presentationName="Fact Model" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-I3nwk9ceAWBch8vvQbHHQg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-I3nwk9ceAWBch8vvQbHHQg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_-VGHUj3hEd-rQL4FfV6WbQ" name="logical_data_model" guid="_-VGHUj3hEd-rQL4FfV6WbQ" presentationName="Logical Data Model" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_-VGHUj3hEd-rQL4FfV6WbQ" name="logical_data_model" guid="_-VGHUj3hEd-rQL4FfV6WbQ" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-FcKKMUfPt3EWzE4_ZOTsnA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-FcKKMUfPt3EWzE4_ZOTsnA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="__LyewD3hEd-rQL4FfV6WbQ" name="build_test_scenario" guid="__LyewD3hEd-rQL4FfV6WbQ" presentationName="Build Test Scenarios" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" additionallyPerformedBy="_8oxIYT3hEd-rQL4FfV6WbQ _8oxIYj3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5ET3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="__LyewD3hEd-rQL4FfV6WbQ" name="build_test_scenario" guid="__LyewD3hEd-rQL4FfV6WbQ" presentationName="Build Test Scenarios" briefDescription="Work with analysis team to define concrete scenario with real data so that we can later on test the process and the rules." superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-OXURYcVJKojeI03hChFCsQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-OXURYcVJKojeI03hChFCsQ"/>
+ <guidelines href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <supportingMaterials href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_vLvAUGjFEd2PJ-nlV-86WA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1dlWkH3GEd2sJcA0evSBQw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="__wS6AD3hEd-rQL4FfV6WbQ" name="synchronize_data_model" guid="__wS6AD3hEd-rQL4FfV6WbQ" presentationName="Synchronize Data Models" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ" output="_-VGHUj3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5ET3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="__wS6AD3hEd-rQL4FfV6WbQ" name="synchronize_data_model" guid="__wS6AD3hEd-rQL4FfV6WbQ" presentationName="Synchronize Data Models" briefDescription="Ensure the terms and entities used in the rule march element in the different date models used by the IT components" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ" output="_-VGHUj3hEd-rQL4FfV6WbQ _24aTUj3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Du2R_k7pqLRr3WzfdFVfWA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Du2R_k7pqLRr3WzfdFVfWA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_prtzIDmiEdy8N6BRpa8ByQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_FOBuAD3iEd-rQL4FfV6WbQ" name="design_models_for_bre" guid="_FOBuAD3iEd-rQL4FfV6WbQ" presentationName="Design Business Object Models for Rule Engine Processing" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ" output="_FOBuAT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5Ej3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_FOBuAD3iEd-rQL4FfV6WbQ" name="design_models_for_bre" guid="_FOBuAD3iEd-rQL4FfV6WbQ" presentationName="Design Business Object Models for Rule Engine Processing" briefDescription="Design the object model to be processed by the rule engine. " superActivities="_zEeusT3hEd-rQL4FfV6WbQ" mandatoryInput="_-VGHUT3hEd-rQL4FfV6WbQ _-VGHUj3hEd-rQL4FfV6WbQ" output="_FOBuAT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-dYuef8izMNil6scNfR1Dsg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-dYuef8izMNil6scNfR1Dsg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_lYC2IGDAEdyKlZvvtnMrMg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_FOBuAT3iEd-rQL4FfV6WbQ" name="executable_object_model" guid="_FOBuAT3iEd-rQL4FfV6WbQ" presentationName="Executable Object Model" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_FOBuAT3iEd-rQL4FfV6WbQ" name="executable_object_model" guid="_FOBuAT3iEd-rQL4FfV6WbQ" presentationName="Executable Object Model" briefDescription="A Java, .Net or XML schema implementation of the logical data model" isPlanned="false" superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_U003IIm4Ed2cL6yqw-_-uA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_G9L-gD3iEd-rQL4FfV6WbQ" name="design_reference_data_integration" guid="_G9L-gD3iEd-rQL4FfV6WbQ" presentationName="Design Integration to Reference Data" superActivities="_zEeusT3hEd-rQL4FfV6WbQ" performedPrimarilyBy="_0hT5Ej3hEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_G9L-gD3iEd-rQL4FfV6WbQ" name="design_reference_data_integration" guid="_G9L-gD3iEd-rQL4FfV6WbQ" presentationName="Design Integration to Reference Data" briefDescription="Reference data are everywhere in business application, from basic enumeration value like the US sates to business codes with business meaning (like medical code). Those references data should be managed in a central Data Base or repository. The Rule engine needs to access them at execution but also during the authoring phase." superActivities="_zEeusT3hEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-mVHqO6S50kezALZgP08etA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-mVHqO6S50kezALZgP08etA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_HMQasGDFEdyKlZvvtnMrMg"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUyLekEd-D7YZN9NgldQ" name="Iteration En" guid="_9tgUyLekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_ST6mMT3iEd-rQL4FfV6WbQ" name="Iteration En" guid="_ST6mMT3iEd-rQL4FfV6WbQ" presentationName="Iteration En" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_Wzz48D3iEd-rQL4FfV6WbQ _Wzz48T3iEd-rQL4FfV6WbQ _Wzz48j3iEd-rQL4FfV6WbQ _Wzz48z3iEd-rQL4FfV6WbQ _Wzz49D3iEd-rQL4FfV6WbQ _Wzz49T3iEd-rQL4FfV6WbQ _Wzz49j3iEd-rQL4FfV6WbQ _Wzz49z3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ _Wzz4-T3iEd-rQL4FfV6WbQ _ZdreMD3iEd-rQL4FfV6WbQ _ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ _Z4M3AD3iEd-rQL4FfV6WbQ _a8TYUD3iEd-rQL4FfV6WbQ _a8dJUD3iEd-rQL4FfV6WbQ _dWrwED3iEd-rQL4FfV6WbQ _dWrwET3iEd-rQL4FfV6WbQ _dqy-4D3iEd-rQL4FfV6WbQ _dqy-4T3iEd-rQL4FfV6WbQ _eEuh0D3iEd-rQL4FfV6WbQ _ecapED3iEd-rQL4FfV6WbQ _fYUQoD3iEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Wzz48D3iEd-rQL4FfV6WbQ" name="execute_rule_discovery_roadmap" guid="_Wzz48D3iEd-rQL4FfV6WbQ" presentationName="Execute Rule Discovery Roadmap" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_Wzz48j3iEd-rQL4FfV6WbQ _Wzz48z3iEd-rQL4FfV6WbQ" mandatoryInput="_Wzz49D3iEd-rQL4FfV6WbQ _Wzz49T3iEd-rQL4FfV6WbQ" optionalInput="_Wzz49j3iEd-rQL4FfV6WbQ" output="_Wzz49z3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ _Wzz4-T3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_Wzz48T3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_ST6mMT3iEd-rQL4FfV6WbQ" name="Iteration En" guid="_ST6mMT3iEd-rQL4FfV6WbQ" presentationName="Iteration En" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_Wzz48D3iEd-rQL4FfV6WbQ _Wzz49D3iEd-rQL4FfV6WbQ _Wzz49T3iEd-rQL4FfV6WbQ _Wzz49j3iEd-rQL4FfV6WbQ _Wzz49z3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ _Wzz4-T3iEd-rQL4FfV6WbQ _ZdreMD3iEd-rQL4FfV6WbQ _ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ _Z4M3AD3iEd-rQL4FfV6WbQ _a8TYUD3iEd-rQL4FfV6WbQ _dWrwED3iEd-rQL4FfV6WbQ _dqy-4D3iEd-rQL4FfV6WbQ _dqy-4T3iEd-rQL4FfV6WbQ _eEuh0D3iEd-rQL4FfV6WbQ _ecapED3iEd-rQL4FfV6WbQ _fYUQoD3iEd-rQL4FfV6WbQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Wzz48D3iEd-rQL4FfV6WbQ" name="execute_rule_discovery_roadmap" guid="_Wzz48D3iEd-rQL4FfV6WbQ" presentationName="Execute Rule Discovery Roadmap" briefDescription="This activity or task includes the three types of rule discovery: business users and experts workshop session, document study, legacy code mining. Even if the main source of rules are documents or code, it is still important to come back to a SME to get feedbacks on the team findings." superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" mandatoryInput="_Wzz49D3iEd-rQL4FfV6WbQ _Wzz49T3iEd-rQL4FfV6WbQ" optionalInput="_Wzz49j3iEd-rQL4FfV6WbQ" output="_Wzz49z3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ _Wzz4-T3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-iYlO6aUGnY1vebmXAhABKA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-iYlO6aUGnY1vebmXAhABKA"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1gjqEdyj5bYZ0eCR5g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW3AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4QjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW4AjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3gjqEdyj5bYZ0eCR5g"/>
<selectedSteps href="uma://-QyQxGy-JR3YceDG_VUN5aw#_sruW3QjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Wzz48T3iEd-rQL4FfV6WbQ" name="rule_analyst" guid="_Wzz48T3iEd-rQL4FfV6WbQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" modifies="_Wzz49z3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ _Wzz4-T3iEd-rQL4FfV6WbQ _ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ" responsibleFor="_ZdreMj3iEd-rQL4FfV6WbQ _ZdreMT3iEd-rQL4FfV6WbQ _Wzz4-T3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ _Wzz49z3iEd-rQL4FfV6WbQ _Wzz49j3iEd-rQL4FfV6WbQ _Wzz49T3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Wzz48j3iEd-rQL4FfV6WbQ" name="business_analyst" guid="_Wzz48j3iEd-rQL4FfV6WbQ" presentationName="Business Analyst" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" modifies="_ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Wzz48z3iEd-rQL4FfV6WbQ" name="subject_matter_expert" guid="_Wzz48z3iEd-rQL4FfV6WbQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz49D3iEd-rQL4FfV6WbQ" name="business_process_map" guid="_Wzz49D3iEd-rQL4FfV6WbQ" presentationName="Business Process Map" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz49D3iEd-rQL4FfV6WbQ" name="business_process_map" guid="_Wzz49D3iEd-rQL4FfV6WbQ" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-2gR5Uv4Dg17eMzBEYhAfEg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-2gR5Uv4Dg17eMzBEYhAfEg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz49T3iEd-rQL4FfV6WbQ" name="decision_point_table" guid="_Wzz49T3iEd-rQL4FfV6WbQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-av1HXdO41OcHPsHpp8yBzg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-av1HXdO41OcHPsHpp8yBzg"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz49j3iEd-rQL4FfV6WbQ" name="discovery_workshop_itinerary" guid="_Wzz49j3iEd-rQL4FfV6WbQ" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Kcs9trmpnkNOX4TveXHX1g" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Kcs9trmpnkNOX4TveXHX1g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz49z3iEd-rQL4FfV6WbQ" name="business_terms_glossary" guid="_Wzz49z3iEd-rQL4FfV6WbQ" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz49z3iEd-rQL4FfV6WbQ" name="business_terms_glossary" guid="_Wzz49z3iEd-rQL4FfV6WbQ" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Ht-F7YiTjgYImbeM8j5V_Q" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Ht-F7YiTjgYImbeM8j5V_Q"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz4-D3iEd-rQL4FfV6WbQ" name="rule_description_doc" guid="_Wzz4-D3iEd-rQL4FfV6WbQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz4-D3iEd-rQL4FfV6WbQ" name="rule_description_doc" guid="_Wzz4-D3iEd-rQL4FfV6WbQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-1lp43bPxm97SeyOxlld5Ag" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-1lp43bPxm97SeyOxlld5Ag"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Wzz4-T3iEd-rQL4FfV6WbQ" name="conceptual_data_model" guid="_Wzz4-T3iEd-rQL4FfV6WbQ" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-vG3KWcPkjzvhkK3yNX7dhA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-vG3KWcPkjzvhkK3yNX7dhA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ZdreMD3iEd-rQL4FfV6WbQ" name="extract_rule_meaning" guid="_ZdreMD3iEd-rQL4FfV6WbQ" presentationName="Extract Rule Meaning" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" mandatoryInput="_Wzz4-D3iEd-rQL4FfV6WbQ" output="_ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_Wzz48j3iEd-rQL4FfV6WbQ _Wzz48T3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ZdreMD3iEd-rQL4FfV6WbQ" name="extract_rule_meaning" guid="_ZdreMD3iEd-rQL4FfV6WbQ" presentationName="Extract Rule Meaning" briefDescription="Extract the semantic of the rule to prepare for a data model and to remove any ambiguity and redundancy." superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" mandatoryInput="_Wzz4-D3iEd-rQL4FfV6WbQ" output="_ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-KITSfYrioY198dVTPssPvg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-KITSfYrioY198dVTPssPvg"/>
+ <concepts href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_gPfSoIpzEd2gksNyFVJN4g"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8_mWgH3GEd2sJcA0evSBQw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_o19QgF2BEd2T6cNSe41mOg"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ZdreMT3iEd-rQL4FfV6WbQ" name="fact_model" guid="_ZdreMT3iEd-rQL4FfV6WbQ" presentationName="Fact Model" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-eDpZ1oHsWw_cx-CCwn_Uww" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-eDpZ1oHsWw_cx-CCwn_Uww"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ZdreMj3iEd-rQL4FfV6WbQ" name="logical_data_model" guid="_ZdreMj3iEd-rQL4FfV6WbQ" presentationName="Logical Data Model" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_ZdreMj3iEd-rQL4FfV6WbQ" name="logical_data_model" guid="_ZdreMj3iEd-rQL4FfV6WbQ" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-qJLlsHiPcRs5jWYwmFql7A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-qJLlsHiPcRs5jWYwmFql7A"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Z4M3AD3iEd-rQL4FfV6WbQ" name="transform_rules" guid="_Z4M3AD3iEd-rQL4FfV6WbQ" presentationName="Transform Rules" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" mandatoryInput="_ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ" output="_ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_Wzz48T3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Z4M3AD3iEd-rQL4FfV6WbQ" name="transform_rules" guid="_Z4M3AD3iEd-rQL4FfV6WbQ" presentationName="Transform Rules" briefDescription="Transform the rule to avoid ambiguity and make them more atomic" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" mandatoryInput="_ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ" output="_ZdreMT3iEd-rQL4FfV6WbQ _ZdreMj3iEd-rQL4FfV6WbQ _Wzz4-D3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Toq2oNaIeiDkWe6DYjZU8A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Toq2oNaIeiDkWe6DYjZU8A"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_K6-3kDmnEdy8N6BRpa8ByQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x_5XgH9iEd26h9j0X6pKmw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_8mZw8DmhEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_7HEPsDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_tFwpYDmoEdy8N6BRpa8ByQ"/>
@@ -309,7 +499,9 @@
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_w3cyUDmoEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-kaG_G7QLbZmoHMO8_47GiQ#_0-T6ADmoEdy8N6BRpa8ByQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_a8TYUD3iEd-rQL4FfV6WbQ" name="prototype_rules" guid="_a8TYUD3iEd-rQL4FfV6WbQ" presentationName="Prototype Rules" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_a8dJUD3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_Wzz48T3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_a8TYUD3iEd-rQL4FfV6WbQ" name="prototype_rules" guid="_a8TYUD3iEd-rQL4FfV6WbQ" presentationName="Prototype Rules" briefDescription="Prototyping rules is an important step of the rule analysis, as it is when we are really coding that issues arrived. Paper work is fine, but working rules is far better." superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-zj5wWJIbnJrzTsbw9RkoQw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-zj5wWJIbnJrzTsbw9RkoQw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_x-GVQIsqEd2gksNyFVJN4g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_dds-IDmiEdy8N6BRpa8ByQ"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_tA5YEDyIEdyA6a_I80swHw"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_usf-QDyIEdyA6a_I80swHw"/>
@@ -317,16 +509,12 @@
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_8RaUwDyIEdyA6a_I80swHw"/>
<selectedSteps href="uma://-bFlEvOsmuJvDiRkZZcf_uA#_-ThWcDyIEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_a8dJUD3iEd-rQL4FfV6WbQ" name="rule_writer" guid="_a8dJUD3iEd-rQL4FfV6WbQ" presentationName="Rule Writer" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" modifies="_dqy-4T3iEd-rQL4FfV6WbQ" responsibleFor="_dqy-4T3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_dWrwED3iEd-rQL4FfV6WbQ" name="develop_unit_tests" guid="_dWrwED3iEd-rQL4FfV6WbQ" presentationName="Develop Rule Unit Tests" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_dWrwET3iEd-rQL4FfV6WbQ _a8dJUD3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_dWrwED3iEd-rQL4FfV6WbQ" name="develop_unit_tests" guid="_dWrwED3iEd-rQL4FfV6WbQ" presentationName="Develop Rule Unit Tests" briefDescription="The goal of this task is to track down anomalies in the rules such as conflicts, redundancies or overlaps.
" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-rTl3lsevKBV4DoNtHb85Rw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-rTl3lsevKBV4DoNtHb85Rw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ioCPkDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_dWrwET3iEd-rQL4FfV6WbQ" name="developer" guid="_dWrwET3iEd-rQL4FfV6WbQ" presentationName="Developer" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_dqy-4D3iEd-rQL4FfV6WbQ" name="develop_rules" guid="_dqy-4D3iEd-rQL4FfV6WbQ" presentationName="Develop Rules" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" output="_dqy-4T3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_a8dJUD3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_dqy-4D3iEd-rQL4FfV6WbQ" name="develop_rules" guid="_dqy-4D3iEd-rQL4FfV6WbQ" presentationName="Develop Rules" briefDescription="This task is about developing each rule in the rule project." superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" output="_dqy-4T3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-urGvDzu_Rw1bMkZ4dV3VBw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-urGvDzu_Rw1bMkZ4dV3VBw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Y2CxEDzEEdyA6a_I80swHw"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_bsPp8ErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_qfzk4ErtEdyEE-k1R6LmOA"/>
@@ -334,58 +522,81 @@
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_zAvrMErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_GvK9oEruEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_dqy-4T3iEd-rQL4FfV6WbQ" name="ruleset" guid="_dqy-4T3iEd-rQL4FfV6WbQ" presentationName="Ruleset" isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_dqy-4T3iEd-rQL4FfV6WbQ" name="ruleset" guid="_dqy-4T3iEd-rQL4FfV6WbQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-OFG1oHaKBSeEnVNZHIOO6w" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-OFG1oHaKBSeEnVNZHIOO6w"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_eEuh0D3iEd-rQL4FfV6WbQ" name="enhance_object_models" guid="_eEuh0D3iEd-rQL4FfV6WbQ" presentationName="Enhance Object Models" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_dWrwET3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_eEuh0D3iEd-rQL4FfV6WbQ" name="enhance_object_models" guid="_eEuh0D3iEd-rQL4FfV6WbQ" presentationName="Enhance Object Models" briefDescription="The data model is started during the analysis and design tasks. But it will involve over time. So this activity supports the enhancement of the object models." superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-mKbOrvuons9rChmJPeFspg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-mKbOrvuons9rChmJPeFspg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_UXrv8Eb3EdySHMdInS9eGA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ecapED3iEd-rQL4FfV6WbQ" name="execute_rule_set" guid="_ecapED3iEd-rQL4FfV6WbQ" presentationName="Execute Rule Set" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" output="_dqy-4T3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_a8dJUD3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_ecapED3iEd-rQL4FfV6WbQ" name="execute_rule_set" guid="_ecapED3iEd-rQL4FfV6WbQ" presentationName="Execute Rule Set" briefDescription="Execute the tests to trigger the rule execution. Analyze the output logs. Report issues." superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" output="_dqy-4T3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Nv1ViqClCaa8E7xNjuhsPA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Nv1ViqClCaa8E7xNjuhsPA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_JCHfMEXhEdy14e5PT9v3HQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_fYUQoD3iEd-rQL4FfV6WbQ" name="log_issue" guid="_fYUQoD3iEd-rQL4FfV6WbQ" presentationName="Log Issue" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_a8dJUD3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_fYUQoD3iEd-rQL4FfV6WbQ" name="log_issue" guid="_fYUQoD3iEd-rQL4FfV6WbQ" presentationName="Log Issue" superActivities="_ST6mMT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Fm2vVPiLcQvfC10FPmT-ag" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Fm2vVPiLcQvfC10FPmT-ag"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yGbYIEb0EdySHMdInS9eGA"/>
</processElements>
</childPackages>
<processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_0HDbcD3gEd-rQL4FfV6WbQ" name="Elaboration" guid="_0HDbcD3gEd-rQL4FfV6WbQ" presentationName="Elaboration" superActivities="_iVgFYT3gEd-rQL4FfV6WbQ" breakdownElements="_e2UMRD3hEd-rQL4FfV6WbQ _e2UMRT3hEd-rQL4FfV6WbQ _e2UMRj3hEd-rQL4FfV6WbQ _e2UMRz3hEd-rQL4FfV6WbQ _e2UMSD3hEd-rQL4FfV6WbQ _e2UMST3hEd-rQL4FfV6WbQ _geBw8T3hEd-rQL4FfV6WbQ _geBw8j3hEd-rQL4FfV6WbQ _sPbicT3hEd-rQL4FfV6WbQ _zEeusT3hEd-rQL4FfV6WbQ _ST6mMT3iEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMRD3hEd-rQL4FfV6WbQ" name="business_process_map" guid="_e2UMRD3hEd-rQL4FfV6WbQ" presentationName="Business Process Map" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMRD3hEd-rQL4FfV6WbQ" name="business_process_map" guid="_e2UMRD3hEd-rQL4FfV6WbQ" presentationName="Business Process Map" briefDescription="A Process map describes graphically using Business Process Management Notation (BPMN) the business process under scope." isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-QPBL2a8vAJa9K6CCLq9_hA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-QPBL2a8vAJa9K6CCLq9_hA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Uw8aYBDGEdyJtJ3PbfdVDw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMRT3hEd-rQL4FfV6WbQ" name="decision_point_table" guid="_e2UMRT3hEd-rQL4FfV6WbQ" presentationName="Decision Point Table" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-4N-ksyL2jIp6fJQXV1HcBQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-4N-ksyL2jIp6fJQXV1HcBQ"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ZDdmQDSmEdyTBtGu8YeFfg"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_kRoWgBDFEdyJtJ3PbfdVDw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_SlELAAsbEdyPCr4G1Tb79A"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMRj3hEd-rQL4FfV6WbQ" name="discovery_workshop_itinerary" guid="_e2UMRj3hEd-rQL4FfV6WbQ" presentationName="Rule Discovery Workshop Itinerary" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-OC5WAbX5mDyrbpG0WkMsTQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-OC5WAbX5mDyrbpG0WkMsTQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW0wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklwQjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMRz3hEd-rQL4FfV6WbQ" name="business_terms_glossary" guid="_e2UMRz3hEd-rQL4FfV6WbQ" presentationName="Business Terms Glossary" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMRz3hEd-rQL4FfV6WbQ" name="business_terms_glossary" guid="_e2UMRz3hEd-rQL4FfV6WbQ" presentationName="Business Terms Glossary" briefDescription="Log in one document the terms and their definition as used by the business user" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-lOo0xOaMfy6RMxOmeK1ntQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-lOo0xOaMfy6RMxOmeK1ntQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW1wjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklygjqEdyj5bYZ0eCR5g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMSD3hEd-rQL4FfV6WbQ" name="rule_description_doc" guid="_e2UMSD3hEd-rQL4FfV6WbQ" presentationName="Rule Description Document" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMSD3hEd-rQL4FfV6WbQ" name="rule_description_doc" guid="_e2UMSD3hEd-rQL4FfV6WbQ" presentationName="Rule Description Document" briefDescription="This document formalize the rule discovery by logging the major rules of a decision point in one document. " isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="--uzQTSOVvRvz9DVCsqCzcw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#--uzQTSOVvRvz9DVCsqCzcw"/>
+ <examples href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_j4-ukDS3EdyTBtGu8YeFfg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_1ZyHAHrZEd2l9d4UccBrvQ"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxAjqEdyj5bYZ0eCR5g"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_srklxQjqEdyj5bYZ0eCR5g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2gjqEdyj5bYZ0eCR5g"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_e2UMST3hEd-rQL4FfV6WbQ" name="conceptual_data_model" guid="_e2UMST3hEd-rQL4FfV6WbQ" presentationName="Conceptual Data Model" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-qKEGOsD8R1M8vTodG0VI9Q" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-qKEGOsD8R1M8vTodG0VI9Q"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_hYc8UHr9Ed2l9d4UccBrvQ"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_geBw8T3hEd-rQL4FfV6WbQ" name="fact_model" guid="_geBw8T3hEd-rQL4FfV6WbQ" presentationName="Fact Model" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-2-4sXJWybjPUMo76gsxUrA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-2-4sXJWybjPUMo76gsxUrA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_csL3wHrMEd2o_5d3MWaNxQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_geBw8j3hEd-rQL4FfV6WbQ" name="logical_data_model" guid="_geBw8j3hEd-rQL4FfV6WbQ" presentationName="Logical Data Model" isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_geBw8j3hEd-rQL4FfV6WbQ" name="logical_data_model" guid="_geBw8j3hEd-rQL4FfV6WbQ" presentationName="Logical Data Model" briefDescription="Logical Data Model represents the organization business-domain concepts in a set of diagram and logical schema. The choice of representation will depend of the design approach and the target audience. It could be relational (Table - columns, association), object oriented (class - attribute association) or XML (tags) defined." isPlanned="false" superActivities="_0HDbcD3gEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-2tm2IktmluDUboGJIcLDSQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-2tm2IktmluDUboGJIcLDSQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_sruW2AjqEdyj5bYZ0eCR5g"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUybekEd-D7YZN9NgldQ" name="Construction" guid="_9tgUybekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUyrekEd-D7YZN9NgldQ" name="Iteration C1" guid="_9tgUyrekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_LvtSUT3iEd-rQL4FfV6WbQ" name="Iteration C1" guid="_LvtSUT3iEd-rQL4FfV6WbQ" presentationName="Iteration C1" superActivities="_4HDtMT3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_iSlpYD3iEd-rQL4FfV6WbQ _iSlpYT3iEd-rQL4FfV6WbQ _lXSJcD3iEd-rQL4FfV6WbQ _lXSJcT3iEd-rQL4FfV6WbQ _lXSJcj3iEd-rQL4FfV6WbQ _lXSJcz3iEd-rQL4FfV6WbQ _lXSJdD3iEd-rQL4FfV6WbQ _lXSJdT3iEd-rQL4FfV6WbQ _lXSJdj3iEd-rQL4FfV6WbQ _lXSJdz3iEd-rQL4FfV6WbQ _qEITET3iEd-rQL4FfV6WbQ _qEITEj3iEd-rQL4FfV6WbQ _qEITEz3iEd-rQL4FfV6WbQ _qEITFD3iEd-rQL4FfV6WbQ _qEITFT3iEd-rQL4FfV6WbQ _qEITFj3iEd-rQL4FfV6WbQ _qFLb8D3iEd-rQL4FfV6WbQ _qFLb8T3iEd-rQL4FfV6WbQ _qFLb8j3iEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_iSlpYD3iEd-rQL4FfV6WbQ" name="integrate_bre" guid="_iSlpYD3iEd-rQL4FfV6WbQ" presentationName="Integrate BRE within Service Layer" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_iSlpYT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_LvtSUT3iEd-rQL4FfV6WbQ" name="Iteration C1" guid="_LvtSUT3iEd-rQL4FfV6WbQ" presentationName="Iteration C1" superActivities="_4HDtMT3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_iSlpYD3iEd-rQL4FfV6WbQ _lXSJcD3iEd-rQL4FfV6WbQ _lXSJcT3iEd-rQL4FfV6WbQ _lXSJcj3iEd-rQL4FfV6WbQ _lXSJcz3iEd-rQL4FfV6WbQ _lXSJdD3iEd-rQL4FfV6WbQ _lXSJdz3iEd-rQL4FfV6WbQ _qEITET3iEd-rQL4FfV6WbQ _qEITEj3iEd-rQL4FfV6WbQ _qEITEz3iEd-rQL4FfV6WbQ _qEITFD3iEd-rQL4FfV6WbQ _qFLb8D3iEd-rQL4FfV6WbQ _qFLb8T3iEd-rQL4FfV6WbQ _qFLb8j3iEd-rQL4FfV6WbQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_iSlpYD3iEd-rQL4FfV6WbQ" name="integrate_bre" guid="_iSlpYD3iEd-rQL4FfV6WbQ" presentationName="Integrate BRE within Service Layer" briefDescription="The integration of the rule engine can be done in different approaches depending of the type of application, and architecture." superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-SPRTmKcOY8uhXSYUElJD_A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-SPRTmKcOY8uhXSYUElJD_A"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_IuFgEIm-Ed2dvb7--2nAHw"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_YRiuIItDEd2gksNyFVJN4g"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_6-p2EH_BEd2YWI_0AZcMOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_iSlpYT3iEd-rQL4FfV6WbQ" name="rule_architect" guid="_iSlpYT3iEd-rQL4FfV6WbQ" presentationName="Rule Architect" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJcD3iEd-rQL4FfV6WbQ" name="develop_unit_tests" guid="_lXSJcD3iEd-rQL4FfV6WbQ" presentationName="Develop Rule Unit Tests" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_lXSJdT3iEd-rQL4FfV6WbQ _lXSJdj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJcD3iEd-rQL4FfV6WbQ" name="develop_unit_tests" guid="_lXSJcD3iEd-rQL4FfV6WbQ" presentationName="Develop Rule Unit Tests" briefDescription="The goal of this task is to track down anomalies in the rules such as conflicts, redundancies or overlaps.
" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-xGdRIdwQIVt3-32feera7A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-xGdRIdwQIVt3-32feera7A"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ioCPkDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJcT3iEd-rQL4FfV6WbQ" name="develop_rules" guid="_lXSJcT3iEd-rQL4FfV6WbQ" presentationName="Develop Rules" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" output="_lXSJdz3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_lXSJdj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJcT3iEd-rQL4FfV6WbQ" name="develop_rules" guid="_lXSJcT3iEd-rQL4FfV6WbQ" presentationName="Develop Rules" briefDescription="This task is about developing each rule in the rule project." superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" output="_lXSJdz3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-K9no0Y8fd2qLSwFy6snYnw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-K9no0Y8fd2qLSwFy6snYnw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Y2CxEDzEEdyA6a_I80swHw"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_bsPp8ErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_qfzk4ErtEdyEE-k1R6LmOA"/>
@@ -393,83 +604,88 @@
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_zAvrMErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_GvK9oEruEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJcj3iEd-rQL4FfV6WbQ" name="enhance_object_models" guid="_lXSJcj3iEd-rQL4FfV6WbQ" presentationName="Enhance Object Models" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_lXSJdT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJcj3iEd-rQL4FfV6WbQ" name="enhance_object_models" guid="_lXSJcj3iEd-rQL4FfV6WbQ" presentationName="Enhance Object Models" briefDescription="The data model is started during the analysis and design tasks. But it will involve over time. So this activity supports the enhancement of the object models." superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-dbVJh3-7KeKo_CdIOQGj5Q" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-dbVJh3-7KeKo_CdIOQGj5Q"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_UXrv8Eb3EdySHMdInS9eGA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJcz3iEd-rQL4FfV6WbQ" name="execute_rule_set" guid="_lXSJcz3iEd-rQL4FfV6WbQ" presentationName="Execute Rule Set" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" output="_lXSJdz3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_lXSJdj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJcz3iEd-rQL4FfV6WbQ" name="execute_rule_set" guid="_lXSJcz3iEd-rQL4FfV6WbQ" presentationName="Execute Rule Set" briefDescription="Execute the tests to trigger the rule execution. Analyze the output logs. Report issues." superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" output="_lXSJdz3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-DSGeVrVTJjT0MRy0TvuDSw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-DSGeVrVTJjT0MRy0TvuDSw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_JCHfMEXhEdy14e5PT9v3HQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJdD3iEd-rQL4FfV6WbQ" name="log_issue" guid="_lXSJdD3iEd-rQL4FfV6WbQ" presentationName="Log Issue" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_lXSJdj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_lXSJdD3iEd-rQL4FfV6WbQ" name="log_issue" guid="_lXSJdD3iEd-rQL4FfV6WbQ" presentationName="Log Issue" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-QZu83uvVme58aHkxlEaTmQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-QZu83uvVme58aHkxlEaTmQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_yGbYIEb0EdySHMdInS9eGA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_lXSJdT3iEd-rQL4FfV6WbQ" name="developer" guid="_lXSJdT3iEd-rQL4FfV6WbQ" presentationName="Developer" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_lXSJdj3iEd-rQL4FfV6WbQ" name="rule_writer" guid="_lXSJdj3iEd-rQL4FfV6WbQ" presentationName="Rule Writer" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" modifies="_lXSJdz3iEd-rQL4FfV6WbQ" responsibleFor="_qFLb8D3iEd-rQL4FfV6WbQ _lXSJdz3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_lXSJdz3iEd-rQL4FfV6WbQ" name="ruleset" guid="_lXSJdz3iEd-rQL4FfV6WbQ" presentationName="Ruleset" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_lXSJdz3iEd-rQL4FfV6WbQ" name="ruleset" guid="_lXSJdz3iEd-rQL4FfV6WbQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-ebM0psxnCwWPQYF7YFMdWA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-ebM0psxnCwWPQYF7YFMdWA"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_qEITET3iEd-rQL4FfV6WbQ" name="execute_ruleset_functional_test" guid="_qEITET3iEd-rQL4FfV6WbQ" presentationName="Execute Rule Set Functional Tests" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" mandatoryInput="_lXSJdz3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_qEITFj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_qEITET3iEd-rQL4FfV6WbQ" name="execute_ruleset_functional_test" guid="_qEITET3iEd-rQL4FfV6WbQ" presentationName="Execute Rule Set Functional Tests" briefDescription="Validate the function supported by the rule set with end to end scenarios. This involve client code calling the rule service." superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" mandatoryInput="_lXSJdz3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-fVJV90U2K24PRA6BOiyuTg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-fVJV90U2K24PRA6BOiyuTg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_euAb8FtuEdykEsBjRsVfZw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_qEITEj3iEd-rQL4FfV6WbQ" name="get_rule_set_reports" guid="_qEITEj3iEd-rQL4FfV6WbQ" presentationName="Get Rule Set Reports" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" output="_qFLb8D3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_qEITFj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_qEITEj3iEd-rQL4FfV6WbQ" name="get_rule_set_reports" guid="_qEITEj3iEd-rQL4FfV6WbQ" presentationName="Get Rule Set Reports" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" output="_qFLb8D3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-drsUrP20wfWfu6engv0bvA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-drsUrP20wfWfu6engv0bvA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_LGd_MFtvEdykEsBjRsVfZw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_qEITEz3iEd-rQL4FfV6WbQ" name="get_sme_feedback" guid="_qEITEz3iEd-rQL4FfV6WbQ" presentationName="Get SME Feedback" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" mandatoryInput="_qFLb8D3iEd-rQL4FfV6WbQ" output="_qFLb8T3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_qEITFT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_qEITEz3iEd-rQL4FfV6WbQ" name="get_sme_feedback" guid="_qEITEz3iEd-rQL4FfV6WbQ" presentationName="Get SME Feedback" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" mandatoryInput="_qFLb8D3iEd-rQL4FfV6WbQ" output="_qFLb8T3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-sjX0ZCEDiQdwyXRi2_xwPg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-sjX0ZCEDiQdwyXRi2_xwPg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_CmBe4EtaEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_qEITFD3iEd-rQL4FfV6WbQ" name="test_analysis" guid="_qEITFD3iEd-rQL4FfV6WbQ" presentationName="Test Analysis" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" mandatoryInput="_qFLb8j3iEd-rQL4FfV6WbQ _qFLb8D3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_qEITFj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_qEITFD3iEd-rQL4FfV6WbQ" name="test_analysis" guid="_qEITFD3iEd-rQL4FfV6WbQ" presentationName="Test Analysis" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" mandatoryInput="_qFLb8j3iEd-rQL4FfV6WbQ _qFLb8D3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-spzcqoK0HWQUSwAvjzoRHQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-spzcqoK0HWQUSwAvjzoRHQ"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_OmI3QEtZEdyEE-k1R6LmOA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_cik88EtZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik88UtZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik880tZEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-Ad6YqvwEevWhaZQqLrL8Tw#_cik88ktZEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_qEITFT3iEd-rQL4FfV6WbQ" name="rule_analyst" guid="_qEITFT3iEd-rQL4FfV6WbQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" modifies="_qFLb8T3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_qEITFj3iEd-rQL4FfV6WbQ" name="tester" guid="_qEITFj3iEd-rQL4FfV6WbQ" presentationName="Tester" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ" modifies="_qFLb8D3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_qFLb8D3iEd-rQL4FfV6WbQ" name="rule_report" guid="_qFLb8D3iEd-rQL4FfV6WbQ" presentationName="Rule Report" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-DepNFUaxj7vgjyQjYJjMOQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-DepNFUaxj7vgjyQjYJjMOQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_arqeoUtZEdyEE-k1R6LmOA"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_qFLb8T3iEd-rQL4FfV6WbQ" name="sme_recommendations" guid="_qFLb8T3iEd-rQL4FfV6WbQ" presentationName="SME Recommendations" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-R2JrKH_RtyJIwW3nJszhMg" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-R2JrKH_RtyJIwW3nJszhMg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_BnlgsEtaEdyEE-k1R6LmOA"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_qFLb8j3iEd-rQL4FfV6WbQ" name="rsm_report" guid="_qFLb8j3iEd-rQL4FfV6WbQ" presentationName="RSM Report" isPlanned="false" superActivities="_LvtSUT3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-1E7v5wKf27pEV1Pu3M1c1g" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-1E7v5wKf27pEV1Pu3M1c1g"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_arqeoEtZEdyEE-k1R6LmOA"/>
</processElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUy7ekEd-D7YZN9NgldQ" name="Iteration Cn" guid="_9tgUy7ekEd-D7YZN9NgldQ">
<childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9tgUzLekEd-D7YZN9NgldQ" name="define_rule_governance" guid="_9tgUzLekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_59SkID3iEd-rQL4FfV6WbQ" name="define_rule_governance" guid="_59SkID3iEd-rQL4FfV6WbQ" presentationName="Define Rule Governance" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" breakdownElements="_59SkLz3iEd-rQL4FfV6WbQ _59SkMz3iEd-rQL4FfV6WbQ _59SkLD3iEd-rQL4FfV6WbQ _59SkIz3iEd-rQL4FfV6WbQ _59SkIj3iEd-rQL4FfV6WbQ _59SkLj3iEd-rQL4FfV6WbQ _59SkMD3iEd-rQL4FfV6WbQ _59SkMj3iEd-rQL4FfV6WbQ _54hY4T3iEd-rQL4FfV6WbQ _59SkJj3iEd-rQL4FfV6WbQ _59SkJT3iEd-rQL4FfV6WbQ _54hY4j3iEd-rQL4FfV6WbQ _59SkKz3iEd-rQL4FfV6WbQ _59SkJD3iEd-rQL4FfV6WbQ _59SkKj3iEd-rQL4FfV6WbQ _59SkKT3iEd-rQL4FfV6WbQ _59SkIT3iEd-rQL4FfV6WbQ _59SkMT3iEd-rQL4FfV6WbQ _59SkJz3iEd-rQL4FfV6WbQ _59SkLT3iEd-rQL4FfV6WbQ _59SkKD3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_59SkID3iEd-rQL4FfV6WbQ" name="define_rule_governance" guid="_59SkID3iEd-rQL4FfV6WbQ" presentationName="Define Rule Governance" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" breakdownElements="_59SkLz3iEd-rQL4FfV6WbQ _59SkMz3iEd-rQL4FfV6WbQ _59SkLD3iEd-rQL4FfV6WbQ _59SkIz3iEd-rQL4FfV6WbQ _59SkIj3iEd-rQL4FfV6WbQ _59SkLj3iEd-rQL4FfV6WbQ _59SkMD3iEd-rQL4FfV6WbQ _59SkMj3iEd-rQL4FfV6WbQ _54hY4T3iEd-rQL4FfV6WbQ _59SkIT3iEd-rQL4FfV6WbQ _59SkMT3iEd-rQL4FfV6WbQ _59SkJz3iEd-rQL4FfV6WbQ _59SkLT3iEd-rQL4FfV6WbQ _59SkKD3iEd-rQL4FfV6WbQ">
<presentation xmi:id="-qwh4CuVnjaLX6IHR9ARntQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-qwh4CuVnjaLX6IHR9ARntQ"/>
- <validContext href="uma://_T6l317ekEd-D7YZN9NgldQ#_PFU-AMVeEd2n6fDcl3UsZg"/>
+ <validContext href="uma://_jcxvKVmREeCcpdiAcH0w-w#_PFU-AMVeEd2n6fDcl3UsZg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkLz3iEd-rQL4FfV6WbQ" name="develop_organization_map" guid="_59SkLz3iEd-rQL4FfV6WbQ" presentationName="Develop Organization Map" superActivities="_59SkID3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_59SkJT3iEd-rQL4FfV6WbQ" output="_59SkIT3iEd-rQL4FfV6WbQ _59SkMT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkJj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkLz3iEd-rQL4FfV6WbQ" name="develop_organization_map" guid="_59SkLz3iEd-rQL4FfV6WbQ" presentationName="Develop Organization Map" briefDescription="The first task in rule governance consists in understanding the enterprise's organizational structure to help in defining the adequate rule governance actors and the Rule Management Team." superActivities="_59SkID3iEd-rQL4FfV6WbQ" output="_59SkIT3iEd-rQL4FfV6WbQ _59SkMT3iEd-rQL4FfV6WbQ">
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_fCRxoGDmEdyKlZvvtnMrMg"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_npFyQGDtEdyKlZvvtnMrMg"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_IFeJQKveEd2Pv_z50upsAg"/>
<selectedSteps href="uma://-AnRIdz0rPYyQVyzGVBxSqA#__8xccKvgEd2Pv_z50upsAg"/>
<selectedSteps href="uma://-AnRIdz0rPYyQVyzGVBxSqA#_MJLScKviEd2Pv_z50upsAg"/>
<selectedSteps href="uma://-AnRIdz0rPYyQVyzGVBxSqA#_U7ZWAKviEd2Pv_z50upsAg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkMz3iEd-rQL4FfV6WbQ" name="define_ruleset_ownership" guid="_59SkMz3iEd-rQL4FfV6WbQ" presentationName="Define Rule Set Ownership and Access Control" superActivities="_59SkID3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_59SkJj3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkJT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkMz3iEd-rQL4FfV6WbQ" name="define_ruleset_ownership" guid="_59SkMz3iEd-rQL4FfV6WbQ" presentationName="Define Rule Set Ownership and Access Control" briefDescription="For each rule set it has to be defined one owner and access control for team members and others. " superActivities="_59SkID3iEd-rQL4FfV6WbQ">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_O93X4KvzEd2Pv_z50upsAg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkLD3iEd-rQL4FfV6WbQ" name="define_policy_change_templates" guid="_59SkLD3iEd-rQL4FfV6WbQ" presentationName="Define Business Policy Change Templates" superActivities="_59SkID3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_59SkKT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkKz3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkLD3iEd-rQL4FfV6WbQ" name="define_policy_change_templates" guid="_59SkLD3iEd-rQL4FfV6WbQ" presentationName="Define Business Policy Change Templates" briefDescription="Define an inventory of probable ways in which the policies may or will change and with which frequency." superActivities="_59SkID3iEd-rQL4FfV6WbQ">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_tzUvgKv7Ed2Pv_z50upsAg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkIz3iEd-rQL4FfV6WbQ" name="define_rule_life_cycle" guid="_59SkIz3iEd-rQL4FfV6WbQ" presentationName="Define Rule Life Cycle" superActivities="_59SkID3iEd-rQL4FfV6WbQ" output="_59SkJz3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkJT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkIz3iEd-rQL4FfV6WbQ" name="define_rule_life_cycle" guid="_59SkIz3iEd-rQL4FfV6WbQ" presentationName="Define Rule Life Cycle" superActivities="_59SkID3iEd-rQL4FfV6WbQ" output="_59SkJz3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-barsvSUZoK-B2IRctfkyug" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-barsvSUZoK-B2IRctfkyug"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_RBu1YFH7Edy72tV0zV7--Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkIj3iEd-rQL4FfV6WbQ" name="define_ruleset_life_cycle" guid="_59SkIj3iEd-rQL4FfV6WbQ" presentationName="Define Rule Set Life Cycle " superActivities="_59SkID3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_54hY4j3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkJT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkIj3iEd-rQL4FfV6WbQ" name="define_ruleset_life_cycle" guid="_59SkIj3iEd-rQL4FfV6WbQ" presentationName="Define Rule Set Life Cycle " superActivities="_59SkID3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-zgwCbo2xDbSoVQ6xzPR8Jw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-zgwCbo2xDbSoVQ6xzPR8Jw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_RBu1YVH7Edy72tV0zV7--Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkLj3iEd-rQL4FfV6WbQ" name="plan_deployment" guid="_59SkLj3iEd-rQL4FfV6WbQ" presentationName="Plan Deployment" superActivities="_59SkID3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkJT3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkLj3iEd-rQL4FfV6WbQ" name="plan_deployment" guid="_59SkLj3iEd-rQL4FfV6WbQ" presentationName="Plan Deployment" briefDescription="Plan deployment procedures for the different platforms: testing, staging and production. Also plan for production monitoring. " superActivities="_59SkID3iEd-rQL4FfV6WbQ">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_E5968Kv8Ed2Pv_z50upsAg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkMD3iEd-rQL4FfV6WbQ" name="develop_process_maps" guid="_59SkMD3iEd-rQL4FfV6WbQ" presentationName="Develop Process Maps" superActivities="_59SkID3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_59SkJT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkJj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkMD3iEd-rQL4FfV6WbQ" name="develop_process_maps" guid="_59SkMD3iEd-rQL4FfV6WbQ" presentationName="Develop Process Maps" briefDescription="For each of the rule development and management processes, the architect should develop a process map to be followed during rule governance." superActivities="_59SkID3iEd-rQL4FfV6WbQ">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_deyUkKv8Ed2Pv_z50upsAg"/>
<selectedSteps href="uma://-aim_xTKZyZptD_PbMWAtVA#_9jqRIKy-Ed2aLdlF48Bk1g"/>
<selectedSteps href="uma://-aim_xTKZyZptD_PbMWAtVA#_K4JmAKy_Ed2aLdlF48Bk1g"/>
@@ -478,54 +694,42 @@
<selectedSteps href="uma://-aim_xTKZyZptD_PbMWAtVA#_rMlWsKy_Ed2aLdlF48Bk1g"/>
<selectedSteps href="uma://-aim_xTKZyZptD_PbMWAtVA#__pNL4Ky_Ed2aLdlF48Bk1g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkMj3iEd-rQL4FfV6WbQ" name="monitor_improve_process" guid="_59SkMj3iEd-rQL4FfV6WbQ" presentationName="Monitor and Improve Process" superActivities="_59SkID3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_59SkJT3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkJj3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_59SkMj3iEd-rQL4FfV6WbQ" name="monitor_improve_process" guid="_59SkMj3iEd-rQL4FfV6WbQ" presentationName="Monitor and Improve Process" briefDescription="Rule governance process should be monitored and improved to achieve better efficiency." superActivities="_59SkID3iEd-rQL4FfV6WbQ">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_w0x40KzAEd2aLdlF48Bk1g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_54hY4T3iEd-rQL4FfV6WbQ" name="maintain_rules" guid="_54hY4T3iEd-rQL4FfV6WbQ" presentationName="Maintain Rules" superActivities="_59SkID3iEd-rQL4FfV6WbQ" additionallyPerformedBy="_59SkKj3iEd-rQL4FfV6WbQ" mandatoryInput="_59SkLT3iEd-rQL4FfV6WbQ _59SkKD3iEd-rQL4FfV6WbQ" output="_59SkLT3iEd-rQL4FfV6WbQ _59SkKD3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_59SkKz3iEd-rQL4FfV6WbQ _59SkJD3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_54hY4T3iEd-rQL4FfV6WbQ" name="maintain_rules" guid="_54hY4T3iEd-rQL4FfV6WbQ" presentationName="Maintain Rules" briefDescription="The goal of this task is to maintain the rules in order to correct faults or improve performance." superActivities="_59SkID3iEd-rQL4FfV6WbQ" mandatoryInput="_59SkLT3iEd-rQL4FfV6WbQ _59SkKD3iEd-rQL4FfV6WbQ" output="_59SkLT3iEd-rQL4FfV6WbQ _59SkKD3iEd-rQL4FfV6WbQ">
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_z9ORcKnrEdyzmOHu2kw1UA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_59SkJj3iEd-rQL4FfV6WbQ" name="rule_steward" guid="_59SkJj3iEd-rQL4FfV6WbQ" presentationName="Rule Steward" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ" modifies="_59SkIT3iEd-rQL4FfV6WbQ _59SkMT3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_bYUkIJyiEd23W8_-Tub7Ww"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_59SkJT3iEd-rQL4FfV6WbQ" name="rule_architect" guid="_59SkJT3iEd-rQL4FfV6WbQ" presentationName="Rule Architect" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ" modifies="_59SkJz3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_JkVWIApyEdyKK5Go8zejMw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_54hY4j3iEd-rQL4FfV6WbQ" name="rule_administrator" guid="_54hY4j3iEd-rQL4FfV6WbQ" presentationName="Rule Administrator" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4QqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_59SkKz3iEd-rQL4FfV6WbQ" name="rule_analyst" guid="_59SkKz3iEd-rQL4FfV6WbQ" presentationName="Rule Analyst" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ" modifies="_59SkLT3iEd-rQL4FfV6WbQ _59SkKD3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4gqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_59SkJD3iEd-rQL4FfV6WbQ" name="rule_writer" guid="_59SkJD3iEd-rQL4FfV6WbQ" presentationName="Rule Writer" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ" modifies="_59SkLT3iEd-rQL4FfV6WbQ _59SkKD3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_59SkKj3iEd-rQL4FfV6WbQ" name="business_analyst" guid="_59SkKj3iEd-rQL4FfV6WbQ" presentationName="Business Analyst" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_Xh-X4AqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_59SkKT3iEd-rQL4FfV6WbQ" name="Subject Matter Expert" guid="_59SkKT3iEd-rQL4FfV6WbQ" presentationName="Subject Matter Expert" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII5AqBEdyPCr4G1Tb79A"/>
- </processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_59SkIT3iEd-rQL4FfV6WbQ" name="brms_organization_chart" guid="_59SkIT3iEd-rQL4FfV6WbQ" presentationName="Organization Chart" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-xR_MU1qVIqmI3vD8JwvX1A" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-xR_MU1qVIqmI3vD8JwvX1A"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#__hcZYGDrEdyKlZvvtnMrMg"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_59SkMT3iEd-rQL4FfV6WbQ" name="rule_governance_actors" guid="_59SkMT3iEd-rQL4FfV6WbQ" presentationName="Rule Governance Actors" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-0F1JpRACvQlhzf8uibcIKA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-0F1JpRACvQlhzf8uibcIKA"/>
+ <guidelines href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_npFyQGDtEdyKlZvvtnMrMg"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_VzXG0GDtEdyKlZvvtnMrMg"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_59SkJz3iEd-rQL4FfV6WbQ" name="rule_life_cycle" guid="_59SkJz3iEd-rQL4FfV6WbQ" presentationName="Rule Life Cycle" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-Hc7JvaQ0-snFgiJmpWD2OA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-Hc7JvaQ0-snFgiJmpWD2OA"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_DmUjsFH8Edy72tV0zV7--Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_59SkLT3iEd-rQL4FfV6WbQ" name="ruleset" guid="_59SkLT3iEd-rQL4FfV6WbQ" presentationName="Rule Set" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_59SkLT3iEd-rQL4FfV6WbQ" name="ruleset" guid="_59SkLT3iEd-rQL4FfV6WbQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-FS7huAe4PXfu1q_QQJGtIA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-FS7huAe4PXfu1q_QQJGtIA"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
<processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_59SkKD3iEd-rQL4FfV6WbQ" name="rule_repository_in_db" guid="_59SkKD3iEd-rQL4FfV6WbQ" presentationName="Rule Repository in DB" isPlanned="false" superActivities="_59SkID3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-6eacylaMdMYfqb7p28Owqw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-6eacylaMdMYfqb7p28Owqw"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_jqxtYFttEdykEsBjRsVfZw"/>
</processElements>
</childPackages>
- <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_NlH70T3iEd-rQL4FfV6WbQ" name="Iteration Cn" guid="_NlH70T3iEd-rQL4FfV6WbQ" presentationName="Iteration Cn" superActivities="_4HDtMT3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_59SkID3iEd-rQL4FfV6WbQ _Qz1eED3jEd-rQL4FfV6WbQ _Qz1eET3jEd-rQL4FfV6WbQ _Qz1eEj3jEd-rQL4FfV6WbQ _Qz1eEz3jEd-rQL4FfV6WbQ _Qz1eFD3jEd-rQL4FfV6WbQ _Qz1eFT3jEd-rQL4FfV6WbQ _Qz1eFj3jEd-rQL4FfV6WbQ _SI7BsD3jEd-rQL4FfV6WbQ _SI7BsT3jEd-rQL4FfV6WbQ"/>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Qz1eED3jEd-rQL4FfV6WbQ" name="develop_unit_tests" guid="_Qz1eED3jEd-rQL4FfV6WbQ" presentationName="Develop Rule Unit Tests" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_Qz1eFD3jEd-rQL4FfV6WbQ _Qz1eFT3jEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_NlH70T3iEd-rQL4FfV6WbQ" name="Iteration Cn" guid="_NlH70T3iEd-rQL4FfV6WbQ" presentationName="Iteration Cn" superActivities="_4HDtMT3gEd-rQL4FfV6WbQ" isRepeatable="true" breakdownElements="_59SkID3iEd-rQL4FfV6WbQ _Qz1eED3jEd-rQL4FfV6WbQ _Qz1eET3jEd-rQL4FfV6WbQ _Qz1eEj3jEd-rQL4FfV6WbQ _Qz1eEz3jEd-rQL4FfV6WbQ _Qz1eFj3jEd-rQL4FfV6WbQ _SI7BsD3jEd-rQL4FfV6WbQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Qz1eED3jEd-rQL4FfV6WbQ" name="develop_unit_tests" guid="_Qz1eED3jEd-rQL4FfV6WbQ" presentationName="Develop Rule Unit Tests" briefDescription="The goal of this task is to track down anomalies in the rules such as conflicts, redundancies or overlaps.
" superActivities="_NlH70T3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-EQNfnV9bxYjmfZMCotuUHA" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-EQNfnV9bxYjmfZMCotuUHA"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_ioCPkDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Qz1eET3jEd-rQL4FfV6WbQ" name="develop_rules" guid="_Qz1eET3jEd-rQL4FfV6WbQ" presentationName="Develop Rules" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" output="_Qz1eFj3jEd-rQL4FfV6WbQ" performedPrimarilyBy="_Qz1eFT3jEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Qz1eET3jEd-rQL4FfV6WbQ" name="develop_rules" guid="_Qz1eET3jEd-rQL4FfV6WbQ" presentationName="Develop Rules" briefDescription="This task is about developing each rule in the rule project." superActivities="_NlH70T3iEd-rQL4FfV6WbQ" output="_Qz1eFj3jEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-eivV0I3d5NflWdDxFN11Iw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-eivV0I3d5NflWdDxFN11Iw"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_Y2CxEDzEEdyA6a_I80swHw"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_bsPp8ErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_qfzk4ErtEdyEE-k1R6LmOA"/>
@@ -533,27 +737,23 @@
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_zAvrMErtEdyEE-k1R6LmOA"/>
<selectedSteps href="uma://-J2_dBqOPRwbukM0MbrxpRg#_GvK9oEruEdyEE-k1R6LmOA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Qz1eEj3jEd-rQL4FfV6WbQ" name="enhance_object_models" guid="_Qz1eEj3jEd-rQL4FfV6WbQ" presentationName="Enhance Object Models" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" performedPrimarilyBy="_Qz1eFD3jEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Qz1eEj3jEd-rQL4FfV6WbQ" name="enhance_object_models" guid="_Qz1eEj3jEd-rQL4FfV6WbQ" presentationName="Enhance Object Models" briefDescription="The data model is started during the analysis and design tasks. But it will involve over time. So this activity supports the enhancement of the object models." superActivities="_NlH70T3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-JW1SrN4HN2vfMWdXhwx0ww" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-JW1SrN4HN2vfMWdXhwx0ww"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_UXrv8Eb3EdySHMdInS9eGA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Qz1eEz3jEd-rQL4FfV6WbQ" name="execute_rule_set" guid="_Qz1eEz3jEd-rQL4FfV6WbQ" presentationName="Execute Rule Set" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" output="_Qz1eFj3jEd-rQL4FfV6WbQ" performedPrimarilyBy="_Qz1eFT3jEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Qz1eEz3jEd-rQL4FfV6WbQ" name="execute_rule_set" guid="_Qz1eEz3jEd-rQL4FfV6WbQ" presentationName="Execute Rule Set" briefDescription="Execute the tests to trigger the rule execution. Analyze the output logs. Report issues." superActivities="_NlH70T3iEd-rQL4FfV6WbQ" output="_Qz1eFj3jEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-sq25iSf421_q4x2ZbYXkKQ" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-sq25iSf421_q4x2ZbYXkKQ"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_JCHfMEXhEdy14e5PT9v3HQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Qz1eFD3jEd-rQL4FfV6WbQ" name="developer" guid="_Qz1eFD3jEd-rQL4FfV6WbQ" presentationName="Developer" isPlanned="false" superActivities="_NlH70T3iEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Qz1eFT3jEd-rQL4FfV6WbQ" name="rule_writer" guid="_Qz1eFT3jEd-rQL4FfV6WbQ" presentationName="Rule Writer" isPlanned="false" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" modifies="_Qz1eFj3jEd-rQL4FfV6WbQ" responsibleFor="_Qz1eFj3jEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4wqBEdyPCr4G1Tb79A"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Qz1eFj3jEd-rQL4FfV6WbQ" name="ruleset" guid="_Qz1eFj3jEd-rQL4FfV6WbQ" presentationName="Ruleset" isPlanned="false" superActivities="_NlH70T3iEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Qz1eFj3jEd-rQL4FfV6WbQ" name="ruleset" guid="_Qz1eFj3jEd-rQL4FfV6WbQ" presentationName="Ruleset" briefDescription="Set of rule as a standalone component executed by a rule engine. " isPlanned="false" superActivities="_NlH70T3iEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-RjvG1D-ZAteachI2o5oCQw" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-RjvG1D-ZAteachI2o5oCQw"/>
+ <templates href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_mqnOETmsEdy8N6BRpa8ByQ"/>
<WorkProduct href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_vjWPcDzEEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_SI7BsD3jEd-rQL4FfV6WbQ" name="deploy_rules" guid="_SI7BsD3jEd-rQL4FfV6WbQ" presentationName="Deploy Rules" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" mandatoryInput="_Qz1eFj3jEd-rQL4FfV6WbQ" output="_Qz1eFj3jEd-rQL4FfV6WbQ" performedPrimarilyBy="_SI7BsT3jEd-rQL4FfV6WbQ _Qz1eFT3jEd-rQL4FfV6WbQ">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_SI7BsD3jEd-rQL4FfV6WbQ" name="deploy_rules" guid="_SI7BsD3jEd-rQL4FfV6WbQ" presentationName="Deploy Rules" briefDescription="Deploy rule set in the integrated core application" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" mandatoryInput="_Qz1eFj3jEd-rQL4FfV6WbQ" output="_Qz1eFj3jEd-rQL4FfV6WbQ">
+ <presentation xmi:id="-gXDJs-AADHuo-Up6bT4Vow" href="uma://-qwh4CuVnjaLX6IHR9ARntQ#-gXDJs-AADHuo-Up6bT4Vow"/>
<Task href="uma://_XLuWYHn8Ed2ozs6whO3m5w#_AgQVAD5QEdyA6a_I80swHw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_SI7BsT3jEd-rQL4FfV6WbQ" name="rule_administrator" guid="_SI7BsT3jEd-rQL4FfV6WbQ" presentationName="Rule Administrator" isPlanned="false" superActivities="_NlH70T3iEd-rQL4FfV6WbQ" modifies="_Qz1eFj3jEd-rQL4FfV6WbQ">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_XiII4QqBEdyPCr4G1Tb79A"/>
- </processElements>
</childPackages>
<processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_4HDtMT3gEd-rQL4FfV6WbQ" name="Construction" guid="_4HDtMT3gEd-rQL4FfV6WbQ" presentationName="Construction" superActivities="_iVgFYT3gEd-rQL4FfV6WbQ" breakdownElements="_LvtSUT3iEd-rQL4FfV6WbQ _NlH70T3iEd-rQL4FfV6WbQ"/>
</childPackages>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/agree_technical_approach/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/agree_technical_approach/content.xmi
index a73d84b..2542f8e 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/agree_technical_approach/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/agree_technical_approach/content.xmi
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-BZ8afnvoVBJs82vzcOBaCw" name="agree_technical_approach,_4ouDUdOEEdyqlogshP8l4g" guid="-BZ8afnvoVBJs82vzcOBaCw" version="7.2.0">
- <mainDescription><p>
+<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="-BZ8afnvoVBJs82vzcOBaCw" name="agree_technical_approach,_4ouDUdOEEdyqlogshP8l4g" guid="-BZ8afnvoVBJs82vzcOBaCw" version="7.2.0">
+ <mainDescription><p>
The goal of this activity is to define a technical approach to the system that supports the project requirements,
within the constraints placed on the system and the development team. The architect should do the following:
</p>
@@ -30,12 +31,75 @@
demonstrate its viability to the customer. This allows the project to move forward, enabling you to refine and baseline
the architecture.
</p></mainDescription>
- <howtoStaff><p>
+ <howtoStaff><p>
This activity is best carried out collaboratively by the team, with the architect acting as a focal point for
coordinating and facilitating the decisions.
</p></howtoStaff>
- <usageNotes><p>
+ <usageNotes><p>
The major effort occurs early in the project; thereafter, you should assess the system regularly to ensure that the
design is still on track with the architecture.
</p></usageNotes>
-</org.eclipse.epf.uma:ProcessDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-5pBUhaIFdJ75MLPerQSnoA" name="architecture_notebook,_BWf5gtOKEdyqlogshP8l4g" guid="-5pBUhaIFdJ75MLPerQSnoA">
+ <refinedDescription><p>
+ This artifact&nbsp;describes the <a class="elementLink"
+ href="./../../core.tech.common.extend_supp/guidances/concepts/software_architecture_59A08DE0.html"
+ guid="__O7tAMVvEduLYZUGfgZrkQ">Software Architecture</a>.
+</p>
+<p>
+ It provides a place for maintaining the list of architectural issues, along with the associated architectural
+ decisions, designs, patterns, code documented (or pointed to), and so forth -- all at appropriate levels to make it
+ easy to understand what architectural decisions have been made and remain to be made.
+</p>
+<p>
+ It is helpful for architects to use this artifact to collaborate with other team members in developing the architecture
+ and to help team members understand the motivation behind architectural decisions so that those decisions can be
+ robustly implemented. For example, the architect may put constraints on how data is packaged and communicated between
+ different parts of the system. This may appear to be a burden, but the justification in the Architecture Notebook can
+ explain that there is a significant performance bottleneck when communicating with a legacy system. The rest of the
+ system must adapt to this bottleneck by following a specific data packaging scheme.
+</p>
+<p>
+ This artifact should also inform the team members how the system is partitioned or organized so that the team can adapt
+ to the needs of the system. It also gives a first glimpse of the system and its technical motivations to whoever must
+ maintain and change the architecture later.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-raSQ2CIQMJXnNHFqWWi7Kg" name="envision_the_arch,_sjccUN_1EdyOsumnGvWsEg" guid="-raSQ2CIQMJXnNHFqWWi7Kg">
+ <keyConsiderations><p>
+ It&nbsp;is important to reduce the complexity of the&nbsp;solution by raising the levels of abstraction.&nbsp;For more
+ information, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.extend_supp/guidances/guidelines/abstract_away_complexity_DBF13AE6.html"
+ guid="_we3F4ACpEdu8m4dIntu6jA">Guideline: Abstract Away Complexity</a>.
+</p>
+<p>
+ It is critical that this task be performed collaboratively with active involvement of other team members and project
+ stakeholders so that consensus and common understanding is reached. It is particularly vital to involve the
+ developer(s) throughout this task. The architecture effort&nbsp;is about providing leadership and coordination of the
+ technical work rather than putting in a solo performance.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This task focuses on envisioning the initial architecture and outlining the&nbsp;architectural decisions that will
+ guide development and testing. It relies on gathering experience gained in similar systems or problem domains to
+ constrain and focus the architecture so that effort is not wasted in re-inventing architecture.
+</p>
+<p>
+ The results are captured for future reference and are communicated across the team. It is important that the team has
+ enough information to understand the technical approach being taken.
+</p>
+<p>
+ The architecture evolves organically over time by outlining and refining portions of it. A few people get together in a
+ room and sketch out what they think the architecture will be. This envisioning effort sets the foundation for
+ prototyping. If the solution is similar to a previously produced solution (or is a well-known solution domain), then it
+ will probably be good enough to reference that example as evidence of the feasibility of the approach. In some cases,
+ it may be necessary to develop one or more prototypes to validate some of the decisions or clarify some of the
+ requirements.
+</p>
+<p>
+ The work done here does not seek to produce a detailed and comprehensive technical specification for the system.
+ Rather, the approach should be to decide the overall technical approach at a high level. The conclusion of this work
+ should produce just enough information to communicate the architecture to the team, and to demonstrate its viability to
+ the customer. This allows the project to move forward, enabling you to refine and baseline the architecture.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/agree_technical_approach/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/agree_technical_approach/model.xmi
index 019a344..e9dc68b 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/agree_technical_approach/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/agree_technical_approach/model.xmi
@@ -2,30 +2,30 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__f8iwbekEd-D7YZN9NgldQ" guid="__f8iwbekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__f8iwrekEd-D7YZN9NgldQ" id="-BZ8afnvoVBJs82vzcOBaCw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_UzK2cVmQEeCcpdiAcH0w-w" id="-5pBUhaIFdJ75MLPerQSnoA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_UzK2clmQEeCcpdiAcH0w-w" id="-raSQ2CIQMJXnNHFqWWi7Kg" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_4ouDUNOEEdyqlogshP8l4g" name="agree_technical_approach" guid="_4ouDUNOEEdyqlogshP8l4g">
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_BWWIgdOKEdyqlogshP8l4g" name="architect" guid="_BWWIgdOKEdyqlogshP8l4g" presentationName="Architect" isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g" modifies="_BWf5gtOKEdyqlogshP8l4g" responsibleFor="_BWf5gtOKEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_BWf5gtOKEdyqlogshP8l4g" name="architecture_notebook" guid="_BWf5gtOKEdyqlogshP8l4g" presentationName="Architecture Notebook" isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_BWf5gtOKEdyqlogshP8l4g" name="architecture_notebook" guid="_BWf5gtOKEdyqlogshP8l4g" presentationName="Architecture Notebook" briefDescription="This artifact describes the rationale, assumptions, explanation, and implications of the decisions that were made in forming the architecture." isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-5pBUhaIFdJ75MLPerQSnoA" href="uma://-BZ8afnvoVBJs82vzcOBaCw#-5pBUhaIFdJ75MLPerQSnoA"/>
+ <checklists href="uma://_4gaS4LPREduocbW-TPTq7A#_17PYUNd6EdmIm-bsRSNCgw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ <templates href="uma://_4gaS4LPREduocbW-TPTq7A#_me8WcAANEdyRS9uciXlZ6g"/>
<WorkProduct href="uma://_4gaS4LPREduocbW-TPTq7A#_0XAf0MlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_n75CcdfeEdy8T_PKWvNDBA" name="analyst" guid="_n75CcdfeEdy8T_PKWvNDBA" presentationName="Analyst" isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_n75CctfeEdy8T_PKWvNDBA" name="developer" guid="_n75CctfeEdy8T_PKWvNDBA" presentationName="Developer" isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_n75Cc9feEdy8T_PKWvNDBA" name="project_manager" guid="_n75Cc9feEdy8T_PKWvNDBA" presentationName="Project Manager" isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_n75CdNfeEdy8T_PKWvNDBA" name="stakeholder" guid="_n75CdNfeEdy8T_PKWvNDBA" presentationName="Stakeholder" isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_n75CddfeEdy8T_PKWvNDBA" name="technical_specification_slot" guid="_n75CddfeEdy8T_PKWvNDBA" presentationName="[Technical Specification]" isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_n75CddfeEdy8T_PKWvNDBA" name="technical_specification_slot" guid="_n75CddfeEdy8T_PKWvNDBA" presentationName="[Technical Specification]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe requirements, constraints, and goals for the solution." isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_sjccUN_1EdyOsumnGvWsEg" name="envision_the_arch" guid="_sjccUN_1EdyOsumnGvWsEg" presentationName="Envision the Architecture" superActivities="_4ouDUdOEEdyqlogshP8l4g" additionallyPerformedBy="_n75CcdfeEdy8T_PKWvNDBA _n75CctfeEdy8T_PKWvNDBA _n75Cc9feEdy8T_PKWvNDBA _n75CdNfeEdy8T_PKWvNDBA" mandatoryInput="_n75CddfeEdy8T_PKWvNDBA" optionalInput="_BWf5gtOKEdyqlogshP8l4g" output="_BWf5gtOKEdyqlogshP8l4g" performedPrimarilyBy="_BWWIgdOKEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_sjccUN_1EdyOsumnGvWsEg" name="envision_the_arch" guid="_sjccUN_1EdyOsumnGvWsEg" presentationName="Envision the Architecture" briefDescription="This task is where the "vision" for the architecture is developed through analysis of the architecturally significant requirements and identification of architectural constraints, decisions and objectives." superActivities="_4ouDUdOEEdyqlogshP8l4g" mandatoryInput="_n75CddfeEdy8T_PKWvNDBA" optionalInput="_BWf5gtOKEdyqlogshP8l4g" output="_BWf5gtOKEdyqlogshP8l4g">
+ <presentation xmi:id="-raSQ2CIQMJXnNHFqWWi7Kg" href="uma://-BZ8afnvoVBJs82vzcOBaCw#-raSQ2CIQMJXnNHFqWWi7Kg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_HrZGIA4MEduibvKwrGxWxA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_HlRqANpbEdyP58ppo1Ieaw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_jdKSsNpiEdyP58ppo1Ieaw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_pLEGUNqGEdy88NBoQgfGyg"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gpkAMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_we3F4ACpEdu8m4dIntu6jA"/>
<Task href="uma://_4gaS4LPREduocbW-TPTq7A#_0f-1oMlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_3nMQQA3rEduibvKwrGxWxA"/>
<selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_f0y2kM25Edym_ZFqrJcXUg"/>
@@ -39,7 +39,7 @@
<selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_Q2PRIFHSEd2zrOgIte8oWg"/>
<selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_Xia1QFHSEd2zrOgIte8oWg"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_4ouDUdOEEdyqlogshP8l4g" name="agree_technical_approach" guid="_4ouDUdOEEdyqlogshP8l4g" presentationName="Agree on Technical Approach" briefDescription="Reach agreement on a viable technical approach to developing the solution." breakdownElements="_BWWIgdOKEdyqlogshP8l4g _BWf5gtOKEdyqlogshP8l4g _n75CcdfeEdy8T_PKWvNDBA _n75CctfeEdy8T_PKWvNDBA _n75Cc9feEdy8T_PKWvNDBA _n75CdNfeEdy8T_PKWvNDBA _n75CddfeEdy8T_PKWvNDBA _sjccUN_1EdyOsumnGvWsEg">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_4ouDUdOEEdyqlogshP8l4g" name="agree_technical_approach" guid="_4ouDUdOEEdyqlogshP8l4g" presentationName="Agree on Technical Approach" briefDescription="Reach agreement on a viable technical approach to developing the solution." breakdownElements="_BWf5gtOKEdyqlogshP8l4g _n75CddfeEdy8T_PKWvNDBA _sjccUN_1EdyOsumnGvWsEg">
<presentation xmi:id="-BZ8afnvoVBJs82vzcOBaCw" href="uma://-BZ8afnvoVBJs82vzcOBaCw#-BZ8afnvoVBJs82vzcOBaCw"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi
index 8e2b53f..6c52655 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi
@@ -68,4 +68,107 @@
</tbody>
</table></mainDescription>
</org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ZgdHcIUeC0fczWjxdRhZmQ" name="system_wide_requirements,_AQJYp9OOEdyqlogshP8l4g" guid="-ZgdHcIUeC0fczWjxdRhZmQ">
+ <keyConsiderations><ul>
+ <li>
+ When you document system-wide requirements, ensure that the needs of all of the stakeholders are represented. In
+ particular, include the needs of those who are responsible for maintaining or supporting the system after it is
+ delivered.
+ </li>
+ <li>
+ Typically, there are some overlaps and gray areas between system-wide requirements and other requirements work
+ products. For example, the authorization behavior of a system can be specified as use cases or as statements within
+ system-wide requirements. The overall driving need is that no important requirements are missed or duplicated, and
+ that there is an agreed upon approach for capturing and processing every type of requirement.
+ </li>
+ <li>
+ System-wide requirements originate from many places. Documenting the source of the requirement is particularly
+ important when you separate externally mandated requirements.
+ </li>
+ <li>
+ Requirements are often thought of as "Qualitative" (specifying a quality or desirable characteristic) versus
+ "Quantitative" (specifying a quantity). Qualitative requirements can sometimes be elaborated into quantitative
+ requirements.
+ </li>
+ <li>
+ A good quality requirement is one that you can verify, either through testing or some other objective evaluation.
+ </li>
+ <li>
+ You must evaluate system-wide requirements for cost, schedule impact, and level of contribution to business goals.
+ Based on your evaluation, the system-wide requirements should be iteratively challenged, defended, and amended.
+ </li>
+</ul></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-LXsJtWauw8OXFBPA5LtlUw" name="glossary,_AQJYqdOOEdyqlogshP8l4g" guid="-LXsJtWauw8OXFBPA5LtlUw">
+ <keyConsiderations><p>
+ Although listed as an <i>output from</i> and an <i>input to</i> tasks associated with the requirements discipline, this
+ artifact can be updated at any time and by any role as new terms are identified. The terms defined should be used
+ according to the recorded definitions in all project documentation so that all stakeholders can clearly see that terms
+ are being used consistently.
+</p>
+<p>
+ One of the primary decisions when developing&nbsp;this artifact&nbsp;is whether to have all terms in a single glossary
+ or to maintain terms in several glossaries, business terms artifacts, or models.&nbsp;If terms are defined in multiple
+ places, you need to communicate all of those sources to the team and decide which take precedence.
+</p>
+<p>
+ It may be important, even in small projects, to reference and use existing broader glossaries, business terms
+ artifacts, or data models, where they exist.
+</p>
+<p>
+ Industry- and organization-wide glossaries may be referenced, and compliance with such specific chosen standards may be
+ required.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This artifact&nbsp;helps you avoid miscommunication by providing two essential resources:
+</p>
+<ul>
+ <li>
+ A central location to look for terms and abbreviations that are new to development team members
+ </li>
+ <li>
+ Definitions of terms that are used in specific ways within the domain
+ </li>
+</ul>
+<p>
+ Definitions for the glossary terms come from several sources, such as requirements documents, specifications, and
+ discussions with stakeholders and domain experts.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-M0XmBkehezZMI-pmbjQ9SA" name="detail_use_case_scenarios,_AVhA0NOOEdyqlogshP8l4g" guid="-M0XmBkehezZMI-pmbjQ9SA">
+ <keyConsiderations><p>
+ To avoid unnecessary rework, only those use-case scenarios that are scheduled for implementation in the near term (in
+ the next iteration or two)&nbsp;must be detailed.&nbsp;
+</p>
+<p>
+ Not all use-case scenarios require detailing.
+</p></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-p2uRMHIOQI2c6fLh6CUIbw" name="detail_system_wide_requirements,_AVhA0dOOEdyqlogshP8l4g" guid="-p2uRMHIOQI2c6fLh6CUIbw">
+ <keyConsiderations>To avoid unnecessary rework, only those requirements that are scheduled for implementation in the near term (in the next
+iteration or two)&nbsp;must be detailed.</keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-nIF2UE5rqiDXuJIzOZcQuA" name="create_test_cases,_AVhA0tOOEdyqlogshP8l4g" guid="-nIF2UE5rqiDXuJIzOZcQuA">
+ <keyConsiderations><p>
+ Develop test cases in parallel with requirements so that Analysts and Stakeholders can agree with the specific
+ conditions of satisfaction for each requirement. The test cases act as acceptance criteria by expanding on the intent
+ of the system&nbsp;through actual scenarios of use.&nbsp;This allows team members to measure progress in terms of
+ passing test cases.&nbsp;
+</p></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-vyRUbVNrluvyfjsHPKp2fw" name="test_case,_AVhA1NOOEdyqlogshP8l4g" guid="-vyRUbVNrluvyfjsHPKp2fw">
+ <refinedDescription><p>
+ A test case specifies the conditions that must be validated to enable an assessment of aspects of the system under
+ test. A test case is more formal than a test idea; typically, a test case takes the form of a specification. In less
+ formal environments, you can create test cases by identifying a unique ID, name, associated test data, and expected
+ results.
+</p>
+<p>
+ Test cases can be derived from many sources, and typically include a subset of the requirements (such as use cases,
+ performance characteristics, and reliability concerns) and other types of quality attributes. For more information on
+ types of tests and their relationships to quality test attributes, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.extend_supp/guidances/concepts/testing_qualitative_rqmts_CAE80710.html"
+ guid="_0aJ6cMlgEdmt3adZL5Dmdw">Concept: Testing Qualitative Requirements</a>.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/model.xmi
index 5a68065..72a2443 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/model.xmi
@@ -3,68 +3,84 @@
<org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="__fM74bekEd-D7YZN9NgldQ" guid="__fM74bekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__fM74rekEd-D7YZN9NgldQ" id="-2VY1Jl_Sw2Mmk8IfX0ONNw" uri="content.xmi"/>
<resourceDescriptors xmi:id="__fM747ekEd-D7YZN9NgldQ" id="-pszgT2UQY1AzlzJLFM1S5g" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_Nun1oFmQEeCcpdiAcH0w-w" id="-ZgdHcIUeC0fczWjxdRhZmQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_NvD6gFmQEeCcpdiAcH0w-w" id="-LXsJtWauw8OXFBPA5LtlUw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_NvD6gVmQEeCcpdiAcH0w-w" id="-M0XmBkehezZMI-pmbjQ9SA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_NvD6glmQEeCcpdiAcH0w-w" id="-p2uRMHIOQI2c6fLh6CUIbw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_NvNrgFmQEeCcpdiAcH0w-w" id="-nIF2UE5rqiDXuJIzOZcQuA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_NvNrgVmQEeCcpdiAcH0w-w" id="-vyRUbVNrluvyfjsHPKp2fw" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_RQi0ANONEdyqlogshP8l4g" name="construction_phase_iteration" guid="_RQi0ANONEdyqlogshP8l4g">
- <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AsLekEd-D7YZN9NgldQ" guid="_9t9AsLekEd-D7YZN9NgldQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AsLekEd-D7YZN9NgldQ" name="plan_manage_iteration" guid="_9t9AsLekEd-D7YZN9NgldQ">
<processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_3s7aYdONEdyqlogshP8l4g" name="plan_manage_iteration" guid="_3s7aYdONEdyqlogshP8l4g" superActivities="_RQi0AdONEdyqlogshP8l4g" variabilityType="extends">
<variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern" href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsdOEEdyqlogshP8l4g"/>
</processElements>
</childPackages>
- <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AsbekEd-D7YZN9NgldQ" guid="_9t9AsbekEd-D7YZN9NgldQ">
- <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_AP_nodOOEdyqlogshP8l4g" name="identify_and_refine_requirements" guid="_AP_nodOOEdyqlogshP8l4g" presentationName="Identify and Refine Requirements" superActivities="_RQi0AdONEdyqlogshP8l4g" breakdownElements="_AQJYodOOEdyqlogshP8l4g _AQJYotOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g _AQJYpdOOEdyqlogshP8l4g _AQJYp9OOEdyqlogshP8l4g _AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqtOOEdyqlogshP8l4g _AQJYoNOOEdyqlogshP8l4g _AVhA0NOOEdyqlogshP8l4g _AVhA0dOOEdyqlogshP8l4g _AVhA0tOOEdyqlogshP8l4g _AVhA09OOEdyqlogshP8l4g _AVhA1NOOEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AsbekEd-D7YZN9NgldQ" name="identify_and_refine_requirements" guid="_9t9AsbekEd-D7YZN9NgldQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_AP_nodOOEdyqlogshP8l4g" name="identify_and_refine_requirements" guid="_AP_nodOOEdyqlogshP8l4g" presentationName="Identify and Refine Requirements" superActivities="_RQi0AdONEdyqlogshP8l4g" breakdownElements="_AQJYp9OOEdyqlogshP8l4g _AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqtOOEdyqlogshP8l4g _AQJYoNOOEdyqlogshP8l4g _AVhA0NOOEdyqlogshP8l4g _AVhA0dOOEdyqlogshP8l4g _AVhA0tOOEdyqlogshP8l4g _AVhA09OOEdyqlogshP8l4g _AVhA1NOOEdyqlogshP8l4g">
<presentation xmi:id="-2VY1Jl_Sw2Mmk8IfX0ONNw" href="uma://-2VY1Jl_Sw2Mmk8IfX0ONNw#-2VY1Jl_Sw2Mmk8IfX0ONNw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYodOOEdyqlogshP8l4g" name="analyst" guid="_AQJYodOOEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g" modifies="_AQJYp9OOEdyqlogshP8l4g _AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqtOOEdyqlogshP8l4g" responsibleFor="_AQJYqtOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqNOOEdyqlogshP8l4g _AQJYp9OOEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYotOOEdyqlogshP8l4g" name="architect" guid="_AQJYotOOEdyqlogshP8l4g" presentationName="Architect" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYo9OOEdyqlogshP8l4g" name="developer" guid="_AQJYo9OOEdyqlogshP8l4g" presentationName="Developer" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYpNOOEdyqlogshP8l4g" name="stakeholder" guid="_AQJYpNOOEdyqlogshP8l4g" presentationName="Stakeholder" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYpdOOEdyqlogshP8l4g" name="tester" guid="_AQJYpdOOEdyqlogshP8l4g" presentationName="Tester" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g" modifies="_AVhA1NOOEdyqlogshP8l4g" responsibleFor="_AVhA1NOOEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYp9OOEdyqlogshP8l4g" name="system_wide_requirements" guid="_AQJYp9OOEdyqlogshP8l4g" presentationName="System-WideRequirements" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYp9OOEdyqlogshP8l4g" name="system_wide_requirements" guid="_AQJYp9OOEdyqlogshP8l4g" presentationName="System-Wide Requirements" briefDescription="This artifact captures the quality attributes and constraints that have system-wide scope. It also captures system-wide functional requirements." isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <presentation xmi:id="-ZgdHcIUeC0fczWjxdRhZmQ" href="uma://-2VY1Jl_Sw2Mmk8IfX0ONNw#-ZgdHcIUeC0fczWjxdRhZmQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_6jXzYNcKEdqz_d2XWoVt6Q"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_m7p-AI5fEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqNOOEdyqlogshP8l4g" name="use_case" guid="_AQJYqNOOEdyqlogshP8l4g" presentationName="Use Case" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqNOOEdyqlogshP8l4g" name="use_case" guid="_AQJYqNOOEdyqlogshP8l4g" presentationName="Use Case" briefDescription="This artifact captures the system behavior to yield an observable result of value to those who interact with the system." isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kNwINk1Edq2Q8qZoWbvGA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_JLOiIMNvEdu2IdAIaWZyAw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_3Y3XUI5fEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqdOOEdyqlogshP8l4g" name="glossary" guid="_AQJYqdOOEdyqlogshP8l4g" presentationName="Glossary" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqdOOEdyqlogshP8l4g" name="glossary" guid="_AQJYqdOOEdyqlogshP8l4g" presentationName="Glossary" briefDescription="This artifact defines important terms used by the project. The collection of terms clarifies the vocabulary used on the project." isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <presentation xmi:id="-LXsJtWauw8OXFBPA5LtlUw" href="uma://-2VY1Jl_Sw2Mmk8IfX0ONNw#-LXsJtWauw8OXFBPA5LtlUw"/>
<WorkProduct href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqtOOEdyqlogshP8l4g" name="use_case_model" guid="_AQJYqtOOEdyqlogshP8l4g" presentationName="Use-Case Model" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqtOOEdyqlogshP8l4g" name="use_case_model" guid="_AQJYqtOOEdyqlogshP8l4g" presentationName="Use-Case Model" briefDescription="This artifact captures a model of the intended functions and environment of the system and serves as a contract between the customer and the team." isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AQJYoNOOEdyqlogshP8l4g" name="identify_and_outline_requirements" guid="_AQJYoNOOEdyqlogshP8l4g" presentationName="Identify and Outline Requirements" superActivities="_AP_nodOOEdyqlogshP8l4g" additionallyPerformedBy="_AQJYotOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g _AQJYpdOOEdyqlogshP8l4g" optionalInput="_AVhA09OOEdyqlogshP8l4g" output="_AQJYp9OOEdyqlogshP8l4g _AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqtOOEdyqlogshP8l4g" performedPrimarilyBy="_AQJYodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AQJYoNOOEdyqlogshP8l4g" name="identify_and_outline_requirements" guid="_AQJYoNOOEdyqlogshP8l4g" presentationName="Identify and Outline Requirements" briefDescription="This task describes how to identify and outline the requirements for the system so that the scope of work can be determined." superActivities="_AP_nodOOEdyqlogshP8l4g" optionalInput="_AVhA09OOEdyqlogshP8l4g" output="_AQJYp9OOEdyqlogshP8l4g _AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g">
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Wh-sMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_VXZ5wO0IEdqHTdbLTmC5IQ"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_eyL0wCu-EdqSxKAVa9kmvA"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_wr24gNcGEdqz_d2XWoVt6Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_OnoNQNSAEdmLhZ9H5Plxyw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
<Task href="uma://_GbYfULPaEduocbW-TPTq7A#_P9cMUPV_EdmdHa9MmVPgqQ"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_ckG-cCY-EdqNHcQ-rAojXw"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_GAr3IOz3Edq2wJOsmRwmhg"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_fDbgkCY-EdqNHcQ-rAojXw"/>
- <selectedSteps href="uma://-Yt8TXGkE1rwydXR34apsrg#_N66nkApAEdyT57ElgMr6TA"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_CD_a8JJKEdyk6dG0ehkW5Q"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_Ql45gEI6Edyrh7YaMjqrlA"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_0WhHsN-eEdqiM_wFaqLjNg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0NOOEdyqlogshP8l4g" name="detail_use_case_scenarios" guid="_AVhA0NOOEdyqlogshP8l4g" presentationName="Detail Use-Case Scenarios" superActivities="_AP_nodOOEdyqlogshP8l4g" additionallyPerformedBy="_AQJYotOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g _AQJYpdOOEdyqlogshP8l4g" mandatoryInput="_AQJYqNOOEdyqlogshP8l4g" output="_AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqtOOEdyqlogshP8l4g" performedPrimarilyBy="_AQJYodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0NOOEdyqlogshP8l4g" name="detail_use_case_scenarios" guid="_AVhA0NOOEdyqlogshP8l4g" presentationName="Detail Use-Case Scenarios" briefDescription="This task describes how to detail a use-case scenarios for the system." superActivities="_AP_nodOOEdyqlogshP8l4g" mandatoryInput="_AQJYqNOOEdyqlogshP8l4g" output="_AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g">
+ <presentation xmi:id="-M0XmBkehezZMI-pmbjQ9SA" href="uma://-2VY1Jl_Sw2Mmk8IfX0ONNw#-M0XmBkehezZMI-pmbjQ9SA"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_4BJ_YCxSEdqjsdw1QLH_6Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
<Task href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
<selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_fAWPkJLZEdyk6dG0ehkW5Q"/>
- <selectedSteps href="uma://-locCQOxOUM8zej2tBD6M6Q#_-pOLIUbEEdyx8quJU3Grxg"/>
<selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_iEvYMJLaEdyk6dG0ehkW5Q"/>
<selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_kojt4JLcEdyk6dG0ehkW5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0dOOEdyqlogshP8l4g" name="detail_system_wide_requirements" guid="_AVhA0dOOEdyqlogshP8l4g" presentationName="Detail System-Wide Requirements" superActivities="_AP_nodOOEdyqlogshP8l4g" additionallyPerformedBy="_AQJYotOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g _AQJYpdOOEdyqlogshP8l4g" mandatoryInput="_AQJYp9OOEdyqlogshP8l4g" optionalInput="_AQJYqNOOEdyqlogshP8l4g" output="_AQJYp9OOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g" performedPrimarilyBy="_AQJYodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0dOOEdyqlogshP8l4g" name="detail_system_wide_requirements" guid="_AVhA0dOOEdyqlogshP8l4g" presentationName="Detail System-Wide Requirements" briefDescription="This task details one or more requirement that does not apply to a specific use case." superActivities="_AP_nodOOEdyqlogshP8l4g" mandatoryInput="_AQJYp9OOEdyqlogshP8l4g" optionalInput="_AQJYqNOOEdyqlogshP8l4g" output="_AQJYp9OOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g">
+ <presentation xmi:id="-p2uRMHIOQI2c6fLh6CUIbw" href="uma://-2VY1Jl_Sw2Mmk8IfX0ONNw#-p2uRMHIOQI2c6fLh6CUIbw"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_wr24gNcGEdqz_d2XWoVt6Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
<Task href="uma://_GbYfULPaEduocbW-TPTq7A#_4z8Z0EbEEdyx8quJU3Grxg"/>
<selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z1EbEEdyx8quJU3Grxg"/>
<selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z0UbEEdyx8quJU3Grxg"/>
<selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z0kbEEdyx8quJU3Grxg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0tOOEdyqlogshP8l4g" name="create_test_cases" guid="_AVhA0tOOEdyqlogshP8l4g" presentationName="Create Test Cases" superActivities="_AP_nodOOEdyqlogshP8l4g" additionallyPerformedBy="_AQJYodOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g" mandatoryInput="_AVhA09OOEdyqlogshP8l4g" optionalInput="_AVhA1NOOEdyqlogshP8l4g" output="_AVhA1NOOEdyqlogshP8l4g" performedPrimarilyBy="_AQJYpdOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0tOOEdyqlogshP8l4g" name="create_test_cases" guid="_AVhA0tOOEdyqlogshP8l4g" presentationName="Create Test Cases" briefDescription="Develop the test cases and test data for the requirements to be tested." superActivities="_AP_nodOOEdyqlogshP8l4g" mandatoryInput="_AVhA09OOEdyqlogshP8l4g" optionalInput="_AVhA1NOOEdyqlogshP8l4g" output="_AVhA1NOOEdyqlogshP8l4g">
+ <presentation xmi:id="-nIF2UE5rqiDXuJIzOZcQuA" href="uma://-2VY1Jl_Sw2Mmk8IfX0ONNw#-nIF2UE5rqiDXuJIzOZcQuA"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jzlsMlgEdmt3adZL5Dmdw"/>
<Task href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0iwc0clgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_IJFSsKuSEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_aDe_ILGcEdubqf8m_Zrvvg"/>
@@ -72,24 +88,28 @@
<selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_NK18YKuSEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_Ok_mMKuSEdmhFZtkg1nakg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AVhA09OOEdyqlogshP8l4g" name="technical_specification_slot" guid="_AVhA09OOEdyqlogshP8l4g" presentationName="[Technical Specification]" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AVhA09OOEdyqlogshP8l4g" name="technical_specification_slot" guid="_AVhA09OOEdyqlogshP8l4g" presentationName="[Technical Specification]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe requirements, constraints, and goals for the solution." isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AVhA1NOOEdyqlogshP8l4g" name="test_case" guid="_AVhA1NOOEdyqlogshP8l4g" presentationName="Test Case" isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AVhA1NOOEdyqlogshP8l4g" name="test_case" guid="_AVhA1NOOEdyqlogshP8l4g" presentationName="Test Case" briefDescription="This artifact is the specification of a set of test inputs, execution conditions, and expected results that you identify to evaluate a particular aspect of a scenario." isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <presentation xmi:id="-vyRUbVNrluvyfjsHPKp2fw" href="uma://-2VY1Jl_Sw2Mmk8IfX0ONNw#-vyRUbVNrluvyfjsHPKp2fw"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Zxf8MlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aJ6cMlgEdmt3adZL5Dmdw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_yWaKEI5fEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
</processElements>
</childPackages>
- <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AsrekEd-D7YZN9NgldQ" guid="_9t9AsrekEd-D7YZN9NgldQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AsrekEd-D7YZN9NgldQ" name="develop_solution" guid="_9t9AsrekEd-D7YZN9NgldQ">
<processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_CqFrgdOOEdyqlogshP8l4g" name="develop_solution" guid="_CqFrgdOOEdyqlogshP8l4g" superActivities="_RQi0AdONEdyqlogshP8l4g" variabilityType="extends">
<variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern" href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGoodOFEdyqlogshP8l4g"/>
</processElements>
</childPackages>
- <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9As7ekEd-D7YZN9NgldQ" guid="_9t9As7ekEd-D7YZN9NgldQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9As7ekEd-D7YZN9NgldQ" name="test_solution" guid="_9t9As7ekEd-D7YZN9NgldQ">
<processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_HhjJsdOOEdyqlogshP8l4g" name="test_solution" guid="_HhjJsdOOEdyqlogshP8l4g" superActivities="_RQi0AdONEdyqlogshP8l4g" variabilityType="extends">
<variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern" href="uma://_buG4sNOFEdyqlogshP8l4g#_buG4sdOFEdyqlogshP8l4g"/>
</processElements>
</childPackages>
- <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AtLekEd-D7YZN9NgldQ" guid="_9t9AtLekEd-D7YZN9NgldQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AtLekEd-D7YZN9NgldQ" name="ongoing_tasks" guid="_9t9AtLekEd-D7YZN9NgldQ">
<processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_GQejYdOOEdyqlogshP8l4g" name="ongoing_tasks" guid="_GQejYdOOEdyqlogshP8l4g" isPlanned="false" superActivities="_RQi0AdONEdyqlogshP8l4g" isOngoing="true" variabilityType="extends">
<variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern" href="uma://__ZInMNOEEdyqlogshP8l4g#__ZInMdOEEdyqlogshP8l4g"/>
</processElements>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/develop_architecture/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/develop_architecture/content.xmi
index a4ae416..b9df5d8 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/develop_architecture/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/develop_architecture/content.xmi
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-VFp5B68iro5ga1pz4nbQFw" name="develop_architecture,_KaeNsdOFEdyqlogshP8l4g" guid="-VFp5B68iro5ga1pz4nbQFw" version="7.2.0">
- <mainDescription><p>
+<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="-VFp5B68iro5ga1pz4nbQFw" name="develop_architecture,_KaeNsdOFEdyqlogshP8l4g" guid="-VFp5B68iro5ga1pz4nbQFw" version="7.2.0">
+ <mainDescription><p>
This activity refines the initial high-level architecture into working software. The objective is to produce stable
software that adequately addresses the technical risks in scope.
</p>
@@ -27,11 +28,92 @@
pass. Rather, they should focus on meeting the requirements in scope for the current iteration, while making decisions
in the context of the wider project.
</p></mainDescription>
- <howtoStaff><p>
+ <howtoStaff><p>
These activities are best carried out as a collaborative effort by the team, with the architect acting as a focal point
for coordinating and facilitating the decisions.
</p></howtoStaff>
- <usageNotes><p>
+ <usageNotes><p>
The work is best done in several sessions, perhaps performed over a few days.
</p></usageNotes>
-</org.eclipse.epf.uma:ProcessDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-V51fxSq2AzJuVZF90kMOmA" name="architecture_notebook,_EjG_cNOKEdyqlogshP8l4g" guid="-V51fxSq2AzJuVZF90kMOmA">
+ <refinedDescription><p>
+ This artifact&nbsp;describes the <a class="elementLink"
+ href="./../../core.tech.common.extend_supp/guidances/concepts/software_architecture_59A08DE0.html"
+ guid="__O7tAMVvEduLYZUGfgZrkQ">Software Architecture</a>.
+</p>
+<p>
+ It provides a place for maintaining the list of architectural issues, along with the associated architectural
+ decisions, designs, patterns, code documented (or pointed to), and so forth -- all at appropriate levels to make it
+ easy to understand what architectural decisions have been made and remain to be made.
+</p>
+<p>
+ It is helpful for architects to use this artifact to collaborate with other team members in developing the architecture
+ and to help team members understand the motivation behind architectural decisions so that those decisions can be
+ robustly implemented. For example, the architect may put constraints on how data is packaged and communicated between
+ different parts of the system. This may appear to be a burden, but the justification in the Architecture Notebook can
+ explain that there is a significant performance bottleneck when communicating with a legacy system. The rest of the
+ system must adapt to this bottleneck by following a specific data packaging scheme.
+</p>
+<p>
+ This artifact should also inform the team members how the system is partitioned or organized so that the team can adapt
+ to the needs of the system. It also gives a first glimpse of the system and its technical motivations to whoever must
+ maintain and change the architecture later.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-j18JWuRaOWhpi32MRwfW7A" name="refine_the_arch,_6RuKMN_1EdyOsumnGvWsEg" guid="-j18JWuRaOWhpi32MRwfW7A">
+ <keyConsiderations><p>
+ It is important to continue to reduce the complexity of the&nbsp;solution by raising the levels of abstraction.&nbsp;
+ For more information, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.extend_supp/guidances/guidelines/abstract_away_complexity_DBF13AE6.html"
+ guid="_we3F4ACpEdu8m4dIntu6jA">Guideline: Abstract Away Complexity</a>.
+</p>
+<p>
+ Continue the collaboration with the whole&nbsp;team on the refining of the architecture in order to promote consensus
+ and a common understanding of the overall solution. The architect should be working to coordinate and guide the
+ technical activities of the team rather than doing all the work alone.&nbsp;Place special emphasis&nbsp;on
+ involving&nbsp;the developer(s) throughout this task since it's the developed solution that will prove out the
+ architecture and may result in refinements to the architecture documentation.
+</p>
+<p>
+ Ensure that those who need to act upon the architectural work&nbsp;understand&nbsp;it and are able to work with
+ it.&nbsp;Make sure that the description of the architecture clearly conveys not only the solution but also the
+ motivation and objectives related to the&nbsp;decisions that have been made in shaping the architecture. This will make
+ it easier for others to understand the architecture and to adapt it over time.
+</p>
+<p>
+ You can communicate your decisions as many ways as you wish.&nbsp; For example:
+</p>
+<ul>
+ <li>
+ Publication of&nbsp;reference source code
+ </li>
+ <li>
+ Publication of&nbsp;reference models
+ </li>
+ <li>
+ Publication of&nbsp;software architecture documentation
+ </li>
+ <li>
+ Formal&nbsp;presentations of the material
+ </li>
+ <li>
+ Informal walkthroughs of the architecture
+ </li>
+</ul></keyConsiderations>
+ <refinedDescription><p>
+ This task&nbsp;builds upon the outlined architecture and makes concrete and unambiguous architectural decisions to
+ support development.&nbsp; It takes into&nbsp;account any design and implementation work products that have been
+ developed so far.&nbsp; In other words, the architecture evolves as the solution is designed and implemented, and the
+ architecture documentation is updated to reflect any changes made during development. This is&nbsp;a key,&nbsp;since
+ the actual implementation is the only real "proof" that the software architecture is viable and provides the definitive
+ basis for validating the suitability&nbsp;of the architecture.&nbsp; For more information, see <a
+ class="elementLinkWithType"
+ href="./../../core.tech.common.extend_supp/guidances/concepts/executable_arch_D4E68CBD.html"
+ guid="_O1kAANvfEduv2KOT-Teh6w">Concept: Executable Architecture</a>.
+</p>
+<p>
+ The results are captured for future reference and are communicated across the team.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/develop_architecture/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/develop_architecture/model.xmi
index 82100fb..2523c32 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/develop_architecture/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/develop_architecture/model.xmi
@@ -2,20 +2,34 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__gPdsbekEd-D7YZN9NgldQ" guid="__gPdsbekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__gPdsrekEd-D7YZN9NgldQ" id="-VFp5B68iro5ga1pz4nbQFw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WemdgVmQEeCcpdiAcH0w-w" id="-V51fxSq2AzJuVZF90kMOmA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_WemdglmQEeCcpdiAcH0w-w" id="-j18JWuRaOWhpi32MRwfW7A" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_KaeNsNOFEdyqlogshP8l4g" name="develop_architecture" guid="_KaeNsNOFEdyqlogshP8l4g">
- <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AxbekEd-D7YZN9NgldQ" guid="_9t9AxbekEd-D7YZN9NgldQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9t9AxbekEd-D7YZN9NgldQ" name="develop_solution" guid="_9t9AxbekEd-D7YZN9NgldQ">
<processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_TV_k8dOKEdyqlogshP8l4g" name="develop_solution" guid="_TV_k8dOKEdyqlogshP8l4g" superActivities="_KaeNsdOFEdyqlogshP8l4g" variabilityType="extends">
<variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern" href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGoodOFEdyqlogshP8l4g"/>
</processElements>
</childPackages>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Ei9OcdOKEdyqlogshP8l4g" name="architect" guid="_Ei9OcdOKEdyqlogshP8l4g" presentationName="Architect" isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g" modifies="_EjG_cNOKEdyqlogshP8l4g" responsibleFor="_EjG_cNOKEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EjG_cNOKEdyqlogshP8l4g" name="architecture_notebook" guid="_EjG_cNOKEdyqlogshP8l4g" presentationName="Architecture Notebook" isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EjG_cNOKEdyqlogshP8l4g" name="architecture_notebook" guid="_EjG_cNOKEdyqlogshP8l4g" presentationName="Architecture Notebook" briefDescription="This artifact describes the rationale, assumptions, explanation, and implications of the decisions that were made in forming the architecture." isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <presentation xmi:id="-V51fxSq2AzJuVZF90kMOmA" href="uma://-VFp5B68iro5ga1pz4nbQFw#-V51fxSq2AzJuVZF90kMOmA"/>
+ <checklists href="uma://_4gaS4LPREduocbW-TPTq7A#_17PYUNd6EdmIm-bsRSNCgw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ <templates href="uma://_4gaS4LPREduocbW-TPTq7A#_me8WcAANEdyRS9uciXlZ6g"/>
<WorkProduct href="uma://_4gaS4LPREduocbW-TPTq7A#_0XAf0MlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6RuKMN_1EdyOsumnGvWsEg" name="refine_the_arch" guid="_6RuKMN_1EdyOsumnGvWsEg" presentationName="Refine the Architecture" superActivities="_KaeNsdOFEdyqlogshP8l4g" additionallyPerformedBy="_6RuKMd_1EdyOsumnGvWsEg _6RuKMt_1EdyOsumnGvWsEg" mandatoryInput="_6R37MN_1EdyOsumnGvWsEg _EjG_cNOKEdyqlogshP8l4g" optionalInput="_6R37Md_1EdyOsumnGvWsEg _6R37Mt_1EdyOsumnGvWsEg" output="_EjG_cNOKEdyqlogshP8l4g" performedPrimarilyBy="_Ei9OcdOKEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6RuKMN_1EdyOsumnGvWsEg" name="refine_the_arch" guid="_6RuKMN_1EdyOsumnGvWsEg" presentationName="Refine the Architecture" briefDescription="Refine the architecture to an appropriate level of detail to support development." superActivities="_KaeNsdOFEdyqlogshP8l4g" mandatoryInput="_6R37MN_1EdyOsumnGvWsEg _EjG_cNOKEdyqlogshP8l4g" optionalInput="_6R37Md_1EdyOsumnGvWsEg _6R37Mt_1EdyOsumnGvWsEg" output="_EjG_cNOKEdyqlogshP8l4g">
+ <presentation xmi:id="-j18JWuRaOWhpi32MRwfW7A" href="uma://-VFp5B68iro5ga1pz4nbQFw#-j18JWuRaOWhpi32MRwfW7A"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_HrZGIA4MEduibvKwrGxWxA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_O1kAANvfEduv2KOT-Teh6w"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_HlRqANpbEdyP58ppo1Ieaw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_pLEGUNqGEdy88NBoQgfGyg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0YP18MlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_jdKSsNpiEdyP58ppo1Ieaw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gjdYMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_we3F4ACpEdu8m4dIntu6jA"/>
<Task href="uma://_4gaS4LPREduocbW-TPTq7A#_0gRJgMlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_l92AYNpaEdyP58ppo1Ieaw"/>
<selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_G_k1kBaqEduSTJywppIxVQ"/>
@@ -26,22 +40,16 @@
<selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_xIIVkMUbEdu5GrwIlTJV7g"/>
<selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_pyyVoFHPEd2zrOgIte8oWg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6RuKMd_1EdyOsumnGvWsEg" name="developer" guid="_6RuKMd_1EdyOsumnGvWsEg" presentationName="Developer" isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6RuKMt_1EdyOsumnGvWsEg" name="project_manager" guid="_6RuKMt_1EdyOsumnGvWsEg" presentationName="Project Manager" isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37MN_1EdyOsumnGvWsEg" name="technical_specification_slot" guid="_6R37MN_1EdyOsumnGvWsEg" presentationName="[Technical Specification]" isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37MN_1EdyOsumnGvWsEg" name="technical_specification_slot" guid="_6R37MN_1EdyOsumnGvWsEg" presentationName="[Technical Specification]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe requirements, constraints, and goals for the solution." isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37Md_1EdyOsumnGvWsEg" name="software_design_slot" guid="_6R37Md_1EdyOsumnGvWsEg" presentationName="[Software Design]" isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37Md_1EdyOsumnGvWsEg" name="technical_design_slot" guid="_6R37Md_1EdyOsumnGvWsEg" presentationName="[Technical Design]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe the realization of required system functionality, and serves as an abstraction of the solution." isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_IcQOUEqdEdyi3_jfs__bIQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37Mt_1EdyOsumnGvWsEg" name="software_implementation_slot" guid="_6R37Mt_1EdyOsumnGvWsEg" presentationName="[Software Implementation]" isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37Mt_1EdyOsumnGvWsEg" name="technical_implementation_slot" guid="_6R37Mt_1EdyOsumnGvWsEg" presentationName="[Technical Implementation]" briefDescription="This slot holds the artifacts that represent a technical implementation. This can include source code, executable code, data, and software/hardware configurations." isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_KaeNsdOFEdyqlogshP8l4g" name="develop_architecture" guid="_KaeNsdOFEdyqlogshP8l4g" presentationName="Develop the Architecture" briefDescription="Develop the architecturally significant requirements prioritized for this iteration." breakdownElements="_Ei9OcdOKEdyqlogshP8l4g _EjG_cNOKEdyqlogshP8l4g _TV_k8dOKEdyqlogshP8l4g _6RuKMN_1EdyOsumnGvWsEg _6RuKMd_1EdyOsumnGvWsEg _6RuKMt_1EdyOsumnGvWsEg _6R37MN_1EdyOsumnGvWsEg _6R37Md_1EdyOsumnGvWsEg _6R37Mt_1EdyOsumnGvWsEg">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_KaeNsdOFEdyqlogshP8l4g" name="develop_architecture" guid="_KaeNsdOFEdyqlogshP8l4g" presentationName="Develop the Architecture" briefDescription="Develop the architecturally significant requirements prioritized for this iteration." breakdownElements="_EjG_cNOKEdyqlogshP8l4g _TV_k8dOKEdyqlogshP8l4g _6RuKMN_1EdyOsumnGvWsEg _6R37MN_1EdyOsumnGvWsEg _6R37Md_1EdyOsumnGvWsEg _6R37Mt_1EdyOsumnGvWsEg">
<presentation xmi:id="-VFp5B68iro5ga1pz4nbQFw" href="uma://-VFp5B68iro5ga1pz4nbQFw#-VFp5B68iro5ga1pz4nbQFw"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/develop_solution/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/develop_solution/content.xmi
index d57b6c1..89b747a 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/develop_solution/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/develop_solution/content.xmi
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-ux7ytJ8wsCQm5rzKYxNA7Q" name="develop_solution,_RXGoodOFEdyqlogshP8l4g" guid="-ux7ytJ8wsCQm5rzKYxNA7Q" version="7.2.0">
- <mainDescription><h3>
+<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="-ux7ytJ8wsCQm5rzKYxNA7Q" name="develop_solution,_RXGoodOFEdyqlogshP8l4g" guid="-ux7ytJ8wsCQm5rzKYxNA7Q" version="7.2.0">
+ <mainDescription><h3>
Introduction
</h3>
<p>
@@ -52,7 +53,7 @@
working. Then, in the outermost loop of the activity, go back to the work item and design another chunk to get closer
to completion.
</p></mainDescription>
- <purpose><ul>
+ <purpose><ul>
<li>
For developers: To create a solution for the work item for which they are responsible
</li>
@@ -60,7 +61,7 @@
For project managers: To have a goal-based way of tracking project status
</li>
</ul></purpose>
- <usageNotes><p>
+ <usageNotes><p>
This activity occurs multiple times during each iteration. Usually, there is one instance for each work item planned
for that iteration. When instantiated in a project plan, the pattern becomes a development task to be taken on by one
or more developers, and you should rename it to include the actual requirement name. Optionally, the words <b>Solution
@@ -104,4 +105,190 @@
The last two are related to different requirements, with no context specified.
</li>
</ul></usageNotes>
-</org.eclipse.epf.uma:ProcessDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-vRKhx96vINZLGd2eqNzVyg" name="design_solution,_frOcQNOKEdyqlogshP8l4g" guid="-vRKhx96vINZLGd2eqNzVyg">
+ <keyConsiderations><p>
+ Each step in this task can cause all previous steps to be revisited in light of new information and decisions.&nbsp;
+ For example, while determining how elements collaborate&nbsp;you might find a gap in the requirements that causes you
+ to go back to the beginning after collaborating with the analyst, or when evaluating the design a reviewer
+ could&nbsp;note that a reusable element being used doesn't work as expected and that could cause you to identify new
+ elements to take its place.
+</p>
+<p>
+ Consider the architecture while performing this task.&nbsp; All design work must be done while regarding the
+ architecture within which the design exists.&nbsp; Furthermore, certain design elements will be deemed architecturally
+ significant; those elements will require updates to the architecture.
+</p>
+<p>
+ This task will be applied numerous times.&nbsp; Design is best performed in small chunks.
+</p>
+<p>
+ Even when starting the design for a particular project it&nbsp;is expected that there will be existing frameworks and
+ reusable elements.&nbsp; Every step of this task must give attention to the existing design and existing
+ implementation, utilizing existing elements when possible and emulating or improving existing elements as appropriate
+ while designing this portion of the solution.
+</p>
+<p>
+ Apply patterns throughout this task.&nbsp; Patterns represent proven designs and their usage promotes quality and
+ consistency across the design.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This task is about designing part of the system, not the whole system.&nbsp; It should be applied based upon some small
+ subset of requirements.&nbsp; The requirements driving the design could be scenario-based functional requirements,
+ non-functional requirements, or a combination.
+</p>
+<p>
+ This task can be applied in some specific context such as the database access elements required for some
+ scenario.&nbsp; In this case the task might be applied&nbsp;again later&nbsp;to deal with a different context on the
+ same requirements.&nbsp; Keep in mind that to actually build some functionality of value&nbsp;to the users, all
+ contexts will typically need to be designed and implemented. For example, to actually utilize some system capability it
+ will have to have been designed and implemented all its context such as user interface, business rules, database
+ access, etc.
+</p>
+<p>
+ For cohesion and completeness, this task is described as an end-to-end pass of designing a scenario of system usage. In
+ practice, this task will be revisited many times as the design is first considered, portions are implemented, more
+ design is performed based on what was learned, etc. The healthiest application of this task is in very close proximity
+ to the implementation.
+</p>
+<p>
+ If this task is being performed on an architecturally significant element the results of this design should be
+ referenced by the <a class="elementLink"
+ href="./../../core.tech.slot.base/workproducts/technical_architecture_slot_FF074CDD.html"
+ guid="_8OD-cLPTEduocbW-TPTq7A">[Technical Architecture]</a>.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-UAvglC1beVBhR4tcCsrtIA" name="design,_frh-QtOKEdyqlogshP8l4g" guid="-UAvglC1beVBhR4tcCsrtIA">
+ <refinedDescription><p>
+ This work product describes the elements that will make up the implemented system. It communicates abstractions of
+ particular portions of the implementation.
+</p>
+<p>
+ While architecture focuses on interfaces, patterns, and key decisions, the design fleshes out the technical details in
+ readiness for implementation, or as part of implementation.
+</p>
+<p>
+ This product can describe multiple static and dynamic views of the system for examination. Although various views may
+ focus on divergent, seemingly independent issues of how the system will be put together and work, they should fit
+ together without contradiction.<br />
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-2uPX8tYcrG4NCorQpgu0eA" name="implement_developer_tests,_gXo2UNOKEdyqlogshP8l4g" guid="-2uPX8tYcrG4NCorQpgu0eA">
+ <keyConsiderations><ol>
+ <li>
+ Automate tests via a unit regression testing tool (for example, xUnit) so that tests may be run by developers
+ whenever they make changes to the code.
+ </li>
+ <li>
+ Test to the risk of the implementation element. For example, the more critical an element is, the more important it
+ is to test it thoroughly.
+ </li>
+ <li>
+ Pair with&nbsp;team members with testing skills&nbsp;in all steps of this task to gain insight on testing and
+ quality considerations.
+ </li>
+</ol>
+<p>
+ The&nbsp;[Project Work] is implicitly used in implementation tasks to manage which requirements or change requests are
+ being realized in the code.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ Developer testing is different from other forms of testing in that it is based on the expected behavior of code units
+ rather than being directly based on the system requirements.
+</p>
+<p>
+ It is best to do this at a small scale, much smaller than the complete code base to be authored by a developer over the
+ course of an iteration. This can be done for one operation, one field added to a user interface, one stored procedure,
+ etc. As the code base is incrementally built, new tests will be authored and existing tests might be revisited to test
+ additional behavior.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-fi-xVZ6lCsQU31y75Ax4OA" name="developer_test,_gX7xQtOKEdyqlogshP8l4g" guid="-fi-xVZ6lCsQU31y75Ax4OA">
+ <refinedDescription><p>
+ This artifact covers all of the steps to validate a specific aspect of an implementation element. For example, a test
+ could ensure that the parameters of a method properly accept the uppermost and lowermost required values. A developer
+ test specifies test entries, execution conditions, and expected results. These details are identified to evaluate a
+ particular aspect of a scenario.
+</p>
+<p>
+ When you collect developer tests for a specific implementation element, you can validate that the element performs as
+ specified.
+</p>
+<p>
+ The tests be self-documenting so that it is clear upon completion of the test whether the implementation element has
+ run correctly.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-383xzY4iZ_mRmebRFJ71-Q" name="implement_solution,_hVe-oNOKEdyqlogshP8l4g" guid="-383xzY4iZ_mRmebRFJ71-Q">
+ <keyConsiderations><p>
+ It is best when developer tests already exist so there is an unambiguous definition of what behavior is considered
+ correct. The implementation should be immediately tested.
+</p>The [Project Work]&nbsp; is implicitly used in implementation tasks to manage which requirements or change requests are
+being realized in the code.<br /></keyConsiderations>
+ <refinedDescription><p>
+ Usually, this task is focused on a specific implementation&nbsp;element, such as a class or component, but it does not
+ need to be.
+</p>
+<p>
+ A portion of the design is implemented by performing this task. This task can be performed any number of times during
+ an iteration. In fact it is best to do this task in as small a scope as possible to tighten the loop between it and
+ related tasks involving developer testing and consideration of the design.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-9Jb-Nex6ZZzYbdiQZ5yH9Q" name="build,_aJ1X4No7EdyzZqGyZ7hwdw" guid="-9Jb-Nex6ZZzYbdiQZ5yH9Q">
+ <refinedDescription><p>
+ This working version of the system or part of the system&nbsp;is the result of putting the implementation through a
+ build process (typically an automated build script) that creates an executable version, or one that runs. This
+ executable version will typically have a number of supporting files that are also considered part of this artifact.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-aPWmfmaOCZsb1a9aCKpRSw" name="run_developer_tests,_iRZNQNOKEdyqlogshP8l4g" guid="-aPWmfmaOCZsb1a9aCKpRSw">
+ <keyConsiderations><p>
+ It is common to require that code pass all developer tests before it can be delivered in an integrated source code
+ repository.
+</p>
+<p>
+ Pair with testing experts to gain insight on testing and quality considerations.
+</p>
+<p>
+ The&nbsp;[Project Work]&nbsp;is implicitly used in implementation tasks to manage which requirements or change requests
+ are being realized in the code.
+</p></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-nGFCabBnNthDU5t9ws5fbA" name="integrate_and_create_build,_Dlo8wNo8EdyzZqGyZ7hwdw" guid="-nGFCabBnNthDU5t9ws5fbA">
+ <keyConsiderations><p>
+ In order to be effective at applying the practice of <a class="elementLink"
+ href="./../../practice.tech.continuous_integration.base/guidances/guidelines/continuous_integration_13C1A8CA.html"
+ guid="_i8bUEL6cEdqti4GwqTkbsQ">Continuous Integration</a>,&nbsp;the time to integrate, build, and test the increment
+ must be short enough that it can be performed several times per day.&nbsp; Changes should be broken down into
+ relatively small <a class="elementLink"
+ href="./../../core.mgmt.common.extend_supp/guidances/concepts/change_set_430BF233.html"
+ guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s that can be implemented, integrated and tested quickly.
+</p></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-FB2KP2UFI653oVtHVkndvA" name="implementation,_dC4w4JojEd2XAqcHTC2Siw" guid="-FB2KP2UFI653oVtHVkndvA">
+ <refinedDescription><p>
+ This artifact is the collection of one or more of these elements:
+</p>
+<ul>
+ <li>
+ Source code files
+ </li>
+ <li>
+ Data files
+ </li>
+ <li>
+ Build scripts
+ </li>
+ <li>
+ Other files that are transformed into the executable system
+ </li>
+</ul></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-9NwuPPfPDuUrGL-0O-B1Uw" name="test_log,_dC4w4ZojEd2XAqcHTC2Siw" guid="-9NwuPPfPDuUrGL-0O-B1Uw">
+ <refinedDescription>This artifact provides a detailed, typically time-based record that both verifies that a set of tests were run, and
+provides information that relates to the success of those tests. The focus is typically on providing an accurate audit
+trail, which enables you to undertake a post-run diagnosis of failures. This raw data is subsequently analyzed to determine
+the results of an aspect of the test effort.</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/develop_solution/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/develop_solution/model.xmi
index 77466c1..021c93d 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/develop_solution/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/develop_solution/model.xmi
@@ -2,44 +2,56 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__gZOsLekEd-D7YZN9NgldQ" guid="__gZOsLekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__gZOsbekEd-D7YZN9NgldQ" id="-ux7ytJ8wsCQm5rzKYxNA7Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m1vOkFmREeCcpdiAcH0w-w" id="-vRKhx96vINZLGd2eqNzVyg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m1vOkVmREeCcpdiAcH0w-w" id="-UAvglC1beVBhR4tcCsrtIA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m1vOklmREeCcpdiAcH0w-w" id="-2uPX8tYcrG4NCorQpgu0eA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m1vOk1mREeCcpdiAcH0w-w" id="-fi-xVZ6lCsQU31y75Ax4OA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m1vOlFmREeCcpdiAcH0w-w" id="-383xzY4iZ_mRmebRFJ71-Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m1vOlVmREeCcpdiAcH0w-w" id="-9Jb-Nex6ZZzYbdiQZ5yH9Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m14_kFmREeCcpdiAcH0w-w" id="-aPWmfmaOCZsb1a9aCKpRSw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m14_kVmREeCcpdiAcH0w-w" id="-nGFCabBnNthDU5t9ws5fbA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m14_klmREeCcpdiAcH0w-w" id="-FB2KP2UFI653oVtHVkndvA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_m14_k1mREeCcpdiAcH0w-w" id="-9NwuPPfPDuUrGL-0O-B1Uw" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_RXGooNOFEdyqlogshP8l4g" name="develop_solution" guid="_RXGooNOFEdyqlogshP8l4g">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_frOcQNOKEdyqlogshP8l4g" name="design_solution" guid="_frOcQNOKEdyqlogshP8l4g" presentationName="Design the Solution" superActivities="_RXGoodOFEdyqlogshP8l4g" additionallyPerformedBy="_frYNQdOKEdyqlogshP8l4g _frYNQtOKEdyqlogshP8l4g _frYNQ9OKEdyqlogshP8l4g _frYNRNOKEdyqlogshP8l4g" mandatoryInput="_frh-QNOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g" optionalInput="_frh-QtOKEdyqlogshP8l4g" output="_frh-QtOKEdyqlogshP8l4g" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_frOcQNOKEdyqlogshP8l4g" name="design_solution" guid="_frOcQNOKEdyqlogshP8l4g" presentationName="Design the Solution" briefDescription="Identify the elements and devise the interactions, behavior, relations, and data necessary to realize some functionality." superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_frh-QNOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g" optionalInput="_frh-QtOKEdyqlogshP8l4g" output="_frh-QtOKEdyqlogshP8l4g">
+ <presentation xmi:id="-vRKhx96vINZLGd2eqNzVyg" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-vRKhx96vINZLGd2eqNzVyg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <concepts href="uma://_Z2cK0LPPEduocbW-TPTq7A#_bFjlAPTYEduDKIuqTXQ8SA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_w2ACwA4LEduibvKwrGxWxA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0LcUkA4LEduibvKwrGxWxA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0YJvUMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_Z2cK0LPPEduocbW-TPTq7A#_T9FbYFRFEd2o7OqLaYh8nA"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_uF-QYEAhEdq_UJTvM1DM2Q"/>
+ <guidelines href="uma://_Z2cK0LPPEduocbW-TPTq7A#__MnggPTdEduDKIuqTXQ8SA"/>
+ <guidelines href="uma://_Z2cK0LPPEduocbW-TPTq7A#_C4U9QPTeEduDKIuqTXQ8SA"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
<Task href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0fshwMlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_4Z7WYKuKEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_Ci7aYFixEdusJoWkvSRO9Q"/>
<selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_--6tYKuKEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_A_LU8KuLEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_ENwJwKuLEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_KNZYAKuLEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_OGYbwKuLEdmhFZtkg1nakg"/>
- <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_Ci7aYFixEdusJoWkvSRO9Q"/>
<selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_mUVt8BfnEduD353bkQ4frw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNQNOKEdyqlogshP8l4g" name="developer" guid="_frYNQNOKEdyqlogshP8l4g" presentationName="Developer" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g" modifies="_frh-QtOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g _dC4w4JojEd2XAqcHTC2Siw _dC4w4ZojEd2XAqcHTC2Siw _aJ1X4No7EdyzZqGyZ7hwdw" responsibleFor="_dC4w4JojEd2XAqcHTC2Siw _aJ1X4No7EdyzZqGyZ7hwdw _gX7xQtOKEdyqlogshP8l4g _frh-QtOKEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNQdOKEdyqlogshP8l4g" name="analyst" guid="_frYNQdOKEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNQtOKEdyqlogshP8l4g" name="architect" guid="_frYNQtOKEdyqlogshP8l4g" presentationName="Architect" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNQ9OKEdyqlogshP8l4g" name="stakeholder" guid="_frYNQ9OKEdyqlogshP8l4g" presentationName="Stakeholder" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNRNOKEdyqlogshP8l4g" name="tester" guid="_frYNRNOKEdyqlogshP8l4g" presentationName="Tester" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g" responsibleFor="_dC4w4ZojEd2XAqcHTC2Siw _Dlo8wdo8EdyzZqGyZ7hwdw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QNOKEdyqlogshP8l4g" name="technical_architecture_slot" guid="_frh-QNOKEdyqlogshP8l4g" presentationName="[Technical Architecture]" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QNOKEdyqlogshP8l4g" name="technical_architecture_slot" guid="_frh-QNOKEdyqlogshP8l4g" presentationName="[Technical Architecture]" briefDescription="This slot serves as an abstraction of high level artifacts that represent the documentation of the architecture." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_8OD-cLPTEduocbW-TPTq7A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QdOKEdyqlogshP8l4g" name="technical_specification_slot" guid="_frh-QdOKEdyqlogshP8l4g" presentationName="[Technical Specification]" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QdOKEdyqlogshP8l4g" name="technical_specification_slot" guid="_frh-QdOKEdyqlogshP8l4g" presentationName="[Technical Specification]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe requirements, constraints, and goals for the solution." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QtOKEdyqlogshP8l4g" name="design" guid="_frh-QtOKEdyqlogshP8l4g" presentationName="Design" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QtOKEdyqlogshP8l4g" name="design" guid="_frh-QtOKEdyqlogshP8l4g" presentationName="Design" briefDescription="This artifact describes the realization of required system functionality and serves as an abstraction of the source code." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <presentation xmi:id="-UAvglC1beVBhR4tcCsrtIA" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-UAvglC1beVBhR4tcCsrtIA"/>
+ <checklists href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0XSzsMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_Z2cK0LPPEduocbW-TPTq7A#_bFjlAPTYEduDKIuqTXQ8SA"/>
+ <templates href="uma://_Z2cK0LPPEduocbW-TPTq7A#_EOPcMAMUEdylNddAObilIA"/>
<WorkProduct href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0WuL8slgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_gXo2UNOKEdyqlogshP8l4g" name="implement_developer_tests" guid="_gXo2UNOKEdyqlogshP8l4g" presentationName="Implement Developer Tests" superActivities="_RXGoodOFEdyqlogshP8l4g" additionallyPerformedBy="_frYNRNOKEdyqlogshP8l4g" mandatoryInput="_gX7xQNOKEdyqlogshP8l4g" optionalInput="_gX7xQdOKEdyqlogshP8l4g" output="_gX7xQtOKEdyqlogshP8l4g" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_gXo2UNOKEdyqlogshP8l4g" name="implement_developer_tests" guid="_gXo2UNOKEdyqlogshP8l4g" presentationName="Implement Developer Tests" briefDescription="Implement one or more tests that enable the validation of the individual implementation elements through execution." superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_gX7xQNOKEdyqlogshP8l4g" optionalInput="_gX7xQdOKEdyqlogshP8l4g" output="_gX7xQtOKEdyqlogshP8l4g">
+ <presentation xmi:id="-2uPX8tYcrG4NCorQpgu0eA" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-2uPX8tYcrG4NCorQpgu0eA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_ADwlAJRtEdyrdaw_xGakyw"/>
<Task href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_znlIcJR9EdyVKbgqUOtqQA"/>
<selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_C_j_EJR-EdyVKbgqUOtqQA"/>
<selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_Es64wJR-EdyVKbgqUOtqQA"/>
@@ -49,16 +61,21 @@
<selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_JAiqEJR-EdyVKbgqUOtqQA"/>
<selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_KkDrQJR-EdyVKbgqUOtqQA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQNOKEdyqlogshP8l4g" name="software_implementation_slot" guid="_gX7xQNOKEdyqlogshP8l4g" presentationName="[Software Implementation]" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQNOKEdyqlogshP8l4g" name="technical_implementation_slot" guid="_gX7xQNOKEdyqlogshP8l4g" presentationName="[Technical Implementation]" briefDescription="This slot holds the artifacts that represent a technical implementation. This can include source code, executable code, data, and software/hardware configurations." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQdOKEdyqlogshP8l4g" name="software_design_slot" guid="_gX7xQdOKEdyqlogshP8l4g" presentationName="[Software Design]" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQdOKEdyqlogshP8l4g" name="technical_design_slot" guid="_gX7xQdOKEdyqlogshP8l4g" presentationName="[Technical Design]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe the realization of required system functionality, and serves as an abstraction of the solution." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_IcQOUEqdEdyi3_jfs__bIQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQtOKEdyqlogshP8l4g" name="developer_test" guid="_gX7xQtOKEdyqlogshP8l4g" presentationName="DeveloperTest" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQtOKEdyqlogshP8l4g" name="developer_test" guid="_gX7xQtOKEdyqlogshP8l4g" presentationName="Developer Test" briefDescription="The Developer Test validates a specific aspect of an implementation element." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <presentation xmi:id="-fi-xVZ6lCsQU31y75Ax4OA" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-fi-xVZ6lCsQU31y75Ax4OA"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_dxaPUF-BEd2T0JdVjRyaQA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_kh9FcJ02EdyQ3oTO93enUw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_hVe-oNOKEdyqlogshP8l4g" name="implement_solution" guid="_hVe-oNOKEdyqlogshP8l4g" presentationName="Implement Solution" superActivities="_RXGoodOFEdyqlogshP8l4g" additionallyPerformedBy="_frYNQ9OKEdyqlogshP8l4g _frYNRNOKEdyqlogshP8l4g" mandatoryInput="_gX7xQdOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g" optionalInput="_gX7xQNOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g" output="_dC4w4JojEd2XAqcHTC2Siw" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_hVe-oNOKEdyqlogshP8l4g" name="implement_solution" guid="_hVe-oNOKEdyqlogshP8l4g" presentationName="Implement Solution" briefDescription="Implement source code to provide new functionality or fix defects." superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_gX7xQdOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g" optionalInput="_gX7xQNOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g" output="_dC4w4JojEd2XAqcHTC2Siw">
+ <presentation xmi:id="-383xzY4iZ_mRmebRFJ71-Q" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-383xzY4iZ_mRmebRFJ71-Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_mlKb8JyJEdy9brKHb521mQ"/>
<Task href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_Ht-z8JfJEdyZkIR-s-Y8wQ"/>
<selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_RiBg4JfJEdyZkIR-s-Y8wQ"/>
<selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_SW1pAJfJEdyZkIR-s-Y8wQ"/>
@@ -67,17 +84,25 @@
<selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_WpB28JfJEdyZkIR-s-Y8wQ"/>
<selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_XjAL4JfJEdyZkIR-s-Y8wQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_aJ1X4No7EdyzZqGyZ7hwdw" name="build" guid="_aJ1X4No7EdyzZqGyZ7hwdw" presentationName="Build" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_aJ1X4No7EdyzZqGyZ7hwdw" name="build" guid="_aJ1X4No7EdyzZqGyZ7hwdw" presentationName="Build" briefDescription="An operational version of a system or part of a system that demonstrates a subset of the capabilities to be provided in the final product." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <presentation xmi:id="-9Jb-Nex6ZZzYbdiQZ5yH9Q" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-9Jb-Nex6ZZzYbdiQZ5yH9Q"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0YuXEMlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_iRZNQNOKEdyqlogshP8l4g" name="run_developer_tests" guid="_iRZNQNOKEdyqlogshP8l4g" presentationName="Run Developer Tests" superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_gX7xQNOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g" output="_dC4w4ZojEd2XAqcHTC2Siw" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_iRZNQNOKEdyqlogshP8l4g" name="run_developer_tests" guid="_iRZNQNOKEdyqlogshP8l4g" presentationName="Run Developer Tests" briefDescription="Run tests against the individual implementation elements to verify that their internal structures work as specified." superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_gX7xQNOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g" output="_dC4w4ZojEd2XAqcHTC2Siw">
+ <presentation xmi:id="-aPWmfmaOCZsb1a9aCKpRSw" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-aPWmfmaOCZsb1a9aCKpRSw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_ADwlAJRtEdyrdaw_xGakyw"/>
<Task href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_R7atwJfIEdyZkIR-s-Y8wQ"/>
<selectedSteps href="uma://-H6ob8eA7gz_mOsk8ulSFMQ#_gjLBUJfIEdyZkIR-s-Y8wQ"/>
<selectedSteps href="uma://-H6ob8eA7gz_mOsk8ulSFMQ#_haRocJfIEdyZkIR-s-Y8wQ"/>
<selectedSteps href="uma://-H6ob8eA7gz_mOsk8ulSFMQ#_itj1QJfIEdyZkIR-s-Y8wQ"/>
<selectedSteps href="uma://-H6ob8eA7gz_mOsk8ulSFMQ#_C0_fYFQAEd2ECfw27om6fw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Dlo8wNo8EdyzZqGyZ7hwdw" name="integrate_and_create_build" guid="_Dlo8wNo8EdyzZqGyZ7hwdw" presentationName="Integrate and Create Build" superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_Dlo8wdo8EdyzZqGyZ7hwdw _gX7xQNOKEdyqlogshP8l4g" output="_aJ1X4No7EdyzZqGyZ7hwdw" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Dlo8wNo8EdyzZqGyZ7hwdw" name="integrate_and_create_build" guid="_Dlo8wNo8EdyzZqGyZ7hwdw" presentationName="Integrate and Create Build" briefDescription="This task describes how to integrate all changes made by developers into the code base and perform the minimal testing to validate the build." superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_Dlo8wdo8EdyzZqGyZ7hwdw _gX7xQNOKEdyqlogshP8l4g" output="_aJ1X4No7EdyzZqGyZ7hwdw">
+ <presentation xmi:id="-nGFCabBnNthDU5t9ws5fbA" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-nGFCabBnNthDU5t9ws5fbA"/>
+ <concepts href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_1QU9MAIoEdyLh7vsrHZ4YA"/>
+ <concepts href="uma://_D-ExQMktEdygFZkm1d5NtQ#_0cEmAMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_D-ExQMktEdygFZkm1d5NtQ#_i8bUEL6cEdqti4GwqTkbsQ"/>
+ <guidelines href="uma://_D-ExQMktEdygFZkm1d5NtQ#_SM4YIL6dEdqti4GwqTkbsQ"/>
<Task href="uma://_D-ExQMktEdygFZkm1d5NtQ#_kkZBgJOKEdyaRbFYa4AN4A"/>
<selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBhZOKEdyaRbFYa4AN4A"/>
<selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBgpOKEdyaRbFYa4AN4A"/>
@@ -85,16 +110,24 @@
<selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBg5OKEdyaRbFYa4AN4A"/>
<selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBgZOKEdyaRbFYa4AN4A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Dlo8wdo8EdyzZqGyZ7hwdw" name="test_script" guid="_Dlo8wdo8EdyzZqGyZ7hwdw" presentationName="Test Script" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Dlo8wdo8EdyzZqGyZ7hwdw" name="test_script" guid="_Dlo8wdo8EdyzZqGyZ7hwdw" presentationName="Test Script" briefDescription="This artifact contains the step-by-step instructions that compose a test, enabling its run. Text scripts can take the form of either documented textual instructions that are manually followed, or computer-readable instructions that enable
automated testing." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_KZQJMBhBEduxCP6DVVLxsA"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Z9tMMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aDz0MlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0j5sUMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kF5kMlgEdmt3adZL5Dmdw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_yZtgQI5gEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_dC4w4JojEd2XAqcHTC2Siw" name="implementation" guid="_dC4w4JojEd2XAqcHTC2Siw" presentationName="Implementation" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_dC4w4JojEd2XAqcHTC2Siw" name="implementation" guid="_dC4w4JojEd2XAqcHTC2Siw" presentationName="Implementation" briefDescription="Software code files, data files, and supporting files (such as online help files) that represent the raw parts of a system that can be built." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <presentation xmi:id="-FB2KP2UFI653oVtHVkndvA" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-FB2KP2UFI653oVtHVkndvA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_JqYbgJ01EdyQ3oTO93enUw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_dC4w4ZojEd2XAqcHTC2Siw" name="test_log" guid="_dC4w4ZojEd2XAqcHTC2Siw" presentationName="Test Log" isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_dC4w4ZojEd2XAqcHTC2Siw" name="test_log" guid="_dC4w4ZojEd2XAqcHTC2Siw" presentationName="Test Log" briefDescription="This artifact collects the raw output that is captured during a unique run of one or more tests for a single test cycle run." isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <presentation xmi:id="-9NwuPPfPDuUrGL-0O-B1Uw" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-9NwuPPfPDuUrGL-0O-B1Uw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_RXGoodOFEdyqlogshP8l4g" name="develop_solution" guid="_RXGoodOFEdyqlogshP8l4g" presentationName="Develop Solution Increment" briefDescription="Design, implement, test, and integrate the solution for a requirement within a given context." breakdownElements="_frOcQNOKEdyqlogshP8l4g _frYNQNOKEdyqlogshP8l4g _frYNQdOKEdyqlogshP8l4g _frYNQtOKEdyqlogshP8l4g _frYNQ9OKEdyqlogshP8l4g _frYNRNOKEdyqlogshP8l4g _frh-QNOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g _frh-QtOKEdyqlogshP8l4g _gXo2UNOKEdyqlogshP8l4g _gX7xQNOKEdyqlogshP8l4g _gX7xQdOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g _hVe-oNOKEdyqlogshP8l4g _aJ1X4No7EdyzZqGyZ7hwdw _iRZNQNOKEdyqlogshP8l4g _Dlo8wNo8EdyzZqGyZ7hwdw _Dlo8wdo8EdyzZqGyZ7hwdw _dC4w4JojEd2XAqcHTC2Siw _dC4w4ZojEd2XAqcHTC2Siw">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_RXGoodOFEdyqlogshP8l4g" name="develop_solution" guid="_RXGoodOFEdyqlogshP8l4g" presentationName="Develop Solution Increment" briefDescription="Design, implement, test, and integrate the solution for a requirement within a given context." breakdownElements="_frOcQNOKEdyqlogshP8l4g _frh-QNOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g _frh-QtOKEdyqlogshP8l4g _gXo2UNOKEdyqlogshP8l4g _gX7xQNOKEdyqlogshP8l4g _gX7xQdOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g _hVe-oNOKEdyqlogshP8l4g _aJ1X4No7EdyzZqGyZ7hwdw _iRZNQNOKEdyqlogshP8l4g _Dlo8wNo8EdyzZqGyZ7hwdw _Dlo8wdo8EdyzZqGyZ7hwdw _dC4w4JojEd2XAqcHTC2Siw _dC4w4ZojEd2XAqcHTC2Siw">
<presentation xmi:id="-ux7ytJ8wsCQm5rzKYxNA7Q" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-ux7ytJ8wsCQm5rzKYxNA7Q"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi
index b1b70a7..42464bd 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-yNrF2Ac8VgD0WjoUxGOsIQ" name="identify_and_refine_requirements,_xxcpgdOEEdyqlogshP8l4g" guid="-yNrF2Ac8VgD0WjoUxGOsIQ" version="7.2.0">
- <mainDescription><p>
+<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="-yNrF2Ac8VgD0WjoUxGOsIQ" name="identify_and_refine_requirements,_xxcpgdOEEdyqlogshP8l4g" guid="-yNrF2Ac8VgD0WjoUxGOsIQ" version="7.2.0">
+ <mainDescription><p>
This activity describes the tasks you perform to gather, specify, analyze, and validate a subset of system's
requirements prior to implementation and verification. This does not imply that all requirements are detailed prior to
commencing implementation. Rather, you perform this activity throughout the lifecycle with stakeholders and the entire
@@ -25,4 +26,108 @@
requirements and associated test cases as necessary to drive implementation and verification, and managing requirements
change.
</p></mainDescription>
-</org.eclipse.epf.uma:ProcessDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-x896fGqISERWysfNwjvB7w" name="system_wide_requirements,_EOwqptOLEdyqlogshP8l4g" guid="-x896fGqISERWysfNwjvB7w">
+ <keyConsiderations><ul>
+ <li>
+ When you document system-wide requirements, ensure that the needs of all of the stakeholders are represented. In
+ particular, include the needs of those who are responsible for maintaining or supporting the system after it is
+ delivered.
+ </li>
+ <li>
+ Typically, there are some overlaps and gray areas between system-wide requirements and other requirements work
+ products. For example, the authorization behavior of a system can be specified as use cases or as statements within
+ system-wide requirements. The overall driving need is that no important requirements are missed or duplicated, and
+ that there is an agreed upon approach for capturing and processing every type of requirement.
+ </li>
+ <li>
+ System-wide requirements originate from many places. Documenting the source of the requirement is particularly
+ important when you separate externally mandated requirements.
+ </li>
+ <li>
+ Requirements are often thought of as "Qualitative" (specifying a quality or desirable characteristic) versus
+ "Quantitative" (specifying a quantity). Qualitative requirements can sometimes be elaborated into quantitative
+ requirements.
+ </li>
+ <li>
+ A good quality requirement is one that you can verify, either through testing or some other objective evaluation.
+ </li>
+ <li>
+ You must evaluate system-wide requirements for cost, schedule impact, and level of contribution to business goals.
+ Based on your evaluation, the system-wide requirements should be iteratively challenged, defended, and amended.
+ </li>
+</ul></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-T_J_cyYgoF4KWAcGQbdjjA" name="glossary,_EOwqqNOLEdyqlogshP8l4g" guid="-T_J_cyYgoF4KWAcGQbdjjA">
+ <keyConsiderations><p>
+ Although listed as an <i>output from</i> and an <i>input to</i> tasks associated with the requirements discipline, this
+ artifact can be updated at any time and by any role as new terms are identified. The terms defined should be used
+ according to the recorded definitions in all project documentation so that all stakeholders can clearly see that terms
+ are being used consistently.
+</p>
+<p>
+ One of the primary decisions when developing&nbsp;this artifact&nbsp;is whether to have all terms in a single glossary
+ or to maintain terms in several glossaries, business terms artifacts, or models.&nbsp;If terms are defined in multiple
+ places, you need to communicate all of those sources to the team and decide which take precedence.
+</p>
+<p>
+ It may be important, even in small projects, to reference and use existing broader glossaries, business terms
+ artifacts, or data models, where they exist.
+</p>
+<p>
+ Industry- and organization-wide glossaries may be referenced, and compliance with such specific chosen standards may be
+ required.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This artifact&nbsp;helps you avoid miscommunication by providing two essential resources:
+</p>
+<ul>
+ <li>
+ A central location to look for terms and abbreviations that are new to development team members
+ </li>
+ <li>
+ Definitions of terms that are used in specific ways within the domain
+ </li>
+</ul>
+<p>
+ Definitions for the glossary terms come from several sources, such as requirements documents, specifications, and
+ discussions with stakeholders and domain experts.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-7g1n_R9Eg7zeKCdFrem74A" name="detail_use_case_scenarios,_FX7SINOLEdyqlogshP8l4g" guid="-7g1n_R9Eg7zeKCdFrem74A">
+ <keyConsiderations><p>
+ To avoid unnecessary rework, only those use-case scenarios that are scheduled for implementation in the near term (in
+ the next iteration or two)&nbsp;must be detailed.&nbsp;
+</p>
+<p>
+ Not all use-case scenarios require detailing.
+</p></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-snrpmf_Kt0OZ2R7QKJufUQ" name="detail_system_wide_requirements,_F68foNOLEdyqlogshP8l4g" guid="-snrpmf_Kt0OZ2R7QKJufUQ">
+ <keyConsiderations>To avoid unnecessary rework, only those requirements that are scheduled for implementation in the near term (in the next
+iteration or two)&nbsp;must be detailed.</keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Afh79qcpEs6i404AABE0rA" name="create_test_cases,_HDOWUNOLEdyqlogshP8l4g" guid="-Afh79qcpEs6i404AABE0rA">
+ <keyConsiderations><p>
+ Develop test cases in parallel with requirements so that Analysts and Stakeholders can agree with the specific
+ conditions of satisfaction for each requirement. The test cases act as acceptance criteria by expanding on the intent
+ of the system&nbsp;through actual scenarios of use.&nbsp;This allows team members to measure progress in terms of
+ passing test cases.&nbsp;
+</p></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-bQ7hVBwsq2Dzk11CI9pT_g" name="test_case,_HDOWUtOLEdyqlogshP8l4g" guid="-bQ7hVBwsq2Dzk11CI9pT_g">
+ <refinedDescription><p>
+ A test case specifies the conditions that must be validated to enable an assessment of aspects of the system under
+ test. A test case is more formal than a test idea; typically, a test case takes the form of a specification. In less
+ formal environments, you can create test cases by identifying a unique ID, name, associated test data, and expected
+ results.
+</p>
+<p>
+ Test cases can be derived from many sources, and typically include a subset of the requirements (such as use cases,
+ performance characteristics, and reliability concerns) and other types of quality attributes. For more information on
+ types of tests and their relationships to quality test attributes, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.extend_supp/guidances/concepts/testing_qualitative_rqmts_CAE80710.html"
+ guid="_0aJ6cMlgEdmt3adZL5Dmdw">Concept: Testing Qualitative Requirements</a>.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/model.xmi
index 7d89723..f4008f7 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/model.xmi
@@ -2,59 +2,75 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__fyxw7ekEd-D7YZN9NgldQ" guid="__fyxw7ekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__fyxxLekEd-D7YZN9NgldQ" id="-yNrF2Ac8VgD0WjoUxGOsIQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_avS2oVmQEeCcpdiAcH0w-w" id="-x896fGqISERWysfNwjvB7w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_avS2olmQEeCcpdiAcH0w-w" id="-T_J_cyYgoF4KWAcGQbdjjA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_avS2o1mQEeCcpdiAcH0w-w" id="-7g1n_R9Eg7zeKCdFrem74A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_avS2pFmQEeCcpdiAcH0w-w" id="-snrpmf_Kt0OZ2R7QKJufUQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_avS2pVmQEeCcpdiAcH0w-w" id="-Afh79qcpEs6i404AABE0rA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_avcnoFmQEeCcpdiAcH0w-w" id="-bQ7hVBwsq2Dzk11CI9pT_g" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_xxcpgNOEEdyqlogshP8l4g" name="identify_and_refine_requirements" guid="_xxcpgNOEEdyqlogshP8l4g">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_EOm5oNOLEdyqlogshP8l4g" name="identify_and_outline_requirements" guid="_EOm5oNOLEdyqlogshP8l4g" presentationName="Identify and Outline Requirements" superActivities="_xxcpgdOEEdyqlogshP8l4g" additionallyPerformedBy="_EOwqodOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g _EOwqpNOLEdyqlogshP8l4g" optionalInput="_HDOWUdOLEdyqlogshP8l4g" output="_EOwqptOLEdyqlogshP8l4g _EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqqdOLEdyqlogshP8l4g" performedPrimarilyBy="_EOwqoNOLEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_EOm5oNOLEdyqlogshP8l4g" name="identify_and_outline_requirements" guid="_EOm5oNOLEdyqlogshP8l4g" presentationName="Identify and Outline Requirements" briefDescription="This task describes how to identify and outline the requirements for the system so that the scope of work can be determined." superActivities="_xxcpgdOEEdyqlogshP8l4g" optionalInput="_HDOWUdOLEdyqlogshP8l4g" output="_EOwqptOLEdyqlogshP8l4g _EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g">
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Wh-sMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_VXZ5wO0IEdqHTdbLTmC5IQ"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_eyL0wCu-EdqSxKAVa9kmvA"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_wr24gNcGEdqz_d2XWoVt6Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_OnoNQNSAEdmLhZ9H5Plxyw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
<Task href="uma://_GbYfULPaEduocbW-TPTq7A#_P9cMUPV_EdmdHa9MmVPgqQ"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_ckG-cCY-EdqNHcQ-rAojXw"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_GAr3IOz3Edq2wJOsmRwmhg"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_fDbgkCY-EdqNHcQ-rAojXw"/>
- <selectedSteps href="uma://-Yt8TXGkE1rwydXR34apsrg#_N66nkApAEdyT57ElgMr6TA"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_CD_a8JJKEdyk6dG0ehkW5Q"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_Ql45gEI6Edyrh7YaMjqrlA"/>
<selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_0WhHsN-eEdqiM_wFaqLjNg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqoNOLEdyqlogshP8l4g" name="analyst" guid="_EOwqoNOLEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g" modifies="_EOwqptOLEdyqlogshP8l4g _EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqqdOLEdyqlogshP8l4g" responsibleFor="_EOwqqdOLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqp9OLEdyqlogshP8l4g _EOwqptOLEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqodOLEdyqlogshP8l4g" name="architect" guid="_EOwqodOLEdyqlogshP8l4g" presentationName="Architect" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqotOLEdyqlogshP8l4g" name="developer" guid="_EOwqotOLEdyqlogshP8l4g" presentationName="Developer" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqo9OLEdyqlogshP8l4g" name="stakeholder" guid="_EOwqo9OLEdyqlogshP8l4g" presentationName="Stakeholder" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqpNOLEdyqlogshP8l4g" name="tester" guid="_EOwqpNOLEdyqlogshP8l4g" presentationName="Tester" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g" modifies="_HDOWUtOLEdyqlogshP8l4g" responsibleFor="_HDOWUtOLEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqptOLEdyqlogshP8l4g" name="system_wide_requirements" guid="_EOwqptOLEdyqlogshP8l4g" presentationName="System-WideRequirements" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqptOLEdyqlogshP8l4g" name="system_wide_requirements" guid="_EOwqptOLEdyqlogshP8l4g" presentationName="System-Wide Requirements" briefDescription="This artifact captures the quality attributes and constraints that have system-wide scope. It also captures system-wide functional requirements." isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-x896fGqISERWysfNwjvB7w" href="uma://-yNrF2Ac8VgD0WjoUxGOsIQ#-x896fGqISERWysfNwjvB7w"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_6jXzYNcKEdqz_d2XWoVt6Q"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_m7p-AI5fEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqp9OLEdyqlogshP8l4g" name="use_case" guid="_EOwqp9OLEdyqlogshP8l4g" presentationName="Use Case" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqp9OLEdyqlogshP8l4g" name="use_case" guid="_EOwqp9OLEdyqlogshP8l4g" presentationName="Use Case" briefDescription="This artifact captures the system behavior to yield an observable result of value to those who interact with the system." isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kNwINk1Edq2Q8qZoWbvGA"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_JLOiIMNvEdu2IdAIaWZyAw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_3Y3XUI5fEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqqNOLEdyqlogshP8l4g" name="glossary" guid="_EOwqqNOLEdyqlogshP8l4g" presentationName="Glossary" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqqNOLEdyqlogshP8l4g" name="glossary" guid="_EOwqqNOLEdyqlogshP8l4g" presentationName="Glossary" briefDescription="This artifact defines important terms used by the project. The collection of terms clarifies the vocabulary used on the project." isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-T_J_cyYgoF4KWAcGQbdjjA" href="uma://-yNrF2Ac8VgD0WjoUxGOsIQ#-T_J_cyYgoF4KWAcGQbdjjA"/>
<WorkProduct href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqqdOLEdyqlogshP8l4g" name="use_case_model" guid="_EOwqqdOLEdyqlogshP8l4g" presentationName="Use-Case Model" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqqdOLEdyqlogshP8l4g" name="use_case_model" guid="_EOwqqdOLEdyqlogshP8l4g" presentationName="Use-Case Model" briefDescription="This artifact captures a model of the intended functions and environment of the system and serves as a contract between the customer and the team." isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <examples href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_FX7SINOLEdyqlogshP8l4g" name="detail_use_case_scenarios" guid="_FX7SINOLEdyqlogshP8l4g" presentationName="Detail Use-Case Scenarios" superActivities="_xxcpgdOEEdyqlogshP8l4g" additionallyPerformedBy="_EOwqodOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g _EOwqpNOLEdyqlogshP8l4g" mandatoryInput="_EOwqp9OLEdyqlogshP8l4g" output="_EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqqdOLEdyqlogshP8l4g" performedPrimarilyBy="_EOwqoNOLEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_FX7SINOLEdyqlogshP8l4g" name="detail_use_case_scenarios" guid="_FX7SINOLEdyqlogshP8l4g" presentationName="Detail Use-Case Scenarios" briefDescription="This task describes how to detail a use-case scenarios for the system." superActivities="_xxcpgdOEEdyqlogshP8l4g" mandatoryInput="_EOwqp9OLEdyqlogshP8l4g" output="_EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g">
+ <presentation xmi:id="-7g1n_R9Eg7zeKCdFrem74A" href="uma://-yNrF2Ac8VgD0WjoUxGOsIQ#-7g1n_R9Eg7zeKCdFrem74A"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_4BJ_YCxSEdqjsdw1QLH_6Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
<Task href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
<selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_fAWPkJLZEdyk6dG0ehkW5Q"/>
- <selectedSteps href="uma://-locCQOxOUM8zej2tBD6M6Q#_-pOLIUbEEdyx8quJU3Grxg"/>
<selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_iEvYMJLaEdyk6dG0ehkW5Q"/>
<selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_kojt4JLcEdyk6dG0ehkW5Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_F68foNOLEdyqlogshP8l4g" name="detail_system_wide_requirements" guid="_F68foNOLEdyqlogshP8l4g" presentationName="Detail System-Wide Requirements" superActivities="_xxcpgdOEEdyqlogshP8l4g" additionallyPerformedBy="_EOwqodOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g _EOwqpNOLEdyqlogshP8l4g" mandatoryInput="_EOwqptOLEdyqlogshP8l4g" optionalInput="_EOwqp9OLEdyqlogshP8l4g" output="_EOwqptOLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g" performedPrimarilyBy="_EOwqoNOLEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_F68foNOLEdyqlogshP8l4g" name="detail_system_wide_requirements" guid="_F68foNOLEdyqlogshP8l4g" presentationName="Detail System-Wide Requirements" briefDescription="This task details one or more requirement that does not apply to a specific use case." superActivities="_xxcpgdOEEdyqlogshP8l4g" mandatoryInput="_EOwqptOLEdyqlogshP8l4g" optionalInput="_EOwqp9OLEdyqlogshP8l4g" output="_EOwqptOLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g">
+ <presentation xmi:id="-snrpmf_Kt0OZ2R7QKJufUQ" href="uma://-yNrF2Ac8VgD0WjoUxGOsIQ#-snrpmf_Kt0OZ2R7QKJufUQ"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_wr24gNcGEdqz_d2XWoVt6Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
<Task href="uma://_GbYfULPaEduocbW-TPTq7A#_4z8Z0EbEEdyx8quJU3Grxg"/>
<selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z1EbEEdyx8quJU3Grxg"/>
<selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z0UbEEdyx8quJU3Grxg"/>
<selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z0kbEEdyx8quJU3Grxg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_HDOWUNOLEdyqlogshP8l4g" name="create_test_cases" guid="_HDOWUNOLEdyqlogshP8l4g" presentationName="Create Test Cases" superActivities="_xxcpgdOEEdyqlogshP8l4g" additionallyPerformedBy="_EOwqoNOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g" mandatoryInput="_HDOWUdOLEdyqlogshP8l4g" optionalInput="_HDOWUtOLEdyqlogshP8l4g" output="_HDOWUtOLEdyqlogshP8l4g" performedPrimarilyBy="_EOwqpNOLEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_HDOWUNOLEdyqlogshP8l4g" name="create_test_cases" guid="_HDOWUNOLEdyqlogshP8l4g" presentationName="Create Test Cases" briefDescription="Develop the test cases and test data for the requirements to be tested." superActivities="_xxcpgdOEEdyqlogshP8l4g" mandatoryInput="_HDOWUdOLEdyqlogshP8l4g" optionalInput="_HDOWUtOLEdyqlogshP8l4g" output="_HDOWUtOLEdyqlogshP8l4g">
+ <presentation xmi:id="-Afh79qcpEs6i404AABE0rA" href="uma://-yNrF2Ac8VgD0WjoUxGOsIQ#-Afh79qcpEs6i404AABE0rA"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jzlsMlgEdmt3adZL5Dmdw"/>
<Task href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0iwc0clgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_IJFSsKuSEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_aDe_ILGcEdubqf8m_Zrvvg"/>
@@ -62,13 +78,17 @@
<selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_NK18YKuSEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_Ok_mMKuSEdmhFZtkg1nakg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HDOWUdOLEdyqlogshP8l4g" name="technical_specification_slot" guid="_HDOWUdOLEdyqlogshP8l4g" presentationName="[Technical Specification]" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HDOWUdOLEdyqlogshP8l4g" name="technical_specification_slot" guid="_HDOWUdOLEdyqlogshP8l4g" presentationName="[Technical Specification]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe requirements, constraints, and goals for the solution." isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HDOWUtOLEdyqlogshP8l4g" name="test_case" guid="_HDOWUtOLEdyqlogshP8l4g" presentationName="Test Case" isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HDOWUtOLEdyqlogshP8l4g" name="test_case" guid="_HDOWUtOLEdyqlogshP8l4g" presentationName="Test Case" briefDescription="This artifact is the specification of a set of test inputs, execution conditions, and expected results that you identify to evaluate a particular aspect of a scenario." isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-bQ7hVBwsq2Dzk11CI9pT_g" href="uma://-yNrF2Ac8VgD0WjoUxGOsIQ#-bQ7hVBwsq2Dzk11CI9pT_g"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Zxf8MlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aJ6cMlgEdmt3adZL5Dmdw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_yWaKEI5fEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_xxcpgdOEEdyqlogshP8l4g" name="identify_and_refine_requirements" guid="_xxcpgdOEEdyqlogshP8l4g" presentationName="Identify and Refine Requirements" briefDescription="Detail a set of requirements (one or more use cases, scenarios or system-wide requirements)." breakdownElements="_EOm5oNOLEdyqlogshP8l4g _EOwqoNOLEdyqlogshP8l4g _EOwqodOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g _EOwqpNOLEdyqlogshP8l4g _EOwqptOLEdyqlogshP8l4g _EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqqdOLEdyqlogshP8l4g _FX7SINOLEdyqlogshP8l4g _F68foNOLEdyqlogshP8l4g _HDOWUNOLEdyqlogshP8l4g _HDOWUdOLEdyqlogshP8l4g _HDOWUtOLEdyqlogshP8l4g">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_xxcpgdOEEdyqlogshP8l4g" name="identify_and_refine_requirements" guid="_xxcpgdOEEdyqlogshP8l4g" presentationName="Identify and Refine Requirements" briefDescription="Detail a set of requirements (one or more use cases, scenarios or system-wide requirements)." breakdownElements="_EOm5oNOLEdyqlogshP8l4g _EOwqptOLEdyqlogshP8l4g _EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqqdOLEdyqlogshP8l4g _FX7SINOLEdyqlogshP8l4g _F68foNOLEdyqlogshP8l4g _HDOWUNOLEdyqlogshP8l4g _HDOWUdOLEdyqlogshP8l4g _HDOWUtOLEdyqlogshP8l4g">
<presentation xmi:id="-yNrF2Ac8VgD0WjoUxGOsIQ" href="uma://-yNrF2Ac8VgD0WjoUxGOsIQ#-yNrF2Ac8VgD0WjoUxGOsIQ"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/initiate_project/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/initiate_project/content.xmi
index f6c6bf1..6430ef6 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/initiate_project/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/initiate_project/content.xmi
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-kpXvvHptrggypeoQEamfhw" name="initiate_project,_eWxZgdOEEdyqlogshP8l4g" guid="-kpXvvHptrggypeoQEamfhw" version="7.2.0">
- <mainDescription><p>
+<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="-kpXvvHptrggypeoQEamfhw" name="initiate_project,_eWxZgdOEEdyqlogshP8l4g" guid="-kpXvvHptrggypeoQEamfhw" version="7.2.0">
+ <mainDescription><p>
This activity takes place at the beginning of the first iteration, when the project starts. The goal of this activity
is to establish the vision for both the project and the project plan at a high level of granularity.
</p>
@@ -20,4 +21,82 @@
project.
</li>
</ul></mainDescription>
-</org.eclipse.epf.uma:ProcessDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Y4gn4laxnFk1PUA3-GebOg" name="develop_technical_vision,_sopKYNOJEdyqlogshP8l4g" guid="-Y4gn4laxnFk1PUA3-GebOg">
+ <keyConsiderations><p>
+ Use-case modeling&nbsp;is one technique that can prove useful in defining the system boundaries and system behavior.
+</p></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-z5wrOi6JXS768g53hKiYaA" name="vision,_soyUVNOJEdyqlogshP8l4g" guid="-z5wrOi6JXS768g53hKiYaA">
+ <keyConsiderations><p>
+ It is good practice to keep this artifact brief, so you can release it to stakeholders as soon as possible, and to make
+ the artifact easy for stakeholders to read and understand. You can accomplish this by including only the most important
+ features and avoiding details of requirements.
+</p>
+<p>
+ Projects that focus on product development might extend the marketing section and include a more detailed product
+ position statement that is based on their needs and research.
+</p></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-9AN0xXBZYxIDPOg2N3IC6Q" name="plan_the_project,_t7pDUNOJEdyqlogshP8l4g" guid="-9AN0xXBZYxIDPOg2N3IC6Q">
+ <keyConsiderations><p>
+ Gain agreement with stakeholders and the rest of the project team regarding the order of objectives and the duration of
+ the project. Make adjustments as&nbsp;necessary.
+</p></keyConsiderations>
+ <refinedDescription>Developing the project plan provides an opportunity for the team to agree on project scope, objectives, initial timeframe,
+and deliverables. It allows the team to begin demonstrating self-organization by defining success criteria and work
+practices to be used. Collaboration and consensus by all key project participants is the goal, but the role responsible for
+this task must ensure that everybody is committed to the plan.</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ZCPNs3ExxsjnNFRTVybQyA" name="project_plan,_4ypNIO-YEdyEMtC_IfEALw" guid="-ZCPNs3ExxsjnNFRTVybQyA">
+ <keyConsiderations>Create and update the project plan in planning sessions that involve the whole team and appropriate project stakeholders in
+order to make sure that everybody agrees with it.</keyConsiderations>
+ <refinedDescription><p>
+ This artifact describes how the project is organized, and identifies what practices will be followed. Additionally, it
+ defines the parameters for tracking project progress, and specifies the high-level objectives of the iterations and
+ their milestones.
+</p>
+<p>
+ The project plan allows stakeholders and other team members to understand the big picture and, roughly, when to expect
+ a certain level of functionality be available.&nbsp;Update the plan&nbsp;as often as necessary, usually at the end of
+ each iteration, in order to reflect changing priorities and needs, as well as record the lessons learned from the
+ project.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-LpEiAis-mzd1_RcJIRimLA" name="glossary,_OpsH8GpmEd24CboUCnKL3A" guid="-LpEiAis-mzd1_RcJIRimLA">
+ <keyConsiderations><p>
+ Although listed as an <i>output from</i> and an <i>input to</i> tasks associated with the requirements discipline, this
+ artifact can be updated at any time and by any role as new terms are identified. The terms defined should be used
+ according to the recorded definitions in all project documentation so that all stakeholders can clearly see that terms
+ are being used consistently.
+</p>
+<p>
+ One of the primary decisions when developing&nbsp;this artifact&nbsp;is whether to have all terms in a single glossary
+ or to maintain terms in several glossaries, business terms artifacts, or models.&nbsp;If terms are defined in multiple
+ places, you need to communicate all of those sources to the team and decide which take precedence.
+</p>
+<p>
+ It may be important, even in small projects, to reference and use existing broader glossaries, business terms
+ artifacts, or data models, where they exist.
+</p>
+<p>
+ Industry- and organization-wide glossaries may be referenced, and compliance with such specific chosen standards may be
+ required.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This artifact&nbsp;helps you avoid miscommunication by providing two essential resources:
+</p>
+<ul>
+ <li>
+ A central location to look for terms and abbreviations that are new to development team members
+ </li>
+ <li>
+ Definitions of terms that are used in specific ways within the domain
+ </li>
+</ul>
+<p>
+ Definitions for the glossary terms come from several sources, such as requirements documents, specifications, and
+ discussions with stakeholders and domain experts.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/initiate_project/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/initiate_project/model.xmi
index 8ed4c37..f89d5b9 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/initiate_project/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/initiate_project/model.xmi
@@ -2,9 +2,19 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__fDK4LekEd-D7YZN9NgldQ" guid="__fDK4LekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__fDK4bekEd-D7YZN9NgldQ" id="-kpXvvHptrggypeoQEamfhw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_yd2MEVmPEeCcpdiAcH0w-w" id="-Y4gn4laxnFk1PUA3-GebOg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_yd_WAFmPEeCcpdiAcH0w-w" id="-z5wrOi6JXS768g53hKiYaA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_yd_WAVmPEeCcpdiAcH0w-w" id="-9AN0xXBZYxIDPOg2N3IC6Q" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_yd_WAlmPEeCcpdiAcH0w-w" id="-ZCPNs3ExxsjnNFRTVybQyA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_yeJHAFmPEeCcpdiAcH0w-w" id="-LpEiAis-mzd1_RcJIRimLA" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_eWxZgNOEEdyqlogshP8l4g" name="initiate_project" guid="_eWxZgNOEEdyqlogshP8l4g">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_sopKYNOJEdyqlogshP8l4g" name="develop_technical_vision" guid="_sopKYNOJEdyqlogshP8l4g" presentationName="Develop Technical Vision" superActivities="_eWxZgdOEEdyqlogshP8l4g" additionallyPerformedBy="_soyUUdOJEdyqlogshP8l4g _soyUUtOJEdyqlogshP8l4g _soyUU9OJEdyqlogshP8l4g" optionalInput="_soyUVNOJEdyqlogshP8l4g" output="_soyUVNOJEdyqlogshP8l4g _OpsH8GpmEd24CboUCnKL3A" performedPrimarilyBy="_soyUUNOJEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_sopKYNOJEdyqlogshP8l4g" name="develop_technical_vision" guid="_sopKYNOJEdyqlogshP8l4g" presentationName="Develop Technical Vision" briefDescription="Define the vision for the future system. Describe the problem and features based on stakeholder requests." superActivities="_eWxZgdOEEdyqlogshP8l4g" optionalInput="_soyUVNOJEdyqlogshP8l4g" output="_soyUVNOJEdyqlogshP8l4g _OpsH8GpmEd24CboUCnKL3A">
+ <presentation xmi:id="-Y4gn4laxnFk1PUA3-GebOg" href="uma://-kpXvvHptrggypeoQEamfhw#-Y4gn4laxnFk1PUA3-GebOg"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WoFUMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_VQ268O0KEdqHTdbLTmC5IQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_OnoNQNSAEdmLhZ9H5Plxyw"/>
<Task href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_0fOAoMlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_ceK-UED2EdyoefaQkqWN_Q"/>
<selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_h7AacED2EdyoefaQkqWN_Q"/>
@@ -14,50 +24,46 @@
<selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#__nDMkED2EdyoefaQkqWN_Q"/>
<selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_Af_gUEIMEd2omsDpG-BNng"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_soyUUNOJEdyqlogshP8l4g" name="analyst" guid="_soyUUNOJEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g" modifies="_soyUVNOJEdyqlogshP8l4g _OpsH8GpmEd24CboUCnKL3A" responsibleFor="_OpsH8GpmEd24CboUCnKL3A _soyUVNOJEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_soyUUdOJEdyqlogshP8l4g" name="architect" guid="_soyUUdOJEdyqlogshP8l4g" presentationName="Architect" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_soyUUtOJEdyqlogshP8l4g" name="project_manager" guid="_soyUUtOJEdyqlogshP8l4g" presentationName="Project Manager" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g" modifies="_4ypNIO-YEdyEMtC_IfEALw" responsibleFor="_4ypNIO-YEdyEMtC_IfEALw">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_soyUU9OJEdyqlogshP8l4g" name="stakeholder" guid="_soyUU9OJEdyqlogshP8l4g" presentationName="Stakeholder" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_soyUVNOJEdyqlogshP8l4g" name="vision" guid="_soyUVNOJEdyqlogshP8l4g" presentationName="Vision" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_soyUVNOJEdyqlogshP8l4g" name="vision" guid="_soyUVNOJEdyqlogshP8l4g" presentationName="Vision" briefDescription="This artifact defines the view of the stakeholders of the technical solution to be developed. This definition is specified in terms of the key needs and features of the stakeholders. The vision contains an outline of the envisioned core requirements for the system." isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-z5wrOi6JXS768g53hKiYaA" href="uma://-kpXvvHptrggypeoQEamfhw#-z5wrOi6JXS768g53hKiYaA"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WoFUMlgEdmt3adZL5Dmdw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_DtlRQI5gEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_t7pDUNOJEdyqlogshP8l4g" name="plan_the_project" guid="_t7pDUNOJEdyqlogshP8l4g" presentationName="Plan Project" superActivities="_eWxZgdOEEdyqlogshP8l4g" additionallyPerformedBy="_soyUUNOJEdyqlogshP8l4g _soyUUdOJEdyqlogshP8l4g _t7pDUdOJEdyqlogshP8l4g _soyUU9OJEdyqlogshP8l4g _t7pDUtOJEdyqlogshP8l4g" mandatoryInput="_tzWYwNnFEdyNWvE4rz3mXQ _wU5YkG7rEd2yFK8n6tDvyw" output="_4ypNIO-YEdyEMtC_IfEALw" performedPrimarilyBy="_soyUUtOJEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_t7pDUNOJEdyqlogshP8l4g" name="plan_the_project" guid="_t7pDUNOJEdyqlogshP8l4g" presentationName="Plan Project" briefDescription="A collaborative task that outlines an initial agreement on how the project will achieve its goals. The resulting project plan provides a summary-level overview of the project." superActivities="_eWxZgdOEEdyqlogshP8l4g" mandatoryInput="_tzWYwNnFEdyNWvE4rz3mXQ _wU5YkG7rEd2yFK8n6tDvyw" output="_4ypNIO-YEdyEMtC_IfEALw">
+ <presentation xmi:id="-9AN0xXBZYxIDPOg2N3IC6Q" href="uma://-kpXvvHptrggypeoQEamfhw#-9AN0xXBZYxIDPOg2N3IC6Q"/>
+ <guidelines href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_Jq64EJjsEduad8I_c-ogIA"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_CGHskBEdEdqY7JB6N6CW2w"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_VNxL4ACsEdu8m4dIntu6jA"/>
+ <guidelines href="uma://_vJYucEfUEdyiPI8btkmvmw#_sLQ6AN8-Edyhmsbt0Xyl8A"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_yYlQoC3xEdycYKq0PulnEQ"/>
<Task href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0lC70MlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_gu-PgIyBEdyhZb-MhCJrlA"/>
<selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_jknm8IyBEdyhZb-MhCJrlA"/>
- <selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_lrYj0MBAEdqSgKaj2SZBmg"/>
<selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_4Xg3QOFpEdyhmsbt0Xyl8A"/>
- <selectedSteps href="uma://-3Jpwts4YZlF8GJjQaSINRA#_X63B4OFtEdyhmsbt0Xyl8A"/>
+ <selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_lrYj0MBAEdqSgKaj2SZBmg"/>
<selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_xWBhUIyBEdyhZb-MhCJrlA"/>
<selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_zeN84IyBEdyhZb-MhCJrlA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_t7pDUdOJEdyqlogshP8l4g" name="developer" guid="_t7pDUdOJEdyqlogshP8l4g" presentationName="Developer" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_t7pDUtOJEdyqlogshP8l4g" name="tester" guid="_t7pDUtOJEdyqlogshP8l4g" presentationName="Tester" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_tzWYwNnFEdyNWvE4rz3mXQ" name="technical_specification_slot" guid="_tzWYwNnFEdyNWvE4rz3mXQ" presentationName="[Technical Specification]" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_tzWYwNnFEdyNWvE4rz3mXQ" name="technical_specification_slot" guid="_tzWYwNnFEdyNWvE4rz3mXQ" presentationName="[Technical Specification]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe requirements, constraints, and goals for the solution." isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4ypNIO-YEdyEMtC_IfEALw" name="project_plan" guid="_4ypNIO-YEdyEMtC_IfEALw" presentationName="Project Plan" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_4ypNIO-YEdyEMtC_IfEALw" name="project_plan" guid="_4ypNIO-YEdyEMtC_IfEALw" presentationName="Project Plan" briefDescription="This artifact gathers all of the information required to manage the project on a strategic level. Its main part consists of a coarse-grained plan, identifying project iterations and their goals." isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-ZCPNs3ExxsjnNFRTVybQyA" href="uma://-kpXvvHptrggypeoQEamfhw#-ZCPNs3ExxsjnNFRTVybQyA"/>
+ <checklists href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_-qtjsAasEdy1uLAzgK8btg"/>
+ <examples href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_Yiq2EDcGEdyTZ9G7ByfQTw"/>
+ <templates href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0c7hoMlgEdmt3adZL5Dmdw"/>
+ <reports href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_ePrt8Dj3EduxovfWMDsntw"/>
<WorkProduct href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0a6vcMlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_OpsH8GpmEd24CboUCnKL3A" name="glossary" guid="_OpsH8GpmEd24CboUCnKL3A" presentationName="Glossary" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_OpsH8GpmEd24CboUCnKL3A" name="glossary" guid="_OpsH8GpmEd24CboUCnKL3A" presentationName="Glossary" briefDescription="This artifact defines important terms used by the project. The collection of terms clarifies the vocabulary used on the project." isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-LpEiAis-mzd1_RcJIRimLA" href="uma://-kpXvvHptrggypeoQEamfhw#-LpEiAis-mzd1_RcJIRimLA"/>
<WorkProduct href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_wU5YkG7rEd2yFK8n6tDvyw" name="project_work_slot" guid="_wU5YkG7rEd2yFK8n6tDvyw" presentationName="[Project Work]" isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_wU5YkG7rEd2yFK8n6tDvyw" name="project_work_slot" guid="_wU5YkG7rEd2yFK8n6tDvyw" presentationName="[Project Work]" briefDescription="This slot serves as an abstraction for any type of work being done on the project. It could be represented as a work items list, an operational schedule, a work breakdown structure, and so on." isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
<WorkProduct href="uma://_vJYucEfUEdyiPI8btkmvmw#_1QZI8EfUEdyiPI8btkmvmw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_eWxZgdOEEdyqlogshP8l4g" name="initiate_project" guid="_eWxZgdOEEdyqlogshP8l4g" presentationName="Initiate Project" briefDescription="Kick off the project and gain agreement with the stakeholders on the scope of the project, and an initial plan for achieving it. This activity bundles tasks required to define the vision and create a project plan." breakdownElements="_sopKYNOJEdyqlogshP8l4g _soyUUNOJEdyqlogshP8l4g _soyUUdOJEdyqlogshP8l4g _soyUUtOJEdyqlogshP8l4g _soyUU9OJEdyqlogshP8l4g _soyUVNOJEdyqlogshP8l4g _t7pDUNOJEdyqlogshP8l4g _t7pDUdOJEdyqlogshP8l4g _t7pDUtOJEdyqlogshP8l4g _tzWYwNnFEdyNWvE4rz3mXQ _4ypNIO-YEdyEMtC_IfEALw _OpsH8GpmEd24CboUCnKL3A _wU5YkG7rEd2yFK8n6tDvyw">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_eWxZgdOEEdyqlogshP8l4g" name="initiate_project" guid="_eWxZgdOEEdyqlogshP8l4g" presentationName="Initiate Project" briefDescription="Kick off the project and gain agreement with the stakeholders on the scope of the project, and an initial plan for achieving it. This activity bundles tasks required to define the vision and create a project plan." breakdownElements="_sopKYNOJEdyqlogshP8l4g _soyUVNOJEdyqlogshP8l4g _t7pDUNOJEdyqlogshP8l4g _tzWYwNnFEdyNWvE4rz3mXQ _4ypNIO-YEdyEMtC_IfEALw _OpsH8GpmEd24CboUCnKL3A _wU5YkG7rEd2yFK8n6tDvyw">
<presentation xmi:id="-kpXvvHptrggypeoQEamfhw" href="uma://-kpXvvHptrggypeoQEamfhw#-kpXvvHptrggypeoQEamfhw"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/ongoing_tasks/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/ongoing_tasks/content.xmi
index 96b4b9d..1aa11ca 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/ongoing_tasks/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/ongoing_tasks/content.xmi
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-aXudKqi6rjimd3UsF0smZA" name="ongoing_tasks,__ZInMdOEEdyqlogshP8l4g" guid="-aXudKqi6rjimd3UsF0smZA" version="7.2.0">
- <mainDescription><p>
+<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="-aXudKqi6rjimd3UsF0smZA" name="ongoing_tasks,__ZInMdOEEdyqlogshP8l4g" guid="-aXudKqi6rjimd3UsF0smZA" version="7.2.0">
+ <mainDescription><p>
This activity includes a task for requesting changes. This task may occur any time during the lifecycle in response to
an observed defect, a desired enhancement, or a change request. It is not planned, which means that it does not appear
as a scheduled activity on the project plan, iteration plan, or work items list. Nevertheless, it is a critical
@@ -10,4 +11,55 @@
Any role may perform this task, however the most common sources of <a class="elementLink" href="./../../practice.tech.continuous_integration.base/guidances/concepts/change_requests_AD4868FE.html" guid="_6jdvECb3Edqh1LYUOGRh2A">Change Requests</a> are stakeholders (enhancement requests and change requests) and
testers (defect reports).
</p></mainDescription>
-</org.eclipse.epf.uma:ProcessDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-giG0nmV9ZE9q-25Wm3nzBQ" name="work_items_list,_HGqkMdnTEdyNj6EOmqy5Rg" guid="-giG0nmV9ZE9q-25Wm3nzBQ">
+ <keyConsiderations><p>
+ Work Items should contain estimates. See guidelines on managing work items and agile estimation.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This artifact provides a focal point for the entire team:
+</p>
+<ul>
+ <li>
+ It provides one list containing all requests for additional capabilities or enhancement for that application. Note
+ that some of these requests may never be implemented, or be implemented in later projects.
+ </li>
+ <li>
+ It provides one list of all the work to be prioritized, estimated, and assigned within the project. The risk list
+ is prioritized separately.
+ </li>
+ <li>
+ It provides one place to go to for the development team to understand what&nbsp;micro-increments&nbsp;need to be
+ delivered, get references to material required to carry out the work, and report progress made.
+ </li>
+</ul>
+<p>
+ These are the typical work items that go on this list:
+</p>
+<ul>
+ <li>
+ Use cases (and references to use-case specifications)
+ </li>
+ <li>
+ System-wide requirements
+ </li>
+ <li>
+ Changes and enhancement requests
+ </li>
+ <li>
+ Defects
+ </li>
+ <li>
+ Development tasks
+ </li>
+</ul>
+<p>
+ Work items can be very large in scope, especially when capturing requests for enhancements, such as "Support Financial
+ Planning" for a personal finance application. To allow the application to be developed in micro-increments, work items
+ are analyzed and broken down into smaller work items so that they can be assigned to an iteration, such as a use-case
+ scenario for&nbsp;"Calculate Net Worth". Further breakdown may be required to identify suitable tasks to be assigned to
+ developers, such as "Develop UI for Calculate Net Worth". This means that work items often have parent/child
+ relationships, where the lowest level is a specification and tracking device for micro-increments.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/ongoing_tasks/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/ongoing_tasks/model.xmi
index 4985d9a..c8e0b24 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/ongoing_tasks/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/ongoing_tasks/model.xmi
@@ -2,20 +2,24 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__gFssbekEd-D7YZN9NgldQ" guid="__gFssbekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__gFssrekEd-D7YZN9NgldQ" id="-aXudKqi6rjimd3UsF0smZA" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_b87ucVmQEeCcpdiAcH0w-w" id="-giG0nmV9ZE9q-25Wm3nzBQ" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="__ZInMNOEEdyqlogshP8l4g" name="ongoing_tasks" guid="__ZInMNOEEdyqlogshP8l4g">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_HGqkMNnTEdyNj6EOmqy5Rg" name="request_change" guid="_HGqkMNnTEdyNj6EOmqy5Rg" presentationName="Request Change" superActivities="__ZInMdOEEdyqlogshP8l4g" output="_HGqkMdnTEdyNj6EOmqy5Rg" performedPrimarilyBy="_WjtCIO-ZEdyEMtC_IfEALw">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_HGqkMNnTEdyNj6EOmqy5Rg" name="request_change" guid="_HGqkMNnTEdyNj6EOmqy5Rg" presentationName="Request Change" briefDescription="Capture and record change requests." superActivities="__ZInMdOEEdyqlogshP8l4g" output="_HGqkMdnTEdyNj6EOmqy5Rg">
+ <guidelines href="uma://_44o4AOvVEdyp6czxLiQq9g#_fnZj0NVXEdqy9sbRhejO5Q"/>
<Task href="uma://_44o4AOvVEdyp6czxLiQq9g#_0mwzEclgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_Nr0S4KeqEdmKDbQuyzCoqQ#_qEkewKuoEdmEGLSmmpF1Sg"/>
<selectedSteps href="uma://_Nr0S4KeqEdmKDbQuyzCoqQ#_r2aP0KuoEdmEGLSmmpF1Sg"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HGqkMdnTEdyNj6EOmqy5Rg" name="work_items_list" guid="_HGqkMdnTEdyNj6EOmqy5Rg" presentationName="Work Items List" isPlanned="false" superActivities="__ZInMdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HGqkMdnTEdyNj6EOmqy5Rg" name="work_items_list" guid="_HGqkMdnTEdyNj6EOmqy5Rg" presentationName="Work Items List" briefDescription="This artifact contains a list of all of the scheduled work to be done within the project, as well as proposed work that may affect the product in this or future projects. Each work item may contain references to information relevant to carry out the work described within the work item." isPlanned="false" superActivities="__ZInMdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-giG0nmV9ZE9q-25Wm3nzBQ" href="uma://-aXudKqi6rjimd3UsF0smZA#-giG0nmV9ZE9q-25Wm3nzBQ"/>
+ <checklists href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_xlrdEAVtEdy3F_fZDaPZVA"/>
+ <examples href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_nHomIDgzEdu4E8ZdmlYjtA"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_CGHskBEdEdqY7JB6N6CW2w"/>
+ <templates href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_QwUJYDg0Edu4E8ZdmlYjtA"/>
<WorkProduct href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_rGNWsCbSEdqh1LYUOGRh2A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_WjtCIO-ZEdyEMtC_IfEALw" name="any_role" guid="_WjtCIO-ZEdyEMtC_IfEALw" presentationName="Any Role" isPlanned="false" superActivities="__ZInMdOEEdyqlogshP8l4g" modifies="_HGqkMdnTEdyNj6EOmqy5Rg">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0dsWoMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="__ZInMdOEEdyqlogshP8l4g" name="ongoing_tasks" guid="__ZInMdOEEdyqlogshP8l4g" presentationName="Ongoing Tasks" briefDescription="Perform ongoing tasks that are not necessarily part of the project schedule." isPlanned="false" breakdownElements="_HGqkMNnTEdyNj6EOmqy5Rg _HGqkMdnTEdyNj6EOmqy5Rg _WjtCIO-ZEdyEMtC_IfEALw">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="__ZInMdOEEdyqlogshP8l4g" name="ongoing_tasks" guid="__ZInMdOEEdyqlogshP8l4g" presentationName="Ongoing Tasks" briefDescription="Perform ongoing tasks that are not necessarily part of the project schedule." isPlanned="false" breakdownElements="_HGqkMNnTEdyNj6EOmqy5Rg _HGqkMdnTEdyNj6EOmqy5Rg">
<presentation xmi:id="-aXudKqi6rjimd3UsF0smZA" href="uma://-aXudKqi6rjimd3UsF0smZA#-aXudKqi6rjimd3UsF0smZA"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/plan_manage_iteration/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/plan_manage_iteration/content.xmi
index 5a74f15..e8f2020 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/plan_manage_iteration/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/plan_manage_iteration/content.xmi
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="-b6sTuOuA7eFhaR_H3EfgBw" name="plan_manage_iteration,_oZgCsdOEEdyqlogshP8l4g" guid="-b6sTuOuA7eFhaR_H3EfgBw" version="7.2.0">
- <mainDescription><p>
+<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="-b6sTuOuA7eFhaR_H3EfgBw" name="plan_manage_iteration,_oZgCsdOEEdyqlogshP8l4g" guid="-b6sTuOuA7eFhaR_H3EfgBw" version="7.2.0">
+ <mainDescription><p>
This activity is performed throughout the project lifecycle. The goal of this activity is to identify risks and issues
early enough that they can be mitigated, to establish the goals for the iteration, and to support the development team
in reaching these goals.
@@ -26,4 +27,138 @@
implemented. Lessons learned are captured in order to modify the project or improve the process. If the iteration end
coincides with the phase end, make sure the objectives for that phase have been met (see <a class="elementLinkWithType" href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones_5678231E.html" guid="_HNxbwMBJEdqSgKaj2SZBmg">Concept: Phase Milestones</a> for more information).
</p></mainDescription>
-</org.eclipse.epf.uma:ProcessDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-HoXXyN2BKM1DoI1eHGVrGw" name="plan_iteration,_y05RQNOJEdyqlogshP8l4g" guid="-HoXXyN2BKM1DoI1eHGVrGw">
+ <refinedDescription><p>
+ During project planning, iterations are identified, but the estimates have an acceptable uncertainty due to the lack of
+ detail at the project inception. This task is repeated for each iteration within a release. It allows the team to
+ increase the accuracy of the estimates for one iteration, as more detail is known along the project.
+</p>
+<p>
+ Ensure that the team commits to a reasonable amount of work for the iteration, based on team performance from previous
+ iterations.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-b0cwbrvCtusECT9Bx_eEkQ" name="iteration_plan,_y1MMMNOJEdyqlogshP8l4g" guid="-b0cwbrvCtusECT9Bx_eEkQ">
+ <keyConsiderations><p>
+ Work items assigned to an iteration do not necessarily have the same priority. When selecting work items from the Work
+ Items List, the iteration plan may end up having work items with different priorities (for example, you assign the
+ remaining high priority work items, plus a few mid-priority ones from the Work Items List). Once work items have been
+ assigned to the iteration, the team ensures that they can complete all work, regardless of original work item
+ priorities. Deciding what to develop first on an iteration will vary across projects and iterations.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This artifact captures the key milestones of an iteration, showing start and end dates, intermediate milestones,
+ synchronization points with other teams, demos, and so on. This artifact is also used to capture issues that need to be
+ solved during the iteration.
+</p>
+<p>
+ You should list a few objectives for the iteration, which will help guide you throughout the iteration. Also, assess at
+ the end if those objectives have been achieved.
+</p>
+<p>
+ The task assignments for an iteration are a subset of all tasks on the <a class="elementLinkWithType"
+ href="./../../core.mgmt.common.extend_supp/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>. Therefore, the iteration plan ideally references those
+ work items.
+</p>
+<p>
+ The evaluation criteria and iteration assessment information are captured in this artifact, so that you can communicate
+ results and actions from assessments.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-uiigawastH3uIscV6br3Mg" name="risk_list,_y1MMMdOJEdyqlogshP8l4g" guid="-uiigawastH3uIscV6br3Mg">
+ <keyConsiderations><p>
+ This list should capture the critical and serious risks. If you find this list extending beyond 20 items, carefully
+ consider whether they are really serious risks. Tracking more than 20 risks is an onerous task.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This list identifies, in decreasing order of priority, all the <a class="elementLinkWithUserText"
+ href="./../../core.mgmt.common.base/guidances/termdefinitions/risk_33255339.html"
+ guid="_ii2LUEvGEdunZcj9T5hrMQ">risks</a> associated to a project.&nbsp;It serves as a focal point for project
+ activities, and is the basis around which iterations are organized.
+</p>
+<p>
+ See <a class="elementLinkWithType" href="./../../core.mgmt.common.extend_supp/guidances/concepts/risk_AF5840DA.html"
+ guid="_0bsLgMlgEdmt3adZL5Dmdw">Concept: Risk</a>&nbsp;for more details.<!--EndFragment-->
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-mTtAiA6WcEVWloBE8ZdcOg" name="work_items_list,_y1MMMtOJEdyqlogshP8l4g" guid="-mTtAiA6WcEVWloBE8ZdcOg">
+ <keyConsiderations><p>
+ Work Items should contain estimates. See guidelines on managing work items and agile estimation.
+</p></keyConsiderations>
+ <refinedDescription><p>
+ This artifact provides a focal point for the entire team:
+</p>
+<ul>
+ <li>
+ It provides one list containing all requests for additional capabilities or enhancement for that application. Note
+ that some of these requests may never be implemented, or be implemented in later projects.
+ </li>
+ <li>
+ It provides one list of all the work to be prioritized, estimated, and assigned within the project. The risk list
+ is prioritized separately.
+ </li>
+ <li>
+ It provides one place to go to for the development team to understand what&nbsp;micro-increments&nbsp;need to be
+ delivered, get references to material required to carry out the work, and report progress made.
+ </li>
+</ul>
+<p>
+ These are the typical work items that go on this list:
+</p>
+<ul>
+ <li>
+ Use cases (and references to use-case specifications)
+ </li>
+ <li>
+ System-wide requirements
+ </li>
+ <li>
+ Changes and enhancement requests
+ </li>
+ <li>
+ Defects
+ </li>
+ <li>
+ Development tasks
+ </li>
+</ul>
+<p>
+ Work items can be very large in scope, especially when capturing requests for enhancements, such as "Support Financial
+ Planning" for a personal finance application. To allow the application to be developed in micro-increments, work items
+ are analyzed and broken down into smaller work items so that they can be assigned to an iteration, such as a use-case
+ scenario for&nbsp;"Calculate Net Worth". Further breakdown may be required to identify suitable tasks to be assigned to
+ developers, such as "Develop UI for Calculate Net Worth". This means that work items often have parent/child
+ relationships, where the lowest level is a specification and tracking device for micro-increments.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ZTgIJKYY8ZpIoo7b-pFrFg" name="manage_iteration,_zjF0ANOJEdyqlogshP8l4g" guid="-ZTgIJKYY8ZpIoo7b-pFrFg">
+ <refinedDescription><p>
+ Developing the team is part of executing the project. Improve the interactions and trust between team members,
+ incorporating team building into project activities, and empowering the team to make decisions. Management is done by
+ objectives and not by time reporting.
+</p>
+<p>
+ Help the team meet the iteration objectives by removing constraints, and by monitoring the progress and work remaining
+ to completion. When the team is falling behind, help the team assess how it can reduce work and still meet the
+ iteration goals. Involve stakeholders in approving changes and actions that affect them, so that their objectives for
+ the iteration can be met, and the issues they raise can be solved throughout the iteration.
+</p>
+<p>
+ Select an approach for the collection of basic metrics: ideally, they are automatically generated from the tools at
+ hand, but can be manually assembled, or both. <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Outline
+ which metrics the project should use in the <a class="elementLink"
+ href="./../../core.mgmt.slot.base/workproducts/project_definition_and_scope_slot_BB8EB6F7.html"
+ guid="_RJMUcNpUEdyzZqGyZ7hwdw">[Project Definition and Scope]</a>.</span>
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-2lpprtg7ud6uXyuBYZMnIg" name="assess_results,_0Qiv4NOJEdyqlogshP8l4g" guid="-2lpprtg7ud6uXyuBYZMnIg">
+ <refinedDescription>Coordinate the assessment and discuss with the team how the iteration results will be best presented to stakeholders, so
+that they can learn as much about the solution as possible. Listen to what the team has to say about what went wrong (and
+what went right) during the iteration. This knowledge will help everybody make informed decisions about the next iteration
+planning, and determine the best course of action for the project. This task is performed at the end of every iteration
+until the end of the project.</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/plan_manage_iteration/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/plan_manage_iteration/model.xmi
index 29b9aab..7453018 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/plan_manage_iteration/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/plan_manage_iteration/model.xmi
@@ -2,48 +2,64 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__fDK47ekEd-D7YZN9NgldQ" guid="__fDK47ekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__fDK5LekEd-D7YZN9NgldQ" id="-b6sTuOuA7eFhaR_H3EfgBw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_AIPfgFmQEeCcpdiAcH0w-w" id="-HoXXyN2BKM1DoI1eHGVrGw" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_AIPfgVmQEeCcpdiAcH0w-w" id="-b0cwbrvCtusECT9Bx_eEkQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_AIPfglmQEeCcpdiAcH0w-w" id="-uiigawastH3uIscV6br3Mg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_AIPfg1mQEeCcpdiAcH0w-w" id="-mTtAiA6WcEVWloBE8ZdcOg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_AIZQgFmQEeCcpdiAcH0w-w" id="-ZTgIJKYY8ZpIoo7b-pFrFg" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_AIZQgVmQEeCcpdiAcH0w-w" id="-2lpprtg7ud6uXyuBYZMnIg" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_oZgCsNOEEdyqlogshP8l4g" name="plan_manage_iteration" guid="_oZgCsNOEEdyqlogshP8l4g">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_y05RQNOJEdyqlogshP8l4g" name="plan_iteration" guid="_y05RQNOJEdyqlogshP8l4g" presentationName="Plan Iteration" superActivities="_oZgCsdOEEdyqlogshP8l4g" additionallyPerformedBy="_y1CbMdOJEdyqlogshP8l4g _y1CbMtOJEdyqlogshP8l4g _y1CbM9OJEdyqlogshP8l4g _y1CbNNOJEdyqlogshP8l4g _y1CbNdOJEdyqlogshP8l4g" mandatoryInput="_y1MMMtOJEdyqlogshP8l4g" optionalInput="_y1MMM9OJEdyqlogshP8l4g _LxTaQNnGEdyNWvE4rz3mXQ _y1MMMdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g" output="_y1MMMdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g" performedPrimarilyBy="_y1CbMNOJEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_y05RQNOJEdyqlogshP8l4g" name="plan_iteration" guid="_y05RQNOJEdyqlogshP8l4g" presentationName="Plan Iteration" briefDescription="Plan the scope and responsibilities for a single iteration." superActivities="_oZgCsdOEEdyqlogshP8l4g" mandatoryInput="_y1MMMtOJEdyqlogshP8l4g" optionalInput="_y1MMM9OJEdyqlogshP8l4g _LxTaQNnGEdyNWvE4rz3mXQ _y1MMMdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g" output="_y1MMMdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g">
+ <presentation xmi:id="-HoXXyN2BKM1DoI1eHGVrGw" href="uma://-b6sTuOuA7eFhaR_H3EfgBw#-HoXXyN2BKM1DoI1eHGVrGw"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_CGHskBEdEdqY7JB6N6CW2w"/>
+ <guidelines href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0auiMMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_VNxL4ACsEdu8m4dIntu6jA"/>
+ <guidelines href="uma://_vJYucEfUEdyiPI8btkmvmw#_sLQ6AN8-Edyhmsbt0Xyl8A"/>
+ <guidelines href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_oVMZADSoEdy07ZJqOGUGaQ"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#__yQQ4L6REdqti4GwqTkbsQ"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_yYlQoC3xEdycYKq0PulnEQ"/>
<Task href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0keUEMlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_7bz7AIyAEdyhZb-MhCJrlA"/>
<selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_CtKCMMBHEdqSgKaj2SZBmg"/>
- <selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_307v0MMsEdmdo9HxCRR_Gw"/>
<selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_HzNVgIyBEdyhZb-MhCJrlA"/>
+ <selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_307v0MMsEdmdo9HxCRR_Gw"/>
<selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_7Hqr4MMsEdmdo9HxCRR_Gw"/>
<selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_-tp18FHjEd2IaYFd32DrjQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbMNOJEdyqlogshP8l4g" name="project_manager" guid="_y1CbMNOJEdyqlogshP8l4g" presentationName="Project Manager" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g" modifies="_y1MMMdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g" responsibleFor="_y1MMMtOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbMdOJEdyqlogshP8l4g" name="analyst" guid="_y1CbMdOJEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbMtOJEdyqlogshP8l4g" name="architect" guid="_y1CbMtOJEdyqlogshP8l4g" presentationName="Architect" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbM9OJEdyqlogshP8l4g" name="developer" guid="_y1CbM9OJEdyqlogshP8l4g" presentationName="Developer" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbNNOJEdyqlogshP8l4g" name="stakeholder" guid="_y1CbNNOJEdyqlogshP8l4g" presentationName="Stakeholder" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbNdOJEdyqlogshP8l4g" name="tester" guid="_y1CbNdOJEdyqlogshP8l4g" presentationName="Tester" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMNOJEdyqlogshP8l4g" name="iteration_plan" guid="_y1MMMNOJEdyqlogshP8l4g" presentationName="Iteration Plan" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMNOJEdyqlogshP8l4g" name="iteration_plan" guid="_y1MMMNOJEdyqlogshP8l4g" presentationName="Iteration Plan" briefDescription="A fine-grained plan describing the objectives, work assignments, and evaluation criteria for the iteration." isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-b0cwbrvCtusECT9Bx_eEkQ" href="uma://-b6sTuOuA7eFhaR_H3EfgBw#-b0cwbrvCtusECT9Bx_eEkQ"/>
+ <concepts href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lam4ADkBEduxovfWMDsntw"/>
+ <examples href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_GtGisDcGEdyTZ9G7ByfQTw"/>
+ <examples href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_TuNhIEE4EdulKujnGUuxbg"/>
+ <templates href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0dBoQMlgEdmt3adZL5Dmdw"/>
+ <reports href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_uAzgkDg3Edu4E8ZdmlYjtA"/>
<WorkProduct href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0aQBEslgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMdOJEdyqlogshP8l4g" name="risk_list" guid="_y1MMMdOJEdyqlogshP8l4g" presentationName="Risk List" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMdOJEdyqlogshP8l4g" name="risk_list" guid="_y1MMMdOJEdyqlogshP8l4g" presentationName="Risk List" briefDescription="This artifact is a sorted list of known and open risks to the project, sorted in order of importance and associated with specific mitigation or contingency actions." isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-uiigawastH3uIscV6br3Mg" href="uma://-b6sTuOuA7eFhaR_H3EfgBw#-uiigawastH3uIscV6br3Mg"/>
+ <checklists href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_7BZa0DIdEduDTv4Y1akVTA"/>
+ <concepts href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0bsLgMlgEdmt3adZL5Dmdw"/>
+ <templates href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_MIUO0C8FEduzydamRseoUw"/>
<WorkProduct href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMtOJEdyqlogshP8l4g" name="work_items_list" guid="_y1MMMtOJEdyqlogshP8l4g" presentationName="Work Items List" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMtOJEdyqlogshP8l4g" name="work_items_list" guid="_y1MMMtOJEdyqlogshP8l4g" presentationName="Work Items List" briefDescription="This artifact contains a list of all of the scheduled work to be done within the project, as well as proposed work that may affect the product in this or future projects. Each work item may contain references to information relevant to carry out the work described within the work item." isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <presentation xmi:id="-mTtAiA6WcEVWloBE8ZdcOg" href="uma://-b6sTuOuA7eFhaR_H3EfgBw#-mTtAiA6WcEVWloBE8ZdcOg"/>
+ <checklists href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_xlrdEAVtEdy3F_fZDaPZVA"/>
+ <examples href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_nHomIDgzEdu4E8ZdmlYjtA"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_CGHskBEdEdqY7JB6N6CW2w"/>
+ <templates href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_QwUJYDg0Edu4E8ZdmlYjtA"/>
<WorkProduct href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_rGNWsCbSEdqh1LYUOGRh2A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMM9OJEdyqlogshP8l4g" name="technical_architecture_slot" guid="_y1MMM9OJEdyqlogshP8l4g" presentationName="[Technical Architecture]" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMM9OJEdyqlogshP8l4g" name="technical_architecture_slot" guid="_y1MMM9OJEdyqlogshP8l4g" presentationName="[Technical Architecture]" briefDescription="This slot serves as an abstraction of high level artifacts that represent the documentation of the architecture." isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_8OD-cLPTEduocbW-TPTq7A"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_zjF0ANOJEdyqlogshP8l4g" name="manage_iteration" guid="_zjF0ANOJEdyqlogshP8l4g" presentationName="Manage Iteration" superActivities="_oZgCsdOEEdyqlogshP8l4g" additionallyPerformedBy="_y1CbMdOJEdyqlogshP8l4g _y1CbMtOJEdyqlogshP8l4g _y1CbM9OJEdyqlogshP8l4g _y1CbNNOJEdyqlogshP8l4g _y1CbNdOJEdyqlogshP8l4g" mandatoryInput="_y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g _-AGJcO-YEdyEMtC_IfEALw" output="_y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g" performedPrimarilyBy="_y1CbMNOJEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_zjF0ANOJEdyqlogshP8l4g" name="manage_iteration" guid="_zjF0ANOJEdyqlogshP8l4g" presentationName="Manage Iteration" briefDescription="Assess project status and identify any blocking issues and opportunities. Identify and manage exceptions, problems, and risks. Communicate project status." superActivities="_oZgCsdOEEdyqlogshP8l4g" mandatoryInput="_y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g _-AGJcO-YEdyEMtC_IfEALw" output="_y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g">
+ <presentation xmi:id="-ZTgIJKYY8ZpIoo7b-pFrFg" href="uma://-b6sTuOuA7eFhaR_H3EfgBw#-ZTgIJKYY8ZpIoo7b-pFrFg"/>
+ <concepts href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0bsLgMlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0mYYkMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#__yQQ4L6REdqti4GwqTkbsQ"/>
+ <guidelines href="uma://_vJYucEfUEdyiPI8btkmvmw#_68JUYN8-Edyhmsbt0Xyl8A"/>
<Task href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_8S2aICbYEdqh1LYUOGRh2A"/>
<selectedSteps href="uma://-PbfqVxB_j9KN-Jx39_pEUA#_OE65ICuxEdqTIKp3l5PtzQ"/>
<selectedSteps href="uma://-PbfqVxB_j9KN-Jx39_pEUA#_urvQkGSyEd2DNqLAFatITA"/>
@@ -51,24 +67,29 @@
<selectedSteps href="uma://-PbfqVxB_j9KN-Jx39_pEUA#_xiFJwCbZEdqh1LYUOGRh2A"/>
<selectedSteps href="uma://-PbfqVxB_j9KN-Jx39_pEUA#_Br6VECuxEdqTIKp3l5PtzQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0Qiv4NOJEdyqlogshP8l4g" name="assess_results" guid="_0Qiv4NOJEdyqlogshP8l4g" presentationName="Assess Results" superActivities="_oZgCsdOEEdyqlogshP8l4g" additionallyPerformedBy="_y1CbMdOJEdyqlogshP8l4g _y1CbMtOJEdyqlogshP8l4g _y1CbM9OJEdyqlogshP8l4g _y1CbNNOJEdyqlogshP8l4g _y1CbNdOJEdyqlogshP8l4g" mandatoryInput="_y1MMMNOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g" optionalInput="_LxTaQNnGEdyNWvE4rz3mXQ _LxTaQdnGEdyNWvE4rz3mXQ _-AGJcO-YEdyEMtC_IfEALw" output="_y1MMMNOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g" performedPrimarilyBy="_y1CbMNOJEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0Qiv4NOJEdyqlogshP8l4g" name="assess_results" guid="_0Qiv4NOJEdyqlogshP8l4g" presentationName="Assess Results" briefDescription="Determine success or failure of the iteration. Apply the lessons learned to modify the project or improve the process." superActivities="_oZgCsdOEEdyqlogshP8l4g" mandatoryInput="_y1MMMNOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g" optionalInput="_LxTaQNnGEdyNWvE4rz3mXQ _LxTaQdnGEdyNWvE4rz3mXQ _-AGJcO-YEdyEMtC_IfEALw" output="_y1MMMNOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g">
+ <presentation xmi:id="-2lpprtg7ud6uXyuBYZMnIg" href="uma://-b6sTuOuA7eFhaR_H3EfgBw#-2lpprtg7ud6uXyuBYZMnIg"/>
+ <concepts href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_2PfbIA4QEdy2q5zsU8WDnA"/>
+ <guidelines href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_277QEA4gEdy63f1yVoPyfA"/>
+ <guidelines href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_FekBAC4IEdyhZrtGEIITGQ"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_yYlQoC3xEdycYKq0PulnEQ"/>
+ <toolmentor href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_pJJuIOFSEdyhmsbt0Xyl8A"/>
<Task href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0l53cMlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_o28GgMMsEdmdo9HxCRR_Gw"/>
<selectedSteps href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_iSiDEIx4Edyzd4h-mxj9YA"/>
<selectedSteps href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_iL7cQEpqEdup0IY9DKDPkg"/>
- <selectedSteps href="uma://-EYuybNBtVpvW4i5T_j805w#_uYLJAOFYEdyhmsbt0Xyl8A"/>
<selectedSteps href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_1YHH8DLqEdueZPye-FaNgA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_LxTaQNnGEdyNWvE4rz3mXQ" name="technical_specification_slot" guid="_LxTaQNnGEdyNWvE4rz3mXQ" presentationName="[Technical Specification]" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_LxTaQNnGEdyNWvE4rz3mXQ" name="technical_specification_slot" guid="_LxTaQNnGEdyNWvE4rz3mXQ" presentationName="[Technical Specification]" briefDescription="This slot serves as an abstraction of high-level artifacts that describe requirements, constraints, and goals for the solution." isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_LxTaQdnGEdyNWvE4rz3mXQ" name="technical_test_results_slot" guid="_LxTaQdnGEdyNWvE4rz3mXQ" presentationName="[Technical Test Results]" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_LxTaQdnGEdyNWvE4rz3mXQ" name="technical_test_results_slot" guid="_LxTaQdnGEdyNWvE4rz3mXQ" presentationName="[Technical Test Results]" briefDescription="This slot serves as an abstraction of high level artifacts that define the results of testing the hardware and software for the system being developed." isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_fahB0EfUEdyiPI8btkmvmw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_-AGJcO-YEdyEMtC_IfEALw" name="project_definition_and_scope_slot" guid="_-AGJcO-YEdyEMtC_IfEALw" presentationName="[Project Definition and Scope]" isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_-AGJcO-YEdyEMtC_IfEALw" name="project_definition_and_scope_slot" guid="_-AGJcO-YEdyEMtC_IfEALw" presentationName="[Project Definition and Scope]" briefDescription="This slot serves as an abstraction of high-level artifacts that define the project and its scope. Typical examples of such artifacts could be a project definition, and a high-level project schedule identifying major milestones and major deliverables." isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
<WorkProduct href="uma://_vJYucEfUEdyiPI8btkmvmw#_RJMUcNpUEdyzZqGyZ7hwdw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_oZgCsdOEEdyqlogshP8l4g" name="plan_manage_iteration" guid="_oZgCsdOEEdyqlogshP8l4g" presentationName="Plan and Manage Iteration" briefDescription="Initiate the iteration and allow team members to sign up for development tasks. Monitor and communicate project status to external stakeholders. Identify and handle exceptions and problems." breakdownElements="_y05RQNOJEdyqlogshP8l4g _y1CbMNOJEdyqlogshP8l4g _y1CbMdOJEdyqlogshP8l4g _y1CbMtOJEdyqlogshP8l4g _y1CbM9OJEdyqlogshP8l4g _y1CbNNOJEdyqlogshP8l4g _y1CbNdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g _y1MMM9OJEdyqlogshP8l4g _zjF0ANOJEdyqlogshP8l4g _0Qiv4NOJEdyqlogshP8l4g _LxTaQNnGEdyNWvE4rz3mXQ _LxTaQdnGEdyNWvE4rz3mXQ _-AGJcO-YEdyEMtC_IfEALw">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_oZgCsdOEEdyqlogshP8l4g" name="plan_manage_iteration" guid="_oZgCsdOEEdyqlogshP8l4g" presentationName="Plan and Manage Iteration" briefDescription="Initiate the iteration and allow team members to sign up for development tasks. Monitor and communicate project status to external stakeholders. Identify and handle exceptions and problems." breakdownElements="_y05RQNOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g _y1MMM9OJEdyqlogshP8l4g _zjF0ANOJEdyqlogshP8l4g _0Qiv4NOJEdyqlogshP8l4g _LxTaQNnGEdyNWvE4rz3mXQ _LxTaQdnGEdyNWvE4rz3mXQ _-AGJcO-YEdyEMtC_IfEALw">
<presentation xmi:id="-b6sTuOuA7eFhaR_H3EfgBw" href="uma://-b6sTuOuA7eFhaR_H3EfgBw#-b6sTuOuA7eFhaR_H3EfgBw"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/content.xmi
index df8c019..a5fe790 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/content.xmi
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ProcessDescription 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" xmi:id="--GUCGSJomnx0WV9XKvVyXQ" name="test_solution,_buG4sdOFEdyqlogshP8l4g" guid="--GUCGSJomnx0WV9XKvVyXQ" version="7.2.0">
- <mainDescription><p>
+<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="--GUCGSJomnx0WV9XKvVyXQ" name="test_solution,_buG4sdOFEdyqlogshP8l4g" guid="--GUCGSJomnx0WV9XKvVyXQ" version="7.2.0">
+ <mainDescription><p>
This activity is repeated throughout the project lifecycle. The main goal of this activity is to validate that the
current build of the system satisfies the requirements allocated to it.
</p>
@@ -16,13 +17,48 @@
<p>
Stakeholders and end-users also may also be involved in performing tests to accept the release.
</p></mainDescription>
- <purpose>Develop and run test scripts to validate that the system satisfies the requirements.</purpose>
- <howtoStaff><p>
+ <purpose>Develop and run test scripts to validate that the system satisfies the requirements.</purpose>
+ <howtoStaff><p>
The staff performing this activity must be integrated into the team.
</p></howtoStaff>
- <usageNotes><p>
+ <usageNotes><p>
Testing must occur throughout the process and throughout each iteration. Testing is not a final inspection to be
performed at the end of the project. As requirements are implemented and integrated into a build, you should test them
as soon as possible.
</p></usageNotes>
-</org.eclipse.epf.uma:ProcessDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-dGeCbV3mYf6d7tqFxsHq4A" name="test_case,_Vi5r8NOLEdyqlogshP8l4g" guid="-dGeCbV3mYf6d7tqFxsHq4A">
+ <refinedDescription><p>
+ A test case specifies the conditions that must be validated to enable an assessment of aspects of the system under
+ test. A test case is more formal than a test idea; typically, a test case takes the form of a specification. In less
+ formal environments, you can create test cases by identifying a unique ID, name, associated test data, and expected
+ results.
+</p>
+<p>
+ Test cases can be derived from many sources, and typically include a subset of the requirements (such as use cases,
+ performance characteristics, and reliability concerns) and other types of quality attributes. For more information on
+ types of tests and their relationships to quality test attributes, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.extend_supp/guidances/concepts/testing_qualitative_rqmts_CAE80710.html"
+ guid="_0aJ6cMlgEdmt3adZL5Dmdw">Concept: Testing Qualitative Requirements</a>.
+</p></refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-S7RJDT8En1BwhtenbO3p8w" name="run_tests,_WttSMNOLEdyqlogshP8l4g" guid="-S7RJDT8En1BwhtenbO3p8w">
+ <keyConsiderations><ul>
+ <li>
+ Run all tests as frequently as possible. Ideally, run all test scripts against each build deployed to the test
+ environment. If this is impractical, run regression tests for existing functionality, and&nbsp;focus the test cycle
+ on work items completed in the new build.
+ </li>
+ <li>
+ Even test scripts that are expected to fail provide valuable feedback. However, once a test script is passing, it
+ should not fail&nbsp;against subsequent builds of the solution.
+ </li>
+</ul></keyConsiderations>
+ </org.eclipse.epf.uma:DescriptorDescription>
+ <org.eclipse.epf.uma:DescriptorDescription xmi:id="-kjFCWWTMDhXbgfduK1uQCQ" name="test_log,_WttSMdOLEdyqlogshP8l4g" guid="-kjFCWWTMDhXbgfduK1uQCQ">
+ <refinedDescription>This artifact provides a detailed, typically time-based record that both verifies that a set of tests were run, and
+provides information that relates to the success of those tests. The focus is typically on providing an accurate audit
+trail, which enables you to undertake a post-run diagnosis of failures. This raw data is subsequently analyzed to determine
+the results of an aspect of the test effort.</refinedDescription>
+ </org.eclipse.epf.uma:DescriptorDescription>
+</xmi:XMI>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/model.xmi
index 20a5da9..d34dc7f 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/model.xmi
@@ -2,9 +2,16 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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.resourcemanager:ResourceManager xmi:id="__gZOs7ekEd-D7YZN9NgldQ" guid="__gZOs7ekEd-D7YZN9NgldQ">
<resourceDescriptors xmi:id="__gZOtLekEd-D7YZN9NgldQ" id="--GUCGSJomnx0WV9XKvVyXQ" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_de0_AVmQEeCcpdiAcH0w-w" id="-dGeCbV3mYf6d7tqFxsHq4A" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_de0_AlmQEeCcpdiAcH0w-w" id="-S7RJDT8En1BwhtenbO3p8w" uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_de0_A1mQEeCcpdiAcH0w-w" id="-kjFCWWTMDhXbgfduK1uQCQ" uri="content.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
<org.eclipse.epf.uma:ProcessComponent xmi:id="_buG4sNOFEdyqlogshP8l4g" name="test_solution" guid="_buG4sNOFEdyqlogshP8l4g">
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Viv68NOLEdyqlogshP8l4g" name="implement_tests" guid="_Viv68NOLEdyqlogshP8l4g" presentationName="Implement Tests" superActivities="_buG4sdOFEdyqlogshP8l4g" additionallyPerformedBy="_Viv68tOLEdyqlogshP8l4g _Viv689OLEdyqlogshP8l4g _Viv69NOLEdyqlogshP8l4g" mandatoryInput="_Vi5r8NOLEdyqlogshP8l4g" optionalInput="_Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g" output="_Vi5r8dOLEdyqlogshP8l4g" performedPrimarilyBy="_Viv68dOLEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Viv68NOLEdyqlogshP8l4g" name="implement_tests" guid="_Viv68NOLEdyqlogshP8l4g" presentationName="Implement Tests" briefDescription="Implement Test Scripts to validate a Build of the solution. Organize Test Scripts into suites, and collaborate to ensure appropriate depth and breadth of test feedback." superActivities="_buG4sdOFEdyqlogshP8l4g" mandatoryInput="_Vi5r8NOLEdyqlogshP8l4g" optionalInput="_Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g" output="_Vi5r8dOLEdyqlogshP8l4g">
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jnYcMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kF5kMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0j5sUMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jzlsMlgEdmt3adZL5Dmdw"/>
<Task href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jO98MlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_A56NkKRKEdyLP-jEVj8Kyw"/>
<selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_WucQ4KRKEdyLP-jEVj8Kyw"/>
@@ -14,28 +21,30 @@
<selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_X0dmcKuSEdmhFZtkg1nakg"/>
<selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_ABwoIKRLEdyLP-jEVj8Kyw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Viv68dOLEdyqlogshP8l4g" name="tester" guid="_Viv68dOLEdyqlogshP8l4g" presentationName="Tester" isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g" modifies="_Vi5r8dOLEdyqlogshP8l4g _WttSMdOLEdyqlogshP8l4g" responsibleFor="_WttSMdOLEdyqlogshP8l4g _Vi5r8dOLEdyqlogshP8l4g _Vi5r8NOLEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Viv68tOLEdyqlogshP8l4g" name="analyst" guid="_Viv68tOLEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Viv689OLEdyqlogshP8l4g" name="developer" guid="_Viv689OLEdyqlogshP8l4g" presentationName="Developer" isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Viv69NOLEdyqlogshP8l4g" name="stakeholder" guid="_Viv69NOLEdyqlogshP8l4g" presentationName="Stakeholder" isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
- <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
- </processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8NOLEdyqlogshP8l4g" name="test_case" guid="_Vi5r8NOLEdyqlogshP8l4g" presentationName="Test Case" isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8NOLEdyqlogshP8l4g" name="test_case" guid="_Vi5r8NOLEdyqlogshP8l4g" presentationName="Test Case" briefDescription="This artifact is the specification of a set of test inputs, execution conditions, and expected results that you identify to evaluate a particular aspect of a scenario." isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <presentation xmi:id="-dGeCbV3mYf6d7tqFxsHq4A" href="uma://--GUCGSJomnx0WV9XKvVyXQ#-dGeCbV3mYf6d7tqFxsHq4A"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Zxf8MlgEdmt3adZL5Dmdw"/>
+ <concepts href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aJ6cMlgEdmt3adZL5Dmdw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_yWaKEI5fEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8dOLEdyqlogshP8l4g" name="test_script" guid="_Vi5r8dOLEdyqlogshP8l4g" presentationName="Test Script" isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8dOLEdyqlogshP8l4g" name="test_script" guid="_Vi5r8dOLEdyqlogshP8l4g" presentationName="Test Script" briefDescription="This artifact contains the step-by-step instructions that compose a test, enabling its run. Text scripts can take the form of either documented textual instructions that are manually followed, or computer-readable instructions that enable
automated testing." isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_KZQJMBhBEduxCP6DVVLxsA"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Z9tMMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aDz0MlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0j5sUMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kF5kMlgEdmt3adZL5Dmdw"/>
+ <templates href="uma://_OOB2AAouEdyhlpBPrduOMw#_yZtgQI5gEdyO5aWob1UGDA"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8tOLEdyqlogshP8l4g" name="software_implementation_slot" guid="_Vi5r8tOLEdyqlogshP8l4g" presentationName="[Software Implementation]" isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8tOLEdyqlogshP8l4g" name="technical_implementation_slot" guid="_Vi5r8tOLEdyqlogshP8l4g" presentationName="[Technical Implementation]" briefDescription="This slot holds the artifacts that represent a technical implementation. This can include source code, executable code, data, and software/hardware configurations." isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
<WorkProduct href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_WttSMNOLEdyqlogshP8l4g" name="run_tests" guid="_WttSMNOLEdyqlogshP8l4g" presentationName="Run Tests" superActivities="_buG4sdOFEdyqlogshP8l4g" mandatoryInput="_Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g" output="_WttSMdOLEdyqlogshP8l4g" performedPrimarilyBy="_Viv68dOLEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_WttSMNOLEdyqlogshP8l4g" name="run_tests" guid="_WttSMNOLEdyqlogshP8l4g" presentationName="Run Tests" briefDescription="Run the appropriate tests scripts, analyze results, articulate issues, and communicate test results to the team." superActivities="_buG4sdOFEdyqlogshP8l4g" mandatoryInput="_Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g" output="_WttSMdOLEdyqlogshP8l4g">
+ <presentation xmi:id="-S7RJDT8En1BwhtenbO3p8w" href="uma://--GUCGSJomnx0WV9XKvVyXQ#-S7RJDT8En1BwhtenbO3p8w"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kF5kMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0j5sUMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aDz0MlgEdmt3adZL5Dmdw"/>
<Task href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jVEkMlgEdmt3adZL5Dmdw"/>
<selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_xVhnwKRLEdyLP-jEVj8Kyw"/>
<selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_1L1yAKRLEdyLP-jEVj8Kyw"/>
@@ -43,10 +52,11 @@
<selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_sQaC4DO2EduqsLmIADMQ9g"/>
<selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_3t6oADO2EduqsLmIADMQ9g"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_WttSMdOLEdyqlogshP8l4g" name="test_log" guid="_WttSMdOLEdyqlogshP8l4g" presentationName="Test Log" isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_WttSMdOLEdyqlogshP8l4g" name="test_log" guid="_WttSMdOLEdyqlogshP8l4g" presentationName="Test Log" briefDescription="This artifact collects the raw output that is captured during a unique run of one or more tests for a single test cycle run." isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <presentation xmi:id="-kjFCWWTMDhXbgfduK1uQCQ" href="uma://--GUCGSJomnx0WV9XKvVyXQ#-kjFCWWTMDhXbgfduK1uQCQ"/>
<WorkProduct href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
</processElements>
- <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_buG4sdOFEdyqlogshP8l4g" name="test_solution" guid="_buG4sdOFEdyqlogshP8l4g" presentationName="Test Solution" briefDescription="From a system perspective, test and evaluate the developed requirements." breakdownElements="_Viv68NOLEdyqlogshP8l4g _Viv68dOLEdyqlogshP8l4g _Viv68tOLEdyqlogshP8l4g _Viv689OLEdyqlogshP8l4g _Viv69NOLEdyqlogshP8l4g _Vi5r8NOLEdyqlogshP8l4g _Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g _WttSMNOLEdyqlogshP8l4g _WttSMdOLEdyqlogshP8l4g">
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_buG4sdOFEdyqlogshP8l4g" name="test_solution" guid="_buG4sdOFEdyqlogshP8l4g" presentationName="Test Solution" briefDescription="From a system perspective, test and evaluate the developed requirements." breakdownElements="_Viv68NOLEdyqlogshP8l4g _Vi5r8NOLEdyqlogshP8l4g _Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g _WttSMNOLEdyqlogshP8l4g _WttSMdOLEdyqlogshP8l4g">
<presentation xmi:id="--GUCGSJomnx0WV9XKvVyXQ" href="uma://--GUCGSJomnx0WV9XKvVyXQ#--GUCGSJomnx0WV9XKvVyXQ"/>
</process>
</org.eclipse.epf.uma:ProcessComponent>
