Skip to content
Gytis Gurklys
Go back

On Business Rules

Gytis Gurklys
No generative AILT

Slides from a talk I gave to colleagues at Metasite on 10 March 2020. It follows the same line as the earlier talk on business requirements, one step further down: to the rules that get written underneath them.

I opened with a survey of the team. Most were confident they could write a rule; far fewer were confident they could explain one to a stakeholder, and almost nobody thought the topic was a waste of time. We had some conventions, but how a rule actually ends up phrased was left to each analyst.

The rest is what the OMG’s SBVR standard has to say about it — where it came from, how it defines a rule, an advice, and the statements that express them, and what SBVR Structured English looks like.

The research was about a third of the way through when I gave the talk, so this is a report on a direction rather than a finished method.

The slides are as they were in 2020 and are not edited. What is printed under them is for the reader: what was said out loud where the slide does not say it, and, where a slide cites a source, a link to the work.

Agenda
Motivation
Why is it important for us
BR Survey — Do you agree with following statements:
BR Survey Results
Current state of BR usage
Room for improvement
My goal
Current status of my research
Problems of Natural Language
Short history of Business Rules
Business Rules Group
OMG – Object Management Group
MDA – Model Driven Architecture
MDA layers
MOF – Meta-Object Facility
MOF
SBVR - Semantics of Business Vocabulary and Business Rules
SBVR place in MOF — SBVR specification is MOF metamodel
BPMN – SBVR integration
SBVR Aplicability
SBVR Aplicability
Definitions
BR Mantra – SBVR
Noun Concept
Verb Concept
Business Rule
Business Rule
Fundamental Principles for Elements of Guidance
Definitional Elements of Guidance
Definitional Rules — definitional rule
Definitional Advices — advice of possibility
Definitional Advices — advice of contingency
Statements of Definitional Rules
Statements of Definitional Rules — definitional rule statement
Statements of Definitional Advices
Statements of Definitional Advices — statement of advice of possibility
Behavioral Elements of Guidance
Behavioral Rules — behavioral business rule
Behavioral Advices — advice of permission
Behavioral Advices — advice of optionality
Statements of Behavioral Rules
Statements of Behavioral Rules — behavioral business rule statement
Statements of Behavioral Rules — obligation statement
Statements of Behavioral Rules — prohibition statement
Statements of Behavioral Rules — restricted permission statement
Statements of Behavioral Advices
Statements of Behavioral Advices — statement of advice of permission
Statements of Behavioral Advices — permission statement
Statements of Behavioral Advices — non-obligation statement
Statements of Behavioral Advices — optionality statement
Rule (Modelling) Languages
SBVR Structured English
4 font styles
Quantification
Logical operations
Modal operations
Other keywords

Specifications end up in natural language because it is the only medium the business side and the technical side share. The slide lists what that costs: ambiguity, pronouns whose referent is lost between sentences, and behaviour that happens over time written in a flat present tense — the point of the last one is temporal logic, the branch of logic that deals with statements qualified by time ("I am always hungry", "I will be hungry until I eat something").

Source: Nelken & Francez, Automatic translation of natural language system specifications into temporal logic, CAV 1996.

The principles on the slide are the Business Rules Manifesto — the Business Rules Group's 2003 statement of what a rule is and where it belongs.

Source: Business Rules Manifesto, Business Rules Group, 2003.

SBVR is the OMG standard the rest of the talk follows: every definition from here on is its definition, quoted rather than invented.

Source: Semantics of Business Vocabulary and Business Rules (SBVR), OMG.

In alethic logic, a proposition that is possible but not necessary is termed ‘contingent’. If people in a business were to treat it as a definitional rule, they would miscategorize things in the real world. This typically leads to refusal of activity (that should be permitted) because unnecessary preconditions are not met, e.g., refusing to accept a rental booking because the person wishing to rent is under 21.

Download the slides (PDF)



Previous Post
On Business Requirements
Next Post
A Theoretical Basis for Modeling the EUDAMED Domain