1 / 32

CSS 496 Business Process Re-engineering for BS(CS)

CSS 496 Business Process Re-engineering for BS(CS). Chapter 4: Business Process Modeling Notations Khurram Shahzad mks@ciitlahore.edu.pk Based on Petia, Marlon, Aalst and Weske Lectures. Business Process Modeling Notation.

channer
Télécharger la présentation

CSS 496 Business Process Re-engineering for BS(CS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSS 496 Business Process Re-engineering for BS(CS) Chapter 4: Business Process Modeling Notations Khurram Shahzad mks@ciitlahore.edu.pk Based on Petia, Marlon, Aalst and Weske Lectures

  2. Business Process Modeling Notation • Business Process Modeling Notation, developed under the coordination of Object Management Group. • Benefits • Combines best practices of existing approaches • Readily undersandable by all business users • Users can use it without extensive training

  3. BPMN Elements

  4. More Elements OR AND XOR Events Gateways

  5. Principles • Process model starts with an event • Whenever the conditions of a gateway are designed so that always all outgoing edges are activated, the gateway should be marked with the + symbol to indicate the and split semantics of the gateway. • Continue… as patterns

  6. Example 1

  7. Example 2

  8. Possible States

  9. Patterns (Sequence and loop pattern)

  10. Patterns (AND Split)

  11. Patterns (AND Split)

  12. Patterns (XOR Split and Join)

  13. Patterns (XOR Split and Join)

  14. Patterns (OR Split)

  15. Patterns (OR Join)

  16. Example (OR Join)

  17. Patterns (Multiple Merge)

  18. Interacting Processes • Process involving multiple organizational entities can interact with each other • BPMN is not restricted to single organization processes • Ready to express interacting processes of multiple organizations • Swimlanes are used to assign processes/parts to organizational entities • Pools represent specific process participants • business entity role like supplier and customer

  19. Pools • Pools represent business process participants. They are used to partition a set of activities. • Can be a business entity or abusiness role. • Sequence flows cannot cross the boundaries of a Pool. • Interaction between Pools are captured through Message Flow (dashed lines with an arrow)

  20. Interacting Processes • Sequence flow is allowed only between nodes in a single pool • Communication occurs through message flows

  21. Categories of business processes • BPMN support three categories of processes • Private Business Processes • Public Business Processes • Global Business Processes

  22. Private Business Processes • Contains only activities that are enacted within a company • All activities that contribute to process are represented

  23. Public Business Processes • Represent only activities that communicate with other business processes • Externally visible behavior of processes

  24. Global Business Processes • Global view on internals of all other parties

  25. Sub-processes • A task in a process can be decomposed into a “sub-process”. • Use this feature to: • Break down large models into smaller ones, making them easier to understand and to explain

  26. Sub-processes

  27. Sub-processes: example

  28. Example: Publishing Article

  29. Example

  30. Assignment 1

  31. BPMN Exercise 1:Claims Notification process at a car insurer When a claim is received, it is first checked whether the claimant is insured by the organization. If not, the claimant is informed that the claim must be rejected. Otherwise, the severity of the claim is evaluated. Based on the outcome (simple or complex claims), relevant forms are sent to the claimant. Once the forms are returned, they are checked for completeness. If the forms provide all relevant details, the claim is registered in the Claims Management system, which ends the Claims Notification process. Otherwise, the claimant is informed to update the forms. Upon reception of the updated forms, they are checked again.

  32. BPMN Exercise 2 When a claim related to a major car accident is evaluated, a clerk first retrieves the corresponding car accident report in the Police Reports database. If the report is retrieved, it is attached to the claim file. The claim file and the police report serve as input to a claims handler who calculates an initial claim estimate. Then, an “action plan” is created based on a “checklist”. Based on the action plan and the initial claims estimate, a claims manager negotiates a settlement with the customer. After this negotiation, the claims manager makes a final decision, updates the claim file to record this decision, and sends a letter to the claimant to inform him/her of the decision.

More Related