Introduction BPMN and Business Process Management
This article was made to fulfill my reading assignment with the Information Systems and Technology course
Name : Mentina Asri
Task Supervisor : Rinda Cahyana, S.T., M.T.
English Version
Introduction to BPMN and BPM
BPMN (Business Process Modeling Notation) is the new standard for modeling business processes and web service processes, developed by the Business Process Management Initiative (BPMI – www.BPMI.org). The primary goal of BPMN is to provide a notation that is readily understandable by all business users, from analysts creating the initial drafts to technical developers responsible for implementing the technology. A crucial secondary goal is ensuring that execution languages like BPEL4WS and BPML can be visually expressed using this common notation.
BPMN is a core enabler for Business Process Management (BPM). BPM focuses on managing change to improve business processes, unifying previously distinct disciplines such as Process Modeling, Simulation, Workflow, Enterprise Application Integration (EAI), and Business-to-Business (B2B) integration into a single standard. BPMI was established to develop standards facilitating BPM, including BPMN, the Business Process Modeling Language (BPML), and the Business Process Query Language (BPQL).
The Business Process Diagram (BPD) and its Elements
BPMN specifies a single diagram called the Business Process Diagram (BPD). The BPD is designed to be both easy to use and understand for non-technical users while providing the expressiveness required to model very complex business processes.
Key elements of the BPD include:
- Events: Events model occurrences that happen in the business, which can either Start a process flow, happen during the course of the flow (Intermediate Event), or End the flow. For complex modeling, events can specify trigger types such as messages, timers, business rules, or exception conditions.
- Processes, Sub-Processes, and Tasks: Processes are graphically depicted by rounded rectangular symbols. A process can be decomposed into hierarchies by attaching a 'child' BPD to it, indicated by a '+' mark. Processes on a child diagram are considered Sub-processes, and the lowest level process that is not further decomposed is called a Task.
- Gateways: Gateways model decision points, merges, forks, and joins in the process flow. A Gateway asks a question that determines the path taken. Types include Exclusive Decisions (XOR), Inclusive Decisions (OR) (where one or more paths may be taken), and Parallel Forking/Joining (AND) (where all flows are taken).
- Pools and Lanes: These elements specify "who does what". A Pool typically represents an organization, and a Lane is a sub-partition within a Pool, often representing a department. Pools are also used to describe B2B processes where different organizations exchange messages. Pools can be modeled as 'Black Boxes' (details hidden, used for external organizations) or 'White Boxes' (details visible, used for in-scope processes).
- Flows:
- Sequence Flow: Shown by a line with a filled-in arrowhead, it models the order of execution within the same Pool or Lane (organization/department).
- Message Flow: Shown by a dashed line, it models the exchange of messages between different Pools (organizations or applications), which is essential for modeling B2B messaging. Data
- Objects: These are optional artifacts (resembling documents) that can be added to the diagram to show how data is transformed during the process. You can specify the state of the data object in brackets below its name.
Technical Foundation and Execution Languages
The BPMI standards, including BPMN, were developed with a solid mathematical foundation based on the Pi-Calculus branch of Process Calculi. This rigor is crucial because it enables business processes designed using BPMN to be mapped directly to executable business execution languages for immediate execution.
- Execution Standards: The Business Process Modeling Language (BPML) was developed by BPMI as the standard execution language. BPEL4WS (Business Process Execution Language For Web Services) is a competing standard. Both BPML and BPEL4WS were submitted to OASIS (a global consortium driving e-business standards) to establish a single standard called Web Services – Business Process Execution Language (WS-BPEL).
- Orchestration: Making web services work is a four-stage process: design (using BPMN), simulation, publishing using an execution language, and finally, orchestration and coordination using a Business Process Management System (BPMS). BPMS's orchestrate participants (applications, people, partners) into executable, end-to-end processes.
BPMN and UML Comparison
BPMN provides several advantages over the Unified Modeling Language (UML) for business process modeling:
- Target Audience and Approach: UML is primarily targeted at system architects and software engineers, using an object-oriented approach that is considered "alien" to most business analysts. BPMN takes a process-centric approach, which is more natural and intuitive for the business analyst.
- Foundation and Implementation: UML lacks a specific execution meta-model and the mathematical foundation required to map directly to business execution languages like BPELs. In contrast, BPMN is explicitly designed to map directly to these languages.
- Co-existence: BPMN and UML are anticipated to co-exist. BPMN can function as a solid business analysis front-end for systems design that subsequently uses UML.
In conclusion, BPMN is positioned to become the new standard due to its ability to easily model both complex typical processes and B2B messaging, combined with its robust technical foundation for direct execution mapping.
Summary English
BPMN provides a clear, shared visual language—like universal sheet music for a complex business orchestra—ensuring that the business vision (the design) translates flawlessly into executable performance (the technological execution).
English Version
BPMN (Business Process Modeling Notation) is a new standard for modeling business processes and web service processes, developed by the Business Process Management Initiative (BPMI). The main goal of BPMN is to provide easy-to-understand notation for all business users, from business analysts who create initial drafts to technical developers responsible for technology implementation.
BPMN is the core enabler of an enterprise architecture initiative called Business Process Management (BPM). BPM focuses on managing changes to improve business processes. BPM brings together previously disparate disciplines, such as Process Modeling, Simulation, Workflow, Enterprise Application Integration (EAI), and Business-to-Business (B2B) integration into a single standard. BPMI was established to develop standards that facilitate BPM, including BPMN, Business Process Modeling Language (BPML), and Business Process Query Language (BPQL).
BPMN Modeling Diagrams and Elements
BPMN specifies a single diagram, called a Business Process Diagram (BPD). BPD is designed to be easy to use and understand by non-technical users, but it also offers the ability to model highly complex business processes.
The main elements of BPD include:
- Events: Events model what happens in a business, which can start (Start Event), occur during (Intermediate Event), or end (End Event) process flow. For more complex modeling, you can specify trigger types, such as messages, timers, business rules, or exception conditions.
- Processes, Sub-Processes, and Tasks: The process is depicted with a rounded edged rectangular symbol. Processes can be decomposed into a child BPD hierarchy (sub-processes), indicated by a '+' sign on the process symbol. The lowest level process that is no longer described is called a Task.
- Gateways: Gates model decision points, mergers, forks, and joins in a process flow, similar to decision symbols in a flowchart. Gateway types include Exclusive (XOR), Inclusive (OR), and Parallel (AND) decisions.
- Pools and Lanes: This element is used to determine "who does what". Pools typically represent organizations, while lanes are sub-partitions within Pools that typically represent departments within the organization. Pools can also represent functions, applications, or locations.
- Sequence Flow and Message Flow:
- Sequence Flow (garis dengan panah terisi) menunjukkan urutan eksekusi proses dalam Pool atau Lane yang sama.
- Message Flow (garis putus-putus) digunakan untuk memodelkan pertukaran pesan antar organisasi atau aplikasi yang berbeda (antara Pool yang berbeda), yang penting untuk proses B2B dan B2C.
Selain itu, BPMN memungkinkan pemodelan Kotak Hitam (Black Boxes) untuk organisasi di luar lingkup yang detail prosesnya tidak ditampilkan, berbeda dengan Kotak Putih (White Boxes) di mana detail prosesnya terlihat. Objek Data (Data Objects) dapat ditambahkan untuk menunjukkan bagaimana data diubah selama proses, meskipun ini opsional.
Fondasi Teknis dan Bahasa Eksekusi
Standar BPMI memiliki fondasi matematis yang kuat (menggunakan cabang Pi-Calculus dari Process Calculi). Fondasi ini sangat penting karena memungkinkan proses bisnis yang dirancang menggunakan standar BPMN dapat dipetakan secara langsung ke bahasa eksekusi bisnis yang dapat dieksekusi, seperti BPML. BPMN juga dirancang untuk memetakan dengan mudah ke bahasa eksekusi pesaing, seperti Business Process Execution Language For Web Services (BPEL4WS).
BPEL4WS (oleh BEA, IBM, Microsoft, dll.) dan BPML (dari BPMI) telah diserahkan ke OASIS, sebuah konsorsium global yang mendorong pengembangan standar e-bisnis, untuk membentuk standar eksekusi proses bisnis bernama Web Services – Business Execution Language (WS-BPEL).
Proses untuk membuat layanan web berfungsi melibatkan empat tahap: desain dengan BPMN, simulasi untuk efisiensi, penerbitan menggunakan bahasa eksekusi, dan orkestrasi menggunakan Business Process Management System (BPMS). BPMS mengorkestrasi peserta (aplikasi, manusia, mitra) menjadi proses end-to-end yang dapat dieksekusi.
Perbandingan BPMN dan UML
BPMN menyediakan sejumlah keunggulan dibandingkan Unified Modeling Language (UML) dalam pemodelan proses bisnis:
- Target Audiens dan Pendekatan: UML ditujukan terutama untuk arsitek sistem dan insinyur perangkat lunak, menggunakan pendekatan berorientasi objek yang dianggap "asing" bagi sebagian besar analis bisnis. Sebaliknya, BPMN mengambil pendekatan yang berpusat pada proses (process-centric), yang lebih intuitif dan alami bagi analis bisnis.
- Fondasi dan Eksekusi: UML tidak memiliki fondasi matematis yang secara eksplisit dirancang untuk memetakan ke bahasa eksekusi proses bisnis (seperti BPEL). BPMN, dengan fondasi matematisnya, dirancang untuk pemetaan langsung ke bahasa eksekusi.
- Kompatibilitas: UML dan BPMN diantisipasi akan hidup berdampingan (co-exist). BPMN dapat digunakan sebagai front-end pemodelan bisnis yang solid untuk pengembangan sistem berikutnya menggunakan UML.
Singkatnya, BPMN siap menjadi standar baru karena kemudahannya dalam memodelkan proses bisnis dan layanan web yang kompleks, serta fondasi teknisnya yang memungkinkan pemetaan langsung ke bahasa eksekusi, yang mendasar bagi pengelolaan dan peningkatan proses bisnis perusahaan.
Ringkasan Indonesia
BPMN adalah seperti cetak biru arsitektur modern untuk bisnis Anda. Bukan hanya menunjukkan denah ruangan (proses), tetapi juga memastikan bahwa denah itu dapat langsung diubah menjadi kode bangunan (bahasa eksekusi) dengan presisi matematis, sehingga pembangun (BPMS) dapat secara otomatis mengendalikan aliran kerja di seluruh properti (organisasi).
Komentar
Posting Komentar