Development of modern software systems consists of many different phases, the sequence of whom is referred to as the software life cycle. During these phases, business analysts gather requirements from clients and try to design a system in order to fulfil these requirements. Software design of complex systems exploits various notations for representing knowledge about system structure and behaviour, decisions, processes and different cases. These elements are modelled using such graphical notations, maintained by Object Management Group (OMG), such as UML (Unified Modelling Language), DMN (Decision Model and Notation), BPMN (Business Process Model and Notation), and CMMN (Case Management Model and Notation). In this paper, we present our work-in-progress analysis of the current state of the art in knowledge interchange for these notations. Moreover, we identify the integration or interchange approaches in terms of application areas. Our goal is to provide an input for an integrated method of designing systems with the use of these notations.

Unified Modeling Language (UML) is a standardised Object Management Group (OMG) notation among software engineers. There have been many attempts to design alternatives to UML. Recently, new notations such as Business Process Model and Notation (BPMN) and Decision Model and Notation (DMN) have been proposed for modelling processes and decisions. These dedicated notations provide a simpler way of capturing functional requirements in a designer-friendly fashion. Moreover, some concepts as rules cannot be directly modelled in UML. Our research considers a method of translating business models such as BPMN and DMN into a set of consistent UML models, which can be later used by business analysts and developers to understand and implement the system. As a single notation design, it allows the user to take advantage of software supporting UML modelling and consistency checking, in addition using such translation can provide additional insights into OMG business models. Furthermore, the design provided in a single notation can be easier to follow and develop. This approach supports also visualisation of rules. It is important to mention that the proposed solution does not extend any custom UML artifacts and can be used with standard UML tools.