Topic
Business Process Model and Notation
About: Business Process Model and Notation is a research topic. Over the lifetime, 9038 publications have been published within this topic receiving 190712 citations. The topic is also known as: Business Process Modeling Notation & BPMN.
Papers published on a yearly basis
Papers
More filters
01 Jan 2004
TL;DR: This short paper introduces the basic language elements of BPEL4WS using a simple example, and presents the resulting application structure and the resulting economical implications.
Abstract: Business Process Execution Language for Web Services (BPEL4WS) allows defining both, business processes that make use of Web services, and business processes that externalize their functionality as Web services. This short paper introduces the basic language elements of BPEL4WS using a simple example. The concepts underlying the language are briefly explained: establishing bilateral partnerships, correlating messages and processes, defining the order of the activities of a business process, event handling, handling exceptions via long-running transactions, and the usage of BPEL4WS in pure B2B scenarios. The paper finishes off by presenting the resulting application structure and the resulting economical implications.
51 citations
IBM1
TL;DR: A tool to make data warehouses more business-friendly by using Semantic Web technologies and OWL provides an excellent basis for the representation of business semantics in data warehouse, but many necessary extensions are also needed in the real application.
Abstract: Data warehouse is now widely used in business analysis and decision making processes. To adapt the rapidly changing business environment, we develop a tool to make data warehouses more business-friendly by using Semantic Web technologies. The main idea is to make business semantics explicit by uniformly representing the business metadata (i.e. conceptual enterprise data model and multidimensional model) with an extended OWL language. Then a mapping from the business metadata to the schema of the data warehouse is built. When an analysis request is raised, a customized data mart with data populated from the data warehouse can be automatically generated with the help of this built-in knowledge. This tool, called Enterprise Information Asset Workbench (EIAW), is deployed at the Taikang Life Insurance Company, one of the top five insurance companies of China. User feedback shows that OWL provides an excellent basis for the representation of business semantics in data warehouse, but many necessary extensions are also needed in the real application. The user also deemed this tool very helpful because of its flexibility and speeding up data mart deployment in face of business changes.
51 citations
01 Jan 2007
TL;DR: The definition combines the visual appeal of the graph-based BPMN with the expressive power and simplicity of rule-based modeling and can be applied as well to other business process modeling notations, e.g. UML 2.0 activity diagrams.
Abstract: We define an extensible semantical framework for business process modeling notations. Since our definition starts from scratch, it helps to faithfully link the understanding of business processes by analysts and operators, on the process design and management side, by IT technologists and programmers, on the implementation side, and by users, on the application side. We illustrate the framework by a high-level operational definition of the semantics of the BPMN standard of OMG. The definition combines the visual appeal of the graph-based BPMN with the expressive power and simplicity of rule-based modeling and can be applied as well to other business process modeling notations, e.g. UML 2.0 activity diagrams.
51 citations
IBM1
TL;DR: This work presents here a technique to semi-automatically transform use cases into business processes and to create mapping between them so that one can enforce consistency between the two forms of requirements.
Abstract: Use cases are a key technique to elicit software requirements from the point of view of the user of a system. Their prevalence is noticeable ever since the onset of agile programming techniques. Within SOA projects however, business process models are used for capability analysis and gap detection. Business process models present a global view of the system and hence are more suited for gap detection. Therefore, in practice both these forms of requirements continue to be useful and coexist. Often in big software projects and in distributed development environment such coexisting requirement specifications can grow out of synch. We present here a technique to semi-automatically transform use cases into business processes and to create mapping between them. By preserving the mapping between these forms one can enforce consistency between the two forms of requirements.
51 citations
07 Sep 2009
TL;DR: This paper proposes the embedding of social software features, such as collaboration and wiki-like features, in the modeling and execution tools of business processes, which will foster people empowerment in the bottom-up design and execution ofbusiness processes.
Abstract: In today’s changing environments, organizational design must take into account the fact that business processes are incomplete by nature and that they should be managed in such a way that they do not restrain human intervention. In this paper we propose the embedding of social software features, such as collaboration and wiki-like features, in the modeling and execution tools of business processes. These features will foster people empowerment in the bottom-up design and execution of business processes. We conclude this paper by identifying some research issues about the implementation of the tool and its methodological impact on Business Process Management.
51 citations