SBVR uses OMG's Meta-Object Facility (MOF) to provide interchange capabilities MOF/XMI mapping rules, enable generating MOF-compliant models and define an XML schema.
[2] The SBVR proposal was developed by the Business Rules Team, a consortium organized in August 2003 to respond to the BSBR RFP.
Later SBVR proposal was ratified by the Domain Technical Committee (DTC), approved of the OMG Board of Directors, and SBVR finalization task force was launched to convert the proposal into ISO/OMG standard format and perform final editing prior to release as an OMG formal specification.
The actual difficulty lies in the previous step, that is describing problems and expected functionalities.
Stakeholders involved in software development can express their ideas using a language very close to them, but they usually are not able to formalize these concepts in a clear and unambiguous way.
This implies a large effort in order to interpret and understand real meanings and concepts hidden among stakeholders' words.
The focus is on semantic aspects and shared meanings, while syntax is thought in a perspective based on formal logic mapping.
The set of facts instantiates the conceptual schema by assertion to describe one possible world.
The SBVR vocabulary allows one to formally specify representations of concepts, definitions, instances, and rules of any knowledge domain in natural language, including tabular forms.
Rules play a very important role in defining business semantics: they can influence or guide behaviours and support policies, responding to environmental situations and events.
SBVR Structural Business Rules use two alethic modal operators: SBVR Operative Business Rules use two deontic modal operators: Structural business rules (static constraints) are treated as alethic necessities by default, where each state of the fact model corresponds to a possible world.
In SBVR, this tag is assigned the informal semantics: it ought to be the case that p (for all future states of the fact model, until the constraint is revoked or changed).
Formal rules are transformed into a logical formulation that is used for exchange with other rules-based software tools.
An approach to automatically generate SBVR business rules from natural language specification is presented in.
[9] SBVR specification defines a metamodel and allows to instance it, in order to create different vocabularies and to define the related business rules; it is also possible to complete these models with data suitable to describe a specific organization.
CL itself was modified specifically so it potentially can include the modal sentence requirements of SBVR.
ODM provides a bridge to link SBVR to the Web Ontology Language for Services (OWL-S), Resource Description Framework Schema (RDFS), Unified Modeling Language (UML), Topic Map (TM), Entity Relationship Modeling (ER), Description Logic (DL), and CL.