Process Diagram Technique for Business Processes Modeling



Similar documents
Hybrid Development Methodology for Client-Server Applications

Modelling Workflow with Petri Nets. CA4 BPM PetriNets

BIS 3106: Business Process Management. Lecture Two: Modelling the Control-flow Perspective

Analysis and Implementation of Workflowbased Supply Chain Management System

BPMN and Simulation. L. J. Enstone & M. F. Clark The Lanner Group April 2006

ARIS Education Package Process Design & Analysis

SECTION 2 PROGRAMMING & DEVELOPMENT

THE SIMULATION OF SOFTWARE PROCESSES IN THE INTEGRATED COMPUTER ENVIRONMENT IN THE CASE OF TELCO SECTOR

Modeling Complex Time Limits

Using Use Cases for requirements capture. Pete McBreen McBreen.Consulting

Business Process Modeling Information Systems in Industry ( )

BPMN 2.0 Descriptive Constructs

LECTURE 11: PROCESS MODELING

BPMN Business Process Modeling Notation

Chapter 10. Practical Database Design Methodology. The Role of Information Systems in Organizations. Practical Database Design Methodology

IT 3. Mobile Workforce Management. Jan Bára number one in each direction

Business Process Modeling Approaches in the Context of Process Level Audit Risk. Assessment: An Analysis and Comparison.

Process Modelling Notations

Documentation of DES Models for Manufacturing System Life Cycle Simulation

(Refer Slide Time 00:56)

Process / Operation Symbols

IBM Software Group. Introduction to BPMN. Stephen A. White, BPM Architect, IBM October 16, IBM Corporation

Business Process Management and Support Processes

Business Process Standards and Modeling

Dr. Jana Koehler IBM Zurich Research Laboratory

Process for Data Flow Diagram Process Documentation Template: Description

Scenario-based Requirements Engineering and User-Interface Design

Business Process Modeling Notation. Bruce Silver Principal, BPMessentials

Day 3: Modeling and ERP Reference Architectures

Business Process Modelling Notation A tutorial

KS3 Computing Group 1 Programme of Study hours per week

An Automated Workflow System Geared Towards Consumer Goods and Services Companies

Design Patterns for Complex Event Processing

3SL. Requirements Definition and Management Using Cradle

Algorithms, Flowcharts & Program Design. ComPro

Software Engineering UNIT -1 OVERVIEW

CDC UNIFIED PROCESS PRACTICES GUIDE

Workflow Overview And Approach. Steve Hughes Changqing Zhen Natasha Globus

Communication Diagrams

Software, Process, Business Process and Software Process

Business Process Management. Prof. Corrado Cerruti General Management Course

MODELING OF SERVICE ORIENTED ARCHITECTURE: FROM BUSINESS PROCESS TO SERVICE REALISATION

Unit 5: Object-Role Modeling (ORM)

Data Flow Diagrams. Outline. Some Rules for External Entities 1/25/2010. Mechanics

SOFTWARE ENGINEERING INTERVIEW QUESTIONS

White Paper BPMN 2.0 Task Types Explained

MODULE 5 DATA FLOW DIAGRAMS

Why Data Flow Diagrams?

System Modeling / Class Diagra Diagr m a Week 6

TECH. Requirements. Why are requirements important? The Requirements Process REQUIREMENTS ELICITATION AND ANALYSIS. Requirements vs.

Process Modeling using BPMN 2.0

Announcements. SE 1: Software Requirements Specification and Analysis. Review: Use Case Descriptions

INTRODUCTION TO DIGITAL SYSTEMS. IMPLEMENTATION: MODULES (ICs) AND NETWORKS IMPLEMENTATION OF ALGORITHMS IN HARDWARE

Programming Logic controllers

Curriculum Overview. Department of Systems Analysis and IT. Berlin Institute of Technology Prof. Dr. Krallmann. Olga Levina

Business Process Redesign and Modelling

A White Paper. Workflow Management Software: Uniting business with technology to satisfy business process management needs

TOGAF usage in outsourcing of software development

Decomposition into Parts. Software Engineering, Lecture 4. Data and Function Cohesion. Allocation of Functions and Data. Component Interfaces

Interaction Diagrams. Use Cases and Actors INTERACTION MODELING

Lecture 9: Requirements Modelling

Fundamentals of Information Systems, Fifth Edition. Chapter 8 Systems Development

Software Development Methodologies

SECTION 4 TESTING & QUALITY CONTROL

Comprehensive Job Analysis. With MPG s Performance Navigator

Chapter 1 An Introduction to Computers and Problem Solving

Budapest University of Technology and Economics Department of Measurement and Information Systems. Business Process Modeling

Chapter 10 Practical Database Design Methodology and Use of UML Diagrams

From Short Sale to Sold!

Project Time Management

1. Process Modeling. Process Modeling (Cont.) Content. Chapter 7 Structuring System Process Requirements

Software testing. Objectives

zen Platform technical white paper

An MDA Approach for the Development of Web applications

Gates, Circuits, and Boolean Algebra

Chapter 11: Input/Output Organisation. Lesson 06: Programmed IO

MTAT Business Process Management (BPM) (for Masters of IT) Lecture 2: Introduction to BPMN

UML Activities & Actions. Charles ANDRE - UNSA

7. Classification. Business value. Structuring (repetition) Automation. Classification (after Leymann/Roller) Automation.

Applying Use Cases to Microcontroller Code Development. Chris Gilbert Cypress Semiconductor

Nr.: Fakultät für Informatik Otto-von-Guericke-Universität Magdeburg

Sequence Diagrams. Massimo Felici. Massimo Felici Sequence Diagrams c

REQUIREMENTS SPECIFICATION AND MANAGEMENT. Requirements Analysis and Specification

High-level Design. What is software architecture?

Dr. Pat Mirenda. Software Design Specification Document

The Business Process Model

11 Tips to make the requirements definition process more effective and results more usable

Diagramming Techniques:

Semantic Analysis of Business Process Executions

Web Application Architectures

The Role of the Software Architect

Software Engineering

Service Oriented Architecture

Process for Sales Projection Process Documentation Template: Description Sales Projection (Sales Forecasting) Process

Modeling Guidelines Manual

Process Modeling and Process Improvement. Process Modeling

Aerospace Software Engineering

Course Outline. Foundation of Business Analysis Course BA30: 4 days Instructor Led

Java Programming (10155)

Total Quality Management (TQM) Quality, Success and Failure. Total Quality Management (TQM) vs. Process Reengineering (BPR)

Transcription:

Process Diagram Technique for Business Processes Modeling Vaclav Repa University of Economics, Prague, Czech Republic ISD2000 Conference, Kristiansand, Norway, August 2000 V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 1

Agenda The Scope The Technique Diagram Elements Process Meta-Model Different Levels of the Technique Important Topics Events, Activities, and States from the Object vs. Process Point of View (Consistency Rules) Process Memory (Simple/Complex Processes) V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 2

The Scope Model of the system of business processes which: respects basic objectives and goals, current state and specific characteristics of the organization respects objective circumstances (those which are given outside the organization and are independent of the organization) which can play a significant role in the behavior of the organization is "optimal" in the sense of economic efficiency of the processes is "optimal" in the sense of maximum simplicity together with whole functionality is prepared for later optimization, implementation and installation of the system of processes which respect characteristics described above V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 3

Organizational & Technological Infrastructure The Scope Convergence of BPE, WfM, and ISD Sense and Context of Work BP to be performed Workflow Management Business Processes Implementation Business Processes (Re)Engineering BP to be engineered Conceptual Business Processes Analysis Business Interface Analysis (Use Cases) Business Requirements Analysis Information Requirements (Strategic Level) BP to be modeled and supported Information System Development Information Support Information Requirements (Operational Level) Information Support V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 4

The Scope Objects and processes as a basis for IS development Conceptual Business Processes Model Business Activities Actors Products Conceptual Business Objects Model Business Objects Actors Products * I/O functions * Dialogue functions * Interface functions etc. Interface Functions Structure Real World Structure * Objects * Attributes * Life history Technology Constraints and Requirements and Database Design Rules Conceptual IS Model Usability Requirements * buffering needs * user views * data sets extent etc. Real World Structure (static view) Logical Database Structure Real World Behaviour (Object Life Histories) Program Modules Structure Top-Down Function Structure Transition Techniques (Design Rules) Technology Constraints and Requirements and Program Design Rules Technological IS Model V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 5 Back

The Technique Process modeling diagram elements - basic set Diagram Element Activity Decision Symbol Activity Decision Explanation Basic element of the process - input(s) to output(s) processing. Activity is decomposable on principle, i.e. it can be always regarded as the process (on the deeper level of detail). Elementary (i.e. undecomposable) activity. Decision on the particular follow-up of the process. Event Event External stimulus for the activity. Information about the event outside of the process and independent of it. State Logical Connector State AND Internal stimulus for the activity. Result of the preceding activity. Primitive decision without any information at the input (predefined decision). The only AND and OR (XOR) connectors are allowable. V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 6 Back

The Technique Process modeling diagram elements - external elements Diagram Element Information Set Symbol Information Set Explanation Set of the information for process control. Examples: manufacturing plan, strategic investment intention, delivery note etc. Material Set Mixed Set Actor Material Set Mixed Set Actor Set of the subjects of processing. I.e. raw material (at the input) or product (at the output), no matter whether it is material or data. Examples: engine component, car (final product) in the case of car manufacturing. Stock list, investment advice (final product) in the case of broker's business (information plays the role of the material here). Set of the combination of the subjects of processing as well as the information for controlling it. Example: delivery together with the delivery note Abstract person - all kinds of the attendee of the process (person, organization unit, system, position, profession, role, entity etc.). Problem Problem Problem related to the process in the particular point. Organization Unit Organization Unit Unit of the organization where the process runs. V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 7 Back

Process model The Technique Process meta-model Additional Constraints: 1. Activity has to be stimulated by either Stimulus or Control Activity (Decision or Logical Connector) 2. Input Set has to be input for either Processing Activity or Decision Consists of 1 1 State Produces Stimulates Processing Activity 0..* Produces Is input for 1..* 1..* 1..* Input/Output Set 1..* Activity 1..* Event 0..* Stimulus Is connected to 1..* 0..* External Aspect 1..* Is connected to 0..* 1..* Is input for Is input for Actor Problem Organization Unit Stimulates Control Activity Decision Stimulates Logical Connector Information Set Material Set Mixed Set V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 8

The Technique Three levels of model simplification Level Description Purpose of simplification level 0 Full complexity. All elements used. level 1 Model without actors, problems and Description of the process itself without the respect organization units. to the related external aspects (actors, problems and organization). There is no possibility to analyze those external aspects (for the purpose of the level 2 level 3 Level 1 model without sets (material, information or mixed). Level 2 model without states and control activities. information analysis of the legal IS for example). Description of the process itself without the respect to the inputs and outputs of the activities. Such a model describes the succession of the activities together with the process control (activity stimuli). It does not describe the substance of the processing. Description of the process itself without the respect to the inputs and outputs of the activities. Such a model describes the succession of the activities only. No internal control is described. V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 9

Consistency of processes and objects Outline of the consistency rules requirements concerning external facts (different meanings of the same fact) Fact Object Model Business Process Model Event Stimulus for: Stimulus for: object internal state change operation execution possible communication with other objects process state change (send the message) in the case of the output production "common action" possible communication with other Output Consequence of object action object internal state change processes (processes co-ordination) Consequence of: operation execution (product) process state change Outline of the consistency rules requirements concerning internal concepts (different meanings of the same concept) Concept Object Model Business Process Model Action Action executed/allowed by the object Causes: Activity inside the process Causes: object state change process state change possible output production possible output production possible communication with other objects possible communication with other (send the message) in the case of the "common action" processes (co-ordination of processes) State Object life cycle state starting point for action processing result of action processing Process course state starting point for operation execution result of operation execution V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 10 Illustration

Process Memory Why: The need to store the information about the actual process state in controlling complex processes (which often have complex relationships to other processes). The need to reduce the complexity of the process description. Process memory includes: actual process state identification attributes of actual state of the process data gathered by the process activities (once the data are gathered, they exist inside the process and can be used by its activities without any limitation (global data access)) Consequences: criterion for distinguishing between primitive and complex processes. (process without the need to store the information about the state is so simple that it is possible to take it (and implement it, as well) as a simple algorithm) indicates the possible parallelism inside the process or at least in the communication with other processes. V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 11

Primitive Process ( Receiving) Stock entry Formal correctness check Correct Satisfiability check Satisfiable Incorrect Unsatisfiable rejection due to the formal incorrectness rejection due to the unsatisfiability acceptation accepted deficiencies report rejected rejection report Delivery order Invoice V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 12

Primitive Process ( Receiving) - Aris Notation Stock entry Formal correctness check Correct Satisfiability check Satisfiable Incorrect Unsatisfiable rejection due to the formal incorrectness rejection due to the unsatisfiability acceptation accepted deficiencies report rejected rejection report Delivery order Invoice V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 13

Complex Process ( Transaction) Customer Stock Store Manager Goods Dispatched Customer Customer Payment Done entry Receiving accepted Fulfilment Goods Delivered Clearance deficiencies report rejected rejection report Delivery order Invoice Cleared Waiting for Store Action Waiting for Customer Action V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 14