| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-h3v2kueoq4jxIVjo665E5A" |
| name="new_guideline,_1ZyHAHrZEd2l9d4UccBrvQ" guid="-h3v2kueoq4jxIVjo665E5A" authors="Jerome Boyer" |
| changeDate="2008-09-05T15:09:57.982-0700"> |
| <mainDescription><p>
 |
| SBVR is a standard of the Object Management Group intended to formalize complex business rules, and business
 |
| vocabularies. SBVR is part of the OMG’s Model Driven Architecture (MDA). The goal of SBVR&nbsp;is to&nbsp;capture
 |
| specifications in natural language and represent them in formal logic so they can be machine-processed.
 |
| </p>
 |
| <p>
 |
| <a href="http://www.omg.org/docs/formal/08-01-02.pdf" target="_blank" >SBVR</a> includes two specialized vocabularies:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <p>
 |
| Vocabulary for Describing <em>Business Vocabularies</em> which deals with all kinds of terms and meanings.
 |
| </p>
 |
| </li>
 |
| <li>
 |
| <p>
 |
| Vocabulary for Describing <em>Business Rules</em> which deals with the specification of the meaning of business
 |
| rules, and builds on top of the previous vocabulary.
 |
| </p>
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| The meanings are declined into concept, question&nbsp;and proposition. The meaning is what someone intends to express
 |
| or understands. A phrase such as "<em>We deny the invoice if the medical treatment was done after one year of the
 |
| accident"</em> has a&nbsp;clear meaning for a claim processor within a car insurance company. As analyst we need to
 |
| transform logically this meaning into concepts which has a unique interpretation so that we can represent the business
 |
| knowledge within a comprehensive vocabulary.
 |
| </p>
 |
| <p>
 |
| Concept includes a unique combination of characteristics or properties.
 |
| </p>
 |
| <p>
 |
| Business rules are declined into two possible classes:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| structural &nbsp;(definitional) business rule which are&nbsp;about how the business chooses to organize the things
 |
| it deals with, they are considered as necessity. In this context the statements describing the rule can describe
 |
| the necessity, the impossibility or the restricted possibility.
 |
| </li>
 |
| <li>
 |
| operative (behavior)&nbsp;business rule govern the conduct of business activity. They&nbsp;are considered as
 |
| obligation and directly enforceable. When considering operative business rule it is important to look at the level
 |
| of enforcement to specify the severity of action imposed by the rule in order to put or keep it in force.
 |
| Statements to describe the rule include obligation, prohibition, and restricted permission.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| In SBVR, rules are always constructed by applying necessity or obligation to fact types . Fact type is an association
 |
| between two or more concepts.
 |
| </p>
 |
| <p>
 |
| Using SBVR the team can document the semantic of the business entities, facts and business rules. The persistence
 |
| mechanism uses XMI to facilitate interchange between group and tools. SBVR allows multilingual development, since it is
 |
| based on separation between symbols and their meaning. SBVR proposes Structured English as one of possibly many
 |
| notations that can map to the SBVR Metamodel.<br />
 |
| </p>
 |
| <p>
 |
| SBVR is a good fit&nbsp;for describing business domains and requirements for business processes and&nbsp;business rule
 |
| applications.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
