Andrea Nicolai T-6 Italy Angelo Corallo eBMS – ISUFI University of Lecce

1. The Business Modelling Language Andrea Nicolai T-6 Italy Angelo Corallo eBMS – ISUFI University of Lecce

2. Agenda • The Business Modelling Language • BML Framework • BML 1.0 • Semantics of Business Vocabulary and Rules • BML 2.0 • SBEAVER project • Future Agenda

3. The Business Modelling Language

4. Business Modelling Language • BML is thought to capture and model business knowledge in an easy way, in order to make it available for software tools supporting the business. • Objective: to make DBE platform more accessible to business people and, in particular, to those involved in SMEs. A direct action in business modelling by organizational people could be the right way in order to obtain more flexible and effective solutions; • in particular, this should allow: • bridging the existing gap between technology and organization: business models could be designed in a business-oriented perspective, obtaining actual CIMs that preserve formality and rigorousness needed by technology; • reducing costs related to ad hoc solutions development: if part of the development process is performed by business people IT professionals could focus on different activities or they can save time and effort overcoming communication problems.

5. The divide between technology and business knowledge One of the main obstacles in the adoption of digital technologies from organizations and communities depends on the divide between technological solution, which has reached a quite high level of maturity and the methodologies and technologies enabling business processes, and knowledge modeling. These methodologies and technologies are on one hand not enough connected with software development and management processes and on the other poorly usable and understandable from business users. BUSINESS REQUIREMENTS Service Ontology Domain Model PROCESS MODELLING Service Registry PLATFORM PHYSICAL ARCHITECTURE It is necessary to develop new modeling framework allowing to fill the gap between technology and organization, through which it could be possible to model business knowledge, representing the way a company works, in a language as much as possible similar to the language business experts use and at the same time as much as possible formal in order to orient and guide all the life cycle of the technological components, from its inception to its development to the management to the evolution.

6. Directory Service Node 1 Node 4 0 0 1 0 0 2 Node 2 Node 3 Registration in the directory 0 3 Request for service 1 List of suitable service 2 WSDL Semantic web service ebXML BML Direct connection to service 3 Computer Independent Model Platform Independent Model From a computing to a business architecture

7. BML as a language to exchange business knowledge BML can be used to create a new business layer for service architecture, allowing the use of the same languages for both software design and development and for e-business partners selection. RUN TIME DESIGN TIME Natural language editor XMI MOF Natural Language Search engine Business layer Business expert Service List corresponding to Business needs Business Description Service DirectoryService MOF Transaction Develop Service, Deploy it and register in the Directory Service 4 Service Service Developers

8. Model BusinessModel SystemModel LogicalModel PhysicalModel RequirementsModel ComputationalModel Platformindepndent PlatformSpecific Abstract class Concrete class CIM BML as a language to support software development BML should be thought in relation with technology enabling the improvement of productivity in software development and an increased quality, and longevity of the software developed. In such context BML would be a Computer Independent Model in MDA framework.

9. BML Framework

10. Meta-model Model Meta modelling choice We describe BML by a model: the model of the language describes the elements that can be used in the language. Every kind of element that a BML modeller can use in his or her model is defined by the meta model of the language the modeller uses. Because a meta model is also a model, a meta model itself must be written in a well-defined language (meta-language). is written in BMLmetamodel MOF Meta-language is defined by is written in Car rental model Language BML

11. BML metamodel The BML Metamodel defines an abstract syntax for the BML language using the MOF v1.4 model. Its basis are the six interrogatives - What, How, Where, Who, When and Why - of the Zachman Framework for Enterprise Architecture. For each interrogative of the Zachman Framework a corresponding package in the metamodel has been created. Moreover, an additional package containing the root meta-concepts inherited by the other packages has been created. Core, containing the basic elements used to describe other packages meta-concepts characteristics; BusinessOrganization, containing meta-concepts to model each business entity aspect, including its relationships, resources, products and services; BusinessProcess, describing behavioural aspects of a business organization, focusing on interaction with other organizations; BusinessMotivation, containing meta-concepts to describe the way in which an organization makes choices and defines its actions; BusinessLocation, containing the metamodel to define spatial references in a business model; BusinessEvent, describing the occurrences able to influence business behaviours; BusinessObject, containing meta-concepts to define primitive and user-defined data types, typically used for declaring the types of the class attributes.

12. BML Meta model From BML meta model 2.0

13. BML architecture M3 MOF LANGUAGEMETAMODEL BUSINESS META MODEL M2 BML MODEL BUSINESS DOMAIN MODEL M1 BML Model BML Model in Service DNA M0 BML Model + data in Service Manifest From BML framework 2.0

14. BML toward other e-business standard • BML aims at being used as wide as possible; to reach this objective BML should be compatible with the most important standard in the e-business language: • BML uses ebXML core components in its basic vocabulary • BML meta model is compatible with UMM meta model • BML framework is MOF based and compatible with the Model Driven Architecture • BML meta model is compatible with OMG BEI architecture of business modelling (Through the meta model and SBVR) • BML framework is compatible with OWL and OWL-S (Through the meta model and ODM)

15. BML 1.0

16. BML 1.0 MOF M3 << instances>> << instances>> BML METAMODEL ODM METAMODEL M2 << instances>> << instances>> DOMAIN ONTOLOGY BML MODEL M1 << reference>> Further details in the other presentation

17. Semantics of Business Vocabulary and Rules

18. The Rule based approach The Rule based approach came out in the 80s mainly from the work of the “Business Rules Group”. A rule-based approach can be described as a way “for identifying and articulating the rules which define the structure and control the operation of an enterprise”1; it represents a new way to think about enterprise and its rules, in order to enable a complete business representation made by and for business people. Rules could play a very important role in defining business semantics: they can influence or guide behaviours and support policies, responding to environmental situations and events. This means that rules represent the primary means by which an organization can direct its business, defining the operative way to reach its objectives and perform its actions. OMG in its Architecture of Business Modeling is developing an implementation of the business rules approach called “Semantics of Business Vocabulary and Rules” (SBVR) 1The Business Rules Group, July 2000, Defining Business Rules ~ What Are They Really?, Final Report, revision 1.3

19. The OMG Business Model Architecture OMG, in the widest effort of the Model Driven Architecture, is developing a framework called Business Model Architecture in order to model any kind of human work activity, in any domain, in language familiar to domain experts2. Business Model Architecture is based on high level meta-model, that constitute the abstract syntax of the framework and on Semantics of Business Vocabulary and Rulesthat represents the concrete syntax. Such approach allows the evolution in time of vocabularies and rules in different domains, granting simple mapping among domains and semantic integrations between communities; OMG issued Business Semantics of Business Rule (BSBR) Request For Proposal, in order to create a standard “to allow business people to define the policies and rules by which they run their business in their own language, in terms of the things they deal with in the business, and to capture those rules in a way that is clear, unambiguous and readily translatable into other representations”. 2Stan Hendryx, Hendryx & Associates, Architecture of Business Modelling, November 14, 2003

20. Semantics of Business Vocabulary and Rules • Among the most interesting features that Business Modelling proposes we can consider: • SBVR is an innovative language based on a fact-oriented approach allowing semantic interoperability between models and tools in heterogeneous environment; • SBVRallows the production of business vocabularies and rules; vocabulary plus rules constitute a shared domain model with the same expressive power of standard ontological languages; • SBVRallows multilingual development, since it is based on separation between symbols and concepts; • SBVRhas to enable making business rules accessible to software tools, including tools that support the business experts in creating, finding, validating, and managing business rules, and tools that support the information technology experts in converting business rules into implementation rules for automated systems. • SBVRprovides interchange capabilities defining MOF/XMI mapping rules, that enable generating MOF-compliant models and XML schema. • SBVRproposes Structured English as one of possibly many notations that can map to the SVBR Metamodel. • SBVR is a OMG standard from September 2005

21. Natural Language Modelling Methodologies used in software developing, are typically applied only when a problem is already formulated and well described. 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. Special constraints on syntax or predefined linguistic structures can be used in order to overcome this problem, enabling natural language to well represent and formally define problems and requirements. The main purpose of natural language modelling is hence to make natural language suitable for conceptual modelling. The focus is on semantic aspects and shared meanings, while syntax is thought in a perspective based on formal logic mapping.

22. Rule-based approach 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. This means that rules represent the primary means by which an organization can direct its business, defining the operative way to reach its objectives and perform its actions.

23. Rule-based approach • The rule-based approach aims to address two different kinds of users: • it addresses business communities, in order to provide them with a structured approach, based on a clear set of concepts and used to access and manage business rules; • it addresses IT professionals, in order to provide them with a deep understanding about business rules and to help them in models creation.

24. Fact-orientation “rules build on facts, and facts build on concepts as expressed by terms” (Business Rules Group, Business Rules Manifesto - The Principles of Rule Independence, Nov. 2003) People communicate facts, that is the fact is the atomic unit of communication. The fact-oriented approach enables multidimensional categorization; The fact-oriented approach supports time changeability; The fact-oriented approach providessemantic stability; The fact-oriented approach enables extensibility and reuse.

25. BML 2.0

26. SBVR as linguistic metamodel for BML An important reason to chose SBVR as linguistic metamodel for BML is represented by the strong matching between their objectives. BML requirements explicitly assert that it should be a framework enabling business people to represent the business knowledge in a language close to the one they actually use. SBVR is thought in this perspective and it represents a framework aiming to provide linguistic support to business men in order to define the way by which “they run their business in their own language, in terms of the things they deal with in the business” (SBVR RFP).

27. Compliance with MOF 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. the SBVR approach provides means (i.e. mapping rules) to translate natural language artifacts into MOF-compliant artifacts; this allows to exploit all the advantages related to MOF (repository facilities, interchangeability, tools, …), satisfying BML requirements related to its use within a distributed environment.

28. Expressing the BML Metamodel using SBVR The first project phase produced a MOF-compliant metamodel that embeds general concepts useful to describe all kinds of business. In order to introduce SBVR as concrete syntax for BML, it has been necessary to translate this metamodel in accordance with the SBVR syntax. The output of this complex mapping can be named as BML Vocabulary and Rules. This translation is realized on the basis of the converse process, clearly explained in SBVR specification, that defines the way to obtain a graphical (UML-based) representation of an SBVR-compliant vocabulary.

29. Creating a BML business model BML Vocabulary and Rules define standard terms, facts and rules specializing SBVR meta-concepts. In the same way, BML is used in order to create business models: a modeller specializes BML terms and facts in order to define concepts proper of a given business or domain. For example, given thatbusiness entity, serviceand their related fact type (business entityprovidesservice) are concepts defined by the BML metamodel, if an ‘Hotel’ and its main service must be modelled it is possible to write:

30. DOMAIN MODELvocabulary DOMAIN MODEL BML 2.0 MOF M3 << instances>> BML METAMODEL BML METAMODELSE Vocabulary M2 MOF to BSBR Mapping Rules << instances>> << instances>> GENERIC PACKAGE GENERIC PACKAGESE Vocabulary BML MODEL << imports>> M1 Additional package Additional vocabulary

31. BML 2.0 MOF << instances >> M3 << imports >> BSBR METAMODEL M2 M1 GENERIC PACKAGE Vocabulary BUSINESS MODEL Vocabulary BML METAMODEL Vocabulary BSBR Vocabulary DOMAIN MODEL Vocabulary DOMAIN MODEL Vocabulary Organization Definition:theBusinessEntity… BusinessEntity Definition:the Concept… Hotel Definition:the Organization… Hotel Definition:the BusinessEntity…

32. An example of BML 2.0 business description BML Metamodel Generic Package Hotel Domain HOTEL X HOTEL Z BSBR to MOF/XMI Mapping Rules XMI Production Rules XMI Schemas Structured English Mapping Rules BML VALIDATOR LOGICAL PARSER MOF CONVERTER XMI PRODUCER HOTEL YVocabulary & Bus..Rules HOTEL Y Vocabulary Logical Formulation HOTEL YMOF Model HOTEL Y HOTEL Y XMI Schema

33. € BML HOTEL MODEL BSBR to MOF/XMI Mapping Rules XMI Production Rules BusinessEntity XMI Document <XMI.content> <Notification xmi.id=‘notif01’> <Notification.EventTypeRepository xmi.id=‘repos1’> <Notification.EventTypeRepository.contents> <Notification.EventType xmi=n4 domain=‘room’/> <Notification.EventType xmi=‘n2’ domain=‘room’/> <Notification.EventType xmi=‘n3’ domain=‘room’/> </Notification.EventTypeRepository.contents> </Notification.EventTypeRepository> </Notification> </XMI.content> Asset <<instances>> <<instances>> Hotel:BusinessEntity Room:Asset owns An example of BML 2.0 business description hotel is a business entity hotel has a name hotel owns room room is an asset hotel has a name hotel is a business entity room is an asset hotel owns room HOTEL Y Digitalization… Parsing… BML MetaModel in MOF owns M2 M1 BML Hotel Model in MOF Name:Text

34. The SBEAVER project

35. The SBEAVER Project In order to enable creation of SBVR business models (in terms of business vocabulary and business rules, as explained in the previous section) we developed an open source tool called SBEAVER. It allows to define concepts, fact types and business rules following the SBVR semantics in accordance with the Structured English notation and its mapping to formal logic. SBEAVER is designed primarily for business analysts and modelers working in enterprises, who want to specify business policies and rules precisely and using a non technical notation. Their business view is the enterprise business view, or perhaps a view of part of the business. Nevertheless, mapping to formal logic allows to translate natural language based artifacts into different representation formats (e.g. MOF/XMI, XML or UML). Currently we support automatic generation of XMI XML Schema and Prolog. This feature makes the tool suitable for users such as system engineers, integrators and developers responsible for designing, integrating and implementing IT systems following the business rules and contents provided by business people. Automating transformation of software artifacts from business rules represents basis for validating the system design by business people at the business level of understanding.

36. The SBEAVER Project

37. SBEAVER Key Features • Key features: • 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. SBEAVER: Structured English business rules

38. SBEAVER functional architecture • SBEAVER functional architecture point of view provides: • In particular, from a functional architecture 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. • Hierarchical navigation of vocabulary, • Dictionary (at present we embed WordNet dictionary) support for synonyms, hypernyms, hyponyms, meronyms, definitions. • Mapping from in-memory Java representation to logical representation. • XMI XML Schema serialization allowing interchangeability of models between software tools.

39. The SBEAVER tool

40. The SBEAVER project • SBEAVER generates automatically XSD Schemas

41. Future agenda

42. Research Agenda • Formal languages for e-business based on natural language (evolution of SBVR structured English toward e-business); • Tools (editors, parsers, tunable transformation tools, validators) based on natural language modelling paradigm and supporting formal logic; • Distributed MOF repositories for Business knowledge representation (supporting natural language, structured English, MOF and XMI representation); • Query languages search engines, and knowledge discovery systems based on structured English and natural language; • Ontology to SBVR mapping systems; • Computation Independent Business Models to Platform Independent Service Models transformations.

43. Thank you