Introduction to Business Process Modeling

Transcription

1 10/9/2015 Introduction to Business Process Modeling Software Engineering and Databases Group Department of Computer Languages and Systems University of Seville October 2015 La traducción de este material docente ha sido financiada mediante la convocatoria 1.10B - Ayudas de innovación y mejora docente, convocatoria , modalidad B del II Plan Propio de Docencia de la Universidad de Sevilla. No ha habido financiación alguna para este proyecto de otros soportes. Learning objectives 1. Why Understand the need for modeling processes during the process of information systems development. Know BPMN as a graphical to model processes. Develop simple processes models using BPMN. October 2015 Requirements Engineering 1 IISSI / RE 1

2 10/9/2015 Why modeling 1. Why Information systems should help their organizations to Make competitiveness strategic decisions. Make tactical decisions. Perform processes and their related operations. Most information systems developments are operational-level oriented. processes October 2015 Requirements Engineering 2 Why modeling 1. Why Designing an information system without knowing customers organization operations ( processes) is a recipe for failure. A technically correct product can be developed, but it will not succeed because of being useless for their users. October 2015 Requirements Engineering 3 IISSI / RE 2

3 10/9/2015 Why modeling 1. Why Tell me how your works and I will make you a proposal to put it on the Web Customer I need more sales, the crisis is killing me! Requirements engineer / analyst October 2015 Requirements Engineering 4 How to model Textually: description in natural language. 1. Why Diagrammatically: description through a diagram EPC diagrams (event-driven process chain) UML activity diagrams BPMN diagrams (Business Process Modeling Notation) The most recommended practice is to combine both types of descriptions, complementing the diagrams with textual descriptions. October 2015 Requirements Engineering 5 IISSI / RE 3

4 10/9/2015 Manager Librarian User 1. Why How to model EPC diagram example October 2015 Requirements Engineering 6 How to model UML activity diagram example 1. Why Register new book Library Stock Management Remove book [book OK ] Register loan Register return [book KO ] Read book October 2015 Requirements Engineering 7 IISSI / RE 4

5 10/9/2015 BPMN examples: private process 1. Why October 2015 Requirements Engineering 8 BPMN examples: collaboration (I) 1. Why October 2015 Requirements Engineering 9 IISSI / RE 5

6 10/9/2015 BPMN examples: collaboration (II) 1. Why October 2015 Requirements Engineering 10 BPMN examples: the pizza collaboration* 1. Why * Source: BPMN 2.0 by Example October 2015 Requirements Engineering 11 IISSI / RE 6

7 10/9/ Why Task: any activity which is performed during a process. October 2015 Requirements Engineering 12 Task: different types of tasks in BPMN. 1. Why Manual Manual: performed by a person without using any software system. E.g. a telephone technician installing a telephone at a customer location User User: performed by a person using a software system. Usually scheduled through a task list manager. E.g. a phone operator updates a customer record. October 2015 Requirements Engineering 13 IISSI / RE 7

8 10/9/2015 Task: different types of tasks in BPMN. 1. Why Service Receive Service: performed automatically by a software system. E.g. calculate payroll. Receive: it waits until a message from an external participant arrives. Equivalent to Send Send: it sends a message to an external participant. Equivalent to October 2015 Requirements Engineering Why Flow: it indicates the order in which the tasks must be performed. October 2015 Requirements Engineering 15 IISSI / RE 8

9 10/9/ Why Gateway: it represents a fork or a join in the task flow. October 2015 Requirements Engineering 16 Gateway: basic gateway types in BPMN. 1. Why Exclusive gateway: task flow can only take only one of several possible ways. Parallel gateway: task flow takes all possible paths. October 2015 Requirements Engineering 17 IISSI / RE 9

10 10/9/ Why Events: they represent the start of a process, its ending, and other type of events. October 2015 Requirements Engineering Why Pools and swimlanes: they represent the process organization and the roles performing the tasks. October 2015 Requirements Engineering 19 IISSI / RE 10

11 10/9/ Why Pools and swimlanes: they represent the process organization and the roles performing the tasks. October 2015 Requirements Engineering 20 Basic BPMN elements 1. Why Data objects: information flowing through the process, e.g. documents. October 2015 Requirements Engineering 21 IISSI / RE 11

12 10/9/2015 Basic BPMN elements 1. Why Message flows: they represent communication between two organizations (pools). October 2015 Requirements Engineering 22 Basic BPMN elements 1. Why Message flows: they represent communication between two organizations (pools). Receiving and sending messages can be represented through message events. October 2015 Requirements Engineering 23 IISSI / RE 12

13 10/9/2015 Basic BPMN elements 1. Why Message flows: they represent communication between two organizations (pools). Receiving and sending messages can be represented through message events. October 2015 Requirements Engineering 24 Basic BPMN elements 1. Why Temporal events: the most used together with message events. BPMN Ejemplos BPMN Preparar solicitud Fin de plazo Entregar solicitud en registro Task does not end until the temporal event is generated If the temporal event fires before the task is finished, it is interrupted Solicitar prórroga BPMN Ejemplos BPMN Tarea 1 2 días Tarea 2 Task 2 starts two days after Task 1 ends. October 2015 Requirements Engineering 25 IISSI / RE 13

14 10/9/ Why Basic BPMN elements Conditional events: they are usually associated with rules. BPMN Ejemplos BPMN Sancionado Solicitar préstamo libro Más de 3 libros prestados Procesar préstamo Denegar préstamo October 2015 Requirements Engineering Why Basic BPMN elements Event gateways: they select an output flow depending on which event happens first. October 2015 Requirements Engineering 27 IISSI / RE 14

15 10/9/2015 Basic BPMN elements Sub-processes: tasks which contain 1. Why another process. Connectors: they allow the flow to continue elsewhere in the diagram. Comments: they add information to any element in the diagram BPMN Ejemplos BPMN BPMN Ejemplos BPMN Conector 1 Conector 1 Preparar solicitud Fin de plazo Entregar solicitud en registro El registro abre de 9 a 14 y de 16 a 18 de L a V. Debe hacerse directamente al rector. Solicitar prórroga October 2015 Requirements Engineering 28 Bibliography 1. Why B. Silver, BPMN Method & Style (2 nd edition) OMG, BPMN 2.0 by Example. October 2015 Requirements Engineering 29 IISSI / RE 15

16 10/9/2015 Comments, suggestions, 1. Why October 2015 Requirements Engineering 30 IISSI / RE 16