Showing papers on "Process modeling published in 2000"

Guidelines of Business Process Modeling

Abstract: Process modeling becomes more and more an important task not only for the purpose of software engineering, but also for many other purposes besides the development of software. Therefore it is necessary to evaluate the quality of process models from different viewpoints. This is even more important as the increasing number of different end users, different purposes and the availability of different modeling techniques and modeling tools leads to a higher complexity of information models. In this paper the Guidelines of Modeling (GoM)1, a framework to structure factors for the evaluation of process models, is presented. Exemplary, Guidelines of Modeling for workflow management and simulation are presented. Moreover, six general techniques for adjusting models to the perspectives of different types of user and purposes will be explained.

Analyzing process models using graph reduction techniques

Abstract: The foundation of a process model lies in its structural specifications. Using a generic process modeling language for workflows, we show how a structural specification may contain deadlock and lack of synchronization conflicts that could compromise the correct execution of workflows. In general, identification of such conflicts is a computationally complex problem and requires development of effective algorithms specific for the target modeling language. We present a visual verification approach and algorithm that employs a set of graph reduction rules to identify structural conflicts in process models for the given workflow modeling language. We also provide insights into the correctness and complexity of the reduction process. Finally, we show how the reduction algorithm may be used to count possible instance subgraphs of a correct process model. The main contribution of the paper is a new technique for satisfying well-defined correctness criteria in process models. © 2000 Published by Elsevier Science Ltd. All rights reserved.

ARIS Architecture and Reference Models for Business Process Management

Abstract: In this article a general business process architecture is presented, which is based on the Architecture of Integrated Information Systems (ARIS) and which is composed of the four levels of process engineering, process planning and control, workflow control and application systems The ARIS-House of Business Engineering encompasses the whole life-cycle range: from business process design to information technology deployment, leading to a completely new process-oriented software concept At the same time, the architecture bridges the gap between business process modeling and workflow-driven applications, from Business Process Reengineering to Continuous Process Improvement

Process-based models for forest ecosystem management: current state of the art and challenges for practical implementation

Abstract: Recent progress toward the application of process-based models in forestmanagement includes the development of evaluation and parameter estimation methods suitable for models with causal structure, and the accumulation of data that can be used in model evaluation. The current state of the art of process modeling is discussed in the context of forest ecosystem management. We argue that the carbon balance approach is readily applicable for projecting forest yield and productivity, and review several carbon balance models for estimating stand productivity and individual tree growth and competition. We propose that to develop operational models, it is necessary to accept that all models may have both empirical and causal components at the system level. We present examples of hybrid carbon balance models and consider issues that currently require incorporation of empirical information at the system level. We review model calibration and validation methods that take account of the hybrid character of models. The operational implementation of process-based models to practical forest management is discussed. Methods of decision-making in forest management are gradually moving toward a more general, analytical approach, and it seems likely that models that include some process-oriented components will soon be used in forestry enterprises. This development is likely to run parallel with the further development of ecophysiologically based models.

Business Modelling Is Not Process Modelling

Abstract: Innovative e-business projects start with a design of the e-business model.We often encounter the view, in research as well as industry practice, that an e-business model is similar to a business process model, and so can be specified using UML activity diagrams or Petri nets. In this paper, we explain why this is a misunderstanding. The root cause is that a business model is not about process but about value exchanged between actors. Failure to make this separation of concerns leads to poor business decision-making and inadequate business requirements.

Integrated process modeling: an ontological evaluation

Abstract: Process modeling has gained prominence in the information systems modeling area due to its focus on business processes and its usefulness in such business improvement methodologies as Total Quality Management, Business Process Reengineering, and Workflow Management. However, process modeling techniques are not without their criticisms [13]. This paper proposes and uses the Bunge-Wand-Weber (BWW) representation model to analyze the five views - process, data, function, organization and output - provided in the Architecture of Integrated Information Systems (ARIS) popularized by Scheer [39, 40, 41]. The BWW representation model attempts to provide a theoretical base on which to evaluate and thus contribute to the improvement of information systems modeling techniques. The analysis conducted in this paper prompts some propositions. It confirms that the process view alone is not sufficient to model all the real-world constructs required. Some other symbols or views are needed to overcome these deficiencies. However, even when considering all five views in combination, problems may arise in representing all potentially required business rules, specifying the scope and boundaries of the system under consideration, and employing a top-down approach to analysis and design. Further work from this study will involve the operationalization of these propositions and their empirical testing in the field. (C) 2000 Elsevier Science Ltd. All rights reserved.

The Process Specification Language (PSL) Overview and Version 1.0 Specification

Abstract: This document describes Version 1.0 of the Process Specification Language (PSL). PSL is an interchange format designed to help exchange process information automatically among a wide variety of manufacturing applications such as process modeling, process planning, scheduling, simulation, workflow, project management, and business process re-engineering tools. These tools would interoperate by translating between their native format and PSL. Then, any system would be able to automatically exchange process information with any other system via PSL.

Modeling and Composing Service-Based nd Reference Process-Based Multi-enterprise Processes

Abstract: Multi-enterprise processes (MEPs) are workflows consisting of a set of activities that are implemented by different enterprises Tightly coupled Virtual Enterprises (VEs) typically agree on abstract MEPs (reference MEPs), to which each enterprise contributes single-enterprise processes (SEPs) that implement and refine the activities in the reference MEP On the other end of the spectrum, loosely coupled VEs use service-based MEPs that fuse together heterogeneous services implemented and provided by different enterprises Existing process models usually couple activities with their implementation Therefore, they cannot effectively support such MEPs In this paper, we introduce a Polymorphic Process Model (PPM) that supports both reference process- and service-based MEPs To accomplish this, PPM decouples activity interface from activity implementation, and provides process polymorphism to support their mapping In particular, PPM determines activity types from the activity interfaces, permits activity interface subtyping, and provides for the mapping of MEP activity types to concrete implementations via interface matching We illustrate that these key PPM capabilities permit the late binding and use of multiple activity implementations within a MEP without modifying the MEP at run time or enumerating the alternative implementation at specification time

Modeling Processes and Workflows by Business Rules

Abstract: This contribution describes a rule-based method for modeling business processes and workflows. Business rules are defined as statements about guidelines and restrictions with respect to states and processes in an organization. After introducing an extended Event-Condition-Action (ECA) notation, an approach for the refinement of business rules is developed in order to achieve a consistent decomposition of the business processes. Thus, ECA rules serve as an integration layer between different process modeling and (workflow) specification languages. Finally, we propose an architecture of a rule-oriented repository supporting the modeling and refinement process.

Enterprise modeling with UML: designing successful software through business analysis

Abstract: (Each chapter concludes with a Summary.) Preface. Business Engineering. Structure of the Book. Conventions Used in Book. 1. Introduction. Business Basics. Enterprise Modeling. 2. Purpose. Introduction to Purpose. Purpose Components. 3. Processes. What is a Business Process? Process Design with UML. Process Components. 4. Entities. Entity Models. Entity Roles. Entity Values. 5. Organization. Organizations, Systems, and Complexity. Organization Structure. Organization Components. Appendix. Simple System. Entity Components. Process Components. Purpose Components. Glossary. Bibliography. Index. 0201433133T04062001

Knowledge-engineering protocol-suite

Abstract: A Knowledge-Engineering Protocol-Suite is presented that generally includes methods and systems, apparatus for search-space organizational validation, and appurtenances for use therewith. The protocol-suite includes a search-space organizational validation method for synergistically combining knowledge bases of disparate resolution data-sets, such as by actual or simulated integrating of lower resolution expert-experience based model-like templates to higher resolution empirical data-capture dense quantitative search-spaces. Furthermore, from alternative technological vantages, the suite relates to situations where this synergetic combining is beneficially accomplished, such as in control systems, command control systems, command control communications systems, computational apparatus associated with the aforesaid, and to quantitative modeling and measuring tools used therewith. The protocol-suite also includes facile algorithmic tools for use with the method and a process-modeling computer for use in a distributed asynchronous system of process modeling computers.

The Modular Modeling System (MMS)—The Physical Process Modeling Component of a Database-Centered Decision Support System for Water and Ecosystem Management

Abstract: The Modular Modeling System (MMS) is an integrated system of computer software that is being developed to provide the research and operational framework needed to support development, testing, and evaluation of physical-process algorithms, and to facilitate integration of user-selected sets of algorithms into operational physical-process models. MMS uses a module library that contains compatible modules for simulating a variety of water, energy, and biogeochemical processes. A model is created by selectively linking modules from the library using MMS model-building tools. A geographic information system (GIS) interface also is being developed for MMS to support a variety of GIS tools for use in characterizing and parameterizing topographic, hydrologic, and ecosystem features, visualizing spatially and temporally distributed model parameters and variables, and analyzing and validating model results. MMS is being coupled with the Power Reservoir System Model (PRSYM) to provide a database-centered decision support system for making complex operational decisions on multipurpose reservoir systems and watersheds. The U.S. Geological Survey and the Bureau of Reclamation are working collaboratively on a project titled the Watershed Modeling Systems Initiative to develop and apply the coupled MMS — PRSYM models to the San Juan River basin in Colorado, New Mexico, Arizona, and Utah.

Improving Flexibility of Workflow Management Systems

Abstract: In order to support both the redesign of a Business Process and its continuous improvement, the technology supporting it must be as flexible as possible. Since workflow management systems are the main technology for supporting Business Processes, they and, in particular, their modeling framework must satisfy a long list of apparently conflicting requirements: the models must be both cognitive artifacts and executable programs; they must be simple and yet able to support exceptions; they must support both static and dynamic changes. In this chapter, after briefly discussing the above requirements, we present the formal aspects of the modeling framework of the MILANO workflow management system. Its flexibility is based on a net-theoretical modeling framework which lets simple process models deliver a large class of services to its users.

Assessing the quality of business process modelling techniques

Abstract: The conceptual modelling of business processes is becoming popular. The number of techniques and tools is growing fast. At the same time, an appropriate framework for understanding the quality of these modelling techniques is lacking. We report upon the development of a framework for understanding the quality of business process modelling techniques, called the QME framework. The framework defines the elements that constitute a modelling technique and presents a number of quality properties as well as ways to operationalise them. The framework is applied to illustrate the quality of the Dynamic Essential Modelling of Organisations (DEMO) business modelling technique. Conclusions are drawn both on the quality of DEMO and on the application of the framework to study DEMO.

On Capturing Exceptions in Workflow Process Models

Abstract: Exceptions have always been a major source of complexity and limitation in business process automation. In this paper we review exception handling from the perspective of large business processes that involve several, possibly heterogeneous and distributed information systems. The aim is to capture behavior which represents deviations from the normal process, but still can be anticipated, and handled accordingly. These exceptions are useful and a key to effective and flexible processes. Using workflow techniques as instruments of business process modeling, we provide methodological guidelines for analyzing exceptional behavior and designing special constructs within the process model that support useful exceptions.

Processes and Their Frameworks

Abstract: A process is a time-dependent sequence of events governed by a process framework. A group process has five components: the entities performing the process, the steps or elements of a process, the relationship between any pair of elements, the links to other processes, and the resources and their characteristics-in-use involved with the elements. A process framework is denoted by Y = FC where Y is the set of outcomes or consequences of a process, C is the set of considerations or elements in the process, and F is the network linking the considerations to each other and to the outcomes. The properties of the set of considerations, the linkages between pairs of consequences, the set of outcomes or consequences, the network, F, and the use of process frameworks are discussed in detail with examples. Process models are compared to variable models.

Disassembly modeling, planning and application: a review

Abstract: Industrial recycling and remanufacturing is practice of growing importance due to the increasing environmental and economic pressures. It involves product disassembly to retrieve the desired parts and/or subassemblies by separating a product into its constituencies. The disassembly process modeling and planning is more challenging than assembly since its termination goal is not necessarily fixed depending on the system status. Moreover, it is uncontested that disassembly is charged with more uncertainty in system structures and component conditions than assembly. The paper reviews methods for modeling and process planning in disassembly. Its purpose is to survey the state-of-the-art of this emerging area to supply important information for future study.

Quantitative analysis of static models of processes

Abstract: The upstream activities of software development projects are often viewed as both the most important, the least understood, and hence the most problematic. This is particularly noticeable in terms of satisfying customer requirements. Business process modelling is one solution that is being increasingly used in conjunction with traditional software development, often feeding in to requirements and analysis activities. In addition, research in Systems Engineering for Business Process Change,11Systems Engineering for Business Process Change is a UK research programme funded by the Engineering and Physical Sciences Research Council. highlights the importance of modelling business processes in evolving and maintaining legacy systems that support those processes. However, the major use of business process modelling, is to attempt to restructure the business process, in order to improve some given aspect, e.g., cost or time. This restructuring may be seen either as separate activity or as a pre-cursor to the development of systems to support the new or improved process. The analysis of these business models is, therefore, vital to the improvement of the process and the development of supporting software systems. Supporting this analysis is the focus of this paper. Business processes are typically described with static (diagrammatic) models. This paper proposes a quantitative approach to aid analysis and comparison of these models. This is illustrated using the process-modelling notation, Role Activity Diagrams (RADs). We studied 10 prototyping processes across a number of organisations and found that roles of the same type exhibited similar levels of coupling across processes. Where roles did not adhere to tentative threshold values, further investigation revealed unusual circumstances or hidden behaviour. Notably, analysis of the prototyping roles (which exhibited the greatest variation in coupling), found that coupling was highly correlated with the size of the development team and the number of participants. This suggests that prototyping in large projects had a different process to that for small projects and required more mechanisms for communication. We conclude that counts (measures) may be useful in the analysis of static process models.

Beneath the surface of organizational processes: a social representation framework for business process redesign

Abstract: This paper raises the question, “What is an effective representation framework for organizational process design?” By combining our knowledge of existing process models with data from a field study, the paper develops criteria for an effective process representation. Using these criteria and the case study, the paper integrates the process redesign and information system literatures to develop a representation framework that captures a process' social context. The paper argues that this social context framework, which represents people's motivations, social relationships, and social constraints, gives redesigners a richer sense of the process and allows process redesigners to simultaneously change social and logistic systems. The paper demonstrates the framework and some of its benefits and limitations.

On the challenges of business modeling in large-scale reengineering projects

Abstract: Modeling existing and future business processes is crucial to the outcome of large-scale reengineering projects. The use of parameterized or standard components does not render business models redundant, but shifts the modeling focus even more from technical aspects to the real-world business processes. In current reengineering projects, however, there is often a lack of coordination of modeling activities and the consistency of conceptual models across project activities can be threatened. There are often several models of the same phenomenon that are used by different people, in different phases, or for different purposes. This paper discusses some of the challenges of business modeling and presents a three-tier model description that explains some of the model variants found in reengineering projects. The findings from a large-scale SAP project in Europe underline the importance of a balanced business model and show how individually tailored conceptual models may hamper the formation of a common understanding of the domain and badly affect the reengineering of the business processes.

Re‐engineering manufacturing processes through simulation modelling

Abstract: Previous research suggests that developing dynamic models of business processes prior to their radical change could increase the success of BPR projects Identifies barriers encountered in existing business processes and presents an overview of business process modelling methods that can be used to identify ways of eliminating these barriers A case study is used to demonstrate how simulation modelling can be used to effectively re‐engineer manufacturing processes The developed model is then manipulated, with results being generated to discover the possibilities of increasing the through‐put of the system The usability of simulation modelling for evaluating alternative business process strategies is then investigated Guidelines for achieving more widespread use of business process simulation are then proposed

How conceptual system architecture leads to business process

Abstract: While designing a global bank's Money-Link, the clustering of non-functional properties suggested two “lobes”: (1) transactional (enabling payments among affiliate banks), which required high-availability, high-security, and geographical distribution; and (2) analytic, with traditional database requirements These purely architectural components coincided with business processes separately identified by business analysts Architecture provided problem domain insight

Object-oriented modeling: a roadmap

Abstract: Object-oriented modeling has become the de-facto standard in the early phases of a software development process during the last decade. The current state-of-the-art is dominated by the existence of the Unified Modeling Language (UML), the development of which has been initiated and pushed by industry. This paper presents a list of requirements for an ideal object-oriented modeling language and compares it with the achievements of UML and other object-oriented modeling approaches. This forms the base for the discussion of a roadmap for object-oriented modeling, which is structured according to a classification scheme of six different themes, which are language-, modelor process-related, respectively.

Generic Linear Business Process Modeling

Abstract: Visual-oriented process modeling concepts and languages used today often lead to modeling of "spaghetti-processes". Thus, the process models are not applicable effectively in distributed, partially automated and dynamic scenarios. They also support permanent adaptation and composition of process models insufficiently. The approach of Generic Linear Business Process Modeling describes a meta model that aims to avoid these inadequacy. According to the concept of linear programming, nested logic blocks are applied to model the process flow. Additionally, by using generic blocks composition and amplifying of process models on different levels of detail is achieved. Further the approach outlines the visualization of generic linear process models and an XML based format in order to exchange the models in a networked business environment.