Information system development by business process modeling based on adaptability to specification changes

2010 ◽  
Vol 174 (2) ◽  
pp. 54-64
Author(s):  
Tsutomu Okawa ◽  
Syuichi Hirabayashi ◽  
Tsukasa Kaminishi ◽  
Hisao Koizumi
Author(s):  
Azeem Lodhi ◽  
Veit Küppen ◽  
Gunter Saake

An Extension of BPMN Meta-model for Evaluation of Business ProcessesBusiness process modeling is used for better understanding and communication of company's processes. Mostly, business process modeling is discussed from the information system development perspective. Execution of a business process involves various factors (costs and time) which are important and should be represented in business process models. Controlling of business units uses post execution analysis for detection of failures for improvement. The process models conceived for information system development are not sufficient for post execution analysis. This paper focuses on the challenges of business process modeling in the post execution context. We provide a meta model for evaluation of a business process and discuss BPMN in this context. We also extend existing BPMN meta model for performance analysis of business processes. The proposed extensions are presented with the help of an example.


2004 ◽  
Vol 13 (03) ◽  
pp. 289-332 ◽  
Author(s):  
JULIANE DEHNERT ◽  
WIL M. P. VAN DER AALST

This paper presents a methodology to bridge the gap between business process modeling and workflow specification. While the first is concerned with intuitive descriptions that are mainly used for communication, the second is concerned with configuring a process-aware information system, thus requiring a more rigorous language less suitable for communication. Unlike existing approaches the gap is not bridged by providing formal semantics for an informal language. Instead it is assumed that the desired behavior is just a subset of the full behavior obtained using a liberal interpretation of the informal business process modeling language. Using a new correctness criterion (relaxed soundness), it is verified whether a selection of suitable behavior is possible. The methodology consists of five steps and is illustrated using event-driven process chains as a business process modeling language and Petri nets as the workflow specification language.


Author(s):  
Tony Elliman ◽  
Tally Hatzakis ◽  
Alan Serrano

This chapter discusses the idea that even though information systems development (ISD) approaches have long advocated the use of integrated organisational views, the modelling techniques used have not been adapted accordingly and remain focused on the automated information system (IS) solution. Existing research provides evidence that business process simulation (BPS) can be used at different points in the ISD process to provide better-integrated organisational views that aid the design of appropriate IS solutions. Despite this fact, research in this area is not extensive; suggesting that the potential of using BPS for the ISD process is not yet well understood. The paper uses the findings from three different case studies to illustrate the ways BPS has been used at different points in the ISD process, especially in the area of requirements engineering. It compares the results against IS modelling techniques, highlighting the advantages and disadvantages that BPS has over the latter. The research necessary to develop appropriate BPS tools and give guidance on their use in the ISD process is discussed.


Author(s):  
Liu Shuzhou ◽  
Angela Goh Eck Soong

A workflow methodology is required to analyze business logic and model workflow components. Current studies handle business process modeling and workflow modeling in an independent manner, making it hard to analyze the information system and organization requirements while modeling business logic. Moreover, current methodologies also lack support for modeling complex dynamic processes in adaptive workflows. In this chapter, a methodology is proposed to unify business process modeling and workflow automation. The information system and organization perspectives of workflow are identified in each development phase. An analysis of the domain and an object notation in the methodology can help to build a stable system.


Sign in / Sign up

Export Citation Format

Share Document