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

Business Process Execution Language for Web Services Version 1.1

Abstract: This document defines a notation for specifying business process behavior based on Web Services. This notation is called Business Process Execution Language for Web Services (abbreviated to BPEL4WS in the rest of this document). Processes in BPEL4WS export and import functionality by using Web Service interfaces exclusively. Business processes can be described in two ways. Executable business processes model actual behavior of a participant in a business interaction. Business protocols, in contrast, use process descriptions that specify the mutually visible message exchange behavior of each of the parties involved in the protocol, without revealing their internal behavior. The process descriptions for business protocols are called abstract processes. BPEL4WS is meant to be used to model the behavior of both executable and abstract processes. BPEL4WS provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web services interaction model and enables it to support business transactions. BPEL4WS defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intracorporate and the business-to-business spaces. Status of this Document This is an initial public draft release of the BPEL4WS specification. We anticipate a number of extensions to the feature set of BPEL4WS that are discussed briefly at the end of the document. BPEL4WS represents a convergence of the ideas in the XLANG and WSFL specifications. Both XLANG and WSFL are superseded by the BPEL4WS specification. BPEL4WS and related specifications are provided as-is and for review and evaluation only. BEA, IBM and Microsoft hope to solicit your contributions and suggestions in the near future. BEA, IBM and Microsoft make no warrantees or representations regarding the specifications in any manner whatsoever.

Method and apparatus to facilitate development of a customer-specific business process model

Abstract: A business process model (100) pertaining to an application product (102) is associated with a set of views that illustrate the realization of the business process in the appplication product (102). Further, the business process model is displayed to the user together with the set of views to enhance the user's understanding of the business process provided by the application product (102).

Business artifacts: An approach to operational specification

Abstract: Any business, no matter what physical goods or services it produces, relies on business records. It needs to record details of what it produces in terms of concrete information. Business artifacts are a mechanism to record this information in units that are concrete, identifiable, self-describing, and indivisible. We developed the concept of artifacts, or semantic objects, in the context of a technique for constructing formal yet intuitive operational descriptions of a business. This technique, called OpS (Operational Specification), was developed over the course of many business-transformation and business-process-integration engagements for use in IBM's internal processes as well as for use with customers. Business artifacts (or business records) are the basis for the factorization of knowledge that enables the OpS technique. In this paper we present a comprehensive discussion of business artifacts--what they are, how they are represented, and the role they play in operational business modeling. Unlike the more familiar and popular concept of business objects, business artifacts are pure instances rather than instances of a taxonomy of types. Consequently, the key operation on business artifacts is recognition rather than classification.

Method and apparatus for product lifecycle management in a distributed environment enabled by dynamic business process composition and execution by rule inference

Abstract: A system and method for supporting Product Lifecycle Management over a distributed service network topology that connects a hierarchy of functional domains, each domain having a service ontology and one or more service composition schemas defined by the service ontology. Each service composition schema models a business process in its domain. Descriptions of services provided to each domain are published to a service repository by providers of the services, in conformity with one of the service composition schemas. There is a business process proxy provided by the service provider for each service description, which encapsulates for public access the internal processes of the service provider. The invention makes use of an event messaging protocol that enables service collaboration and ad-hoc workflow composition. Each business process is implemented by an ad-hoc workflow comprised of one or more tasks connected by one or more business rules. For each business process there is a business flow manager that dynamically composes ad-hoc workflow prior to execution and dynamically modifies the ad-hoc workflow as the business process executes. The business flow manager uses backward-chain inferencing and then forward-chain inferencing to generate the ad-hoc workflows, based on user identification of a target task. The business flow manager is able to stop execution of the workflow and regenerate a workflow for remaining tasks in response to events received over the network from service providers, and is also able to detect conflicts in the workflows at composition time and at execution time.

Business processes—attempts to find a definition

Abstract: Definitions of business process given in much of the literature on Business Process Management are limited in depth and their related models of business processes are correspondingly constrained. After giving a brief history of the progress of business process modeling techniques from production systems to the office environment, this paper proposes that most definitions are based on machine metaphor type explorations of a process. While these techniques are often rich and illuminating it is suggested that they are too limited to express the true nature of business processes that need to develop and adapt to today's challenging environment.

Principles of the Business Rule Approach

Abstract: The Business Rule Approach represents a major paradigm shift in business-system design and development. Employing a business-driven approach, the use of business rules has been proven to enhance the effectiveness, flexibility, and efficiency of business systems. The technology is appropriate for any kind of organization, and is especially well suited for development in the rapidly expanding Web services industry.Written by the world's leading expert in business rules theory and technology, Principles of the Business Rule Approach is appropriate for business and technical professionals, as well as academics. It serves as a concise introduction and tutorial, presenting understandable explanations and practical techniques.This book explores the rationale behind business rules, as well as the many opportunities presented by this innovative new approach. It explains key business-rule concepts and offers experience-based best practices for expressing business rules. In addition, the book looks at the role of business rules within the context of a wider trend towards model-based development and offers an accessible introduction to the underlying theory of business rules and notation.Topics covered include How the Business Rule Approach is changing the face of business and opening new areas of opportunity The direct impact of business rules on IT projects Organizing basic business knowledge Understanding business structure and processes Working successfully with BRS RuleSpeak,TM including rule categories and sentence patterns for rule statements Expressing business logic using decision tables An in-depth look at fact models Theoretical foundations, including formal constraints and predicatesNumerous appendixes address specific topics in business rule technology, such as the Pattern-R approach and notation, evaluating the truth value of a rule, IF...THEN syntax, and more.Knowledge of the emerging Business Rule Approach is critical for all who are at the leading edge of business system development. Principles of the Business Rule Approach is the authoritative guide and an essential resource. 0201788934B01132003

System and method for the composition, generation, integration and execution of business processes over a network

Abstract: A system and method providing an environment for the composition, generation, integration and execution of business processes and/or transactions over a distributed computing-based network. In a preferred embodiment, a business process expert develops a business model by using a network browser to access the composition environment via the network. The preferred embodiment includes a Composer and a Player. The Composer allows a business process engineer to model the processes, process rules and data structures of an entity upon the basis of a plurality of software resources. The Player executes the modeled processes and access relevant data in real-time, according to rules and resources as related within a software structure generated by the business process engineer. The preferred embodiment dynamically constructs web pages based on the process, rule and data definitions prepared by a business process engineer/expert and does so through a Process Interpreter and Grammar Engine so as to encapsulate all the software resources necessary to complete the desired business process without the need of people programming, scripting or coding. Pages are constructed only when required, ensuring that the solutions are flexible, error free and based upon the most current business practices, providing agile, integrated, error free and real-time software solutions capabilities.

Web Services and Business Transactions

Abstract: Process oriented workflow systems and e-business applications require transactional support in order to orchestrate loosely coupled services into cohesive units of work and guarantee consistent and reliable execution. In this paper we introduce a multi-level transaction model that provides the necessary independence for the participating resource managers, e.g., local database and workflow servers, of organisations engaging in business transactions that are composed of interacting web services. We also present a taxonomy of e-business transaction features such as unconventional atomicity criteria, the need for support for business conversations and the need for distinguishing between three basic business transaction phases. In addition, we review current research and standard activities and outline the main ingredients of a business transaction framework necessary for building flexible e-business applications.

System and method of dynamic service composition for business process outsourcing

Abstract: A system and method for capturing a plurality of business requirements using a Business Process Outsourcing Language (BPOL), an XML representation for expressing business process flow rules, preferences, business rules and event-action mappings as well as service links, to automate the process of generating business processes for use with Web services. BPOL is used to dynamically construct a search script for an advanced Web services discovery engine to find Web services from both UDDI registries and Web services Inspection Language (WSIL) documents and then create a qualified service list. Then a service selection problem is mapped into a solution space {0,1} for use by an optimization algorithm that performs second level service selection of the best set of services based on the requirements.

Systems and methods for monitoring and controlling business level service level agreements

Abstract: Systems and methods for monitoring and controlling business level SLAs (Service level Agreements), and more particularly, systems and method for monitoring and controlling business level SLAs using probe points, KPIs (Key Performance Indicators) and business commitments. An XML (extensible Markup Language)-based specification referred to as BPCL (Business Process Commitment Language) is used to describe business commitments. BPCL specifications are used by a business process management (BPM) system to configure, monitor, and control business processes based on business commitments. Business Commitments and BPCL provide a path toward model-based management for dynamic e-business solutions.

Software business process model

Abstract: A business software framework includes an application framework that has a process model. The process model provides desired services to the business components. The process model arranges operations into activities. The process model can also use an agent/service arrangement.

End-to-end business process solution creation

Abstract: A system and method for creating and managing a business process integration solution comprises modeling a business strategy including elements representing business measurements and initiatives according to defined business goals and objectives of an entity; modeling business operations of the entity in terms of business process elements including process tasks, artifact flows and artifact repositories, and business commitment elements including incorporating key performance indicators; mapping elements of the strategy model with artifact and process elements of the operations model; and, measuring business performance and comparing performance measurements against the key performance indicators. The business strategy and operation model process elements may be continuously refined over a solution development lifecycle as a result of process measurements and comparing. A business level modeling language is further implemented for formally representing the business operations.

UML Modelling of Automated Business Processes with a Mapping to BPEL4WS

Abstract: The Business Process Execution Language for Web Services (BPEL4WS) provides an XML notation and semantics for specifying business process behaviour based on Web Services. A BPEL4WS process is defined in terms of its interactions with partners. A partner may provide services to the process, require services from the process, or participate in a two-way interaction with the process. The Unified Modeling Language— (UML—) is a language, with a visual notation, for modeling software systems. The UML is an OMG— standard and is widely supported by tools. UML can be customized for use in a particular modeling context through a ‘UML profile’. We describe a UML Profile for Automated Business Processes which allows BPEL4WS processes to be modeled using an existing UML tool. We also describe a mapping to BPEL4WS which can be automated to generate web services artifacts (BPEL, WSDL, XSD) from a UML model meeting the profile.

A Framework for Business Rule Driven Service Composition

Abstract: With web services emerging as a promising technology for supporting open and dynamic business processes, it is witnessed that standards for business process specification in the context of web services composition have been fast developed in recent years, e.g. WSFL, XLang, BPEL. However, none of the proposing specifications really address the issues of dynamic business process creation, e.g. a vast service space to search, a variety of services to compare and match, and different ways to construct business processes. One of the assumptions these standards make is that the business process is pre-defined. Obviously this assumption does not hold if the business needs to accommodate changes in applications, technology, and organizational policies. We believe business processes can be dynamically built by composing web services if they are constructed based on and governed by business rules. In this paper we analyze the basic elements in business modelling and how they relate to the web service composition process. As a result a rule driven mechanism is developed to govern and guide the process of service composition in terms of five broad composition phases spanning abstract definition, scheduling, construction, execution, and evolution to support on demand and on the fly business process building.

Method and system for enterprise business process management

Abstract: An enterprise business process management system (100) and method for definition and execution of business processes formed from portions of one or more business applications present in an enterprise. The enterprise business process management system (100) includes a server (101), a router (109), and an interface (111) for defining and executing such business processes. A data quality business process detects, corrects, analyzes, and reports quantitative and qualitative characteristics of application data and transactional data present in the enterprise. An interface module is provided by which a user may select and define function definition information for a business process.

Framework for modeling and providing runtime behavior for business software applications

Abstract: A business software framework supports business software applications. The framework includes a class library component that has a plurality of class libraries of business components, including business entities and business processes. The framework also includes an application framework that has a programming model, the programming model providing a set of application services for relating the business components to one another, and for providing desired services relative to the business components in order to obtain the business application.

Using business‐process simulation within a business‐process reengineering approach

Abstract: This paper presents a case study of the use of business-process simulation within the context of a business-process-reengineering approach to change. The process-based change methodology provides context to the simulation technique in that it connects the aims of a business-process simulation (BPS) study to the strategic aims of the organisation and incorporates a consideration of human factors in order to achieve successful implementation of redesigned processes. Conversely, the ability of BPS to incorporate system variability, scenario analysis and a visual display to communicate process performance makes it a useful technique to provide a realistic assessment of the need for, and results of, change.

Flexible Composition of Enterprise Web Services

Abstract: The process-based composition of Web services is emerging as a promising approach to automate business process within and across organizational boundaries. In this approach, individual Web services are federated into composite Web services whose business logic is expressed as a process model. Business process automation technology such as workflow management systems (WFMSs) can be used to choreograph the component services. However, one of the fundamental assumptions of most WFMSs is that workflow schemas are static and predefined. Such an assumption is impractical for business processes that have an explosive number of options, or dynamic business processes that must be generated and altered on the fly to meet rapid changing business conditions. In this paper, we describe a rule inference framework called DY flow , where end users declaratively define their business objectives or goals and the system dynamically composes Web services

Quality management and improvement: A framework and a business‐process reference model

Abstract: This paper presents a reference model for the process of management of quality and improvement based on a conceptual framework for managing the process of systematically deriving improvement actions from customer expectations and strategic decisions through business processes, and prioritising actions that will most contribute to achievement strategic objectives. After some introductory theoretical background to discuss the need for systematically managing quality and improvement as well as the contribution of mapping business processes, the process reference model is described to a certain extent and detailed by means of activity tree and event‐driven process chain (EPC) diagrams. Finally, some considerations are made on the benefits of using such an approach.

Coordinating Web Services based on business models

Abstract: Coordinating Web Services dynamically revolutionizes how each business collaborates for its performance improvement, so that many IT researchers are recently focusing on them. In order to make the coordination really effective in business, we have to take viewpoints from business models. Though several specifications and approaches were proposed for the coordination, there are no clear relationships between them and business models yet. In this paper, we propose a framework for Web Services coordination based on business models. We have focused on integrating supports for business model management and Web Services based business application development. The framework provides two kinds of repositories for business model management and application development respectively. These repositories enable us to reuse existing models and manage relationships between them, so that we can rapidly reflect business model changes on Web Services coordination.

Business‐process modelling and simulation for manufacturing management: A practical way forward

Abstract: Many companies are taking a process view as a result of business‐process re‐engineering exercises, statutory compliance (e.g. Securities and Futures Authority), reaction to market forces (e.g. to achieve accreditation under ISO9001:2000 or BS5750) and the promotion of integrated computer and information systems (e.g. computer integrated manufacture). This means questioning the way in which companies operate and has implications for management. Business process modelling (BPM) and business‐process simulation (BPS) help to facilitate process thinking. BPM provides management with a static structured approach to business improvement, providing a “holistic” perspective on how the business operates, and provides a means of documenting the business processes while BPS allows management to study the dynamics of the business and consider the effects of changes without risk. There are a number of BPM and BPS methodologies, approaches and tools available, each of which may be applicable to different circumstances. This paper briefly reviews the diverse literature in relation to manufacturing management. Evidence from the literature indicates that few tools are available for supporting manufacturing‐business‐process‐management and that, except for a few small‐scale processes, BPS implementations in manufacturing have had limited success. This paper identifies the reasons for this and suggests a practical way forward until hardware and software limitations are overcome.

Method and apparatus for generating it level executable solution artifacts from the operational specification of a business

Abstract: A system and method that implements top-down and bottom-up model-driven transformations between platform-independent (business view) modeling approaches and platform-specific (IT architectural) models. On the business level, business view models may be expressed in, but not limited to ADF or UML2, whereas on the IT architecture side, service-oriented architectures with Web service interfaces and processes are specified in business process protocol languages including, but not limited to, BPEL4WS, or workflow definitions. An architecture and a transformation method based on typed information flows automatically transforms platform-independent business models into executable information technology (IT) architecture specifications constrained by a specific IT platform, and vice versa. The models generated span the entire life cycle of a software system and ease the software production, deployment and maintenance tasks. That is, the different models generated for the same system are “linked” in a way that relevant changes in one model may be propagated to the other models to keep the model set consistent.

Business process technology for the enterprise

Abstract: A system, method and computer program that enables an application designer to automate the process of software development and develop business applications by modeling the constituent business process models is provided. After identifying the business requirements in terms of the underlying business processes, the same are modeled visually using the inter-relationships across processes. The modeling activity is accomplished by using the visual modeling environment in accordance with the preferred embodiment of the present invention, which, among other tools comprises a set of abstract business components. Each business process is viewed as a collection of business tasks. Each business task is modeled as an instance of an abstract business component. The instance acquires process-specific context with process-specific parameters input by the application designer. Such tasks are then connected together as required for the business process. A runtime execution module of the system executes these business processes at the user's request.

A three-level framework for process and data management of complex e-services

Abstract: Service outsourcing is the business paradigm in which an organization has part of its business process performed by a service provider. In dynamic markets, service providers can be selected on the fly during process enactment. The cooperation between the parties is specified in a dynamically made electronic contract. This contract includes a process specification that is tailored towards service brokering and cross-organizational process enactment and, hence, has to conform to market and specification standards. Process enactment, however, relies on intra-organizational process specifications that have to comply with the infrastructure available in an organization for process and data management. In this paper, we present a three-level process and data specification framework for dynamic contract-based outsourcing of complex services. We focus on services with an externally visible control flow, as opposed to simple, black-box web services. The framework relates the two process specification levels through a third, conceptual level. This approach is inspired by the well-known ANSI-SPARC model for data management. We discuss an abstract architecture for dynamic service outsourcing based on the three-level framework. We show how the framework and architecture can be placed in the context of existing infrastructures for cross-organizational process support. As service outsourcing is used more and more for core business processes requiring reliable execution, we pay special attention to transaction management.

Case-based reasoning as a technique for knowledge management in business process redesign

Abstract: Business Process Redesign (BPR) helps rethinking a process in order to enhance its performance. Practitioners have been developing methodologies to support BPR implementation. However, most methodologies lack actual guidance on deriving a process design threatening the success of BPR. In this paper, we suggest the use of a case-based reasoning technique (CBR) to support solving new problems by adapting previously successful solutions to similar problems to support redesigning new business processes by adapting previously successful redesign to similar business process. An implementation framework for BPR and the CBR's cyclical process are used as a knowledge management technical support to serve for the effective reuses of redesign methods as a knowledge creation and sharing mechanism.

Systems and methods for dynamically configuring business processes

Abstract: Systems and methods for dynamic business process configuration are provided that allow developers to introduce points of variances (parameters/policies) at well-defined places in business processes. The values of these parameters/policies are dependent on the context in which the business process is executed. This context can be defined and modified by business users after deployment based upon the changing needs of the business. The same business processes can be utilized in different contexts without recompilation and involvement of development resources. In one embodiment, to implement dynamic business process configuration, a set of web services APIs is provided that process developers can leverage to add points of variability in their processes. The API talks to a data-model for business processes and trading partners. Once the processes are built leveraging the API, they can be deployed through a set of tools. Also, business users can tailor the business process using an artifact called an agreement using other tools for different scenarios after deployment, as needed, without recompiling or rebuilding the process.

A model-driven transformation method

Abstract: Model-driven architectures (MDA) separate the business or application logic from the underlying platform technology and represent this logic with precise semantic models. These models are supposed to span the entire life cycle of a software system and ease the software production and maintenance tasks. Consequently, tools will be needed that support these tasks. In this paper, we present a method that implements model-driven transformations between particular platform-independent (business view) and platform-specific (IT architectural) models. On the business level, we focus on business view models expressed in ADF or UML2, whereas on the IT architecture side we focus on service-oriented architectures with Web service interfaces and processes specified in business process protocol languages such as BPEL4WS.

Knowledge modelling in weakly‐structured business processes

Abstract: In this paper we present a new approach for integrating knowledge management and business process management. We focus on the modelling of weakly‐structured knowledge‐intensive business processes. We develop a framework for modelling this type of processes that explicitly considers knowledge‐related tasks and knowledge objects and present a workflow tool that is an implementation of our theoretical meta‐model. As an example, we sketch one case study, the process for granting full old age pension as it is performed in the Greek Social Security Institution. Finally we briefly describe some related approaches and compare them to our work and draw the main conclusions and further research directions.

Method and system for automatic continuous monitoring and on-demand optimization of business IT infrastructure according to business objectives

Abstract: A computer implemented method and system for optimizing performance of a business IT infrastructure, wherein business objectives are obtained as input and the IT business infrastructure and/or business level components associated therewith are optimized according to the business objectives. In one embodiment, an objectives definition is created that defines business objectives and business rules determining how IT level metrics affect the business objectives and, optionally, service level agreements or other contract definitions based on the objectives definition. A runtime performance of the business objectives is determined during runtime of the business IT infrastructure by monitoring the business IT infrastructure, its compliance with the contract definitions, and the business objectives achieved by the business IT infrastructure. If a statistically significant change is detected between the runtime performance and a reference optimization of the business objectives, the business model is updated and the reference optimization of the business objectives is re-determined.