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

Slides:



Advertisements
Similar presentations
Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney.
Advertisements

Techniques to analyze workflows (design-time)
Based on: Petri Nets and Industrial Applications: A Tutorial
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Ch 3 System Development Environment
Software Design Process A Process is a set of related and (sequenced) tasks that transforms a set of input to a set of output. Inputs Outputs Design Process.
David Woo (dxw07u).  What is “White Box Testing”  Data Processing and Calculation Correctness Tests  Correctness Tests:  Path Coverage  Line Coverage.
Activity Diagrams [Arlow and Neustadt, 2005] CS 425 / 625 Seminar on Software Engineering University of Nevada, Reno Department of Computer Science & Engineering.
CSC 402 Requirements Engineering 1 Requirements Techniques, cont. Formal requirements analysis techniques include: – DFD (covered) – ERD (covered) – Finite.
12/07/2007Jiacun Wang1 SE-561 Math Foundations Petri Nets - II Dr. Jiacun Wang Department of Software Engineering Monmouth University.
Lecture 6 & 7 System Models.
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
Requirements Techniques, cont. Brief review Formal Requirements Techniques –Finite State Machines –Petri Nets.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
[Title of the course] The Business Motivation Model
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Chapter 3 : Software Process and Other Models Juthawut Chantharamalee Curriculum of Computer Science Faculty of Science and Technology, Suan Dusit University.
Software Design Processes and Management
Architectural Design.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
Continuation From Chapter From Chapter 1
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
程建群 博士(Dr. Jason Cheng) 年03月
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
Business Analysis and Essential Competencies
Modeling with ordinary Petri Nets Events: Actions that take place in the system The occurrence of these events is controlled by the state of the system.
Workflow Management introduktion: Wil van der Aalst has copyrights to the slides conserning his book about Workflow Management. However, some of the slides.
CY2003 Computer Systems Lecture 7 Petri net. © LJMU, 2004CY2003- Week 72 Overview Petri net –concepts –Petri net representation –Firing a transition –Marks.
Procedures for managing workflow components Workflow components: A workflow can usually be described using formal or informal flow diagramming techniques,
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Petri Nets Lecturer: Roohollah Abdipour. Agenda Introduction Petri Net Modelling with Petri Net Analysis of Petri net 2.
Modelling by Petri nets
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
Systems Analysis and Design in a Changing World, Fourth Edition
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
CSCI1600: Embedded and Real Time Software Lecture 11: Modeling IV: Concurrency Steven Reiss, Fall 2015.
/faculteit technologie management PN-1 Petri nets refresher Prof.dr.ir. Wil van der Aalst Eindhoven University of Technology, Faculty of Technology Management,
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS) Chapter 2: Workflow Management Khurram Shahzad
Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?
/faculteit technologie management PN-1 Petri nets refresher Prof.dr.ir. Wil van der Aalst Eindhoven University of Technology, Faculty of Technology Management,
2008/10E-Enterprise Integration - eEI1 Lecture 6 Petri Net Techniques for Modeling Workflows and Their Support of Reuse.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
Technology of information systems Lecture 5 Process management.
Tools Of Structured Analysis
Requirements Techniques, cont.
Concurrent Systems Modeling using Petri Nets
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Information systems modeling tools
Introduction to Unified Modeling Language (UML)
CSS 496 Business Process Re-engineering for BS(CS)
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
COIT20235 Business Process Modelling
Software Architecture & Design Pattern
CHAPTER 4 Test Design Techniques
MSc in Artificial Intelligence Student: Hsiang-Ling Kuo
Concurrent Systems Modeling using Petri Nets – Part II
Workflow Management Systems
Wil van der Aalst Eindhoven University of Technology
Modeling based on Petri-nets.
BPMN - Business Process Modeling Notations
Petri nets refresher Prof.dr.ir. Wil van der Aalst
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
CSS 496 Business Process Re-engineering for BS(CS)
Systems Architecture & Design Lecture 3 Architecture Frameworks
Petri nets.
Basic Concepts of Algorithm
Petri Nets Laurie Frazier.
Presentation transcript:

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

Enterprise Resource Planning ERP definition Software solution that addresses the enterprise needs taking the process view of an organisation to meet the organisational goals tightly integrating all functions of an enterprise ERP means integration of Processes Databases Tools Applications Interfaces

Enterprise Resource Planning Drawback of ERP Costly implementation Dependency on vendor Forgoing “best-of-breed” solutions Solution: EAI Enterprise Application Integration (EAI) is “the unrestricted sharing of data and business processes among any connected applications and data sources in the enterprise”.

Architectures of EAI Message Broker Process Broker Point to Point

Goal Modeling How to make the goals of an enterprise explicit Purpose of Goal Modeling Describing the goals of an enterprise Showing how the goals are interrelated Finding problems that hinder goal fulfillment Finding opportunities that facilitate goal fulfillment

Components of a Goal Model

An Example

An Example

A Goal Model for a Library

Goal Decomposition

Goal Decomposition

An Example Per runs a campaign for president. His main opponent is Eva. Construct a goal model for the following: Victory in the election Get support from EU supporters Get support from EU critics Make the opponent look dishonourable Per has misused credit cards Eva has misused credit cards Get many TV commercials The budget is limited Get financial support from big business Get an image as independent Get an image as trustworthy

Solution

Process Modeling Purpose of Process Modeling

Basic Workflow Concepts Task - a logical unit of work that is carried out as a single whole Resource - a person or a machine that can perform specific tasks Activity - the performance of a task by a a resource Case - a sequence of activities performed to achieve some goal, an order, an insurance claim, a car assembly Work item - the combination of a case and a task that is just to be carried out Process - describes how a particular category of cases shall be managed Control flow construct - sequence, selection, iteration, parallelisation

Process Modeling Focus on Petri Nets BPMN EPC

Petri Nets Petri Nets – a formal approach based upon an established formalism for the modeling and analysis of processes Advantages It forces precise definitions Ambiguities, uncertainties, and contradictions are thus prevented, in contrast to many informal diagramming techniques Formalism often enables the use of number of analytical techniques

Petri Nets Classic Petri nets Simple process model Just three elements: places, transitions and arcs. Graphical and mathematical description. Formal semantics and allows for analysis.

Petri Nets A Petri nets consists of places and transitions Places are indicated by a circle A transition is shown as a rectangle

Petri Nets Rules Connections are directed. No connections between two places or two transitions. Places may hold zero or more tokens. First, we consider the case of at most one arc between two nodes.

Petri Nets Enabled A transition is enabled if each of its input places contains at least one token. enabled Not enabled Not enabled

Petri Nets Firing fired An enabled transition can fire (i.e., it occurs). When it fires it consumes a token from each input place and produces a token for each output place. fired

Petri Nets Example

Petri Nets Enabled Transition A transition is enabled when there is token in each of its input places

Petri Nets Traffic Light Example

Petri Nets Traffic Light Example

Petri Nets Traffic Light Example

Petri Nets Two traffic light

Colored Petri Nets

Petri Nets with Time Every token gets a timestamp, indicating the time from which the token is available A transition is enabled when each token to be consumed has a timestamp equal or prior to the current time Each transition gives a delay to a token produced by the transition.

Traffic Lights with Time

Swimming School Exercise

Basic Workflow Concepts Task - a logical unit of work that is carried out as a single whole Resource - a person or a machine that can perform specific tasks Activity - the performance of a task by a a resource Case - a sequence of activities performed to achieve some goal, an order, an insurance claim, a car assembly Work item - the combination of a case and a task that is just to be carried out Process - describes how a particular category of cases shall be managed Control flow construct - sequence, selection, iteration, parallelisation

Workflow Concepts in Petri Nets Task - transition Resource - token Activity - transition that fires Case - token Work item - enabled transition Process - Petri net Control flow construct - modelled by places and transitions

Swimming School Exercise

Workflow Analysis Types of Analysis Qualitative (correctness) Deadlock Livelock … Quantitative (performance) Average completion time Level of service

Reachability Analysis

Reachability Analysis

Reachability Analysis

Reachability Analysis

Reachability Graph Exercies

Quantitative Analysis Resource utilization Number of cases in progress Waiting time System time

Resource utilization Consider a process with one task Number of cases in progress λ is the number of incoming cases per time unit µ is the number of cases the resource is able to process per time unit The resource utilization is ρ = λ / µ

Resource utilization λ = 4 µ = 5 The resource utilisation is ρ = λ / µ = 4 / 5 = 0.8

Slides 6 from Paul Johannesson