Showing papers on "Business Process Model and Notation published in 2007"

Business Process Management: Concepts, Languages, Architectures

Abstract: Business process management is usually treated from two different perspectives: business administration and computer science. While business administration professionals tend to consider information technology as a subordinate aspect in business process management for experts to handle, by contrast computer science professionals often consider business goals and organizational regulations as terms that do not deserve much thought but require the appropriate level of abstraction. Matthias Weske argues that all communities involved need to have a common understanding of the different aspects of business process management. To this end, he details the complete business process lifecycle from the modeling phase to process enactment and improvement, taking into account all different stakeholders involved. After starting with a presentation of general foundations and abstraction models, he explains concepts like process orchestrations and choreographies, as well as process properties and data dependencies. Finally, he presents both traditional and advanced business process management architectures, covering, for example, workflow management systems, service-oriented architectures, and data-driven approaches. In addition, he shows how standards like WfMC, SOAP, WSDL, and BPEL fit into the picture. This textbook is ideally suited for classes on business process management, information systems architecture, and workflow management. This 2nd edition contains major updates on BPMN Version 2 process orchestration and process choreographies, and the chapter on BPM methodologies has been completely rewritten. The accompanying website www.bpm-book.com contains further information and additional teaching material.

Business model innovation: it's not just about technology anymore

Abstract: Purpose – To innovate the company business model, executives must first understand what it is, and then examine what paths exist for them to improve on it. This article aims to examine this issue.Design/methodology/approach – The article provides a practical definition of business models and offers a Business Model Framework (BMF) that illuminates the opportunities for business model innovation.Findings – The article finds that BMF sequences possible business models from very basic (and not very valuable) models to far more advanced (and very valuable) models. Using the BMF, companies can assess where their current business model stands in relation to its potential and then define appropriate next steps for the further advancement of it.Practical implications – An organization must give a senior manager the resources and authority to define and launch business‐model experiments.Originality/value – The article provides a cogent model for assessing the potential for new business model innovation, a framewor...

Modeling control objectives for business process compliance

Abstract: Business process design is primarily driven by process improvementobjectives. However, the role of control objectives stemming from regulationsand standards is becoming increasingly important for businesses in light ofrecent events that led to some of the largest scandals in corporate history. Asorganizations strive to meet compliance agendas, there is an evident need toprovide systematic approaches that assist in the understanding of the interplaybetween (often conflicting) business and control objectives during businessprocess design. In this paper, our objective is twofold. We will firstly present aresearch agenda in the space of business process compliance, identifying majortechnical and organizational challenges. We then tackle a part of the overallproblem space, which deals with the effective modeling of control objectivesand subsequently their propagation onto business process models. Controlobjective modeling is proposed through a specialized modal logic based onnormative systems theory, and the visualization of control objectives onbusiness process models is achieved procedurally. The proposed approach isdemonstrated in the context of a purchase-to-pay scenario.

A static compliance-checking framework for business process models

Abstract: Regulatory compliance of business operations is a critical problem for enterprises. As enterprises increasingly use business process management systems to automate their business processes, technologies to automatically check the compliance of process models against compliance rules are becoming important. In this paper, we present a method to improve the reliability and minimize the risk of failure of business process management systems from a compliance perspective. The proposed method allows separate modeling of both process models and compliance concerns. Business process models expressed in the Business Process Execution Language are transformed into pi-calculus and then into finite state machines. Compliance rules captured in the graphical Business Property Specification Language are translated into linear temporal logic. Thus, process models can be verified against these compliance rules by means of model-checking technology. The benefit of our method is threefold: Through the automated verification of a large set of business process models, our approach increases deployment efficiency and lowers the risk of installing noncompliant processes; it reduces the cost associated with inspecting business process models for compliance; and compliance checking may ensure compliance of new process models before their execution and thereby increase the reliability of business operations in general.

Measuring similarity between semantic business process models

Abstract: A business process may be modeled in different ways by different modelers even when utilizing the same modeling language. An appropriate method for solving ambiguity issues in process models caused by the use of synonyms, homonyms or different abstraction levels for process element names is the use of ontology-based descriptions of process models. So-called semantic business process models promise to support business process interoperability and interconnectivity. But, for (semi-) automatic process interoperability and interconnectivity two problems need to be solved. How can similar terms for process element names be automatically discovered and how can semantic business process composition be facilitated. In this paper we will present solutions for these problems based upon an OWL DL-based description of Petri nets.

A BPMN Extension for the Modeling of Security Requirements in Business Processes

Abstract: Business Processes are considered a crucial issue by many enterprises because they are the key to maintain competitiveness. Moreover, business processes are important for software developers, since they can capture from them the necessary requirements for software design and creation. Besides, business process modeling is the center for conducting and improving how the business is operated. Security is important for business performance, but traditionally, it is considered after the business processes definition. Empirical studies show that, at the business process level, customers, end users, and business analysts are able to express their security needs. In this work, we will present a proposal aimed at integrating security requirements through business process modeling. We will summarize our Business Process Modeling Notation extension for modeling secure business process through Business Process Diagrams, and we will apply this approach to a typical health-care business process.

Auditing Business Process Compliance

Abstract: Compliance issues impose significant management and reporting requirements upon organizations. We present an approach to enhance business process modeling notations with the capability to detect and resolve many broad compliance related issues. We provide a semantic characterization of a minimal revision strategy that helps us obtain compliant process models from models that might be initially non-compliant, in a manner that accommodates the structural and semantic dimensions of parsimoniously annotated process models. We also provide a heuristic approach to compliance resolution using a notion of compliance patterns. This allows us to partially automate compliance resolution, leading to reduced levels of analyst involvement and improved decision support.

An Ontology Framework for Semantic Business Process Management

Abstract: A core challenge in Business Process Management is the continuous, bi-directional translation between (1) a business requirements view on the process space of an enterprise and (2) the actual process space of this enterprise, constituted by the multiplicity of IT systems, resources, and human labor. Semantic Business Process Management (SBPM) [HeLD'05] 1 is a novel approach of increasing the level of automation in the translation between these two spheres, and is currently driven by major players from the ERP, BPM, and Semantic Web Services domain, namely SAP 2 . One core paradigm of SPBM is to represent the two spheres and their parts using ontology languages and to employ machine reasoning for the automated or semi-automated translation. In this paper, we (1) outline the representational requirements of SBPM, (2) propose a set of ontologies and formalisms, and (3) define the scope of these ontologies by giving competency questions, which is a common technique in the ontology engineering process.

A survey of comparative business process modeling approaches

Abstract: There has been a huge influx of business process modeling langu ages as business process management (BPM) and process-aware information systems continue to expand into various business domains. The origins of process modeling languages are quite diverse, although two dominant approaches can be observed; one based on graphical models, and the other based on rule specifications. However, at this time, there is no report in literature that specifically targets a comparative analysis of these two approaches, on aspects such as the relative areas of application, power of expression, and limitations. In this paper we have attempted to address this question. We will present both a survey of the two approaches as well as a critical and comparative analysis.

Quality metrics for business process models

Abstract: In the area of software engineering, quality metrics have shown their importance for good programming practices and software designs. A design developed by the help of these metrics (e.g. coupling, cohesion, complexity, modularity and size) as guiding principals is likely to be less error-prone, easy to understand, maintain, and manage, and is more efficient. Several researchers already identified similarities between software programs and business process designs and recognized the potential of quality metrics in business process management (Cardoso, Mendling, Neuman & Reliers, 2006; Gruhn & Laue, 2006; Latva-Koivisto, 2001). This chapter elaborates on the importance of quality metrics for business process modeling. It presents a classification and an overview of current business process metrics and it gives an example of the implementation of these metrics using the ProM tool. ProM is an analysis tool, freely available, that can be used to study process models implemented in more than eight languages.

Generation of business process models for object life cycle compliance

Abstract: Business process models usually capture data exchanged betweentasks in terms of objects. These objects are commonly standardizedusing reference data models that prescribe, among other things, allowedobject states. Allowed state transitions can be modeled as objectlife cycles that require compliance of business processes. In this paper, wefirst establish a notion of compliance of a business process model with anobject life cycle. We then propose a technique for generating a compliantbusiness process model from a set of given reference object life cycles.

BPMN-Q: A Language to Query Business Processes

Abstract: With the growing role business processes play in today’s business life, they are being seen as an asset for the organization. With hundreds of process models developed by different process designers it would be helpful to look up the repository for models that could handle a similar situation before developing new ones. In this paper we introduce a new visual query language for business processes. The language addresses processes definitions. It extends BPMN for its abstract syntax as BPMN is a standard visual notation for modeling business processes. The overall architecture of the system in which the language can fit, in addition to the details of the query processing are also discussed.

Business process map management

Abstract: Methods and apparatuses enable providing a workflow management environment that provides different workflow management perspectives with different views on a variety of reusable workflow components or workflow resources. The different views may include a swim lane view having multiple separate sections that each represents a different performer, and a list view that represents the resources in transactional order. The workflow management environment defines reusable workflow components and associates the components with the different performers and with each other. The defining of the components and the relationships can define a portion of a workflow.

Modeling business contexture and behavior using business artifacts

Abstract: Traditional process modeling approaches focus on the activities needed to achieve a business goal. However, these approaches often pose obstacles in consolidating processes across an organization because they fail to capture the informational structure pertinent to the business context or contexture. In this paper, we discuss business artifact-centered operational modeling. Artifacts capture the contexture of a business and operational models describe how a business goal is achieved by acting upon the business artifact. Business artifacts, such as Purchase Order or Insurance Claim, provide business analysts an additional dimension to model their business. With operational models, they can describe how a business operates by processing business artifacts and adding business value to the artifacts. This approach has been successfully employed in a variety of customer engagements. We summarize our best practices by describing nine operational patterns. Furthermore, we develop a computational model for operational models based on Petri Nets to enable formal analysis and verification thereof.

Requirements-driven design and configuration management of business processes

Abstract: The success of a business process (BP) depends on whether it meetsits business goal as well as non-functional requirements associated with it. BPspecifications frequently need to accommodate changing business priorities,varying client preferences, etc. However, since business process goals and preferencesare Rarely captured explicitly in the dominant BP modeling approaches,adapting business processes proves difficult. We propose a systematic requirements-driven approach for BP design and configuration management that usesrequirements goal models to capture alternative process configurations and providesthe ability to tailor deployed processes to changing business priorities orcustomer preferences (i.e., non-functional constraints) by configuring their correspondinggoal models at the goal level. A set of design time and runtime toolsfor configuring business processes implemented using WS-BPEL is provided,allowing to easily change the behaviour of deployed BP instances at a highlevel, based on business priorities and stakeholder preferences.

Modeling of task-based authorization constraints in BPMN

Abstract: Workflows model and control the execution of business processes inan organisation by defining a set of tasks to be done. The specification of workflowsis well-elaborated and heavily tool supported. Task-based access control istailored to specify authorization constraints for task allocation in workflows. Existingworkflow modeling notations do not support the description of authorizationconstraints for task allocation commonly referred to as resource allocationpatterns. In this paper we propose an extension for the Business Process Modeling Notation(BPMN) to express such authorizations within the workflow model, enablingthe support of resource allocation pattern, such as Separation of Duty,Role-Based Allocation, Case Handling, or History-Based Allocation in BPMN.These pattern allow to specify authorization constraints, for instance role-task assignments,separation of duty, and binding of duty constraints. Based on a formalapproach we develop an authorization constraint artifact for BPMN to describesuch constraints. As a pragmatic demonstration of the feasibility of our proposed extensionwe model authorization constraints inspired by a real world banking workflowscenario. In the course of this paper we identify several aspects of future workrelated to verification and consistency analysis of modeled authorization constraints,tool-supported and pattern-driven authorization constraint description,and automatic derivation of authorization policies, such as defined by the eXtensibleAccess Control Markup Language (XACML).

Pattern-based design and validation of business process compliance

Abstract: In this paper we present a novel approach for the modeling and implementation of Internal Controls in Business Processes. The approach is based on the formal modeling of Internal Controls in the validation process under the usage of frequently recurring control patterns. The main idea is the introduction of a semantic layer in which the process instances are interpreted according to an independently designed set of controls. This ensures separation of business and control objectives in a Business Process. A prototypical implementation of the approach is presented.

Specification and Verification of Artifact Behaviors in Business Process Models

Abstract: SOA has influenced business process modeling and management. Recent business process models have elevated data representation to the same level as control flows, for example, the artifact-centric business process models allow the life cycle properties of artifacts (data objects) to be specified and analyzed. In this paper, we develop a specification language ABSL based on computation tree logic for artifact life cycle behaviors (e.g., reachability). We show that given a business model and starting configuration, it can be decided if an ABSL sentence is satisfied when the domains are bounded, and if an ABSL-core (sublanguage of ABSL) sentence is satisfied when the domains are totally ordered but unbounded. We also show that if the starting configuration is not given, ABSL(-core) is still decidable if the number of artifacts is bounded with bounded (resp. unbounded but ordered) domains.

Does It Matter Which Process Modelling Language We Teach or Use? An Experimental Study on Understanding Process Modelling Languages without Formal Education

Abstract: Process modelling has over the years become an essential skill in Information Systems and Business Process Management practice Consequently, more and more training programs have evolved, teaching different process modelling languages Two popular process modelling languages are being compared in this experimental study Experiment participants received extensive training in one language but not the other, leading to the expectation that learning outcomes would be better in the case of the familiar language Our study provides empirical evidence that this is not the case In fact, it is shown that participants achieved similar learning outcomes when confronted with the unfamiliar language Our results lead to a fundamental question, namely whether it is actually an important teaching decision what sort of process modelling language is being taught Our findings suggest that education and research in process modelling should focus on aspects other than the style, nature or features of languages and tools

Semantic Business Process Management: A Lifecycle Based Requirements Analysis

Abstract: Despite of increasing software support for Business Process Management (BPM), currently there is still a low degree of automation in the BPM lifecycle, especially when it comes to bridge between the business and IT view on business processes. The goal of Semantic Business Process Management is to achieve more automation in BPM by using semantic technologies. In this paper, we describe on a conceptual level how ontologies and semantic web service technologies can be used throughout the BPM lifecycle, consisting of process modeling, implementation, execution, and analysis phases. The use of semantics in BPM results in new functionality a Semantic Business Process Management System (SBPMS) has to implement. For each phase of the BPM lifecycle, we identify the new functional requirements for a SBPMS, and explain the benefits of adopting semantic technologies in SBPM.

Elements of a business process management system: Theory and practice

Abstract: Purpose – To construct, test and illustrate a sophisticated and theory-based architecture for analyzing business process management systems (BPMS) used for business process change. Design/methodology/approach – Exploration of business process modeling-based BPMS via a meta-survey of academic and business literatures. Two main dimensions are used based upon semiotics and a block-based BPMS pyramid architecture. Each block is a core technology required for the functioning of the BPMS and include: the subject being modeled; the software formalism; the IT infrastructure; the modeling language and notation; and the underlying technical infrastructure. Findings – Theoretically explains and empirically illustrates each core technology in the proposed architecture then does the same for the architecture, its arrangement as a whole and its interrelationships. Recognizes the lack of a theoretical basis for business process modeling constructs and the dangers that this generates. Explains why automatic BPMS require formal construct transmission from subject modeled to modeling hardware and software. Research limitations/implications – The architecture’s core technologies span numerous disciplines so each set of literatures introduces the component concepts and their bases but is not exhaustive. Originality/value – This paper proposes a considerably more sophisticated framework for BPMS analysis than is currently available; it is theoretically and not just empirically based; it uses a novel method of theoretical justification concerned with the transmission of modeled properties and characteristics between several technological media; and it illustrates the innovative analytical use of this architecture and the practical use of BPMS with three different case vignettes.

User-friendly semantic annotation in business process modeling

Abstract: Current problems in Business Process Management consist of terminology mismatches and unstructured and isolated knowledge representation in process models Semantic Business Process Management aims at overcoming many of those weaknesses of Business Processes Management through the use of explicit semantic descriptions of process artifacts However, this vision has a prerequisite: semantic annotations need to be added to the process models In this paper, we present an approach that allows flexibly annotating semantics in a user-friendly way, by exposing ontological knowledge to the business user in appropriate forms and by employing matchmaking and filtering techniques to display options with high relevance only By adding semantic information the precision of process models increases, ultimately supporting Web Service discovery and composition As a proof-of-concept, the work has been implemented prototypically in a process modeling tool

A Service-oriented Architecture for Business Intelligence

Abstract: Business intelligence is a business management term used to describe applications and technologies which are used to gather, provide access to and analyze data and information about the organization, to help make better business decisions. In other words, the purpose of business intelligence is to provide actionable insight Business intelligence technologies include traditional data warehousing technologies such as reporting, ad-hoc querying, online analytical processing (OLAP). More advanced business intelligence tools - such as HP Openview DecisionCenter - also include data-mining, predictive analysis using rule-based simulations, Web services and advanced visualization capabilities. In this paper we describe a service-oriented architecture for business intelligence that makes possible a seamless integration of technologies into a coherent business intelligence environment, thus enabling simplified data delivery and low-latency analytics. We compare our service-oriented approach with traditional BI architectures, illustrate the advantages of the service oriented paradigm and share our experience and the lessons learned in architecting and implementing the framework.

Verification of Business Process Quality Constraints Based on Visual Process Patterns

Abstract: Business processes usually have to consider certain constraints like domain specific and quality requirements. The automated formal verification of these constraints is desirable, but requires the user to provide an unambiguous formal specification. In particular since the notations for business process modeling are usually visual flow-oriented languages, the notational gap to the languages usually employed for the formal specification of constraints, e.g., temporal logic, is significant and hard to bridge. Thus, our approach relies on UML Activities as a single language for the specification of both business processes and the corresponding constraints. For the expression of such constraints, we have provided a process pattern definition language based on specialized Activities. In this paper, we describe how model checking can be employed for formal verification of business processes against such patterns. For this, we present an automated transformation of the business process and the corresponding patterns into a transition system and temporal logic, respectively.

Semantically enhanced Business Process Modelling Notation.

Abstract: This position paper presents the semantically enhanced Business Process Modelling Notation, namely the sBPMN ontology, developed within the SUPER project Moreover, it elaborates shortly on drawbacks of the BPMN to BPEL translation and proposes to use semantics to overcome them

Towards a formal framework for reuse in business process modeling

Abstract: Business process models are created by business users with an objective to capture business requirements, enable a better understanding of business processes, facilitate communication between business analysts and IT experts, identify process improvement options and serve as a basis for derivation of executable business processes. Designing a new process model is a highly complex, time consuming and error prone task. In order to address this problem, we propose an approach to business process modeling through reuse of existing business process artifacts - process fragments. In addition, we provide a rich formalism for business process description based on π-calculus and ontologies as a basis of the approach. The formalism integrates different workflow perspectives and thus exposes the complete process model description to expressive querying and reasoning.

Transformation of BPMN Models for Behaviour Analysis

Abstract: In industry, many business processes are modelled and stored in Enterprise Information Systems (EIS). Tools supporting the verification and validation of business processes can help to improve the quality of these business processes. However, existing tools can not directly be applied to models used in industry. In this paper, we present our approach for model verification and validation: translating industrial models to Petri nets and mCRL2, and subsequently applying existing tools on the models derived from the initial industrial models. The following translations are described: BPMN models to Petri nets and Petri nets to mCRL2. It is shown what the analysis on the derived models can reveal about the original models.

Process extension wizard for coherent multi-dimensional business process models

Abstract: This disclosure relates to methods, systems, and software for processing a coherent multi-dimensional business process model. The software includes computer-readable instructions embodied on media to identify a coherent multi-dimensional business process model based on at least a portion of a first model for a business process and at least a portion of a second model for the business process. The software then parses the multi-dimensional business process model to identify at least one extension point, each extension point operable to interface a disparate business tool with the business process. The software is further operable to present an extension wizard to a client for a particular one of the identified extension points. It can create entities and extensions in various modeling environments and development environments.