We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byMarley Matt
Modified over 2 years ago
Business Process Modelling - 12.2/2013 - Marcello La Rosa Queensland University of Technology Brisbane, 17 October 2013
© INB/INN320 12.2/2013 – 17 October 2013 Quick Repeat from Week 11 What is process identification? Why is it important to conduct process identification properly? What is a process architecture? What are the typical artifacts of a process hierarchy?
© INB/INN320 12.2/2013 – 17 October 2013 BPM Lifecycle
© INB/INN320 12.2/2013 – 17 October 2013 Process Discovery 1.Defining the setting: assemble a team in a company that will be responsible for working on the process. 2.Gathering information: build an understanding of the process. Different discovery methods can be used to acquire information on a process. 3.Conducting the modeling task: organize the creation of the process model. The modeling methodology gives guidance for mapping out the process in a systematic way. 4.Assuring process model quality: guarantee that the resulting process model meets different quality criteria. This phase is important for establishing trust in the process model.
© INB/INN320 12.2/2013 – 17 October 2013 Who is involved? Domain ExpertProcess Analyst
© INB/INN320 12.2/2013 – 17 October 2013 Challenge 1: Fragmented Process Knowledge Why can‘t I directly provide cash after approval? We bundle refinancing to get better interest rates. I make a photocopy before handing over the application Iterative validation process
© INB/INN320 12.2/2013 – 17 October 2013 Challenge 2: Domain Experts think on Instance Level “Every trip is different” “You cannot really compare. Our customers go to different places in different seasons using different modes of transportation” “We can never do anything exactly in the same way. There are so many special conditions” Abstraction from instance level to process level
© INB/INN320 12.2/2013 – 17 October 2013 Challenge 3: Knowledge of Process Modelling is uncommon “Could you please tell me, whether this diagram correctly shows your process?” Translation to natural-language
© INB/INN320 12.2/2013 – 17 October 2013 What Makes a Good Process Analyst Getting the right people on board Formulate and test hypotheses Identify patterns Pay attention to model aesthetics
© INB/INN320 12.2/2013 – 17 October 2013 Process Discovery Methods Evidence-based –Document analysis –Observation –Automatic process discovery Interview-based Workshop-based 10
© INB/INN320 12.2/2013 – 17 October 2013 Document Analysis Documents point to existing roles, activities and business objects: –Process descriptions (ideal scenario) –Internal policies –Organization charts –Employment plans –Quality certificate reports –Glossaries and handbooks –Forms –Work instructions May not be process-oriented and trustworthy. Could be used to gather information before approaching domain experts. 11
© INB/INN320 12.2/2013 – 17 October 2013 Observation Follow directly the processing of individual cases: –Active role: play a specific role, e.g. customer –Passive role: observe participants and their environment Trace business objects in the course of their lifecycle Active role: no big picture Passive role: participants’ bias 12
© INB/INN320 12.2/2013 – 17 October 2013 Automated discovery via Process Mining 13 model / event log event stream DB extract model Discovery Conformance
© INB/INN320 12.2/2013 – 17 October 2013 Interviews Interview ModellingValidation Verification 14 Forward vs. backward Structured vs. unstructured Assumption: analyst and stakeholder share terminology Pitfall: exceptional behavior neglected > use questions that aim to identify such behavior
© INB/INN320 12.2/2013 – 17 October 2013 Workshops Gather all key stakeholders together Participants interact to create shared understanding Typically one process analyst (facilitator), multiple domain experts, process owner may also attend May be software-supported, a model is directly created during the workshop (typically a separate role – tool operator) Model is used as reference point for discussions Alternative: brown-paper workshops Usually 3 to 5 half-day sessions
© INB/INN320 12.2/2013 – 17 October 2013 Any Difference in Discovery? Consider the following two companies: Company A is young, founded three years ago, and has grown rapidly to a current toll of one hundred employees. Company B is owned by the state and operates in a domain with extensive health and security regulations. How might these different characteristics influence a workshop-based discovery approach?
© INB/INN320 12.2/2013 – 17 October 2013 Discovery and Culture Before starting with process discovery, it is important to understand the culture and the sentiment of an organization. There are companies that preach and practice an open culture in which all employees are encouraged to utter their ideas and their criticism. Such organizations can benefit a lot from workshops as participants are likely to present their ideas freely. In strictly hierarchical organizations, it is necessary to take special care that every participant gets an equal share of parole in a workshop and that ideas and critique are not held back. It might be the case that the young dynamic company has a more open culture than the company with extensive health and security regulations. This has to be taken into account when organizing a workshop.
© INB/INN320 12.2/2013 – 17 October 2013 Strengths and Weaknesses TechniqueStrengthWeakness Document AnalysisStructured information Independent from availability of stakeholders Outdated material Wrong level of abstraction ObservationContext-rich insight into process Potentially intrusive Stakeholders likely to behave differently Only few cases Automatic DiscoveryExtensive set of cases Objective data Potential issue with data quality InterviewDetailed inquiry into process Requires sparse time of process stakeholders Several iterations required before sign-off WorkshopDirect resolution of conflicting views Requires availability of several stakeholders at the same time
© INB/INN320 12.2/2013 – 17 October 2013 Effort of Process Discovery Consider the order-to-cash process of your favorite online book retailer has ten major activities that are conducted by different persons. How much time do you approximately need for creating a process model that is validated and approved by the process owner? Make appropriate assumptions.
© INB/INN320 12.2/2013 – 17 October 2013 Process Discovery Effort This process contains ten major activities that are executed by different persons. We can assume that there will be a kickoff meeting with the process owner and some important domain experts on day one. 1 day might be required to study the available documentation. An interview with one domain expert can take 2-3 hours, so we would be able to meet two persons per day, and document the interview results at nighttime (yes, at nighttime). Let us assume that we meet some persons only once while we seek feedback from important domain experts in 2 additional interviews. Then, there would be a final approval from the process owner. This adds up to 1 day for the kickoff, 1 for studying the documentation, 5 days for the first iteration interviews, and further 5 days if we assume that we meet 5 experts 3 times. Then, we need 1 day for preparing the meeting for final approval with the process owner, which would be on the following day. If there are no delays and scheduling problems, this yields 2 + 5 + 5 + 2 = 14 days of work as a minimum.
© INB/INN320 12.2/2013 – 17 October 2013 Organizing the Gathered Material 1.Identify the process boundaries 2.Identify activities and events 3.Identify resources and their handovers 4.Identify the control flow 5.Identify additional elements
© INB/INN320 12.2/2013 – 17 October 2013 Process Boundaries Under which condition does the process start? With which result does it end? Which perspective do we assume? What data are required as input and output to the process?
© INB/INN320 12.2/2013 – 17 October 2013 Identify Activities and Events
© INB/INN320 12.2/2013 – 17 October 2013 Identify Resources and Handovers
© INB/INN320 12.2/2013 – 17 October 2013 Identify Control Flow
© INB/INN320 12.2/2013 – 17 October 2013 Process Modelling Quality Assurance Validity Completeness Structural correctness Behavioral correctness Understandibility Mantainability
© INB/INN320 12.2/2013 – 17 October 2013 Is this process model of good quality? Deadlock
© INB/INN320 12.2/2013 – 17 October 2013 Syntactic Quality: Verification
© INB/INN320 12.2/2013 – 17 October 2013 Is this process model of good quality? Deadlock Labeling
© INB/INN320 12.2/2013 – 17 October 2013 Formulate Labels Adequately Activities as Verb-Object Events as Object-Past-Participle Verb Conditions with reference to Object
© INB/INN320 12.2/2013 – 17 October 2013 Semantic Quality: Validation Validity Completeness Domain ExpertProcess Analyst
© INB/INN320 12.2/2013 – 17 October 2013 Pragmatic Quality – Example: Layout Better layout helps understanding
© INB/INN320 12.2/2013 – 17 October 2013 Seven Process Modeling Guidelines (7PMG) G1 Use as few elements in the model as possible G2 Minimize the routing paths per element G3 Use one start and one end event G4 Model as structured as possible G5 Avoid, where possible, OR routing elements G6 Use verb-object activity labels G7 Decompose a model with more than 30 elements
© INB/INN320 12.2/2013 – 17 October 2013 Example: explain which 7PMG guidelines point to potential for improvement. Remodel the process based on your observations.
© INB/INN320 12.2/2013 – 17 October 2013 Solution
© INB/INN320 12.2/2013 – 17 October 2013 Process Discovery - Summary Domain expert and process analyst have different strengths and limitations in process discovery There are various discovery methods Quality Assurance is important
© INB/INN320 12.2/2013 – 17 October 2013 References Required Chapter 5 of textbook “Fundamentals of BPM” Recommended M. Rosemann, “Potential pitfalls of process modeling: Part A”. Bus. Process. Manag. J. 12(2), 249–254 (2006) M. Rosemann, “Potential pitfalls of process modeling: Part B”. Bus. Process. Manag. J. 12(3), 377–384 (2006) J. Mendling, H.A. Reijers, W.M.P. van der Aalst, “Seven process modeling guidelines (7PMG)”. Inf. Softw. Technol. 52(2), 127–136 (2010) J. Mendling, L. Sánchez-González, F. García, M. La Rosa, “Thresholds for error probability measures of business process models”. J. Syst. Softw. 85(5), 1188– 1197 (2012) J. Mendling, H.A. Reijers, J. Recker, “Activity labeling in process modeling: empirical in- sights and recommendations.” Inf. Syst. 35(4), 467–482 (2010) Books A. Sharp, P. McDermott, “Workflow Modeling: Tools for Process Improvement and Application Development”, 2 nd edn., Artech House (2008)
© INB/INN320 10.2/2013 – 26 September 2013 A/Prof. Marcello La Rosa IS School Academic Director (Corporate Programs and Partnerships) BPM Discipline, IS School Science & Engineering Faculty Queensland University of Technology 126 Margaret Street Brisbane QLD 4000 Australia p +61 (0)7 3138-9482 e firstname.lastname@example.org w www.marcellolarosa.com
Process-oriented System Analysis Process Discovery.
Business Process Modelling
Prof. Marcello La Rosa BPM Discipline Queensland University of Technology.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Writing Good Use Cases - Instructor Notes
Effective systems development requires a team effort from stakeholders, users, managers, systems development specialists, and various support personnel,
Business Process Modelling -8.2/2013 -
Chapter 4: Beginning the Analysis: Investigating System Requirements
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Fundamentals of Information Systems, Second Edition
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
En1hanced Performance. Enduring Results.
What is Business Analysis Planning & Monitoring?
Module 4: Systems Development Chapter 13: Investigation and Analysis.
S/W Project Management
Systems Analysis and Design in a Changing World, Fourth Edition
Practical Business Modeling in the Unified Process Tom Morgan Software Architect, Fidelity National Information Services
Week 2 The Object-Oriented Approach to Requirements
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Process Modelling - 1.2/ Marcello La Rosa Queensland University of Technology Brisbane, 25 July 2013.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
12 C H A P T E R Systems Investigation and Analysis and Analysis.
Chapter 8: Systems Development Please turn your cell phone off.
Systems Investigation and Analysis
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
The “Lifecycle” of Software. Chapter 5. Alternatives to the Waterfall Model The “Waterfall” model can mislead: boundaries between phases are not always.
Smart Home Technologies
© INB/INN /2012 – 25 July 2013 Your Unit Coordinator A/Professor Marcello La Rosa Academic Director (corporate programs and partnerships) for IS.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Module N° 7 – Introduction to SMS
Internal Auditing and Outsourcing
Requirements Engineering Process – 1
Chapter 1 Business Driven Technology
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
Summary.ppt1 TDT Modelling of information systems, Fall 2004 Summary of the course Guttorm Sindre / Hallvard Trætteberg, IDI.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Project Cycle Management and Statistics
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Systems Development Environment
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
© 2017 SlidePlayer.com Inc. All rights reserved.