<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription 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="-ahQOe8UmyVyogbRDnkzo7Q" name="ntroduction,_QXY14CDkEduCWc6M2bh46w" guid="-ahQOe8UmyVyogbRDnkzo7Q" authors="Jerome Boyer " changeDate="2009-12-10T11:35:29.000-0800" version="1.0.0">
  <mainDescription>&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    The Agile Business Rule Development plug-in for the Eclipse Process Framework presents a pragmatic approach &lt;a
    id=&quot;XE_ABRD__introduction&quot; name=&quot;XE_ABRD__introduction&quot;>&lt;span
    style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
     face=&quot;Arial&quot; size=&quot;2&quot;>(&lt;/font>&lt;/span>&lt;/a>&lt;a class=&quot;elementLink&quot;
    href=&quot;./../../../practice.tech.abrd.base/guidances/concepts/cycle_approach_7FA44D8F.html&quot;
    guid=&quot;_ftAoIAjrEdyj5bYZ0eCR5g&quot;>Cycle Approach to Rules Development&lt;/a>) to the development of a Business Rule
    Application using Rule Engine and Business Rules Management System (BRMS) technology such as ILOG JRules, ILOG Rules
    for .Net,&amp;nbsp;Fair Isaac Blaze Advisor, Drools&amp;nbsp;or any other Rule Engine and BRMS on the market. This methodology
    supports the rule governance process description, and the architecture disciplines to deploy a Business Rule Engine
    into a Service Oriented Architecture and Business Process Management System.
&lt;/p>&lt;br />
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    Business rules are an expression of business policy in a form that is both comprehensible to business users and
    executable by a rule engine. From a business perspective, a business rule is a precise statement that describes,
    constrains, or controls some aspect of the business.
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    Let's illustrate this concept with a simple example coming from the lending industry. The following business policy can
    be established to limit the loan amount a bank can purchase:&lt;br />
&lt;/p>
&lt;div
style=&quot;BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 3pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; MARGIN-LEFT: 0.5in; BORDER-LEFT: gray 1.5pt solid; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-element: para-border-div&quot;>
    &lt;br />
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>Only prime loans are eligible for purchase&lt;/font>&lt;/span>
    &lt;/p>&lt;br />
&lt;/div>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    This policy may be split into two implemented rules, one defining what a prime loan is and the second taking the
    decision on purchasing it or not.&amp;nbsp;
&lt;/p>
&lt;div
style=&quot;BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 3pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; MARGIN-LEFT: 0.5in; BORDER-LEFT: gray 1.5pt solid; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-element: para-border-div&quot;>
    &lt;br />
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>If the loan amount is less than the prime loan limit, then the loan type is Prime&lt;/font>&lt;/span>&lt;br
        class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot; />
        &lt;br />
    &lt;/p>
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>If the loan type is not Prime then reject the loan&lt;/font>&lt;/span>
    &lt;/p>&lt;br />
&lt;/div>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot; />
&lt;br />
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    Implementing these rules using an Object Oriented Language may look like two if statements testing conditions on
    objects, and applying actions on the same or other objects
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot; />
&lt;br />
&lt;div
style=&quot;BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 3pt; BACKGROUND: #f3f3f3; PADDING-BOTTOM: 0in; MARGIN-LEFT: 0.5in; BORDER-LEFT: gray 1.5pt solid; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-element: para-border-div&quot;>
    &lt;br class=&quot;ISISCodeParagraphCxSpFirst&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 6pt 0in 0pt; mso-add-space: auto&quot; />
    &lt;br />
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>if (loan.amount &amp;lt; PrimeLoanLimit) {&lt;/font>&lt;/span>
    &lt;/p>
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>loan.type = PrimeType;&lt;/font>&lt;/span>
    &lt;/p>
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>}&lt;/font>&lt;/span>
    &lt;/p>&lt;br class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot; />
    &lt;br />
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>if (loan.type != PrimeType) {&lt;/font>&lt;/span>
    &lt;/p>
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>case = new Case(&quot;Loan is not Prime&quot;);&lt;/font>&lt;/span>
    &lt;/p>
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>loan.status = REJECT;&lt;/font>&lt;/span>
    &lt;/p>
    &lt;p class=&quot;ISISCodeParagraphCxSpMiddle&quot; style=&quot;BACKGROUND: #f3f3f3; MARGIN: 0in 0in 0pt; mso-add-space: auto&quot;>
        &lt;span
        style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US&quot;>&lt;font
         face=&quot;Courier&quot;>}&lt;/font>&lt;/span>&lt;br />
    &lt;/p>
&lt;/div>&lt;br />
&lt;p>
    The concept of business rules is not new, and for decades analysts and developers were implementing them within
    business applications. What is more recent is the introduction of a Business Rule Management System application which
    provides tools to manage the rule as a standalone element, outside of the core business application, and in a form
    which is executable by a rule engine.
&lt;/p>
&lt;p>
    Business rules are packaged as a Rule Set which can be considered as a piece of software executed by a rule engine.
    Integrated in a business application, the rule set implements a sub-set of the business logic. This logic is
    externalized from the traditional code and can be easily changed, and maintained by business analysts instead of
    developers.
&lt;/p>
&lt;p>
    As opposed to business logic embedded and hidden in functions, procedures, macros or databases, business rules are
    clearly separated from the rule engine, a software component which executes and activates rules based on matching
    conditions on a set of data.
&lt;/p>
&lt;p>
    Figure 1 below illustrates this fundamental approach in implementing business logic, with the old embedded model on the
    left and the new architecture on the right. In many ways the approach is similar to the separation of code and data
    which Data Base Management Systems (DBMS) brought in the 1970s.&lt;br />
    &amp;nbsp;
&lt;/p>
&lt;p>
    &amp;nbsp;&lt;img height=&quot;386&quot; alt=&quot;&quot; src=&quot;resources/legacy2bre.jpg&quot; width=&quot;599&quot; />
&lt;/p>
&lt;p>
    &lt;span lang=&quot;EN-GB&quot; style=&quot;mso-ansi-language: EN-GB&quot;>A piece of business logic or rule embedded in code will be more
    difficult to identify, locate, and change, therefore increases costs of maintenance.&lt;/span>
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    &lt;span lang=&quot;EN-GB&quot; style=&quot;mso-ansi-language: EN-GB&quot;>A rule which is externalized in a BRMS platform, and whose versions
    are controlled in a rule repository and deployed and executed in a rule engine, will be much easier to modify, thus
    reducing dramatically the time and cost to implement changes required by the business.&lt;/span>
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    &lt;span lang=&quot;EN-GB&quot; style=&quot;mso-ansi-language: EN-GB&quot;>Traditional software life cycles such as the V cycle or waterfall
    model are notorious for leading to systems which costs more than expected, come to market later than planned and with
    outcomes not matching the clients' initial expectations. With such approaches, the business users have little ownership
    of the solution, and the time required to implement changes can easily range from 3 to 6 months if not more. As a
    result, policy owners don't feel comfortable with change which translates into a loss of agility to respond to new
    business and competitive situations: too much time passes between policy owners submitting requirements to IT and the
    actual deployment of new rules.&lt;/span>
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    &lt;span lang=&quot;EN-GB&quot; style=&quot;mso-ansi-language: EN-GB&quot;>Also, with all the fine tuning and iterations, policy owners cannot
    really be sure that the policy is being implemented according to their needs. The only way to actually know is to keep
    performing tests and hope that all the cases are covered in such tests.&lt;/span>
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    As important element of the business decision, the business rules need strong management processes and tools to support
    their life cycle.
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    A BRMS provides solutions to make this management more efficient, both for developers and for the business users of the
    applications. Obviously tooling is not the single answer to the software and business challenges behind the development
    of decision-support systems. Deploying BRMS, BRE, and BPM components into business applications requires to modify
    current development methodologies and practices in order to take into account new concepts as well as providing a
    better collaboration framework between IT and business.
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    The Agile Business Rule Development (ABRD) methodology corresponds to such a need. It is an incremental and iterative
    software development process leveraging the Agile Alliance manifesto (&lt;a href=&quot;http://agilemanifesto.org/&quot;
    target=&quot;_blank&quot;>Agile Manifesto&lt;/a>). Here are some of the Agile development values particularly relevant to the
    implementation of a rule set using the ABRD approach:
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l0 level1 lfo1&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> &lt;i>Individuals and interactions over processes and tools&lt;/i>. The rule
    discovery, analysis and validation activities require an active and efficient communication between the rule developer
    and the Subject Matter Experts (SME). Such processes are defined as light as possible.
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l0 level1 lfo1&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> &lt;i>Working software over comprehensive documentation&lt;/i>. The proposed rule
    set development done per iteration, with its validation step, is based on the evidence that a working and executable
    rule set has much more business value than a rule description manual. All the project stakeholders benefit from such a
    principle but in particular the business users who are then sure that what they see (the rules) is what gets executed
    in the deployed system.
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l0 level1 lfo1&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> &lt;i>Customer collaboration over contract negotiation&lt;/i>. Subject Matter
    Experts who define the business policies and the business rules are strongly involved in the development process. They
    are the customers of the final system, owners of the policies and are conveniently collocated with the development team
    during the project.
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l0 level1 lfo1&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> &lt;i>Responding to change over following a plan&lt;/i>. Business rules evolve, more
    often and faster than other standard pieces of software. This is actually one of the key values of the business rule
    approach. For this fundamental reason the methodology to support the rule set development has to be tailored to such
    rapid life cycle and include the appropriate activities, processes, best practices and work products to support such
    changes efficiently.
&lt;/p>&lt;br />
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    The Agile Business Rule Development methodology addresses in more detail the following goals:
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l1 level1 lfo2&quot;>
    &lt;span
    style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol; mso-bidi-font-size: 10.0pt&quot;>&lt;span
     style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> Separate rules as a manageable artifact using discovery, analysis and
    authoring activities and work products
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l1 level1 lfo2&quot;>
    &lt;span style=&quot;FONT-SIZE: 11pt; FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> Trace rules during their full life cycle from requirement to deployment and
    maintenance
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l1 level1 lfo2&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> Link rules to business context and motivation
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l1 level1 lfo2&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> Develop the rule description using business terms and high level rule language
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l1 level1 lfo2&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> Prepare the logical data model for the rule engine&amp;nbsp;
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l1 level1 lfo2&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> Prepare the Rule set implementation and deployment as decision services in a
    SOA or BPM application
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l1 level1 lfo2&quot;>
    &lt;span style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> Articulate the rule governance processes
&lt;/p>&lt;br />
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    Two fundamental drivers govern successful rule set developments:
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l2 level1 lfo3&quot;>
    &lt;span
    style=&quot;FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol; mso-bidi-font-size: 10.0pt&quot;>&lt;span
     style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> The unforgiving honesty of executable rules
&lt;/p>
&lt;p class=&quot;MsoNormal&quot;
style=&quot;MARGIN: 3pt 0in 3pt 36.3pt; TEXT-INDENT: -0.25in; tab-stops: list 36.3pt; mso-list: l2 level1 lfo3&quot;>
    &lt;span style=&quot;COLOR: navy; FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol&quot;>&lt;span
    style=&quot;mso-list: Ignore&quot;>·&lt;/span>&lt;/span> The effectiveness of people working together with goodwill, shared vision and
    common interests (the business user and the development team).
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    Executable or working rules tell the developers and the Subject Matter Expert what they really do as opposed to promise
    through a paper-based design or specification.
&lt;/p>
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0in&quot;>
    ABRD was developed by ILOG to support implementation and deployment of BRMS by its customers. It is now offered as a
    free open source methodology as part of the Eclipse Process Framework plug-in library.
&lt;/p>&lt;span
style=&quot;FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-bidi-language: AR-SA; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-size: 12.0pt&quot;>ABRD
is a practice and extends other element of EPF practice library to avoid redefining some standard roles, tasks, work
products, guidelines and processes which are also relevant to rule development. As an EPF plug-in, development teams can
leverage it for their own purpose and tailor it to the specific context of their own project, leveraging the EPF Process
Composer tool.&lt;/span>&lt;br /></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
