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

Slides:



Advertisements
Similar presentations
School of Computer Science & Software Engineering
Advertisements

Configuration management
Configuration management
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
1 Petri Nets I Paul Fishwick author From
Task/Incident Tracker Content The Big Picture Design Considerations Scenario Ticket State Model.
An Introduction to Petri Nets
Principles of Engineering System Design Dr T Asokan
Based on: Petri Nets and Industrial Applications: A Tutorial
Interaction Modeling for Testing We would generate the test cases based on our understanding of the interactions that may happen. The source is, again,
CNPq - INRIA Projeto CEMT Instituto de Informática - UFRGS “Features of CEMT Workflow Model” Carlos Zeve.
Using Data Flow Diagrams
Discrete Interaction Design Specification Prof. Dr. Matthias Rauterberg Faculty Industrial Design Technical University of Eindhoven
Petri Nets Overview 1 Definition of Petri Net C = ( P, T, I, O) Places P = { p 1, p 2, p 3, …, p n } Transitions T = { t 1, t 2, t 3, …, t n } Input.
CS5371 Theory of Computation
1 Review Topics 1.Basic understanding of a business process 2.The relationship of a business process with a work flow 3.The different types aspects and.
Using Dataflow Diagrams
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.
Requirements Techniques, cont. Brief review Formal Requirements Techniques –Finite State Machines –Petri Nets.
Chapter 1: Overview of Workflow Management Dr. Shiyong Lu Department of Computer Science Wayne State University.
© 2005 EMC Corporation. All rights reserved. Module 9 Workflows.
Mata kuliah :K0362/ Matematika Diskrit Tahun :2008
Business Process Management with Activiti João Silva (CERN, GS-AIS) 21st of October, 2014 BUSINESS PROCESS MANAGEMENT WITH ACTIVITI.
Configuration Management
Workflow Description Language and Workflow Patterns Yi Wang.
Distributed, Collaborative Processing System (COBRA Virtual Office)
Workflow API and workflow services A case study of biodiversity analysis using Windows Workflow Foundation Boris Milašinović Faculty of Electrical Engineering.
Modeling System Requirements:Events and Things
Chapter Intranet Agents. Chapter Background Intranet: an internal corporate network based on Internet technology. Typically, an intranet can.
System Models Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn Lecture 6 & 7.
CONTENTS Arrival Characters Definition Merits Chararterstics Workflows Wfms Workflow engine Workflows levels & categories.
An Introduction to Petri Nets Marjan Sirjani Formal Methods Laboratory University of Tehran.
Configuration Management (CM)
Pumptheory.com Mark Aufflick OpenACS Workflow Mark Aufflick pumptheory.com.
Chapter 1: Overview of Workflow Management Dr. Shiyong Lu Department of Computer Science Wayne State University.
© 2001 Business & Information Systems 2/e1 Chapter 8 Personal Productivity and Problem Solving.
Lead Black Slide Powered by DeSiaMore1. 2 Chapter 8 Personal Productivity and Problem Solving.
1 Modeling interactions and behavior Lecturer Dr. Mai Fadel.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
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
Ch5: Software Specification. 1 Petri Nets  Introduced by C. Adams Petri in  Widely used in the modeling and analysis of computer systems.  Basic.
Systems Analysis and Design in a Changing World, Fourth Edition
CSCI1600: Embedded and Real Time Software Lecture 11: Modeling IV: Concurrency Steven Reiss, Fall 2015.
Course: COMS-E6125 Professor: Gail E. Kaiser Student: Shanghao Li (sl2967)
School of Computer Science & Software Engineering
Finite State Machines (FSM) OR Finite State Automation (FSA) - are models of the behaviors of a system or a complex object, with a limited number of defined.
Digital System Design using VHDL
Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?
1 Specification A broad term that means definition Used at different stages of software development for different purposes Generally, a statement of agreement.
Université Toulouse I 1 CADUI' June FUNDP Namur Implementation Techniques for Petri Net Based Specifications of Human-Computer Dialogues.
2008/10E-Enterprise Integration - eEI1 Lecture 6 Petri Net Techniques for Modeling Workflows and Their Support of Reuse.
Information Systems and Network Engineering Laboratory I DR. KEN COSH WEEK 1.
Turing Machine Model Are there computations that no “reasonable” computing machine can perform? –the machine should not store the answer to all possible.
Systems Analysis and Design in a Changing World, Fourth Edition
CHAPTER
Advantages of FSM Their simplicity make it easy for inexperienced developers to implement with little to no extra knowledge (low entry level)
Concurrent Systems Modeling using Petri Nets
CSS 496 Business Process Re-engineering for BS(CS)
Dr. Eng Amr T. Abdel-Hamid
Workflow Management Systems
CAP 4800/CAP 5805: Computer Simulation Concepts
CAP 4800/CAP 5805: Computer Simulation Concepts
CAP 4800/CAP 5805: Computer Simulation Concepts
Petri Nets Laurie Frazier.
Presentation transcript:

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Workflow Management Systems Dr. Rafael A. Calvo Web Engineering Group School of Electrical and Information Engineering The University of Sydney Edited by Mark Aufflick

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney This presentation What are workflows? Modelling Workflows Petri Nets Finite State Machines (FSM) Formal representation of workflows Workflow management systems Example implementation

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney What are workflows? Workflow management systems date back to the late The are used to coordinate the work of multiple people in a project that has a fixed process. The automation of a business process, in whole or part, during which documents, information or tasks are passed from one participant* to another for action, according to a set of procedural rules. *participant = resource (human or machine) workflow management consortium

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Why workflow management? Better, Cheaper faster businesses Improved efficiency - mostly through automation of business processes. Improved customer service – through consistency in the processes. Improved process control - helps management and improves overall quality of the outcomes. Flexibility – software control over processes enables their re- design in line with changing business needs Business process improvement - through focus on business processes.

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney A publishing workflow Publishing: Someone commissions and article, authors write it, the editor edits it and the article goes back to the author, then the editor reads it again and if accepted passes it to the publisher to decide the date of publication. Magazines, newspapers, etc… do this hundreds of times a day.

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Bug tracking workflow Most common in software engineering A user submits a bug report, someone looks at it and decides who, how and when should fix it. The developer fixes it, or forward it to another developer, or back to the user asking for more information, eventually the bug is fixed and the user advised.

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Workflow management systems Pure workflow software, Derived form image management systems, Document management systems, Relational or object database systems, And electronic mail systems.

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney To think about… What are the advantages of Web-based workflow management systems?

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Modelling workflows Workflows are modelled so they can be: –Communicated to others (e.g managers, team members). –Exchanged (e.g with other teams doing similar processes) –Integrated (e.g with other computer systems)

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Workflow Mathematical models Useful Mathematical models –Finite State Machine (FSM) FSMs can be described by State Transition Diagrams –Petri Net Petri Nets are used to model concurrent systems, particularly network protocols. The visual description of Petri Nets has been defined by the IEEE

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Petri Nets modelling Petri Nets are a 4-tuple (P,T,I,O) –Places represent possible states of the system (circles) –Transitions are events or actions which cause the change of state (rectangles) –Input relation: an arc that connects transition with a place (arrows). –Output relation: an arc that connects a place with a transition (arrows).

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Petri Nets Transitions… Changes of state are denoted by a movement of token(s) (black dots) from input places to output places; and are caused by the firing of a transition. The firing represents an occurrence of the event or an action taken. The firing is subject to the input conditions, denoted by token availability.

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Petri Nets Transitions (2) A transition is firable or enabled when there at least one token in its input places. After firing, tokens will be moved from the input places (old state) to the output places, denoting the new state. What makes a transition to fire is called trigger.

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Petri Nets Triggers 1.User Trigger, when the transition is caused by a person. (fat arrow pointing to the task) 2.Message Trigger. When the system is triggered by a message generated outside the WF system. 3.Automatic Trigger. Are performed by the system as soon as the transition is enabled. 4.Time trigger. Are automatic transitions that need to occur at a specific time.

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Finite State Machines A basic finite state machine consists of: –States –A start state –Transitions/Actions A simple representation: –[Action] (State) [Action1] (Start State) [Action2] (State2) (State3) [Action4](State4) [Action3]

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney FSM : States & Actions States from our Bug Tracker example: Open Resolved Closed An FSM instance will always be in exactly one such state When you perform an action, the FSM instance will be pushed into a new state States contain almost no information, but they allow us to determine which actions are possible

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney Products Today's workflow management systems include: –COSA (Transflow), –Websphere MQ Workflow (IBM), –Workflow (Eastman Software), –Staffware (Staffware) and –Visual WorkFlo (FileNet) support production/administrative workflow. A number of content management systems have workflows, including Vignette, Interwoven and OACS. Just a few products support ad-hoc workflow, e.g., Ensemble (FileNet).

Workflow Management Systems © Dr. Rafael A. Calvo – Edited by Mark Aufflick (pumptheory.com) School of Electrical and Information Eng, University of Sydney References Carl Adam Petri, Diss Theory of Non-sequential processes (Kommunicakation mit Automaten)