Presentation and exchange of business models with CIMOSA-XML

In the modern competitive business world there is a frequent need for enterprises to modify their structure of business processes to become more effective in the market place. The solution to this management demand is an improved business integration which is only successful when it is supported by effective IT systems. The Esprit project PRIMA aims to create a competitive advantage for European companies in the process sector by providing a route to ‘smarter' IT investments that are effective across the whole enterprise. A process repository which will store business process models in suitable formats would provide users with appropriate views of the models, focusing only on their information needs. However, the existence of many incompatible modelling methodologies and tools makes it impossible to unify the modelling approach. Therefore it would be desirable to have a high level common modelling language. The PRIMA project has identified CIMOSA as the basis for common semantics of the business model language and the XML format, as a suitable format for the transfer of the model structure and content. The PRIMA working group, in an effort to elaborate these concepts, has developed the Document Type Definition concept (DTD) of the CIMOSA-XML meta-model, which can be used to build the partial enterprise models related to the Business Functional Requirements (BFR) of the PRIMA Process Methodology.     

Operational building blocks for business process modelling

The modelling of business processes is a rather complex, difficult and therefore time-consuming process. The efficiency of this process can be significantly enhanced by employing reusable building blocks, rather than to describe business processes from scratch every time a model is being created or modified. The paper describes a reference model which identifies a set of generic building blocks needed for enterprise modelling and identifies their relationships. Further specialisation of these generic building blocks into a profession and/or industry branch oriented set enables business people to model their processes with a minimum requirement on IT know-how. The CIMOSA concepts and language have been selected as the basis for the reference model. Since CIMOSA is one of the basic concepts recognised in the relevant standardisation work, the presented approach also obeys very closely the relevant European and international standards.     

Enterprise modelling methodology for forward and reverse supply chain flows integration

The paper proposes a new enterprise modelling methodology called ERE-GIO applicable to supply chain reengineering and integration. It is based on two major phases: reverse engineering of the supply chain and then forward engineering. It takes advantages of previous enterprise modelling methodologies, especially CIMOSA. The application of the defined methodology on the logistics flow of an industrial company has allowed the integration of the reverse logistics flows in the traditional supply chain, thanks to the modelling of business processes and the flows related to it.     

The pragmatic quality of Resources‐ Events‐Agents diagrams: an experimental evaluation

The Resources‐Events‐Agents (REA) model is a semantic data model for the development of enterprise information systems. Although this model has been proposed as a benchmark for enterprise information modelling, only few studies have attempted to empirically validate the claimed benefits of REA modelling. Moreover, these studies focused on the evaluation of REA‐based system implementations rather than directly assessing the REA‐modelled conceptual schemas that these systems are based on. This paper presents a laboratory experiment that measured the user understanding of diagrammatic conceptual schemas developed using the REA model. The theoretical foundation for the hypotheses are cognitive theories that explain pattern recognition phenomena and the resulting reduction in cognitive effort for understanding conceptual schemas. The results of the experiment indicate a more accurate understanding of the business processes and policies modelled when users recognize the REA model’s core pattern of enterprise information in the diagram. The implication for modelling practice is that the use of the REA model improves the requirements engineering process by facilitating the user validation of conceptual schemas produced by analysts, and thus helps ensuring the quality of the enterprise information system that is developed or implemented.     

New perspectives in ontological analysis: Guidelines and rules for incorporating modelling languages into UEML

Ontological analysis of modelling languages has been mainly used for evaluating quality of modelling language w.r.t. one specific upper ontology. Generally speaking this evaluation has been done by identifying the coverage of the modelling language constructs w.r.t. the ontology and vice-versa. However, a quite limited support has been developed for performing the ontological analysis task. Specifically, various ontologies used for ontological analysis are not associated to a machine readable format; the coverage of modelling language constructs is mostly provided by informal tables mapping one construct on to one ontological concept; the way in which this coverage task is undertaken is poorly specified (resulting in distinct results for distinct experts involved), and finally, preventing any ontology enrichment for dealing with some specialised language constructs. This limited support also prevents application of ontological analysis outcomes to problems and domains dealing with interoperability, integration and integrated usage of enterprise and IS models, which is today one of the key aspects for making interoperable, maintainable and evolvable inter and intra enterprise software systems. The paper provides an overview of the Unified Enterprise Modelling Language (UEML) approach, which introduces advanced support to ontological analysis of modelling languages. The paper is specifically focused on the task of ontological analysis of modelling languages (named incorporation of modelling languages) by introducing and explaining several guidelines and rules for driving the task: therefore, not all the aspects of the UEML approach will be discussed through the paper. The guidelines and rules are illustrated by incorporation of three selected modelling constructs from IDEF3, a well known language for specifying enterprise processes.     

A visual language and environment for enterprise system modelling and automation

ObjectiveWe want to support enterprise service modelling and generation using a more end user-friendly metaphor than current approaches, which fail to scale to large organisations with key issues of “cobweb” and “labyrinth” problems and large numbers of hidden dependencies.MethodWe present and evaluate an integrated visual approach for business process modelling using a novel tree-based overlay structure that effectively mitigate complexity problems. A tree-overlay based visual notation (EML) and its integrated support environment (MaramaEML) supplement and integrate with existing solutions. Complex business architectures are represented as service trees and business processes are modelled as process overlay sequences on the service trees.ResultsMaramaEML integrates EML and BPMN to provide complementary, high-level business service modelling and supports automatic BPEL code generation from the graphical representations to realise web services implementing the specified processes. It facilitates generated service validation using an integrated LTSA checker and provides a distortion-based fisheye and zooming function to enhance complex diagram navigation. Evaluations of EML show its effectiveness.ConclusionsWe have successfully developed and evaluated a novel tree-based metaphor for business process modelling and enterprise service generation. Practice implications: a more user-friendly modelling approach and support tool for business end users.     

Formal process modelling

As the use of formal methods for computer systems development is now widely taught and commonly practised, their use for business process modelling is now considered. In the same way that formal system models are used to rationalize the implementations of complex computer systems, formal process models may be used to rationalize system requirements of complex business processes. The paper examines this thesis by way of a case study in the use of formal modelling to analyse systems requirements for an order fulfilment process.     

Modelling families of business process variants: A decomposition driven method

Business processes usually do not exist as singular entities that can be managed in isolation, but rather as families of business process variants. When modelling such families of variants, analysts are confronted with the choice between modelling each variant separately, or modelling multiple or all variants in a single model. Modelling each variant separately leads to a proliferation of models that share common parts, resulting in redundancies and inconsistencies. Meanwhile, modelling all variants together leads to less but more complex models, thus hindering on comprehensibility. This paper introduces a method for modelling families of process variants that addresses this trade-off. The key tenet of the method is to alternate between steps of decomposition (breaking down processes into sub-processes) and deciding which parts should be modelled together and which ones should be modelled separately. We have applied the method to two case studies: one concerning the consolidation of existing process models, and another dealing with green-field process discovery. In both cases, the method produced fewer models with respect to the baseline and reduced duplicity by up to 50% without significant impact on complexity.     

Towards the development of the framework for inter sensing enterprise architecture

Inter-enterprise architecture (IEA) is a new concept that seeks to apply the tools and methodologies of enterprise architecture (EA) in a collaborative context, in order to model collaborative organizations in an inclusive manner. According to the main enterprise architectures proposed to this point, an EA should be conformed at least for a framework, a methodology and a modelling language. Sensing enterprise (SE) is an attribute of an enterprise or a network that allows it to react to business stimuli originating on the Internet. These fields have come into focus recently, and there is not evidence of the use of IEA for modelling a SE, while finding an interesting gap to work on. Thus, this paper proposes an initial framework for inter sensing enterprise architecture (FISEA), which seeks to classify, organize, store and communicate, at the conceptual level, all the elements for inter-sensing enterprise architectures and their relationships, ensuring their consistency and integrity. This FISEA provides a clear idea about the elements and views that create collaborative network and their inter-relationships, based on the support of Future Internet.     

Agile enterprise architecture modelling: Evaluating the applicability and integration of six modelling standards

ContextAgile enterprise architecture artefacts are initially architected at the high-level and the details of those artefacts iteratively evolve in small project increments. There is a need to model agile enterprise architecture artefacts both at the high and low detailed level for a particular context. ArchiMate is relatively a new high-level architecture modelling standard. There is a growing interest amongst organisations in applying ArchiMate for high-level agile enterprise architecture modelling. However, organisations are unsure how to effectively apply ArchiMate at high-level and integrate it with their existing low detailed level modelling standards in practice for supporting end-to-end agile enterprise architecture modelling.ObjectiveThis paper evaluates the applicability and integration of high-level ArchiMate modelling standard with the existing low-level modelling standards such as BPMN (Business Process Model and Notation), UML (Unified Modelling Language), FAML (FAME [Framework for Agent-Oriented Method Engineering] Language), SoaML (Service Oriented Architecture Modelling Language), and BMM (Business Motivation Model).MethodA qualitative questionnaire-based evaluation criteria has been developed based on the well-known and comprehensive The Open Group Architecture Framework (TOGAF). The evaluation criteria has been applied to evaluate the applicability and integration of the selected six modelling standards from the business, application, infrastructure and extension perspectives.ResultsEach modelling standard is different in scope. A single modelling standard usually does not provide the kind of support required by the agile enterprise architecture modelling. Based on the review results, a hybrid enterprise architecture modelling approach is proposed. This paper demonstrates the application of the proposed hybrid approach with the help of an agile enterprise architecture modelling case study.ConclusionIt is concluded that the ArchiMate does not replace the existing low-level modelling standards, rather it can be used in conjunction with low-level modelling standards. This calls for the adoption of hybrid and integrated approach for agile enterprise architecture modelling.     

A conceptual framework for understanding business processes and business process modelling

It is increasingly common to describe organizations as sets of business processes that can be analysed and improved by approaches such as business process modelling. Successful business process modelling relies on an adequate view of the nature of business processes, but there is a surprising divergence of opinion about the nature of these processes. This paper proposes a conceptual framework to organize different views of business processes under four headings. It also aims at providing an integrated discussion of the different streams of thought, their strengths and limitations, within business process modelling. It argues that the multifaceted nature of business processes calls for pluralistic and multidisciplinary modelling approaches.     

An extensible,generic environmental process modelling framework with an example for a watershed of a shallow lake

We present a modelling framework for the generation of environmental process models. The framework builds on the Direct Computer Mapping method with an editable, process network based expert module and interpreter. The expert interface supports mapping of objects from the GIS layers onto the prototyped state, transition and connection elements of the case specific generic process model. The developed general purpose interpreter generates the standardized declarative facts and clauses, describing the actual model with the locally executable program prototypes. This input is executed by the general kernel. The model interpreter generates also the case specific templates for the (optionally web based) user interface, while map-server utilizes the GIS shape files of expert model. The implementation supports the extension of the model with new components in space and time. The framework is illustrated by an example for the watershed of Lake Balaton.     

GoBIS: An integrated framework to analyse the goal and business process perspectives in information systems

ContextOrganisational reengineering, continuous process improvement, alignment among complementary analysis perspectives, and information traceability are some current motivations to promote investment and scientific effort for integrating goal and business process perspectives. Providing support to integrate information systems analysis becomes a challenge in this complex setting.ObjectiveThe GoBIS framework integrates two goal and business process modelling approaches: i^⁎ (a goal-oriented modelling method) and Communication Analysis (a communication-oriented business process modelling method).MethodIn this paper, we describe the methodological integration of both methods with the aim of fulfilling several criteria: i) to rely on appropriate theories; ii) to provide abstract and concrete syntaxes; iii) to provide scenarios of application; iv) to develop tool support; v) to provide demonstrable benefits to potential adopters.ResultsWe provide guidelines for using the two modelling methods in a top-down analysis scenario. The guidelines are validated by means of a comparative experiment and a focus-group session with students.ConclusionsFrom a practitioner viewpoint (modeller and/or analyst), the guidelines facilitate the traceability between goal and business process models, the experimental results highlight the benefits of GoBIS in performance and usability perceptions, and demonstrate an improvement on the completeness of the latter having an impact on efficiency. From a researcher perspective, the validation has produced useful feedback for future research.     

用Pi演算为业务过程建模的生命周期

随着企业竞争日趋激烈,业务过程建模技术变得越来越重要.由于形式化方法降低了二义性并为模型的分析和验证提供了可行性,因此形式化的业务过程建模技术在学术界引起了很多人的关注,但到目前为止仍缺乏一套既能方便地进行过程建模,又具有对模型进行形式化分析与验证的整套理论体系.从生命周期的角度入手,探讨如何把形式化方法更有效地应用于商业过程建模.主要工作在于提出了基于Pi演算的生命周期,探讨了生命周期各个阶段使用的技术和工具.     

Domain Modelling and the Co-Design of Business Rules in the Telecommunication Business Area

This paper discusses the development of an enterprise domain model in an environment where part of the domain knowledge is vague and not yet formalised in company-wide business rules. The domain model was developed for a young company starting in the telecommunications sector. The company relied on a number of stand-alone business support systems and sought for a manner to integrate them. There was opted for the development of an enterprise-wide domain model that had to serve as an integration layer to coordinate the stand-alone applications. A specific feature of the company was that it could build up its information infrastructure form scratch, so that many aspects of its business were still in the process of being defined. The paper will highlight parts of the Enterprise Model where there was a need for co-designing business rules together with the domain model. A result of this whole effort was that the company got more insight into important domain knowledge and developed a common understanding across functional areas of the way of doing business.