A Rule-Based Approach to Model Business Process

2013 ◽  
pp. 424-441
Author(s):  
Gang Xue ◽  
Zhongwei Wu ◽  
Kun Zhang ◽  
Shaowen Yao
Keyword(s):  
Flow Control ◽  
Business Process ◽  
Process Modeling ◽  
Business Process Modeling ◽  
Process Models ◽  
Business Rules ◽  
Rule Based ◽  
Plain Text ◽  
Business Process Models ◽  
Rule Based Approach

Up to the present, the modeling of business process manly focuses on the flow-control perspective, regardless of the logic relationships between models. Although the value of business rules in business process modeling has been recognized by many organizations, it is not fully clear how business rules can be used to model business process models. Business rules are powerful representation forms that can potentially define the semantics of business process models and business vocabulary. This chapter is committed to model the business process based on SBVR, then use the method mentioned below to transform a plain text rule statement into BPMN files.

A Method for Eliciting Goals for Business Process Models based on Non-Functional Requirements Catalogues

2013 ◽  
pp. 226-244 ◽  
Author(s):  
Evellin Cardoso ◽  
João Paulo A. Almeida ◽  
Renata S. S. Guizzardi ◽  
Giancarlo Guizzardi
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Business Process Modeling ◽  
Process Models ◽  
Functional Requirements ◽  
Business Process Models ◽  
Traditional Approaches ◽  
Goal Models

While traditional approaches in business process modeling tend to focus on “how” the business processes are performed (adopting a behavioral description in which business processes are described in terms of procedural aspects), in goal-oriented business process modeling, the proposals strive to extend traditional business process methodologies by providing a dimension of intentionality to business processes. One of the key difficulties in enabling one to model goal-oriented processes concerns the identification or elicitation of goals. This paper reports on a case study conducted in a Brazilian hospital, which obtained several goal models represented in i*/Tropos, each of which correspond to a business process also modeled in the scope of the study. NFR catalogues were helpful in goal elicitation, uncovering goals that did not come up during previous interviews prior to these catalogues’ use.

scholarly journals Plug-in for Annotating Semantic Efferct on BPMN Business Process Models

2019 ◽  
Vol 4 (2) ◽  
pp. 116
Author(s):  
Hilman Nuril Hadi ◽  
Tri Astoto Kurniawan ◽  
Ismiarta Aknuranda
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Process Model ◽  
Business Process Modeling ◽  
Process Models ◽  
Business Process Model ◽  
Activity Type ◽  
Modeling Tools ◽  
Business Process Models ◽  
Design Time

BPMN has become the standard of business process modeling indescribing the existing series of business process. By engaging BPMN, an analystwould possibly able to model the whole business process activities in whichhe/she may analyze business process upon design time. It can be done byanalyzing the structure, behavior, or semantic of process model. In certaincondition one may ask a question what would the effects of the process be if itwere to be executed up to this point?. However, it cannot be solved with onlygraphical notation, but with its semantics. In practice, several modeling tools stilldo not provide a feature for managing information regarding the effects/resultsin the business process model. In fact, analysts should be supported with a toolin order to semantically enrich a process model with its effects. This articledescribes effect annotation semantically towards activity in the BPMN modelincluding the rules in representing its effects. The effect annotation will be suitedtowards activity type (atomic and compound activities). The outcomes of plugin development of eclipse BPMN2 modeler for representing semantic effect arealso described in this paper.

Software Engineering Security Based on Business Process Modeling

2012 ◽  
pp. 52-68
Author(s):  
Joseph Barjis
Keyword(s):  
Business Process ◽  
Software Design ◽  
Process Modeling ◽  
Business Process Modeling ◽  
Process Models ◽  
Security Requirements ◽  
Business Process Models ◽  
Security Breaches ◽  
Organizational Semiotics ◽  
Enterprise Ontology

Security requirements must be tackled early in software design and embedded in corresponding business process models. As a blueprint for software design, business process models complemented with security requirements will prevent many security breaches. To accomplish secure business process modeling, the underlying method must adhere to certain capabilities and capture actions, actor roles, and interactions. The resultant models should lend themselves to automatic analysis (simulation) to ensure captured security requirements are correctly aligned with the process flow. Thus, the tradeoff between the level of security and business performance can be studied before actual software design. Since unauthorized actions cause security breaches, the software the system’s social setting could be a cradle for defining security requirements. Security requirements can be identified based on the roles, authorities, and obligations of the social actors using the system. This paper introduces a method for security embedded business process modeling. The proposed method draws on two well-tested theoretical foundations—enterprise ontology and organizational semiotics.

scholarly journals Common Process Extraction pada Model Proses Bisnis Tebang Muat Angkut (TMA)

2020 ◽  
Vol 7 (2) ◽  
pp. 71-76
Author(s):  
Salma Fatia ◽  
Muhammad Ainul Yaqin ◽  
Adi Heru Utomo
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Process Model ◽  
Structural Similarity ◽  
Business Process Modeling ◽  
Process Models ◽  
Business Process Models ◽  
Common Fragment ◽  
Behavioral Similarity ◽  
Business Process Modeling Notation

Abstract— In an organizational environment, there are various business process models with the same procedures. If an organization builds a system with the same procedure repeatedly, it will undoubtedly incur a lot of effort and money. Therefore, it is necessary to extract common fragments to save effort. This research uses four scenarios of business process models: sequence, branching, nested branching, and looping. This study uses Business Process Modeling Notation (BPMN) notation so that the process model consists of activities, connectors, and gateways. Structural similarity is measured using the Jaccard similarity formula by comparing the process model. The similarity of behavior is measured using the Transition Adjacency Relations (TARs) method to obtain common fragments. The results show that the sequence process model will produce a common fragment that tends to be sequential too. The branching will produce a common fragment that tends to branch, and nested branching will produce a common fragment that tends to be branched and nested, as well as looping will produce a common fragment contains looping too. The experimental results show that the proposed method can extract common fragments based on the available business process models. Keywords—BPMN; common fragment; behavioral similarity; TARs   Abstrak— Dalam lingkungan organisasi, terdapat berbagai model proses bisnis dengan prosedur yang sama. Jika suatu organisasi membangun sistem dengan prosedur yang sama secara berulang-ulang, niscaya akan mengeluarkan banyak tenaga dan biaya. Oleh karena itu, perlu mengekstrak fragmen umum untuk menghemat tenaga. Penelitian ini menggunakan empat skenario model proses bisnis yaitu sequence, branching, nested branching, dan looping. Penelitian ini menggunakan notasi Business Process Modeling Notation (BPMN) sehingga model proses terdiri dari aktivitas, konektor, dan gateway. Kemiripan struktural diukur menggunakan rumus kemiripan Jaccard dengan membandingkan model proses. Kesamaan perilaku diukur menggunakan metode Transition Adjacency Relations (TARs) untuk mendapatkan fragmen yang sama. Hasil penelitian menunjukkan bahwa model sequence process akan menghasilkan common fragment yang cenderung berurutan juga. Percabangan akan menghasilkan fragmen umum yang cenderung bercabang, dan percabangan bersarang akan menghasilkan fragmen umum yang cenderung bercabang dan bersarang, serta perulangan akan menghasilkan fragmen umum yang berisi perulangan juga. Hasil eksperimen menunjukkan bahwa metode yang diusulkan dapat mengekstrak fragmen umum berdasarkan model proses bisnis yang tersedia. Keywords—BPMN; common fragment; kemiripan perilaku; TARs

scholarly journals Spreadsheets as Interoperability Solution for Business Process Representation

2019 ◽  
Vol 9 (2) ◽  
pp. 345 ◽  
Author(s):  
Piotr Wiśniewski ◽  
Krzysztof Kluza ◽  
Edyta Kucharska ◽  
Antoni Ligęza
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Process Model ◽  
Business Process Modeling ◽  
Process Models ◽  
The Other ◽  
Business Process Models ◽  
Task List ◽  
Process Representation ◽  
A Company

Business process models help to visualize processes of an organization. In enterprises, these processes are often specified in internal regulations, resolutions or other law acts of a company. Such descriptions, like task lists, have mostly form of enumerated lists or spreadsheets. In this paper, we present a mapping of process model elements into a spreadsheet representation. As a process model can be represented in various notations, this can be seen as an interoperability solution for process knowledge interchange between different representations. In presenting the details of the solution, we focus on the popular BPMN representation, which is a de facto standard for business process modeling. We present a method how to generate a BPMN process model from a spreadsheet-based representation. In contrast to the other existing approaches concerning spreadsheets, our method does not require explicit specification of gateways in the spreadsheet, but it takes advantage of nested list form. Such a spreadsheet can be created either manually or merged from the task list specifications provided by users.

Business Alignment Methodology

2014 ◽  
Vol 27 (1) ◽  
pp. 1-20 ◽  
Author(s):  
Marielba Zacarias ◽  
Paula Ventura Martins
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Business Process Modeling ◽  
Two Dimensions ◽  
Process Models ◽  
Work Practices ◽  
Organizational Setting ◽  
Business Process Models ◽  
Business Alignment

Current business process modeling methodologies offer little guidance regarding how to discover and maintain business process models aligned with their actual execution. This paper describes how to achieve this goal by uncovering, supervising and improving business process models based on actual work practices, using the Business Alignment Methodology (BAM). BAM aims at enabling business process modeling, supervision and improvement through the distinction of two dimensions; (1) business processes and (2) work practices. BAM encompasses three phases; (1) Business Process Discovery, (2) Business Process Supervision and (3) Business Process Assessment and Improvement. This paper illustrates the business discovery phase of BAM with a case study in a real organizational setting.

Towards semantically-aided domain specific business process modeling

2018 ◽  
Vol 52 (4) ◽  
pp. 463-481 ◽  
Author(s):  
Nikolaos Lagos ◽  
Adrian Mos ◽  
Mario Cortes-cornax
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Process Modeling ◽  
Process Models ◽  
Data Governance ◽  
Content Type ◽  
Specific Process ◽  
Business Process Models ◽  
Domain Specific ◽  
The Impact

Purpose Domain-specific process modeling has been proposed in the literature as a solution to several problems in business process management. The problems arise when using only the generic Business Process Model and Notation (BPMN) standard for modeling. This language includes domain ambiguity and difficult long-term model evolution. Domain-specific modeling involves developing concept definitions, domain-specific processes and eventually industry-standard BPMN models. This entails a multi-layered modeling approach, where any of these artifacts can be modified by various stakeholders and changes done by one person may influence models used by others. There is therefore a need for tool support to keep track of changes done and their potential impacts. The paper aims to discuss these issues. Design/methodology/approach The authors use a multi-context systems-based approach to infer the impacts that changes may cause in the models; and alsothe authors incrementally map components of business process models to ontologies. Findings Advantages of the framework include: identifying conflicts/inconsistencies across different business modeling layers; expressing rich information on the relations between two layers; calculating the impact of changes taking place in one layer to the rest of the layers; and selecting incrementally the most appropriate semantic models on which the transformations can be based. Research limitations/implications The authors consider this work as one of the foundational bricks that will enable further advances toward the governance of multi-layer business process modeling systems. Extensive usability tests would enable to further confirm the findings of the paper. Practical implications The approach described here should improve the maintainability, reuse and clarity of business process models and in extension improve data governance in large organizations. The approaches described here should improve the maintainability, reuse and clarity of business process models. This can improve data governance in large organizations and for large collections of processes by aiding various stakeholders to understand problems with process evolutions, changes and inconsistencies with business goals. Originality/value This paper fulfills an identified gap to enabling semantically aided domain–specific process modeling.

scholarly journals Gesture-Based Process Modeling Using Multi-Touch Devices

2013 ◽  
Vol 4 (4) ◽  
pp. 48-69 ◽  
Author(s):  
Jens Kolb ◽  
Benjamin Rudner ◽  
Manfred Reichert
Keyword(s):  
Business Process ◽  
User Interfaces ◽  
Process Modeling ◽  
Business Process Modeling ◽  
Process Models ◽  
Modeling Tools ◽  
Business Process Models ◽  
Desktop Computers ◽  
Touch Devices ◽  
Collaborative Business Process

Contemporary business process modeling tools provide menu-based user interfaces for defining and visualizing process models. Such menu-based interactions have been optimized for applications running on desktop computers, but are limited regarding their use on multi-touch devices. At the same time, the widespread use of mobile devices in daily business life as well as their multi-touch capabilities offer promising perspectives for intuitively defining and changing business process models. Additionally, multi-touch tables will foster collaborative business process modeling based on natural as well as intuitive gestures and interactions. This paper presents the results of an experiment that investigated the way users define and change business process models using multi-touch devices. Based on experiment results, a core gesture set is designed enabling the easy definition and change of business process models with multi-touch devices. Finally, a proof-of-concept implementation of this core gesture set is presented. Overall, gesture-based process modeling and multi-touch devices will foster new ways of (collaborative) business process modeling.

Software Engineering Security Based on Business Process Modeling

2010 ◽  
Vol 1 (2) ◽  
pp. 1-17
Author(s):  
Joseph Barjis
Keyword(s):  
Business Process ◽  
Software Design ◽  
Process Modeling ◽  
Business Performance ◽  
Business Process Modeling ◽  
Process Models ◽  
Security Requirements ◽  
Business Process Models ◽  
Security Breaches ◽  
Enterprise Ontology

Security requirements must be tackled early in software design and embedded in corresponding business process models. As a blueprint for software design, business process models complemented with security requirements will prevent many security breaches. To accomplish secure business process modeling, the underlying method must adhere to certain capabilities and capture actions, actor roles, and interactions. The resultant models should lend themselves to automatic analysis (simulation) to ensure captured security requirements are correctly aligned with the process flow. Thus, the tradeoff between the level of security and business performance can be studied before actual software design. Since unauthorized actions cause security breaches, the software the system’s social setting could be a cradle for defining security requirements. Security requirements can be identified based on the roles, authorities, and obligations of the social actors using the system. This paper introduces a method for security embedded business process modeling. The proposed method draws on two well-tested theoretical foundations—enterprise ontology and organizational semiotics.

Sign in / Sign up

Export Citation Format

Share Document