| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-Guj2mWoOjjzdPkcqGihq4g" |
| name="extract_rule_meaning,_o19QgF2BEd2T6cNSe41mOg" guid="-Guj2mWoOjjzdPkcqGihq4g" |
| authors="Jerome Boyer" changeDate="2008-09-08T09:43:11.516-0700"> |
| <mainDescription><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 diagrma, generates java code and import such code
 |
| in the rule IDE.<br />
 |
| &nbsp;
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:TaskDescription> |
