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. New Approaches of Developing Information SystemsThere are two fundamental ways of (re-)engineering information systems. The "formal driven" approach is based on the goal of developing and implementing a technical correct running system. The "content driven" approach is based on the goal of developing and implementing an organizational correct running system. By using reference models, content and technology can be combined in a new way.The content driven approach starts with the design of the strategic business opportunities and the organizational requirements. The resulting models are the basis for an iterative business improvement and technological implementation. The content driven approach can be structured as a layer model and described in an architectural framework for business process management. Reference models as "blue prints" for business engineering can be used to model and optimize business processes.The term "business process" is defined universally. A business process is described as a procedure relevant for adding value to an organization. It is viewed in its entirety, from beginning to end. Figure 1 illustrates the business process of order entry processing. The initial requirements of the customer lead to order acceptance by the manufacturer's Sales department. Sales then relays information to Purchasing, in order for them to supply bought-in parts. Finally, Production plans and executes the work-order.

No abstract

This article presents an XML-based interchange format for eventdriven process chains (EPC) that is called EPC markup language (EPML). EPML builds on EPC syntax related work and is tailored to be a serialization format for EPC modelling tools. Design principles inspired by other standardization efforts and XML design guidelines have governed the specification of EPML. After giving an overview of EPML concepts we present examples to illustrate its features including flat and hierarchical EPCs, business views, graphical information, and syntactical correctness.

No abstract

No abstract