Moulding USDL in SBVR using Business Semantics Glossary: Part 1


I truly believe in co-creation. For example, we have our Collibra software and methods regularly scrutinized by numerous master students from both technical as well as more business-oriented computer science programmes in universities across Europe.

At VU University, for example, in the context of my Business Semantics Management master class, 21 MSc students playing the role of steward formed the Amsterdam Service Modelling Community with one common purpose: building an SBVR version of the USDL service description language. There were two additional members invited playing the role of observer: Carlos Pedrinaci (representing the USDL W3C incubator group) and Ivan Razo-Zapata (our PhD student at VU working on dynamic service market place composition). Finally there was me playing the role of administrator, making a total of 24 members.

The Amsterdam Service Modelling community has 24 members (21 playing the role of "steward"; 2 as "observer"; 1 as "administrator") and is subdivided in 5 speech communities. (Note: this is an older release of the Business Semantics Glossary software)

The figure below depicts the Business Semantics Management (BSM) methodology that is established by two operational cycles (reconciliation and application) each grouping a number of modeling activities. For a summary go here and for more details see my dissertation.

Business semantics management is established by two operational cycles each grouping a number of modeling activities.

The experiment extended over a total period of 4 weeks; hence we limited ourselves to the first 4 steps of semantic reconciliation only: scope, create, refine, articulate. In September we plan to repeat this experiment  over a period of 8 weeks where we will have time to do one full cycle of BSM. Later I will also blog about similar experiments we conduct at VUB University of Brussels.

Community-driven Approach

The Amsterdam Service Modelling Community (ASMC) is modelled (in SBVR) as a semantic community. SBVR takes into account the existence of multiple perspectives on how to represent concepts (by means of vocabularies).

  • A semantic community is a group of stakeholders having a body of shared meanings. Stakeholders are people representing an organisation or a business unit.
  • A body of shared meanings is a unifying and shared understanding (perception) of the business concepts in a particular domain.  Concepts are identified by a URI.
  • A speech community is a sub-community of a semantic community having a shared set of vocabularies to refer to the body of shared meanings. A speech community groups stakeholders and vocabularies from a particular natural language in a multi-lingual community, or from a certain technical jargon.
  • A vocabulary is a set of terms and fact types (called vocabulary entries) primarily drawn from a single language to express concepts within a body of shared meanings.

Within the ASMC community, the 21 students grouped in 5 speech communities each focusing on a specific part of the USDL framework. In SBVR, speech communities are part of one semantic community and each manage their own set of vocabularies to refer to this body of shared meanings. This allows for different representations of the same business concepts.

The navigator shows (from left to right) the structure of communities and their vocabularies.

Scoping the Semantic Reconciliation Cycle

The module-based decomposition of USDL depicted below makes it easy for teams to scope. However, they all had to start from the Service and Pricing module so we could observe divergence in definitions as well, an important step in the ontology evolution process (see the Perspective Rendering principle of my PhD on BSM).

The module-based USDL framework allows for clear scoping among speech communities (by courtesy of http://www.internet-of-services.com/).

Create, Refine, Articulate

Below is a screenshot of the term “Service” in the Pricing and Participant vocabulary in development by the “VAAF” speech community team. The steward (indicated on the top-right) “Vlant” is responsible for selecting the right stakeholders (bottom-right) among his fellow members and engage them into the reconciliation of the term.

A term can be defined using different kinds of attributes, going from (business-oriented) descriptions and definitions to more (formal) fact types and business rules.  Currently the level of articulation is below threshold (37.5%) incentivizing the steward and stakeholders to elaborate more.

Term "Service" in the Pricing and Participant vocabulary in development by the "VAAF" speech community team.

Next time we will talk about vocabulary statistics and workflows in the software. Workflows practically implement the orchestration of reconciliation tasks to members according to their roles and responsibilities.

Advertisements

Tags: , , , , , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: