To jest stara wersja strony!
BizRulesVocabularies
Tomasz, Bochen, tomasz_bochen@o2.pl
:!:It is a common visual notation used in the Business_Process_Modeling that is a modeling/design problem in the Business_process_management. The BPMN is officially standarized by OMG. Some possible areas of investigation(at 1st sight):
input
relation between BPMN and UML, e.g. see Use of UML and Model Transformations for Workflow Process Definitions
how could we use Business_Process_Execution_Language
the general idea of workflow and tools such as yawl is worth digging in…
SBVR
output
Extended ARD.
Spotkania
08.03.04
080318
080401
080415
zapis słownika do thermostato w sbcr
model thermostatu w sbeaver?
wyszukanie narzędzi do SBVR w Internecie
080520
początek sprawozdania: co to jest sbvr, structured english, skąd dok., narzędzia obecne i przyszle, opis therm w sbvr, przejscie do uml, prpozycja algorytmu ard↔sbvr, obserwacje→przyszłe możliwośći rozwoju
Projekt
Sprawozdanie
Materiały
Próba opisu termostatu w SBVR
Próba opisu termostatu za pomocą UML (Activity Diagram)
Sprawozdanie
1. Getting started with SBVR ..
SBVR is an OMG specification that details how business rules and business vocabulary can be captured and specified in unambiguous terms.
SBVR is targeted at business rules and business vocabularies, including those
relevant for usage in conjunction with those rules. Other aspects of business
models also have to be developed, including business process and organization
structure, which are being addressed by the OMG in RFPs concurrent with that for
BSBR.
SBVR is an integral part of the OMG’s Model Driven Architecture (MDA). Picture below shows positioning of SBVR in Model-Driven Architecture.
SBVR is targeted at business rules and business vocabularies, including those
relevant for usage in conjunction with those rules. Other aspects of business
models also have to be developed, including business process and organization
structure, which are being addressed by the OMG in RFPs concurrent with that for
BSBR.
1.1. What is Semantics?
‘Semantics’ is “the meaning or relationship of meanings of a sign or set of signs”
[Merriam-Webster Collegiate Dictionary]. In SBVR the signs can be of any form:
words, phrases, codes, numbers, icons, sounds, etc.
SVBR includes two specialized vocabularies:
kinds of terms and meanings (other than meanings of Business Rules);
specification of the meaning of business rules, and builds on the „Vocabulary for
Describing Business Vocabularies”.
The two have been separated so that the „Vocabulary for Describing Business
Vocabularies” could be used independently - for example, as a basis for vocabularies
for business processes or organizational roles.
The next two sections deal with the semantics of business vocabularies and the
semantics of business rules.
1.3. What is a Business Vocabulary?
A business vocabulary contains all the specialized terms and definitions of concepts
that a given organization or community uses in their talking and writing in the course
of doing business.
Examples: process rate, order price, customer retention rate, Gold Level Support, Customer, Order, Order Item etc.
The vocabulary does not include the special SBVR syntax or other SBVR compliant syntaxes like in Rule Speak.
Rules are built using Vocabulary and the special SBVR syntax.
1.3. What is a Business Rule?
The SBVR follows a common-sense definition of 'business rule':
Business Rule: rule that is under business jurisdiction
'Under business jurisdiction' is taken to mean that the business can enact, revise and
discontinue business rules as it sees fit. If a rule is not under business jurisdiction in
that sense, then it is not a business rule. For example, the 'law' of gravity is
obviously not a business rule. Neither are the 'rules' of mathematics.
Examining the question more closely, it is obvious that if rules are to serve as guides
for conduct or action, they must also provide the actual criteria for judging and
guiding that conduct or action. In other words, for the context of business rules (and
probably in most other contexts), rules serve as criteria for making decisions. The
SBVR’s interpretation of 'rule' therefore encompasses the sense of 'criteria' as given
by authoritative dictionaries.
Experts in this area recommended that the
best treatment for the SBVR’s interpretation of rules would involve obligation and
necessity claims.
Consequently, in SBVR, a Rule is „an element of guidance that introduces an
obligation or a necessity”. The two fundamental categories of Rule are:
Structural Rule (necessities): These are rules about how the business chooses to organize (i.e., 'structure') the things it deals with.
Structural Rules supplement definitions. For example (from EU-Rent):
Necessity: A Customer has at least one of the following:
Operative Rules (obligations): These are rules that govern the conduct of
business activity. In contrast to Structural Rules, Operative Rules are ones
that can be directly violated by people involved in the affairs of the business.
For example (from EU-Rent):
Obligation: A Customer who appears intoxicated or drugged must not
be given possession of a Rental Car.
1.3.2. Rules, Fact Types and Concepts expressed by Terms
Informally, a fact type is an association („Association” is used here in its everyday, business sense - not the narrower,
technical sense that would apply to a UML class model.) between two or more concepts; for example
„Rental Car is located at Branch”.
In SBVR, rules are always constructed by applying necessity or obligation to fact
types. For example, the rule „A Rental must not have more than three Additional
Drivers” is based on the fact type „Rental has Additional Driver”.
By this means, SBVR realizes a core principle of the Business Rules Approach at the
business level, which is that „Business rules build on fact types, and fact types build
on concepts as expressed by terms.”
One important consequence of the SBVR’s approach in this regard is that concepts
(including fact types) are distinct from rules, which are in a separate Compliance
Point. This design permits SBVR’s support for concepts (including fact types) to be
optionally used on its own for building business vocabularies.
1.4. Notations for Business Vocabulary+Rules
1.4.1. SBVR Structured English
It should be remembered that SBVR Structured English (presented in Appendix C,D) is
just one of possibly many notations that can be used to express the SBVR
Metamodel, and, as a notation, is nonnormative in the SVBR standard.
Two styles of SBVR Structured English are documented in this submission:
Prefixed Rule Keyword Style
Embedded (mixfix) Rule Keyword Style
The Prefix Style introduces rules by prefixing a statement with keywords that convey
a modality. Examples of some of the prefixes are shown in the table below.
Operative | Structural |
It is obligatory that | It is necessary that |
It is prohibited that | It is impossible that |
It is permitted that | It is possible that |
The Embedded Style features the use of rule keywords embedded (usually in front of
verbs) within rules statements of appropriate kinds. The table below shows a
sample of embedded keywords used to form rules.
Operative | Structural |
… must … | … always … |
… must not … | … never … |
… may … | … sometimes … |
1.4.2 State
'State' is an important notion for business vocabularies and business rules. As far as
business people are concerned, ‘state’ is a concept they can refer to and use in
creating definitions, facts and rules. For example, in EU-Rent a car’s states would
include: 'available', 'allocated to rental', 'on rental', 'damaged' and so on. The
company uses these state names in defining business rules, e.g., „The car assigned
to a walk-in rental must be the available car with the lowest odometer reading in the requested car group.” One way to express states is using unary predicates, e.g., „car is available”.
1.5. Business Modeller Editors
1.5.1. SBeaVeR
The SBeaVeR is a tool for modeling business vocabularies and business rules. It is an Eclipse based plugin, part of the Digital Business Ecosystem project.
1.5.1.1. SBeaVeR feature list
SBeaVeR key features are:
Business knowledge representation: SBeaVeR provides a tool for formalizing the semantics of business knowledge using the Structured English notation.
Portability: SBeaVeR is written in Java for portability and could be installed on many different operating systems without code changes. SBeaVeR
comes with all source code with EPL licence which can be modified or tailored to meet a user's specific needs.
Integration and Extensibility: SBeaVeR is based on Eclipse platform which allows to easily extend or integrate the tool by a user through the use of a well-defined framework.
Model validation: SBeaVeR includes a number of features to support the verification and validation of business models including semantic analysis of rule to determine possible inconsistencies.
From a functional point of view, SBeaVeR provides:
Presentation and user modification of SBVR Structured English business vocabularies and business rules.
Standard text editing operations (cut, copy, paste, find, replace).
Automatic syntax highlighting following the SBVR Structured English font styles.
Content assist to allow easy and fast creation of contents (automatic completion of known statements/words, automatic text formatting, collapse/expand).
Hierarchical navigation of vocabulary (multiple views).
Dictionary (at present we embed WordNet dictionary) support for synonyms, hypernyms, hyponyms, meronyms, definitions.
Mapping from in-memory Java representation of vocabulary and rules to logical representation.
XMI XML Schema serialization (following SBVR specs) allowing interchangeability of models between software tools.
1.5.1.2. Screenshots
1.5.2. Part of Model Development Tools (MDT)
The Model Development Tools (MDT) project focuses on modeling within the Modeling project. Its purpose is twofold:
To provide an implementation of industry standard metamodels.
To provide exemplary tools for developing models based on those metamodels.
The next release of MDT is tentatively scheduled for the end of June 2008. For the previous release, see New & Noteworthy.
SBVR provides a metamodel implementation and sample tools based on the adopted Semantics of Business Vocabulary and Business Rules (SBVR) OMG specification.
The objectives of the SBVR component are to provide:
an open source „reference” implementation of the SBVR specification
an EMF-based foundation on which business vocabulary and business rules modeling tools can be built
a basis for integrating and interchanging artifacts between business vocabulary and business rules tools
a forum for engaging the community in validation of the SBVR specification
In addition to an implementation of the SBVR metamodel, this component will include sample tools that aid in testing and validating the metamodel implementation, and that help SBVR newcomers to better understand its use and potential.
Project Explorer navigator view for business vocabularies and rules
Import business vocabulary from UML domain models
Code generation to Platform-Independent Model (PIM) technologies, such as UML and OCL
For more details on SBVR, see the Wiki.
Downloads coming soon!
Modelling 'thermostat' in SBVR